A wise old hermit known only as Torsten Terp <[EMAIL PROTECTED]> once said:
> As far as I can tell it is not possible to add application
> server specific deployment info about external class files
> used in an application. I.e., if i include a class file in
> my app containing an EJB, the merge feature can only be
> used to add bean info to ejb-jar.xml, not jboss.xml etc.
In principle, there are (or should be) merge points in the templates for
the various app servers to do what you want, just as for the ejb-jar.xml.
In practise, we may have overlooked them. If there's any particular merge
points you need which aren't there (or documented), then raise a bug
report or feature request for them.
> Its my understanding that bean info in the mergedir is only
> added if xdoclet has processed a java file in the src dir
> with the same directory structure.
Wrong. It depends on whether the merge point's name has a "{0}"
placeholder in it for the EJB name. It still picks up the session.xml
merge file, for example, and the ejb-jar.xml template isn't treated any
different to the others.
> Because of this jndi info
> etc. are not added, while ejb-jar.xml info IS added (ejb-jar.xml
> info is placed in session.xml or entity.xml in the root of merge
> dir, hence it will be included, despite of the fact that a java
> source file is not present for this bean)
It could just be that the ejb-jar.xml defines a session.xml merge point
while the jboss template has no corresponding jboss-session.xml merge
point defined.
Andrew.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
