> From: Hani Suleiman [mailto:[EMAIL PROTECTED]]
> be core, and come as part of a 'standard' xdoclet. If after that you > needed support for pramati specific stuff, then you'd get the pramati > plugin. Nevertheless, it would be good to have sort of coordination. In my source I now have: * @jboss.ejb-ref-jndi * jndi-name="jnp://entw05:1099/ejb/Hello" * ref-name="RemoteHello" * * @weblogic.ejb-reference-description * jndi-name="t3://192.168.100.131:7001/ejb/Hello" * ejb-ref-name="RemoteHello" */ In one case the sub-tag is called ejb-ref-jndi and in the other it is ejb.reference-description. While those more or less follow the names in the respective deployment descriptors, they are not othogonal or abstract. Someone that e.g. wants to migrate from jboss to bea would need to learn a new subtag (which at the moment is not even in the docs), while it would only be necessary to replace 'jboss'with 'bea' and you are nearly done. Xdoclet should abstract from the names in the implementation and more go for an easy to learn scheme. In the long term, this could also reduce support questions, as users would think 'hm, this is @foo.bla. I need it for bar, so I give a try to @bar.bla' and voila, they're done. Heiko ------------------------------------------------------- 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
