On Fri, 2004-04-23 at 17:41, [EMAIL PROTECTED] wrote:
> OK, This is bumming me out now! Not to mention I am a week late on this.
> 
> On windows, I seem to get the same "couldn't load" statements but everything
> seems to work fine.

Can you post your build script, and the relevant bits of one of your
beans?  Maybe someone will spot something amiss.

> Here is now the same thing but off my windows build:
> 
> 
> ==========================================================================
> [ejbdoclet] (XDocletMain.start                   47  ) Running
> <valueobject/>
> Finding class xjavadoc.XJavaDoc$NoInnerClassesPredicate
> Class xjavadoc.XJavaDoc$NoInnerClassesPredicate loaded from ant loader
[snip]
> Finding class xjavadoc.ReturnType
> Class xjavadoc.ReturnType loaded from ant loader
> Class java.lang.reflect.AccessibleObject loaded from parent loader
> Finding class javax.ejb.CreateException
> Class javax.ejb.CreateException loaded from ant loader
> Finding class javax.ejb.EJBException
> Class javax.ejb.EJBException loaded from ant loader
> Finding class javax.ejb.FinderException
> Class javax.ejb.FinderException loaded from ant loader
> Finding class javax.ejb.SessionBean
> Class javax.ejb.SessionBean loaded from ant loader
> Finding class javax.ejb.SessionContext
> Finding class javax.ejb.EJBContext
> Class javax.ejb.EJBContext loaded from ant loader
> Class javax.ejb.SessionContext loaded from ant loader
> Finding class com.wf.bd.ice.alert.AlertManagerBean.SessionBean
> Finding class com.wf.bd.ice.alert.SessionBean
> Finding class java.lang.SessionBean
> Finding class
> com.wf.bd.ice.creditapplication.CreditApplicationManagerBean.SessionBean
> Finding class com.wf.bd.ice.creditapplication.SessionBean
> Finding class java.lang.SessionBean

Strange - why's it looking all over the place for SessionBean?  It found
it okay earlier on.  I assume you've imported it okay in those two
classes?

> Finding class org.apache.commons.collections.CollectionUtils
[snip]
> Finding class com.wf.bd.ice.alert.AlertManagerBean.EJBException
> Finding class com.wf.bd.ice.alert.EJBException
> Finding class java.lang.EJBException

Ditto - why's it looking all over the place for EJBException?  It found
it okay earlier on, so why doesn't it know what it is now?  Perhaps you
could try changing the AlertManager bean to use fully qualified
classnames, and see if that makes any difference?


Andrew.



-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to