camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrej Zachar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5815) camel-spring-ws - Support for WS-Addressing Action
Date Thu, 29 Nov 2012 06:34:58 GMT

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

Andrej Zachar updated CAMEL-5815:
---------------------------------

    Attachment: camel-spring-ws-2.11.patch

Hello Claus, 
I am sending you my first implementation of the WS-Addressing consuming. 
The patch add supported following routes uri definitions:

<from uri="spring-ws:action:<your wsa action>?endpointMapping=#wsaEndpointMapping"/>
<from uri="spring-ws:action:<your wsa action>:<your wsa to>?endpointMapping=#wsaEndpointMapping"/>
<from uri="spring-ws:to:<your wsa to address>?endpointMapping=#wsaEndpointMapping"/>
<form uri="spring-ws:to:<your wsa to address>:<your wsa action>?endpointMapping=#wsaEndpointMapping"/>

		
If you need to specify reply action for response or fault response you can use similar params
to spring ws's @Action, e.g. the output and the fault action. This will cause to generate
a response using the WS-Adressing with the explicit stated actions other wise is default response
action used as the same as in spring ws impl.
		
		<route>
			<from
				uri="spring-ws:action:http://www.stockquotes.edu/WSAddresingActionReply?output=http://myOuputAction&amp;fault=http://myFaultAction&amp;endpointMapping=#wsaEndpointMapping"
/>
			<to uri="mock:testOutputAndFault" />
		</route>
Fault and ouput are in this patch supported for spring-ws:action, for spring-ws:to action
i will impl. them soon.


In the examples above I am using the wsaEndpointMapping, which is a brand new implementation
of EndpointMapping for action and to préfixes. Impl. is based and extends spring ws addressing
classes to avoid duplicities. Also are supported actors and roles.





<bean id="wsaEndpointMapping"
		class="org.apache.camel.component.spring.ws.bean.WSACamelEndpointMapping">
		<property name="messageSender"> <!-- for replyTo -->
			 <!--here is used only sample in memory sender, but it could be mail for instance or
http sender. 
			 I think at this point should be here a class that manage reply using camel. For example
it would be nice to specify here 
			 <to uri="direct:sendMail"> instead of the raw mail impl. of WebServiceMessageSender.
This needs to be clarified with the comunity.
			 -->
			<bean 
				class="net.javacrumbs.springws.test.helper.InMemoryWebServiceMessageSender" />
		</property>
	</bean>

You can also specify the sender in order to support wsa replyTo. This functionality is still
under the conceptual development and It would be nice to discuss it with you.

Anyway I think the first part of work (consuming) is done and I am looking forward to hear
about your comments.
Tests are essential part of the patch. Documentation will be delivered at the end of impl.
- it depends on our father discussion.

The patch is created against the trunk.

PS: I have created eclipse project using maven but -Psetup.eclipse did not prepare a formatter.
Could you suggest what to do in order to get your code formatter? Thanks.


Your camel's rider,
Andrej
                
> camel-spring-ws - Support for WS-Addressing Action
> --------------------------------------------------
>
>                 Key: CAMEL-5815
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5815
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-spring-ws
>    Affects Versions: 2.11.0
>            Reporter: Andrej Zachar
>            Assignee: Andrej Zachar
>              Labels: patch
>             Fix For: Future
>
>         Attachments: camel-spring-ws-2.11.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The camel spring-ws consumer doesn't currently support the WS-Addressing Action and camel
cannot dispatch such a message properly. There is only one workaround available using a xpath,
which is not a very straight forward solution.
> Based on my previous experience with the patch for attachments and headers I would like
to implement this functionality.
> Please let me know if you have any comments or ideas that are left.
> In the solution I would like to implement a new universal endpoint mapping key:
> action 
> which will act as the same as the key soapaction but it will add also a possibility to
retrieve action from soap wsa:action header instead of current http SOAPAction.
> BTW: Are there any ideas how should be supported wsa:replyTo inside the camel-spring-ws
or how should be supported other attributes of WS-Addressing?
> Cheers,
> Andrej

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message