Message: The following issue has been re-assigned.
Assignee: xdoclet-devel (Use for new issues) (mailto:xdoclet-devel@lists.sourceforge.net) Assigner: Magnus Larsson (mailto:[EMAIL PROTECTED]) Date: Tue, 2 Aug 2005 1:49 AM Comment: I'm unfortunately currently not working on the XDoclet project and simply had forgotten to unassign myself from this issue. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1217 Here is an overview of the issue: --------------------------------------------------------------------- Key: XDT-1217 Summary: ejb tag names in websphere module differ from ejb module Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: XDoclet Components: IBM Module Versions: 1.2.3 Assignee: xdoclet-devel (Use for new issues) Reporter: Matthias Germann Created: Wed, 29 Dec 2004 4:19 AM Updated: Tue, 2 Aug 2005 1:49 AM Description: I create this issue as discussed with Magnus Larsson on the xdoclet-devel mailing list. I think that the tag names in the websphere module are not consistent compared to the ejb module. As a user of the module, i would ask the following questions: Why does the WebSphere module not use a coarse-grained websphere.bean tag as the ejb module does? If the module uses fine-grained tags, why is the tag for the sessions beans called websphere.bean (and not websphere.sb or so)? How will the tag for the common attributes be named (shouldn't this be named websphere.bean)? IMHO, we should switch to another naming as long as the new tags are not in a official xdoclet version and we do not have more tags and parameters. I suggest to use the same approach as the ejb module uses. They have one coarse grained ejb.bean tag and use parameter-level conditions to distinguish between the bean types. We could switch to a coarse-grained tag, mark the fine-grained tags deprecated and provide backward-compatibility for the old tags (and remove them in a future version). If you look at the "ejb.bean" tag, you can see that it is possible to mark the parameters of a tag with a condition in xtags.xml. The genearted documentation is also very clear because the description is listed in the Applicability column. <tag> <level>class</level> <name>ejb.bean</name> ... <parameter type="bool"> <name>reentrant</name> <usage-description> Defines the entity bean's reentrancy. </usage-description> <mandatory>false</mandatory> <default>true</default> <condition-description>Entity beans</condition-description> <condition type="type"> <condition-parameter>javax.ejb.EntityBean</condition-parameter> </condition> </parameter> --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ xdoclet-devel mailing list xdoclet-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
