Andrew,
The class that's not being found is my own base class - not anything from struts. i.e, i have
com.foo.MyBaseForm com.foo.MyListForm extends MyBaseForm
However, I think I might know the issue based on your email. The base classes themselves don't have the struts attributes - they're meant to be extended, not actually used as concrete forms. While the source files for the two base classes are passed to webdoclet, the compiled classes aren't (I'm using xdoclet to generate classes for EJBs so I can't actually compile the entire project until after at least ejbdoclet).
I suppose what was confusing me is that the actual struts forms are picked up by webdoclet just from source (i.e, not compiled classes).
Thanks for your help.
David J. Hamilton Software Engineer Bricsnet The CRE Automation Company [EMAIL PROTECTED] +1 415.884.5678x822 http://www.bricsnet.com/
Andrew Stevens wrote:
On Fri, 2004-12-17 at 00:55, David J. Hamilton wrote:
I've experienced some issues using XDtClass:forAllClasses or XDtType:ifIsOfType in a custom struts template, in particular with the extent being set to "hierarchy".
The behavior I'm getting is that the object hierarchy is only partially traversed, which allows me to use XDtType:ifIsOfType only in the context of "super" rather than "hierarchy". For instance, if I have an object graph
A
B,C,D extends A
E extends B
and my template wants to do something for all objects of type "A", only objects B,C,D will be affected, not E.
Tracing xdoclet shows me the issue. The superclass is loaded as an UnknownClass, which implicitly extends Object, which of course ends the hierarchy search. I may be failing to RTFM sufficiently, but what might I do in order for the superclass to be loaded correctly? (i.e, to be loaded such that it knows its own superclass).
If the superclass is an UnknownClass, that suggests the parser (xjavadoc) can't find it in the classpath it's using. You mention Struts; have you included the Struts jar in the classpath you specify when you declare the xdoclet task? That should be enough to let xjavadoc figure out their inheritence hierarchy. Alternatively, you could include their sources in the fileset you pass to xdoclet, but that's more relevant when e.g. you have your own base class which is extended by the classes you want XDoclet to process.
Andrew.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
