Guillaume Nodet schrieb: > On 3/19/07, Björn Hagemeier <[EMAIL PROTECTED]> wrote: >> >> Hi Guillaume, >> >> Guillaume Nodet schrieb: >> > What do you mean exactly ? >> on the client side I do a http POST to send a message. http-consumer is >> configured to use a custom marshaler (see below). It passes the message >> on to another component, which sends a reply as well. However, this >> reply never gets back to the client. None of the sendXXX methods on the >> marshaler are ever called. If I'm not mistaken, they should be and the >> client should also receive a message in response. > > > Did you configure your marshaler so that the exchange created is > an InOut ? If you send an InOnly, there is no response, so that the > marshaler won't be used. > > Just to let you know about the background: >> I tried this in order to avoid routing of messages based on >> WS-Addressing header inside incoming SOAP messages. If there's another >> way of getting around this and route different WS-Addressing Actions to >> the same component, I'd be more than happy to follow that path. Let me >> know if there's an easy way to ignore WS-Addressing headers in SOAP >> messages. > > > Yeah, you can do something like the following: > <http:endpoint> > <http:policies /> > </http:endpoint> I think I tried that before. But maybe I got something wrong that time. Thank you so much. > > The default list of policies contains the AddressingHandler, > but the previous snippet will disable it. > > The WSRF spec. requires different wsa:Action for different >> message exchanges. wsa:Action is mapped to interfaces by ServiceMix. > > > I guess we need to improve ServiceMix to easily support WS-RF. > Keep us informed, if there are other points that need to be improved > or if you have any success :-) I was thinking of a generic WSRF component that could be configured with specific data models for deployment. I'll have to see, how this works out. > > Could a single component support multiple interfaces? If so, how? > > > Yeah, but not with WSDL 1.1. However WSDL 2.0 support interface > inheritance. May be worth looking into.
Björn > > Kind regards, >> >> Björn >> >> >> ######### Activation spec for http-consumer using custom marshaler ##### >> >> <sm:activationSpec> >> <sm:component> >> <http:component> >> <http:endpoints> >> <http:consumer service="aware-test:http" endpoint="http" >> id="http" >> locationURI="http://localhost:8192/services/ASB"; >> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; >> targetService="aware-test:wsrf"> >> <marshaler> >> <bean id="HttpWSRFSoapConsumerMarshaler" >> class="org.aware.test.component.HttpWSRFSoapConsumerMarshaler" /> >> </marshaler> >> </http:consumer> >> </http:endpoints> >> </http:component> >> </sm:component> >> </sm:activationSpec> >> > This work is still in progress, but the consumer side should work. >> > >> > On 3/19/07, Björn Hagemeier <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi there, >> >> >> >> I implemented a HttpConsumerMarshaler and use it with the >> http-consumer >> >> component. The createExchange method of the marshaler is used as >> >> expected, however the sendOut and other sendXXX methods are not. Does >> >> anyone have any idea about why this may be? Do I have to do more than >> >> implementing the interface and set it as a marshaler for the consumer >> >> component? >> >> >> >> >> >> Kind regards, >> >> >> >> Björn -- Björn Hagemeier Division "Distributed Systems and Grid Computing" Central Institute for Applied Mathematics Forschungszentrum Jülich GmbH D-52425 Jülich Germany +49 2461 61 1584 +49 2461 61 6656 [EMAIL PROTECTED] Skype: bhagemeier
