]
Stuart Douglas updated WFLY-1854:
---------------------------------
Fix Version/s: Awaiting Volunteers
Assignee: (was: Stuart Douglas)
web-fragment.xml not loaded from a static module
------------------------------------------------
Key: WFLY-1854
URL:
https://issues.jboss.org/browse/WFLY-1854
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Undertow)
Affects Versions: 8.0.0.Alpha3
Reporter: Marek Schmidt
Fix For: Awaiting Volunteers
Attachments: WFLY-1854.tar
Having a custom static module, e.g. org/jboss/solder which contains solder.jar with
META-INF/web-fragment.xml with some filters defined (e.g. CatchExceptionFilter)
and a WAR application, e.g. catch-basic-servlet (on of Solder examples) with
jboss-deployment-structure.xml such as
{code}
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<dependencies>
<module name="org.jboss.solder"
meta-inf="import"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
The filters defined in the solder's web-fragment.xml don't seem to work, while
the same app works fine if the solder.jar is deployed in the WAR in the WEB-INF/lib
instead of a static module.
People seem to assume that whatever works for WEB-INF/lib would also work for a static
module. This assumption should either be fulfilled or clearly explained to people if it
doesn't hold.