Sure, this is a valid setup; shouldn't be any consequences unless you eventually specify that one module depends on another, in which case you'll get errors unless they're deployed together at the same time.
Also, EAR packaging will allow you to change up the classloading configuration, as you may run into issues down the road depending upon how your classes are being shared within your applications:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
But again, packaging is a choice that should be made based on what'll work best for you. For smaller apps I like to deploy simple JAR (or .ejb3, as you're using) archives. I like greater control over my enterprise applications at work, and those get thrown into EARs as part of the build.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996064#3996064
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996064
I just saw that when it is not an entity creation but rather it is an update on an existing entity, I'm consistently getting the InvalidStateException inside a PersistenceException which is inside a JBossRollba... which is inside a RuntimeException.
This is very inconvenient. Is it possible to force the InvalidStateException to be thrown unwrapped from within the EJB? (aside from the EJBException wrap which can be avoided by the specification defined <application-exception> mark on InvalidStateException, as shown in my previous post).
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996062#3996062
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996062