[
https://issues.apache.org/activemq/browse/SM-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48094#action_48094
]
Guillaume Nodet commented on SM-1721:
-------------------------------------
I have no idea for WSDL2, I would put it aside for now wrt proxy wsdls.
So we should assume the endpoint description is a WSDL 1.1 and process as it
was the case for the previous patches. It should thrown an exception if the
WSDL is not a WSDL 1.1, but it's fine for me (actually, I don't know any JBI
component using WSDL 2.0 but the very very limited support in servicemix-http).
For cleaning up the description, the code provided in the patch I attached
(which is a small modification of your own patches) does the trick and create
the soap binding and service / port with the informations provided from the
endpoint (service name + endpoint name).
> Add WSDL proxy in new HTTP endpoint
> -----------------------------------
>
> Key: SM-1721
> URL: https://issues.apache.org/activemq/browse/SM-1721
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-http
> Affects Versions: servicemix-http-2008.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Guillaume Nodet
> Fix For: servicemix-http-2008.02
>
> Attachments: SM-1721, SM-1721-2.patch, SM-1721-3.patch,
> SM-1721-4.patch, SM-1721.patch
>
>
> Currently, using new HTTP endpoints, the user needs to define the WSDL to use
> (using the wsdl attribute).
> In a lot of cases, the user wants only to expose the WSDL of the
> targetService/targetEndpoint (when available).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
