[
https://issues.apache.org/jira/browse/AXIS2-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988768#comment-12988768
]
Isuru Eranga Suriarachchi commented on AXIS2-4613:
--------------------------------------------------
Hi Andreas,
Actually I tested a normal JAX-WS service earlier and resolved the issue
without checking the Calculator service. So here is the reason for this. In
Calculator service, we have embedded the WSDl in the service and used
@wsdlLocation annotation. So the AxisService object is created using the given
WSDL by WSDL11ToAxisServiceBuilder. Following is the port of the given WSDL.
<port name="CalculatorServicePort" binding="tns:CalculatorServicePortBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
Here the location is just a string and not a URI. So the transportInDescName in
the AxisEndpoint becomes null and when ?wsdl is called, no binding is generated
(see generateSoap11Port on AxisService2WSDL11.java).
This issue is not related to JAX-WS. We can reproduce this even by a pojo with
a WSDL in the META-INF file. So I'll fix the sample by setting the address
"http://localhost:8080/CalculatorService". But I think we have to fix this
because all ports should be properly generated according to existing transports
irrespective of what the WSDL contains.
Thanks,
~Isuru
> WSDL exposed by JAX-WS is missing binding and port definitions
> --------------------------------------------------------------
>
> Key: AXIS2-4613
> URL: https://issues.apache.org/jira/browse/AXIS2-4613
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Affects Versions: nightly
> Reporter: Andreas Veithen
> Assignee: Isuru Eranga Suriarachchi
> Fix For: 1.6
>
>
> Steps to reproduce the issue:
> * Build the jaxws-calculator sample.
> * Deploy the JAR artifact to servicejars.
> * Query the WSDL.
> Result:
> * With 1.5.1, the WSDL is complete.
> * With SNAPSHOT, the WSDL doesn't contain the wsdl:binding and wsdl:port
> elements.
> Tested with Axis2 binary distribution (i.e. SimpleHTTPServer), but seems to
> occur also when using the WAR.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]