It looks like using "header" instead of "property" enables the solution to work (which I suspect you maybe had meant).
Thanks for pointing me in the right direction! jeff On Mon, Nov 17, 2008 at 7:40 PM, Jeff Davis <[EMAIL PROTECTED]> wrote: > Hey Ruwan, > > I'm not entirely sure I follow. Let me describe what I've done. Inside an > iterate mediator, I tried something like (just hard-coding the values for > now, to keep things simple): > > <property name="Action" value="test" /> > <property name="To" value="http://localhost:8280/soap/TestStub"/> > <send> > <endpoint> > <!-- this calls the default, but the addressing doesn't include > the action or to --> > <address uri="http://localhost:8280/";> > <enableAddressing/> > </address> > </endpoint> > </send> > > In the synapse default scope, I have: > > <in> > <log level="custom"> > <property name="Text" value="In Default Sequence"/> > </log> > <send/> > </in> > > It hits the default, but just loops forever and never hits the TestStub > proxy, I presume because the WS-Addressing isn't including the Action or To > property values that I set. > > Maybe it's because I'm setting the property values inside of an iterator? > > jeff > > > On Mon, Nov 17, 2008 at 6:33 PM, Ruwan Linton <[EMAIL PROTECTED]>wrote: > >> Hi Jeff, >> >> You could use the property mediator under the synapse (default) scope to >> achieve this, because SOAPAction has been treated as a special case. >> >> <property name="Action" expression="......"/> >> >> You can do the same for the Endpoint URL, which is to use the property >> mediator set the To value and use the default send mediator as follows; >> >> <property name="To" expression="......"/> >> <send/> >> >> This will solve your problem, I guess. >> >> Thanks, >> Rwuan >> >> On Tue, Nov 18, 2008 at 6:11 AM, Jeff Davis <[EMAIL PROTECTED]> wrote: >> >> > Hi, >> > I'm creating a distributor style service that will receive an inbound >> > request and then, depending upon data within the XML, will forward it to >> a >> > given service. As part of this, I need to dynamically assign both the >> > soapAction and endpoint URL. Is this doable? >> > >> > I tried setting soapAction as a transport-scope property, but it never >> gets >> > set (it seems the only way to set it is through the soapAction attribute >> > associated with the target element, but this doesn't appear to allow for >> > expressions). >> > >> > Thanks in advance! >> > >> > jeff >> > >> >> >> >> -- >> Ruwan Linton >> http://wso2.org - "Oxygenating the Web Services Platform" >> http://ruwansblog.blogspot.com/ >> > >
