Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-2018

JavatoWSDL Package to Namespace mapping does not support multiple packages

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide

      Manually edit the wsdl.

      Show
      Manually edit the wsdl.

    Description

      Consider the following SEI:

      package org.jboss.test.ws.jbws1217;
      public interface MySEI extends java.rmi.Remote
      {

      public void testException() throws com.other.exception.TestException, java.rmi.RemoteException;
      }

      And the additional classes:

      package com.other.exception;

      public class TestException
      extends com.other.base.BaseException{
      public TestException(){
      }
      }

      package com.other.base;

      public class BaseException
      extends Exception{
      public BaseException(){
      }
      }

      Using the following wstools config:

      <configuration xmlns="http://www.jboss.org/jbossws-tools">
      <global>
      <package-namespace package="com.other.base" namespace="http://com.other.base"/>
      <package-namespace package="com.other.exception" namespace="http://com.other.exception"/>
      </global>

      <java-wsdl>
      <service name="MySEI" style="rpc" endpoint="org.jboss.test.ws.jbws1217.MySEI"/>
      <namespaces target-namespace="http://org.jboss.test.ws.jbws1217" type-namespace="http://org.jboss.test.ws.jbws1217"/>
      <mapping file="jaxrpc-mapping.xml" />
      <webservices ejb-link="MyEJB"/>
      </java-wsdl>
      </configuration>

      The WSDL generated ignores the global mappings and the namespace is derived from the class packages.

      Attachments

        Issue Links

          Activity

            People

              mageshbk_jira Magesh Bojan (Inactive)
              mageshbk_jira Magesh Bojan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 days, 4 hours
                  4d 4h