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

Hadrian Zbarcea reopened CAMEL-3105:
------------------------------------


@Claus,

The ASF has a pretty formal way of accepting contributions. Taking code from 
github is not one of them. We have to be able to track the IP grants (see the 
'Software Grants' section at http://apache.org/licenses/#clas).

The easiest option I see is for you to revert your commit and have Richard 
attach his contribution (this qualifies as a significant contribution) as a zip 
to this jira and explicitly grant license to Apache for inclusion. If you have 
any questions please feel free to find me online and ask.


> Contribution: Spring Web Services component
> -------------------------------------------
>
>                 Key: CAMEL-3105
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3105
>             Project: Apache Camel
>          Issue Type: New Feature
>    Affects Versions: 2.3.0
>            Reporter: Richard Kettelerij
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>
> I'd like to contribute a component I've developed to Apache Camel that adds 
> support for Spring Web Services. The component is Apache 2.0 licensed - as is 
> Spring-WS - and available from: 
> http://github.com/rkettelerij/camel-spring-ws. Note that I'll happily remove 
> this repo if and once the component is added to Camel's codebase.
> Currently the component only offers producer support (with help of Spring's 
> WebServiceTemplate). I'm busy developing consumer support that allows you to 
> express Spring-WS endpoint mappings through Camel uri's. This is coming along 
> nicely and I'm hoping to release a tested version soon. Development can be 
> tracked in this branch: 
> http://github.com/rkettelerij/camel-spring-ws/tree/consumer/
> Examples (producer only):
> 1) Route message to webservice:
> {code}
> from("direct:myservice").to("springws:http://somehost/myservice";)
> {code}
> 2) Configuration through url options (e.g SOAP action and WS-Addressing):
> {code}
> from("direct:myservice").to("springws:http://somehost/myservice?soapAction=http://somehost/foo&wsAddressingAction=http://somehost/bar";)
> {code}
> 3) The components allows you to use the full power of Spring-WS client 
> support by referencing a WebServiceTemplate in the Registry 
> (ApplicationContext):
> {code}
> from("direct:myservice").to("springws:http://somehost/myservice?webServiceTemplate=#webServiceTemplate";)
> {code}
> If you only want to use a custom message sender or message factory (e.g for 
> Axiom messages) you can use:
> {code}
> from("direct:myservice").to("springws:http://somehost/myservice?messageFactory=#messageFactory&messageSender=#messageSender";)
> {code}
> I'm open to any suggestions/comments/etc.

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