You get it right (fully qualified) the second time you run XDoclet because, the com.xxxxxx.xxxxx.xxx.xxxxx.SomeDataObject source exists, whereas the first time it doesn't. -And you had to delete the ejb-jar.xml file to get it regenerated (because XDoclet has dependency checking based on timestamps). Try to delete ejb-jar.xml AND the generated com.xxxxxx.xxxxx.xxx.xxxxx.SomeDataObject and run again. Then it will be still wrong!
This was just to explain what's happening. We recently did some changes that hopefully fixes this "qualification of non-existant classes" problem, so if you do a CVS update and rebuild XDoclet, you might get the name correctly qualified even when the class in question doesn't exist yet. Beware that if you don't explicitly import the com.xxxxxx.xxxxx.xxx.xxxxx.SomeDataObject class in your com.xxxxxx.xxxxx.xxx.xxxxx.SomeBean (where your transaction tags probably are), xjavadoc will have trouble guessing what package SomeDataObject belongs to, and it will assume that it belongs to the same package as the referring class (i your version it assumes the default package which is even worse). If you import the whole package where SomeDataObject belongs, it's still impossible for xjavadoc to guess that, because the class doesn't exist. Importing the class explicitly should make the problem vanish. Also note that it's VERY RISKY to pass the generated classes in xdoclet's <fileset>s, because you risk getting different output depending on whether the generated classes already exist or not. Better leave these classes out of the fileset and play with import statements until you get it right. Hope this helps, Aslak > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Gwyn Evans > Sent: 16. juli 2002 14:24 > To: [EMAIL PROTECTED] > Subject: [Xdoclet-user] Problems when setting transaction levels in > ejb-jar.xml > > > Hi, > > Just a note to see if this rings any bells... I'm running a > couple-of-weeks old version of XDoclet, and have just come across > one problem involving the transaction definition sections in > ejb-jar.xml. > > The problem is that if I run the various xdoclet tasks all in one > task, when it should generates the following > > <container-transaction > > <method > > <ejb-name>EjbName</ejb-name> > <method-intf>Remote</method-intf> > <method-name>createX</method-name> > <method-params> > > <method-param>com.xxxxxx.xxxxx.xxx.xxxxx.SomeDataObject</method-param> > </method-params> > </method> > <trans-attribute>Required</trans-attribute> > </container-transaction> > > it instead generates the above but with > > <method-param>SomeDataObject</method-param> > > > If I delete the ejb-jar.xml & re-run the same ant-task, the correct > (fully-qualified) line is generated... > > -- > Best regards, > Gwyn mailto:[EMAIL PROTECTED] > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Jabber - The world's fastest growing > real-time communications platform! Don't just IM. Build it in! > http://www.jabber.com/osdn/xim > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
