-
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
replacement for GlobalWebappConfigBinding #11847
Labels
Comments
@nbartels I think this type of functionality was accidentally omitted from jetty-12, let me have a look at putting something like it back in. |
@nbartels can I see a (sanitized if ncessary) example of the |
@janbartel sure. <?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_3.dtd">
<Configure class="org.eclipse.jetty.ee8.webapp.WebAppContext">
<Set name="throwUnavailableOnStartupException">true</Set>
<Call name="addEventListener">
<Arg><New class="my.namespace.RequestContextScope"/></Arg>
</Call>
<Get id="protected" name="ProtectedTargets"/>
<Set name="ProtectedTargets">
<Call class="org.eclipse.jetty.util.ArrayUtil" name="addToArray">
<Arg><Ref refid="protected"/></Arg>
<Arg>/my.yaml</Arg>
<Arg></Arg>
</Call>
</Set>
<Set name="overrideDescriptor"><Property name="jetty.base"/>/etc/override-web.xml</Set>
</Configure> |
janbartel
added a commit
that referenced
this issue
May 31, 2024
janbartel
added a commit
that referenced
this issue
Jun 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty Version
Jetty 12.0.9
Jetty Environment
ee8
Java Version
21
Question
I'm migrating an application from Jetty 9 to 12 and have some xml configurations here. The most seems to work, but I'm stuck on GlobalWebappConfigBinding. I see this is available until jetty 11 and no longer available in Jetty 12.
Can you give me a hint, how I have to replace it in Jetty 12?
here is the xml snippet I try to get to work again:
The text was updated successfully, but these errors were encountered: