The following comment has been added to this issue: Author: Vassil Dichev Created: Tue, 7 Dec 2004 11:07 AM Body: OK, maybe I didn't provide a good use case and I can use @ejb.ejb-external-ref to solve the problem described.
Still, if the merge files are generated/obtained externally, one cannot just include them in the merge directory, but has to update the xdoclet tags for every change of the merge files (it's hard to do automatically). Regards, Vassil --------------------------------------------------------------------- View this comment: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1183?page=comments#action_15414 --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1183 Here is an overview of the issue: --------------------------------------------------------------------- Key: XDT-1183 Summary: Merge file ejb-ejbrefs-{0}.xml replaces tag-generated references Type: Improvement Status: Open Priority: Trivial Original Estimate: 1 minute Time Spent: Unknown Remaining: 1 minute Project: XDoclet Components: EJB Module Versions: 1.2.2 Assignee: xdoclet-devel (Use for new issues) Reporter: Vassil Dichev Created: Tue, 7 Dec 2004 10:18 AM Updated: Tue, 7 Dec 2004 11:07 AM Environment: All Description: Generating ejb references from the merge file ejb-ejbrefs-{0}.xml removes all reference entries in ejb-jar.xml, previously generated by the @ejb.ejb-ref tags. The use case where I need this: let's say I need to include an EJBean external to my project and have a reference to it from a bean in the project. I can include the EJB in the entity-beans.xml merge file, but if I use xdoclet @ejb.ejb-ref tags, the referred bean is not found unless it's in the source, annotated with xdoclet tags. Possible workarounds: 1) Enter a bean stub for the external bean in the current project. This is ugly and error-prone, however, since all changes in the third-party bean must be duplicated in the stub. 2) I can enter *all* references in the ejb-ejbrefs-{0}.xml merge file instead of xdoclet tags. However, this is even uglier: imagine I have to move all of my 100 xdoclet @ejb.ejb-ref tags to a merge file just because I have to refer a single external bean. Of course, one solution would be to parse entity-beans.xml along with the sources, but an easier solution would be to add entries from the merge file instead of replacing them. The same problem has been experienced already and reported in the xdoclet-user mailing list: http://www.mail-archive.com/xdoclet-user@lists.sourceforge.net/msg09336.html While I'm looking at the whole thread, I was thinking that the documentation needs to be improved too. Regards, Vassil Dichev --------------------------------------------------------------------- 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 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