Having the same names lowers the access for new users to xdoclet like me. Knowing WLS very well, I was pleased by the usage of the same names of weblogic.
Jan -----Original Message----- From: Ben Litchfield [mailto:[EMAIL PROTECTED]] Sent: maandag 17 februari 2003 15:11 To: '[EMAIL PROTECTED]' Subject: RE: [Xdoclet-user] New Misssion [Was: Packaging XDoclet in One Ja r?] I disagree with your statements. I think the tag parameters should match the deployment descriptor of the vendor. Not all vendors support each others tags, if this was the case then I would agree with you. Having the parameters match the name from the vendors descriptors allows a user who is looking at the vendors documentation to easily change their specific tag. Otherwise they would say I want to change X, but xdoclet didn't call it X they called it Y to match another vendors descriptor file. -Ben On Mon, 17 Feb 2003, Rupp,Heiko wrote: > > 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 > -- ------------------------------------------------------- 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
************************************************************************ The information in this email is confidential and is intended solely for the addressee(s). Access to this email by anyone else is unauthorised. If you are not an intended recipient, please notify the sender of this email immediately. You should not copy, use or disseminate the information contained in the email. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Capco. http://www.capco.com ***********************************************************************
