[
https://jira.jboss.org/jira/browse/JBWS-1309?page=com.atlassian.jira.plug...
]
Erik Mattheis commented on JBWS-1309:
-------------------------------------
I did a little deeper investigation, and it looks like JBoss is actually recognizing the
configuration, but it fails to write the correct endpoint address in the WSDL. The WSDL
shows a plain http:// address, but when you try to invoke the endpoint using that address,
JBoss returns an HTTP 302 response with the https:// location. If you manually specify the
https:// location instead of the address in the WSDL, the service works as expected.
Support xml overrides for @WebContext and @EndpointConfig
----------------------------------------------------------
Key: JBWS-1309
URL:
https://jira.jboss.org/jira/browse/JBWS-1309
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-integration, jbossws-native
Reporter: Jason T. Greene
Assignee: Alessio Soldano
Similar to EJB3 annotations, we need to support an xml override for the PortComponent
annotation. The information will then need to be pulled from the JBoss metadata.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira