[jbossws-issues] [JBoss JIRA] Created: (JBWS-2699) BackwardCompatibleURLPatternDeploymentAspect is mangling URLs

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Fri Jul 3 06:56:52 EDT 2009


BackwardCompatibleURLPatternDeploymentAspect is mangling URLs
-------------------------------------------------------------

                 Key: JBWS-2699
                 URL: https://jira.jboss.org/jira/browse/JBWS-2699
             Project: JBoss Web Services
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: jbossws-cxf, jbossws-metro, jbossws-native
            Reporter: Alessio Soldano
            Assignee: Richard Opalka
             Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0


Kevin says:

> StringTokenizer st = new StringTokenizer(urlPattern, "/");
> if (st.countTokens() > 1 && urlPattern.startsWith(contextRoot + "/"))
> {
> urlPattern = urlPattern.substring(contextRoot.length());
> }

Yes, this is the part which does the damage.

The contextRoot, in the case I am investigating, is the same as the first part of the urlPattern.  This means that the generated WSDL contains the wrong endpoint location, as does the JBossWS console, yet the webservice is still deployed at the right location.

So the webservice is actually deployed at /a/a/b but WSDL and WS console report it at /a/b. 

-- 
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

        



More information about the jbossws-issues mailing list