hello, didnt read all the post.. it's quite long deploying ear in jboss is actually straightforward, allyou need to avoid, as you said, is duplication of classes so structure your ear: - war - ear
jars that are commons needs to be placed outside those war/ear/ those common jars needs to be included in the manifest file of the jar that are dependent on them there's no ejb3 issues, i have deployed successfuly an ejb3 app made of jar, war and ear, and didnt need to do anything. my build system (maven2) was taking care of classpath in manifest file go ahead and try to deploy your ear, and you will see that it's easier than what you think hth marco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000788#4000788 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000788 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
