-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve ResourceFactory and Resource list handling #5133
Comments
@janbartel if I remove these 2 lines from the jetty-9.4.x branch then the WebAppClassLoader is not updated from the extraClasspath. Should WebInfConfiguration set the WebAppClassLoader? or is that handled in a later Configuration from the MetaData? |
@joakime I think that WebInfConfiguration should do the parse of the extraClassPath and then poke the results into the WebApPClassLoader, because it is already poking the WEB-INF/classes and WEB-INF/lib jars into it. WebInfConfiguration should not create the WebAppClassLoader, that is handled by the WebAppContext in it's startup sequence, and allows for the user to supply their own. |
+ Now parsed by WebAppContext into List<Resource> + Reintroduced Resource.fromList + Refactored ResourceFactory to never return null and always throw an exception if unable to get/create/resolve the Resource Signed-off-by: Joakim Erdfelt <[email protected]>
+ Reverting name ResourceFactory.newResource(String) to .getResource(String) + Reintroducing Resource.getResource(String) + ResourceHandler.getResource(String) cleaned up in light of Exception handling requirement + Resource.addPath(String) implementations can never return null now Signed-off-by: Joakim Erdfelt <[email protected]>
Opened PR #5142 |
…ded. Signed-off-by: Joakim Erdfelt <[email protected]>
Signed-off-by: Joakim Erdfelt <[email protected]>
Signed-off-by: Joakim Erdfelt <[email protected]>
Jetty version
10.0.x
Description
While reviewing PR #5131 it was discovered that the WebAppClassLoader constructor automatically added the WebAppContext.getExtraClassPath() entries on it's own.
While at the same time WebInfConfiguration was processing the WebAppContext.getExtraClassPath() in it's own Servlet specific ways.
https://github.com/eclipse/jetty.project/blob/e117fbe8281bd43ec5601a30d39f50a09cbcef22/jetty-webapp/src/main/java/org/eclipse/jetty/webapp/WebAppClassLoader.java#L195-L196
This behavior in the WebAppClassLoader constructor should be removed.
The text was updated successfully, but these errors were encountered: