Vincent,
Vincent Massol wrote:
> > I've almost got it right now. The major roadblock is to find and parse
> > the EJB deployment descriptor, so we won't have to put in the name of
> > the remote interface. I'll keep you informed.
>
> hum ... I had not thought about that. I understand that you may need to
> generate mock stubs and home implementations but I don't understand why you
> would have to mess with class files ?
Generating stubs is a complex process. We might generate a .java file,
then compile it. But we'd have the same problems that the Jasper folks
have compiling .jsp pages.
Right now, the Sun folks are going to delete the entry point to javac,
and this means lots of problems to Jasper.
So, I prefer to take some generic .class files, and modify them with a
ClassLoader so they will generate the correct beans. Right now, the
class-loading part has been successful; there are some problems in the
class hierarchy, which I hope to resolve today.
Do you know of any simpler way, that does not involve compiling java
files?
Un saludo,
Alex.
