Hi,
I noticed that the structure of the tags in the IBM WebSphere module does not conform to the structure of the tags in the ejb module.
The ejb module definies one tag (ejb.bean) for all bean types (session, entity, message-driven). Condition tags are defined for the parameters which are not available for all bean types.
The IBM WebSphere module defines tags for each bean type (websphere.bean for session beans, websphere.mdb for message driven beans and websphere.cmp for entity beans).
IMHO this structure has two flaws: 1. there is no tag for parameters which are available for all bean types 2. it's confusing if the ejb and websphere module use different structures
I suggest to restructure the WebSphere tags and to use the same approach as for the ejb module. What do you think about this?
I'm creating a patch for some additional WebSphere parameters. Therefore, i could also restructurate the WebSphere tags.
What about backward compatibility? Should i leave the old tags or can i just remove them?
Regards, Matthias
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
