- This topic has 4 replies, 2 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
maybe this should rather go to the bug section.
Anyway, what I get when I save my model classes and have a compilation error is my tomcat 5.0.27 restarting the context.
Which is rather annoying, as there shouldn’t be anything to be freshly loaded.hope you’ll change it.
thanks,
axelAxel,
If you are using an exploded deployment, and you are changing a class, then the file is getting deployed to Tomcat, tomcat is detecting the change and reloading the context… you can a) use a packaged deployment instead to avoid this or b) turn off reload of contexts in Tomcat.Riyad,
question. Maybe I’m missing something here.
ME is compiling the classes before they get deployed, right?
So if ME can detect a _compilation error_ then, why does it deploy it at all?
No need to deploy anything here (actually I suppose, ME deploys the old class file again, as there shouldn’t be any new one)ME is compiling the classes before they get deployed, right?
Actually its Eclipse… but yes, ME picks up the change and deploys it.
So if ME can detect a _compilation error_ then, why does it deploy it at all?
a) I don’t know if it can’t detect there was an error during the Eclipse compilation b) but if it can, that’s a good idea… I’ll ask the team if its possible.
No need to deploy anything here
Yes I see what you mean, sorry I misunderstood the comment at first.
