What qualifies as being "already persistent"?
Does that mean an entity whose equals() test returns true, or does it look at the @Entity definition at the Id and/or @Column(unique=true) fields only?
Also, does it drill down to the actual database layer at insertion time for tables with unique constraints but no corresponding annotation defined on the entity? Or does that come back as a different kind of error?
I haven't seen this documented anywhere, so I'm wondering...
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994830#3994830
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994830
We have three instances of JBoss running on one machine, to run three separate applications. Each one communicates to other using JMS to publish any broadcasts, and the receivers will refresh their objects if needed.
Once we have a full GC that takes about 20-30 seconds on the HA Master JBoss server, the HA Master server does not respond and the others stop communicating to HA Master. After some other server takes over as HA Master, broadcasting continues, but the receivers who had registered to the old HA Master server do not give up and re-register to the new elected HA Master. If we stop the server that was HA Master before, then the receivers connect to the new HA Master and start getting the broadcasts.
While we try to overcome the GC issue, does anyone know how to make the receivers re-register to the new HA Master?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994827#3994827
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994827
I think its a bad idea for Seam to have its own ViewHandler, because other things like facelets and Ajax4JSF already customize the ViewHandler (and that already causes integration problems). Introducing yet another Viewhandler is going to make things worse.
Just do you bindings on an event scoped object and inject that object in. Or bind them onto Map attributes, and then inject them into the component via the EL #{map.attribute}.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994820#3994820
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994820