[
https://issues.apache.org/jira/browse/AXIS2-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199549#comment-13199549
]
Sagara Gunathunga commented on AXIS2-4692:
-------------------------------------------
I didn't have time to look into this throughly yet but following are some of my
comments on this.
In option (1) since user has to explicitly pass the endpoints I think it's safe
to ignore the Axis2 configuration. Runtime availability of that particular
transport endpoint is a responsibility of the user. In this approach user don't
need to edit axis2.xml or any other configuration file in order to use
JAVA2WSDL tool. If we enforce such constrains it just reduce the usability of
the tool.
Are you aware with any consequences of this approach ?
IMO option (1) is much preferable and simple and I don't think it's hard to
implement this too.
> Java2WSDL not generating location HTTPS
> ---------------------------------------
>
> Key: AXIS2-4692
> URL: https://issues.apache.org/jira/browse/AXIS2-4692
> Project: Axis2
> Issue Type: Bug
> Environment: OS: Debian GNU/Linux
> WSO2 WSAS v3.1.3
> Reporter: Vitor Manuel Alves Rodrigues
> Attachments: Entity_HTTP.wsdl, Entity_HTTPS.wsdl, services.xml
>
>
> Hi everyone,
> I have this in my build.xml, to generate my wsdl:
> ...
> <java classname="org.apache.ws.java2wsdl.Java2WSDL" fork="yes" >
> <arg value="-l"/>
> <arg
> value="https://entitas-d.corp.turismodeportugal.pt:9443/services/Entity"; />
> <arg value="-of"/>
> <arg value="${wsdl.dir}/Entity.wsdl" />
> <arg value="-tn"/>
> <arg value="http://entitas.turismodeportugal.pt"; /> -->
> <!-- <arg value="-cn" />
> <arg value="pt.turismodeportugal.entitas.Entity" />
> <classpath>
> <path refid="axis.classpath"/>
> <pathelement path="${classes.dir}"/>
> </classpath>
> </java>
> ...
> For HTTP(changing the line <arg
> value="https://entitas-d.corp.turismodeportugal.pt:9443/services/Entity"; />
> to <arg
> value="http://entitas-d.corp.turismodeportugal.pt:9763/services/Entity"; />)
> it produces this in the wsdl:
> ....
> <wsdl:service name="Entity">
> <wsdl:port name="EntityHttpSoap11Endpoint"
> binding="ns:EntitySoap11Binding">
> <soap:address
> location="http://entitas-d.corp.turismodeportugal.pt:9763/services/Entity"/>
> </wsdl:port>
> <wsdl:port name="EntityHttpSoap12Endpoint"
> binding="ns:EntitySoap12Binding">
> <soap12:address
> location="http://entitas-d.corp.turismodeportugal.pt:9763/services/Entity"/>
> </wsdl:port>
> <wsdl:port name="EntityHttpEndpoint" binding="ns:EntityHttpBinding">
> <http:address
> location="http://entitas-d.corp.turismodeportugal.pt:9763/services/Entity"/>
> </wsdl:port>
> </wsdl:service>
> ....
> For the HTTPS, it doesn't produce the Endpoints.... Any ideas? Something in
> the services.xml missing? I will attach the files.....
> Help please it urgent :S
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
