[ 
https://issues.apache.org/activemq/browse/SM-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated SM-1721:
-------------------------------------

    Attachment: SM-1721-4.patch

It's a patch snapshot (not the final one).

Guillaume, could you please check if I'm on the correct way.

In this patch, I have :
- dedicated validate() method for the attributes value check (like marshaller)
- create two methods : one for reading the WSDL from the user provided file, 
another one for reading the WSDL from the target endpoint. These two methods 
read the WSDL are put in the description.
- I have override the activate() method to call reading methods

Currently, I have two questions :
- I have validate a WSDL1 reading the WSDL definition from the description but 
how can do that using woden for WSDL2 (see TODO line 198)
- When I read the WSDL from the target endpoint, I guess these WSDL contains 
attributes specific to the target endpoint. I think that I need to cleanup the 
target WSDL and populate with attribute for my component, correct ? (see TODO 
line 177)

> 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.

Reply via email to