> 1. It seems that most of the Vendor specific tags are actually deployment > tags and are relevant to all appservers. Are there are plans to homogenise > via an appserver neutral syntax?
Yes, step by step. v1.2 has a set of @ejb:persistence tags for example which tries to define a common tags for database persistence tags (column-name, table-name stuff like those). We haven't yet applied it on all of the modules but we're moving in that direction. > 2. The EJBUtil classes which can be generated hold statics for the > COMP_NAME > and JNDI_NAME. JNDI_NAME might make sense but COMP_NAME is really specific > to clients of that bean. Shouldn't client beans (which must have ejb-refs > to > these target beans) instead have entries in *their* BeanUtil classes that > provide the COMP_NAMEs for their ejb-refs? Imho it's better to keep everything in a single lookup class. We'll add support for multiple comp_names later, when we implement Tyler Jewel's multi-jndi-deployment pattern, and there will be getHomeOfThisJndi() and getHomeOfThatJndi() methods. Ara. _______________________________________________________________ Multimillion Dollar Computer Inventory Live Webcast Auctions Thru Aug. 2002 - http://www.cowanalexander.com/calendar _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
