Hi, > -----Original Message----- > From: Conor MacNeill [mailto:[EMAIL PROTECTED] > Sent: woensdag 6 september 2000 13:01 > To: [EMAIL PROTECTED] > 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
