It depends. We used classTagValue for ejb:bean name="", but later I created a ejbName template tag, because it was doing some smart checks. For simple stuff just use classTagValue/etc.
Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Andrew Stevens > Sent: Monday, January 14, 2002 3:41 AM > To: [EMAIL PROTECTED] > Subject: RE: [Xdoclet-devel] Another template tag question > > A wise old hermit known only as Ara Abrahamian <[EMAIL PROTECTED]> once > said: > > > But anyway I really think you should write a custom tag instead of > > polluting the template with logic, just a simple forAllLocations and a > > forAllEjbRefsForLocation and use an internal struct to hold current > > location and ejb-ref. The limitation imho is a good thing actually, you > > have to write clean templates this way :o) > > That reminds me, judging by the method in JBossTagsHandler, isn't > <XDtJBoss:jBossResourceClassName/> just equivalent to > <XDtClass:classTagValue tagName="jboss:resource-manager" > paramName="res-man-class"/> ? Should I be using classTagValue for the > Bluestone tags & parameters, or should I be adding new template tags for > those as well as the location loop one? > > > Andrew. > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
