I'm not able to reproduce the problem, Hani.
I have two classes:
public abstract class AbstractEntityAdapter implements javax.ejb.EntityBean
{}
public abstract class LocalEntityAdapter extends AbstractEntityAdapter {}
compiled, and wrapped in a jar. Then I have @tagged EJB: FooBean extends
LocalEntityAdapter. I Run XDoclet, and everyting works fine. I get generated
classes and FooBean entries in the deployment descriptors.
1) Have you included your binary classes on the <taskdef>?
2) Are you really sure you're using the xdoclet-*-b2.jars? (You're talking
about jars without version numbers, but they now _do_ have version numbers
in the file name.
Aslak
> -----Original Message-----
> From: Hani Suleiman [mailto:[EMAIL PROTECTED]]
> Sent: 13. desember 2002 19:15
> To: Aslak Hellesoy
> Subject: Re: [Xdoclet-user] Latest CVS breaks stuff...
>
>
> Binaries.
>
> On Friday, December 13, 2002, at 01:09 PM, Aslak Hellesoy wrote:
>
> >
> >
> >> -----Original Message-----
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED]]On Behalf Of Hani
> >> Suleiman
> >> Sent: 13. desember 2002 18:18
> >> To: [EMAIL PROTECTED]
> >> Subject: [Xdoclet-user] Latest CVS breaks stuff...
> >>
> >>
> >> I just tried to update my xdoclet installation use the latest CVS HEAD
> >> version, and for some reason none of my EJB classes are being picked
> >> up
> >> anymore.
> >>
> >> I have:
> >>
> >> MyBean extends LocalEntityAdapter, and LocalEntityAdapter extends
> >> AbstractEntityAdapter, which in turn implements EntityBean
> >>
> >
> > Are LocalEntityAdapter and AbstractEntityAdapter available to XDoclet
> > as
> > source or binaries?
> >
> > Aslak
> >
> >> Similar sort of mechanism for session beans.
> >>
> >> I've made sure I've updated xjavadoc.jar, xdoclet.jar, and
> >> xdoclet-ejb.jar, it all builds fine (well, it dies at the maven docs
> >> build point since I refuse to install maven, but by then all the jars
> >> I
> >> need have been built).
> >>
> >> The xdoclet task runs over my sources, but doesn't generate anything
> >> for the EJB's, which is rather upsetting. This works fine when I
> >> revert
> >> to xdoclet libs built about a couple of weeks ago. I'm hoping this
> >> info
> >> is sufficient to nudge one of the developers' memories, if not I'll
> >> try
> >> to debug it more thoroughly and find out where things are going wrong.
> >>
> >> Hani
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> This sf.net email is sponsored by:
> >> With Great Power, Comes Great Responsibility
> >> Learn to use your power at OSDN's High Performance Computing Channel
> >> http://hpc.devchannel.org/
> >> _______________________________________________
> >> Xdoclet-user mailing list
> >> [EMAIL PROTECTED]
> >> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
> >
> >
>
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
