[jopr-dev] Re: moving EJB resources under their respective ejb-jars in JBAS5 plugin

[Charles Crouch]

The work associated with con2 turned out to not be a huge amount, and it was deemed that the improvements in the logical structure brought about by moving the EJB resources under their respective ejb-jars outweighed the issues of having to set multiple templates, or the fact this is not the way it works in the JBAS4 plugin. So we're proceeding with the move.

Cheers
Charles
----- "Charles Crouch" <ccrouch at redhat.com> wrote:

> pros and cons of moving the EJB resources under their respective
> ejb-jars in JBAS5 plugin...
> 
> pro1: no duplicate beans next to each other, e.g. foo EJB in two
> different ears, which you could get in the "global" view
> pro2: EJB resources disappear when ejb-jar resource deleted
> pro3: beans grouped by the ejb-jar that contains them - no way to sort
> them that way otherwise
> 
> 
> con1: multiple EJB resource types, one under standalone ejb-jars, one
> under embedded ejb-jars. This means alert/metric templates need to be
> defined twice on EJB resources.
> con2: EJB1/2 beans exposed through the profile service needs massaging
> so that they are related to their ejb-jar deployments in order to
> support this model.
> con3: this is not how it will work with the JBAS4 plugin.
> con4: no way to view all ejbs in one place in embedded except in the
> navtree
> 
> Mitigation
> con1: use xml entity declarations to remove duplication of resource
> type definitions. alert/metric template definitions typically shouldnt
> need to be changed that frequently
> 
> Outstanding concerns
> -Need to know how much work con2 would be.