The "error" you get in Xdoclet is not actually an error. It's tagged as INFO. Joris 
Verbogt [EMAIL PROTECTED] posted the solution to avoid seeing the info at all (use 
fully-qualified class names for value objects).

As for Eclipse, are you having Xdoclet generate code into a different directory (I put 
it into "generated" at the same level as "src")? If so, is that directory in Eclipse's 
source path (if it has one)?

I'll be evaluating Eclipse here after our release in a few weeks, so if you find a 
solution, would you mind following up to the list? Thanks!

Peace,

David Harkness
Sony Pictures Digital Networks
(310) 482-4756

-----Original Message-----
From: Ernst Pl�ss [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 01, 2003 11:39 PM
To: [EMAIL PROTECTED]
Subject: [Xdoclet-user] Not yet generated value objects in eclipse


Hi

I'm useing Xdoclet and Eclipse. Xdoclet generates
everything I need for CMP, Interfaces, CMP classes and
value objects. Perfect!

In order to get e setter method, to set the value
object back to the bean, I had to implement something
like

public abstract void setMyBeanVO(MyBeanVO inMyBeanVO);

in the bean class.

Although Xdoclet is creating exactly the CMP class I'd
like to have, I get an error from Eclipse and Xdoclet,
because they don't know about the MyBeanVO before it's generated.

In Xdoclet I get the following error:
[ejbdoclet] INFO:    Some classes refer to other
classes that were not found among the sources or on
the classpath.
[ejbdoclet]          (Perhaps the referred class
doesn't exist? Hasn't been generated yet?)
[ejbdoclet]          The referring classes do not
import any fully qualified classes matching these
classes.
[ejbdoclet]          However, since no packages are
imported, xjavadoc has assumed that the referred
classes
[ejbdoclet]          belong to the same package as the
referring class. The classes are:

Eclipse complains with:
MyBeanVO cannot be resolved. ...

Especially the eclipse error is nasty, because this
way the syntax checking of eclipse gets useless
because every entitity bean won't compile without
errors.

Any ideas to solve this problem?
TIA
Ernst



__________________________________________________________________

Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingelt�ne f�rs Handy bei http://sms.yahoo.de


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, 
E-commerce, Portals, and Forums are available now. Download today and enter to win an 
XBOX or Visual Studio .NET. 
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to