are the DAOs behing the stateless session beans? or are they standalone POJOs?
the reason to seperate the ejb impl classes to avoid deploying the classes twice (i believe jboss will complain about this) - this makes lots of sense if you have entity beans and are planning to have a read-only and a read-write set. if you're not using entity beans, you can package them together. it's just my preference to keep all the classes together in one jar. this still isn't going to work w/ the scoped ears. if you're really looking to do this type of thing, is there any reason you can't bundle the 5 deperate ears together into one big ear that is scoped? jboss allows for the russian-doll type packaging, so there's no reason that shouldn't work for you. if you could give me some more details on how the app is hosted and more of what is in the individual ears and what gets given to the clients, i can try and offer some more suggestions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840387#3840387 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840387 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
