[
https://issues.jboss.org/browse/AS7-5731?page=com.atlassian.jira.plugin.s...
]
Fernando Rubbo edited comment on AS7-5731 at 10/15/12 1:45 PM:
---------------------------------------------------------------
Since it is not possible, in an unique deployment unit, to use FORM authentication for Web
Pages and BASIC authentication for JAX-RS, then it is not possible to have JAX-RS being
consumed from both Web Pages and other apps.
That is why we are asking for this feature request. If JBoss want to leverage JAX-RS, it
should not have such a restriction.
Actually, I think a @WebContext like solution should be into JavaEE spec. But...
was (Author: fernando.rubbo):
Since it is not possible to user FORM authentication for Web Pages and BASIC
authentication for JAX-RS, then it is not possible to have a unique package which we could
have JAX-RS being consumed from both Web Pages and other apps.
Actually, I think a @WebContext like solution should be into JavaEE spec. But... That is
why we are asking for this feature request.
Add equivalent @WebContext for JAX-RS?
--------------------------------------
Key: AS7-5731
URL:
https://issues.jboss.org/browse/AS7-5731
Project: Application Server 7
Issue Type: Feature Request
Reporter: Fernando Rubbo
Labels: BASIC_AUTH, FORM_AUTH, JAX-RS,
Currently, in our application we use @WebContext to set a different contextRoot for
JAX-WS. For example:
@Stateless
@SecurityDomain("test2")
@WebService(name = "HelloSoap", portName = "HelloSoapPort",
serviceName = "HelloSoap", targetNamespace = "http://com.test")
@WebContext(contextRoot = "/ws", urlPattern = "/HelloSoap",
secureWSDLAccess = false, authMethod = "BASIC", transportGuarantee =
"NONE")
public class HelloSoap { ... }
We would like to have an equivalent annotation for JAX-RS? It is required whenever a web
app uses FORM_AUTH and there exists web services (JAX-WS and JAX-RS), inside of the same
package, using as BASIC_AUTH.
Thankyou in advance,
Fernando Rubbo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira