[ jetty-Bugs-1663031 ] Jetty 6: Deletion of compiled JSPs not detected

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[ jetty-Bugs-1663031 ] Jetty 6: Deletion of compiled JSPs not detected

SourceForge.net
Bugs item #1663031, was opened at 2007-02-18 22:19
Message generated for change (Comment added) made by janb
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=107322&aid=1663031&group_id=7322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Graham Lea (grlea)
>Assigned to: Jan Bartel (janb)
Summary: Jetty 6: Deletion of compiled JSPs not detected

Initial Comment:
If Jetty's compiled JSPs are deleted (while Jetty is running) a 'Page not found' error is returned.

As these are only temporary, generated files, their deletion should be detected and they should be regenerated when next required.

PS - This bug tracker is missing a 'JSP' category and Groups for Jetty 4, 5 & 6.


----------------------------------------------------------------------

>Comment By: Jan Bartel (janb)
Date: 2007-03-05 00:36

Message:
Logged In: YES
user_id=45251
Originator: NO

I can't reproduce this either on jetty-6.1.2rc0.

I will close this bug as unreproduceable for now, but if you can
consistenly reproduce it, then please open a fresh bug on the codehaus
jetty 6 issue tracker at : http://jira.codehaus.org/browse/Jetty

----------------------------------------------------------------------

Comment By: Jan Luehe (jluehe)
Date: 2007-02-26 19:08

Message:
Logged In: YES
user_id=1729620
Originator: NO

Hmm, I'm unable to reproduce this issue with GlassFish.

When any of the generated (.java or .class file) artifacts have been
deleted, they do get regenerated the next time the JSP is accessed, which
is the expected behaviour.


----------------------------------------------------------------------

Comment By: Greg Wilkins (gregwilkins)
Date: 2007-02-23 04:34

Message:
Logged In: YES
user_id=44062
Originator: NO

This is probably a bug on Glassfish, as we use their JSP engine.

Note that we don't really use this issue tracker anymore, as we have
mostly moved to
codehaus.  Follow the links off
http://docs.codehaus.org/display/JETTY/Jetty+Wiki

Please raise this issue on our codehaus tracker and we can follow up with
the
glassfish folks (but probably a little slowly as it is not our core
stuff).
Raise it directly with glassfish if you want a fast resolution.

Does touching the js source file fix the problem?






----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=107322&aid=1663031&group_id=7322

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss