[
https://issues.apache.org/jira/browse/AXIS2-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Eranga Suriarachchi updated AXIS2-4932:
---------------------------------------------
Attachment: EchoInt.jar
EchoString.jar
Attaching the services..
> Problems when two JAX-WS services have the same packageName + ClassName
> -----------------------------------------------------------------------
>
> Key: AXIS2-4932
> URL: https://issues.apache.org/jira/browse/AXIS2-4932
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Isuru Eranga Suriarachchi
> Assignee: Isuru Eranga Suriarachchi
> Fix For: 1.6
>
> Attachments: EchoInt.jar, EchoString.jar
>
>
> When I was trying to reproduce the issue in [1], I realized that, when two
> JAXWS services (in two different jar files) have the same packageName +
> className, the WSDL shown on ?wsdl is wrong.
> Here's the reason. Our JAXWSRIWSDLGenerator creates a folder in the java tmp
> directory to save the generated WSDL and schema files from wsgen. But it
> creates this folder only using the annotated class name. But in the above
> case, both the services have the same fully qualified class name. Therefore,
> in this case both services will share the same folder. But the two service
> have two different WSDLs and Schemas. Thefeore sometimes ?wsdl shows the WSDL
> or schema of the other service.
> Steps to reproduce
> ============
> 1. deploy the attached two services
> 2. do ?wsdl on both services. first time it will show the correct WSDLs
> 3. restart the server
> 4. ?wsdl on both services. you should now see the incorrect WSDL for one of
> the services.
> Thanks,
> ~Isuru
> [1] https://issues.apache.org/jira/browse/AXIS2-4151
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
