hi,

i presume you did an <include> and not an <exclude>.

you're a bit vague. what do you mean with "nothing gets generated"? -"no
java source code is generated"? -"no entries in the deployment descriptors"?
both?

please send mail in plain text. it makes it easier to inline responses.

aslak

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Westlin Peter
Sent: 20. januar 2003 15:14
To: [EMAIL PROTECTED]
Subject: [Xdoclet-user] ejbdoclet and inheritance


Hi all!

I use an CVS versoin of Xdoclet from mid september. We have used this
version since that without problems. We also have a big project so we don't
want to migrate to 1.2b2 just yet.
Ok, my problem:
We are developing three parallell products in our project and the first
product (call it A) implements some common functionality (like base classes
for ejb and so on) and product B and C use these classes. A, B and C have
different ant scripts so B and C includes a JAR-file with the common classes
generated and compiled from A. When I generate CMP's/BMP's in A that extends
my base classes everything is fine but in B and C nothing gets generated for
the CMP's. BMP's are fine though.
Then I thought that Xdoclet maybe needs the source code for the base classes
so I added them to my ejbdoclet task as:
------
<fileset dir="foo">
   <exclude name="**/*.java" />
<fileset />
------
When I did this everything worked fine... Does Xdoclet need the source code
for base classes when generating CMP's? If that is so, why did generation of
BMP's work... :-)

Regards Peter



-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to