We want to update our application running on jboss frequently while users are actually online working whith it.
Has anybody out there done this?
I tried to achieve it by subclassing org.apache.catalina.session.PersistentManagerBase and org.apache.catalina.session.StoreBase to save the objects in the HTTP session to a file and implementing org.jboss.ejb3.cache.StatefulCache to save my stateful session beans to files.
The problem with this approach is, that when activating the passivated SFSBs (which use seam for bijection) in the @PostActivate method the seam-injected objects are not available. But in order to restore the state of the bean this objects are needed.
Is there a better way?
BTW: We use jboss 4.0.5 GA with myfaces, hibernate and seam.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055114#4055114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055114
Hi folks,
I am trying to figure this out for a month and no success so far. We are having a Swing-Client with the need for accessing EJB3 Stateless Session Beans over HTTP only on port 80 (because of the use of different firewalls).
Solving the problem to get JNDI-Lookup over HTTP was quiet easy. But all delivered poxies trying to connect via socket://${jboss.bind.address}:3878 as configured in ejb3.deployer/META-INF/jboss-service.xml.
The use of @RemoteBinding(clientBindUrl=ext-ip:port) is as bad as stated in other posts throughout this forum. In fact we need a configuration within a configfile (i.e. jboss.xml, jboss-service.xml,etc.).
Could any one push me in the right direction?
Regards Sandor
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055113#4055113
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055113
Greetings,
In a simple piece of code Im doing the following:
InitialContext ctx = new InitialContext();
| Queue q = (Queue)ctx.lookup ("queue/B");
This raises the following exception:
Exception in thread "main" java.lang.ClassCastException: javax.naming.Reference
| at ro.happytour.happyledger.jms.client.JMSProviderClient.main(JMSProviderClient.java:13)
Looking at the object returned by the lookup, it appears to be of type javax.naming.Reference. Could someone please help as I already posted this message several time, without any reply ?
Many thanks in advance,
Nicolas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055101#4055101
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055101
Hi,
you two different options:
First one is to changed the loading strategy of your relationship by adding the appropriate attributes to the annotation i.e.
@OneToMany(fetch = FetchType.EAGER).
This is a standard declaration defined by the spec.
Second one is a little bit tricky because of the knowledge of cursor going to be closed. A lazy fetched relationship can be fully loaded by iterating over the collection using an iterator of an attached entity. Thus it is enough to call the relationships iterator method and the assoziated entities must be loaded.
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055100#4055100
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055100
