Tag: akquinet
-

Who we are – working at akquinet tech@spree
by
Are you curious about our team, office and office culture? Then we have a little insight for you here!
-
Exposing a web service via https with JBoss FUSE
by
Exposing a JAX-WS web service via https in JBoss FUSE using OSGI-blueprint was not as obvious to me as I expected. This post presents a way to do it.
-
Clustering of the messaging subsystem HornetQ in JBoss AS7 and EAP 6
by
in akquinet, as7, cluster, eap, failover, high availability, hornetq, jboss, jboss as 7, jms, live backup, load balancing, messaging, redhatIn the recent posts of this series we talked about many different aspects of clustering for the JBoss AS 7 and its quality assured version EAP 6, such as: the basic concepts, managing cluster nodes in domain mode, scalable HA cluster topologies and load-balancing and failover of remote EJB clients. Until now, there is one…
-
Load-balancing and failover of remote EJB clients in EAP6 and JBoss AS7
by
in akquinet, as7, berlin, cluster, clustering, ejb, failover, jboss, jndi, load balancing, lookup, redhat, remote ejb, remote namingDieser Artikel auf Deutsch In the recent posts of this series about the clustering capabilities of the JBoss EAP6 and the AS7, we covered the basic concepts, managing cluster nodes in domain mode and scalable HA cluster topologies. This post will be about clustering capabilities for remote EJB clients. We will explain how to cluster…
-
Scalable HA Clustering with JBoss AS 7 / EAP 6
by
Dieser Artikel auf Deutsch Overview In a recent blog-post Clustering in JBoss AS7/EAP 6 we showed how basic clustering in the new EAP 6 and JBoss AS 7 can be used. The EAP 6 is basically an AS 7 with official RedHat-support. Our cluster we described in that post was small and simple. This post will cover much more complex cluster structures, how to…
-
Use jBPM5 embedded within a Java EE 6 application
Since the first final release of jBPM5 at the beginning of 2011 a little more than one year has passed. Despite of being a final release there have been a couple of bugs and the documentation was having many deficiencies. During the last year, however, jBPM5 was quickly moving forward and many bugs were fixed…

You must be logged in to post a comment.