[
https://issues.jboss.org/browse/ARQ-634?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-634:
------------------------------
Workaround Description:
Manually downgrade the Servlet protocol to 2.5 by defining the @OverProtocol("Servlet
2.5") on the @Deployment
{code}
@Deployment @OverProtocol("Servlet 2.5")
public static WebArchive myDeployment() { ... }
{code}
Workaround: Workaround Exists
Servlet 2.5 support on Servlet 3.0 containers
---------------------------------------------
Key: ARQ-634
URL:
https://issues.jboss.org/browse/ARQ-634
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Protocol SPIs and Implementation
Affects Versions: 1.0.0.CR5
Reporter: Aslak Knutsen
In a Servlet Container that is defined to use the Servlet 3.0 protocol, but the user
defined deployment use a web.xml set to 2.5, the Arquillian Servlet which is added as a
web-fragment.xml in the Servlet 3.0 impl will be ignored and Arquillian can not find
itself.
The Servlet Protocol could possible check the web.xml defined in @Deployment to determine
which Servlet Protocol version to use. Meaning the Servlet 3.0 impl can downgrade to
Servlet 2.5 in the packaging process.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira