You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Marcel Schutte <ma...@schutte.com> on 2000/09/04 13:32:38 UTC
[PATCH]EjbcHelper.java - Extra checks before regenerating
Hi,
Because weblogic's ejbc is so slow, I'm always looking for ways to avoid
running it. This patch will use reflection to compare the home and remote
interface with the generated stubs and skeletons to determine whether it is
really necessary to run ejbc again.
When using an IDE like jbuilder, you sometimes select recompile all. This
will update the timestamp on the .class files and therefore trigger the
current EjbcHelper to regenerate.
Since we don't user entity beans, I couldn't check the patch on them. It
shouldn't be too hard to make the necessary adjustments though.
Regards,
Marcel Schutte
RE: [PATCH]EjbcHelper.java - Extra checks before regenerating
Posted by Marcel Schutte <ma...@schutte.com>.
Hi,
> -----Original Message-----
> From: Conor MacNeill [mailto:conor@m64.com]
> Sent: woensdag 6 september 2000 13:01
> To: ant-dev@jakarta.apache.org
> Subject: RE: [PATCH]EjbcHelper.java - Extra checks before regenerating
>
>
> Marcel,
>
> >
> > Hi,
> >
> > Because weblogic's ejbc is so slow, I'm always looking for ways to avoid
> > running it. This patch will use reflection to compare the home
> and remote
> > interface with the generated stubs and skeletons to determine
> > whether it is
> > really necessary to run ejbc again.
>
> This looks really involved stuff. I haven't gone into the details
> of it but
> I wonder if it is going too far to avoid a recompile. If you selected
> "recompile all" then that is what you really get :-).
I agree that it is going a bit far, and perhaps the code should even be
modified to be useful for WL5.1. But as I said, waiting for several ejbc's
is too much for me, unless it is really necessary.
>
> Also going through the internals of the container's generated
> classes seems
> to be assuming too much about what the container (Weblogic in
> this case) is
> choosing to put in the generated files. If you still think it is a good
> idea, then I think it would be better if this test is controlled by an
> optional attribute.
If there are others who would want to use this functionality, then I'll make
it optional behavior. Any reactions?
>
> Conor
>
>
Marcel
RE: [PATCH]EjbcHelper.java - Extra checks before regenerating
Posted by Conor MacNeill <co...@m64.com>.
Marcel,
>
> Hi,
>
> Because weblogic's ejbc is so slow, I'm always looking for ways to avoid
> running it. This patch will use reflection to compare the home and remote
> interface with the generated stubs and skeletons to determine
> whether it is
> really necessary to run ejbc again.
This looks really involved stuff. I haven't gone into the details of it but
I wonder if it is going too far to avoid a recompile. If you selected
"recompile all" then that is what you really get :-).
Also going through the internals of the container's generated classes seems
to be assuming too much about what the container (Weblogic in this case) is
choosing to put in the generated files. If you still think it is a good
idea, then I think it would be better if this test is controlled by an
optional attribute.
Conor