And why don't you use two different "ejbdoclet" entries?
Each one would have a "deploymentdescriptor" entry and a "fileset" entry.
The "deploymentdescriptor" entry would define its own XML descriptor.
And "fileset" entry would define the right file patterns ( **/*.java or **/*
RO.java )
Could it work ?
2007/1/23, Casey Rayman <[EMAIL PROTECTED]>:
I have a situation where I am attempting to migrate an application to
use Xdoclet, but I've run into a roadblock. This application makes use
of a Weblogic feature where you can have multiple entity bean deployment
descriptors for each entity bean. Each bean has two JNDI "names":
"BeanName" and "BeanNameRO". The only differences are whether the bean
supports transactions(The RO does not) and of course the queries are
different because of the naming. I'm not sure if the best way to
accomplish this is with a modification to a template or whether to
develop another type of @ejb or @weblogic tag. Does anyone have any
ideas?
Thank You,
Casey
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
xdoclet-user mailing list
xdoclet-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
xdoclet-user mailing list
xdoclet-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
