Ejb subtasks substitute {0} with ejbName, all other tasks/subtasks
including <template/> substitute it with class name. It seems like we
should define a set of macros for these cases,
{ejbName}/{packageName}/etc and so on. Atm you have to derive from
EjbSubTask and handle it there but with macros you won't have to do any
coding.Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Michael Szlapa > Sent: Monday, January 07, 2002 3:36 AM > To: [EMAIL PROTECTED] > Subject: [Xdoclet-devel] {0} in <template destinationFile .. /> expands to > incorrect filename > > When using the {0} in destinationFile attribute of </template> element > it expands into equivalent of /<XDtEjb:ejbName/>Bean, while I think it > should expand to just exactly the same as <XDtEjb:ejbName/>. > > So, after running the template below on Account bean I will get > AccountBeanBrowse.java not AccountBrowse.java > > <template templateFile="${template.dir}/entitycmp.j" > destinationFile="{0}Test.java" > ofType="javax.ejb.EntityBean" > extent="hierarchy" havingClassTag="ejb:bean"> > </template> > > I do not know where the Bean is comming from since all predefined xdoclet > (e.g. entitycmp) tasks do not have this problem. > > Michael > > > _______________________________________________ > 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
