You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Je...@cox.com on 2009/03/17 16:30:58 UTC
Tacking messages across several SOAP Request
I have a need to track SOAP request from client across several web service calls as follows:
* Client A request to Server A ( using WS-Addressing I have the MessageID )
* Server A calls Servers B, C, and D.
* Server A aggregates the results and responds to Client A. ( using WS-Addressing I have the ReplyTo )
I have implemented WS-Addressing and I can follow the MessageID in the SOAP header from the Client to the response.
1. How can I track this request in Servers B, C, and D?
2. Can you programmatically set the MessageID or the ReplyTo in the calls to B, C, and D?
a. Is this the right thing to do?
3. Is there an easier way to track a SOAP request across multiple calls?
Thanks in advance,
Jeff
Jeffrey M. Constantin | Cox Communications Inc.
Data Product Services (DPS) | Architecture & Systems Integration (ASI)
Desk: 404-269-3111 | Mobile: 678.643.6528
Re: Tacking messages across several SOAP Request
Posted by Eoghan Glynn <eo...@gmail.com>.
Hi Jeff,
Comments inline ...
> Just for my knowledge, where and by which interceptor method in the
interceptor chain does the MessageId get generated?
> By your comment below, it must be in an interceptor in the PRE_LOGICAL
phase?
Yes, its the WS-A logical interceptor, specifically the class
org.apache.cxf.ws.addressing.MAPAggregator (see
http://svn.apache.org/viewvc/cxf/trunk/rt/ws/addr/src/main/java/org/apache/cxf/ws/addressing/MAPAggregator.java?view=markup
)
> I don't see which interceptors are in each phase and in what order.
> Is there a document that shows all of the interceptors running in each
Phase and each interceptor's responsibility?
Not that I know of in the current docco, but its pretty easy to list the
interceptors associated with each phase by find-grep'ing over the source
tree:
$ find . -name '*.java' | grep -vi test | grep -v PhaseManagerImpl.java |
xargs grep 'Phase\.' | sed 's/\.java.*Phase\./ /' | sed 's/);/ /' | sort +1
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocInInterceptor
INVOKE
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocMessageObserver
INVOKE
./rt/core/src/main/java/org/apache/cxf/interceptor/ServiceInvokerInterceptor
INVOKE
./rt/management/src/main/java/org/apache/cxf/management/interceptor/ResponseTimeMessageInvokerInterceptor
INVOKE
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/DocumentWriterInterceptor
MARSHAL
./rt/bindings/jbi/src/main/java/org/apache/cxf/binding/jbi/interceptor/JBIFaultOutInterceptor
MARSHAL
./rt/bindings/jbi/src/main/java/org/apache/cxf/binding/jbi/interceptor/JBIWrapperOutInterceptor
MARSHAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/RPCOutInterceptor
MARSHAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/Soap11FaultOutInterceptor
MARSHAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/Soap12FaultOutInterceptor
MARSHAL
./rt/bindings/xml/src/main/java/org/apache/cxf/binding/xml/interceptor/XMLFaultOutInterceptor
MARSHAL
./rt/bindings/xml/src/main/java/org/apache/cxf/binding/xml/interceptor/XMLMessageOutInterceptor
MARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/BareOutInterceptor
MARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/WrappedOutInterceptor
MARSHAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/ProviderOutDatabindingInterceptor
MARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/WrappedOutInterceptor
MARSHAL_ENDING
./rt/core/src/main/java/org/apache/cxf/interceptor/OutgoingChainInterceptor
POST_INVOKE
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocOutInterceptor
POST_LOGICAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapActionInterceptor
POST_LOGICAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/WrapperClassInInterceptor
POST_LOGICAL
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/mtom/MTOMPolicyInterceptor
POST_LOGICAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/logical/LogicalHandlerFaultOutInterceptor
POST_MARSHAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/logical/LogicalHandlerOutInterceptor
POST_MARSHAL
./rt/ws/security/src/main/java/org/apache/cxf/ws/security/wss4j/WSS4JOutInterceptor
POST_PROTOCOL
./rt/core/src/main/java/org/apache/cxf/interceptor/StaxInInterceptor
POST_STREAM
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/PolicyVerificationOutInterceptor
POST_STREAM
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocInFaultObserver
PRE_INVOKE
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocOutInterceptor
PRE_INVOKE
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/HolderInInterceptor
PRE_INVOKE
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/SwAInInterceptor
PRE_INVOKE
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/PolicyVerificationInFaultInterceptor
PRE_INVOKE
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/PolicyVerificationInInterceptor
PRE_INVOKE
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/WebFaultInInterceptor
PRE_LOGICAL
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/DatabindingOutSetupInterceptor
PRE_LOGICAL
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/DatabindingOutSetupInterceptor
PRE_LOGICAL
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/DatabindingOutSetupInterceptor
PRE_LOGICAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/HolderOutInterceptor
PRE_LOGICAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/SwAOutInterceptor
PRE_LOGICAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/WrapperClassOutInterceptor
PRE_LOGICAL
./rt/ws/addr/src/main/java/org/apache/cxf/ws/addressing/MAPAggregator
PRE_LOGICAL
./rt/ws/rm/src/main/java/org/apache/cxf/ws/rm/AbstractRMInterceptor
PRE_LOGICAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/logical/LogicalHandlerFaultOutInterceptor
PRE_MARSHAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/logical/LogicalHandlerOutInterceptor
PRE_MARSHAL
./distribution/src/main/release/samples/colocated/src/demo/colocated/common/ThrowFaultInterceptor
PREPARE_SEND
./distribution/src/main/release/samples/ws_rm/src/demo/ws_rm/common/MessageLossSimulator
PREPARE_SEND
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/ContentTypeOutInterceptor
PREPARE_SEND
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/URIParameterOutInterceptor
PREPARE_SEND
./rt/core/src/main/java/org/apache/cxf/interceptor/MessageSenderInterceptor
PREPARE_SEND
./rt/core/src/main/java/org/apache/cxf/interceptor/MessageSenderInterceptor
PREPARE_SEND_ENDING
./rt/bindings/jbi/src/main/java/org/apache/cxf/binding/jbi/interceptor/JBIOperationInInterceptor
PRE_PROTOCOL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/MustUnderstandInterceptor
PRE_PROTOCOL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/saaj/SAAJInInterceptor
PRE_PROTOCOL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/saaj/SAAJOutInterceptor
PRE_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/logical/LogicalHandlerFaultInInterceptor
PRE_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/logical/LogicalHandlerInInterceptor
PRE_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/soap/SOAPHandlerFaultInInterceptor
PRE_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/soap/SOAPHandlerFaultOutInterceptor
PRE_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/soap/SOAPHandlerInterceptor
PRE_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/WebFaultOutInterceptor
PRE_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/support/JaxWsServiceFactoryBean
PRE_PROTOCOL
./rt/ws/addr/src/main/java/org/apache/cxf/ws/addressing/soap/MAPCodec
PRE_PROTOCOL
./rt/ws/rm/src/main/java/org/apache/cxf/ws/rm/soap/RMSoapInterceptor
PRE_PROTOCOL
./rt/ws/security/src/main/java/org/apache/cxf/ws/security/wss4j/WSS4JInInterceptor
PRE_PROTOCOL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/saaj/SAAJOutInterceptor
PRE_PROTOCOL_ENDING
./distribution/src/main/release/samples/streamInterceptor/src/demo/stream/interceptor/StreamInterceptor
PRE_STREAM
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/DispatchInterceptor
PRE_STREAM
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapPreProtocolOutInterceptor
PRE_STREAM
./rt/core/src/main/java/org/apache/cxf/interceptor/AttachmentOutInterceptor
PRE_STREAM
./rt/core/src/main/java/org/apache/cxf/interceptor/LoggingOutInterceptor
PRE_STREAM
./rt/core/src/main/java/org/apache/cxf/interceptor/StaxOutInterceptor
PRE_STREAM
./rt/ws/rm/src/main/java/org/apache/cxf/ws/rm/RetransmissionInterceptor
PRE_STREAM
./rt/core/src/main/java/org/apache/cxf/interceptor/AttachmentOutInterceptor
PRE_STREAM_ENDING
./rt/core/src/main/java/org/apache/cxf/interceptor/StaxOutInterceptor
PRE_STREAM_ENDING
./rt/bindings/object/src/main/java/org/apache/cxf/binding/object/ObjectDispatchInInterceptor
READ
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/EndpointSelectionInterceptor
READ
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/ReadHeadersInterceptor
READ
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/DispatchInInterceptor
READ
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/DatabindingInSetupInterceptor
RECEIVE
./rt/core/src/main/java/org/apache/cxf/interceptor/AttachmentInInterceptor
RECEIVE
./rt/core/src/main/java/org/apache/cxf/interceptor/LoggingInInterceptor
RECEIVE
./rt/management/src/main/java/org/apache/cxf/management/interceptor/ResponseTimeMessageInInterceptor
RECEIVE
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/ClientPolicyInFaultInterceptor
RECEIVE
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/ClientPolicyInInterceptor
RECEIVE
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/ServerPolicyInInterceptor
RECEIVE
./rt/management/src/main/java/org/apache/cxf/management/interceptor/ResponseTimeMessageOutInterceptor
SEND
./rt/bindings/object/src/main/java/org/apache/cxf/binding/object/ObjectDispatchOutInterceptor
SETUP
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/ClientPolicyOutInterceptor
SETUP
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/ServerPolicyOutFaultInterceptor
SETUP
./rt/ws/policy/src/main/java/org/apache/cxf/ws/policy/ServerPolicyOutInterceptor
SETUP
./rt/bindings/http/src/main/java/org/apache/cxf/binding/http/interceptor/URIParameterInInterceptor
UNMARSHAL
./rt/bindings/jbi/src/main/java/org/apache/cxf/binding/jbi/interceptor/JBIFaultInInterceptor
UNMARSHAL
./rt/bindings/jbi/src/main/java/org/apache/cxf/binding/jbi/interceptor/JBIWrapperInInterceptor
UNMARSHAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/RPCInInterceptor
UNMARSHAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/Soap11FaultInInterceptor
UNMARSHAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/Soap12FaultInInterceptor
UNMARSHAL
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapHeaderInterceptor
UNMARSHAL
./rt/bindings/xml/src/main/java/org/apache/cxf/binding/xml/interceptor/XMLFaultInInterceptor
UNMARSHAL
./rt/bindings/xml/src/main/java/org/apache/cxf/binding/xml/interceptor/XMLMessageInInterceptor
UNMARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/BareInInterceptor
UNMARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/ClientFaultConverter
UNMARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/DocLiteralInInterceptor
UNMARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/URIMappingInterceptor
UNMARSHAL
./rt/core/src/main/java/org/apache/cxf/interceptor/WrappedInInterceptor
UNMARSHAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/ProviderInDatabindingInterceptor
UNMARSHAL
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocInInterceptor
USER_LOGICAL
./rt/bindings/coloc/src/main/java/org/apache/cxf/binding/coloc/ColocOutFaultObserver
USER_LOGICAL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/AbstractProtocolHandlerInterceptor
USER_PROTOCOL
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/soap/SOAPHandlerFaultOutInterceptor
USER_PROTOCOL) {
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/soap/SOAPHandlerInterceptor
USER_PROTOCOL) {
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapOutInterceptor
WRITE
./rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/interceptors/DispatchOutInterceptor
WRITE
./rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapOutInterceptor
WRITE_ENDING
RE: Tacking messages across several SOAP Request
Posted by Je...@cox.com.
Good information. Thanks Eoghan.
In my case I will be setting the MessageId in the application layer and this is working great.
Just for my knowledge, where and by which interceptor method in the interceptor chain does the MessageId get generated?
By your comment below, it must be in an interceptor in the PRE_LOGICAL phase?
I am new to CXF. In the CXF documentation I see the ordered list of inbound and outbound Phases but I don't see which interceptors are in each phase and in what order. Is there a document that shows all of the interceptors running in each Phase and each interceptor's responsibility?
Thanks,
Jeff
________________________________
From: Eoghan Glynn [mailto:eoglynn@gmail.com]
Sent: Wednesday, March 18, 2009 11:51 AM
To: users@cxf.apache.org; Constantin, Jeffrey (CCI-Atlanta)
Cc: ulhas.bhole@progress.com
Subject: Re: Tacking messages across several SOAP Request
If using the WS-Addressing headers, just make sure you set this messageID in the AddressingProperties in the request context before the WS-A MAPAggregator interceptor is traversed.
So no problem doing it in the application layer (as per the the ws_a demo). But if you're setting it in an interceptor, make sure this runs in a phase prior to PRE_LOGICAL, or use the PhaseInterceptor.addBefore() mechanism if running in the same phase.
>From the point of view of ID uniqueness, CXF just fabricates a URN with the unique material being provided by java.util.UUID.randomUUID().
Cheers,
Eoghan
2009/3/18 <Je...@cox.com>>
Now I just have to determine when to set this MesssageID and how to ensure it is unique. More fun for me.
Re: Tacking messages across several SOAP Request
Posted by Eoghan Glynn <eo...@gmail.com>.
If using the WS-Addressing headers, just make sure you set this messageID in
the AddressingProperties in the request context *before* the WS-A
MAPAggregator interceptor is traversed.
So no problem doing it in the application layer (as per the the ws_a demo).
But if you're setting it in an interceptor, make sure this runs in a phase
prior to PRE_LOGICAL, or use the PhaseInterceptor.addBefore() mechanism if
running in the same phase.
>From the point of view of ID uniqueness, CXF just fabricates a URN with the
unique material being provided by java.util.UUID.randomUUID().
Cheers,
Eoghan
2009/3/18 <Je...@cox.com>
> Now I just have to determine when to set this MesssageID and how to ensure
> it is unique. More fun for me.
>
>
RE: Tacking messages across several SOAP Request
Posted by Je...@cox.com.
Looks like this will do it: ( modified from the WS-Addressing example in CXF 2.1.3 samples )
final ApplicationContext context =
new ClassPathXmlApplicationContext( "/clientAppContext.xml" );
final JaxWsProxyFactoryBean factory =
( JaxWsProxyFactoryBean ) context.getBean( "clientFactory" );
final Client client = factory.getClientFactoryBean( ).create( );
// get Message Addressing Properties instance
final AddressingBuilder builder =
AddressingBuilder.getAddressingBuilder( );
final AddressingProperties maps =
builder.newAddressingProperties( );
// set MessageID property
final AttributedURIType messageID = new AttributedURIType( );
messageID.setValue( "urn:uuid:" + "TRANSACTION_ID" );
maps.setMessageID( messageID );
// associate MAPs with request context
final Map<String, Object> requestContext =
client.getRequestContext( );
requestContext.put(
CLIENT_ADDRESSING_PROPERTIES,
maps );
Thanks for the input and suggestions. I guess did not look *close* enough at the CXF 2.1.3 WS-Addressing sample code. (see "explicitPropagation" method in the Client.java)
Now I just have to determine when to set this MesssageID and how to ensure it is unique. More fun for me.
The server will have to access this MessageID in the inbound SOAP messages and include it in any transaction logging but I am guessing I can write an interceptor to handle this task.
Thanks to all,
Jeff
-----Original Message-----
From: Ulhas Bhole [mailto:ulhas.bhole@progress.com]
Sent: Wednesday, March 18, 2009 8:51 AM
To: users@cxf.apache.org
Subject: Re: Tacking messages across several SOAP Request
Can adding out-of-band SOAP Header in message be of any help to you?
Which will allow you to set the ID as well as read it from SOAP Message?
But this will involve writing some code though.
If you want to take a look at how the SOAP out-of-band header works you
can have a look at test case here.
http://svn.eu.apache.org/repos/asf/cxf/branches/2.1.x-fixes/systests/src/test/java/org/apache/cxf/systest/outofband/header/
Regards,
Ulhas
Jeffrey.Constantin@cox.com wrote:
> I will talk to our design team about a lightweight workflow system. I really want a unique transactionID generated by the client to follow the SOAP calls throughout our backend provisioning systems. I just don't know how to embed it in the SOAP message. We had an XML over HTTP architecture and we embedded a transactionID in *every* XML schema we passed around. I could add a transactionID to *every* SOAP call but that is not a good solution. I really want it outside of the content.
>
> I could use the MessageID in WS-Addressing if I can set it programmatically but I have not found a way to intercept the MessageID creation. I can read it before it goes out but I don't see how to set it prior to sending the SOAP message. Is this possible?
>
> Thanks for the ideas,
>
> jeff
>
> -----Original Message-----
> From: Bryan Kearney [mailto:bkearney@redhat.com]
> Sent: Tuesday, March 17, 2009 4:32 PM
> To: users@cxf.apache.org
> Subject: Re: Tacking messages across several SOAP Request
>
> Jeffrey.Constantin@cox.com wrote:
>
>> Thanks Andrew.
>>
>> I am attempting to do this without a "home-grown" solution. If this can be done using WS-Addressing or some other well-known method I will be happy. As a last resort I will be writing something like you did.
>>
>> Thanks,
>>
>> Jeff
>>
>
> Can you use a light weigh orchestration/workflow system? This seems to
> be what BPEL was designed for.
>
> -- bk
>
>
>
>
Re: Tacking messages across several SOAP Request
Posted by Ulhas Bhole <ul...@progress.com>.
Can adding out-of-band SOAP Header in message be of any help to you?
Which will allow you to set the ID as well as read it from SOAP Message?
But this will involve writing some code though.
If you want to take a look at how the SOAP out-of-band header works you
can have a look at test case here.
http://svn.eu.apache.org/repos/asf/cxf/branches/2.1.x-fixes/systests/src/test/java/org/apache/cxf/systest/outofband/header/
Regards,
Ulhas
Jeffrey.Constantin@cox.com wrote:
> I will talk to our design team about a lightweight workflow system. I really want a unique transactionID generated by the client to follow the SOAP calls throughout our backend provisioning systems. I just don't know how to embed it in the SOAP message. We had an XML over HTTP architecture and we embedded a transactionID in *every* XML schema we passed around. I could add a transactionID to *every* SOAP call but that is not a good solution. I really want it outside of the content.
>
> I could use the MessageID in WS-Addressing if I can set it programmatically but I have not found a way to intercept the MessageID creation. I can read it before it goes out but I don't see how to set it prior to sending the SOAP message. Is this possible?
>
> Thanks for the ideas,
>
> jeff
>
> -----Original Message-----
> From: Bryan Kearney [mailto:bkearney@redhat.com]
> Sent: Tuesday, March 17, 2009 4:32 PM
> To: users@cxf.apache.org
> Subject: Re: Tacking messages across several SOAP Request
>
> Jeffrey.Constantin@cox.com wrote:
>
>> Thanks Andrew.
>>
>> I am attempting to do this without a "home-grown" solution. If this can be done using WS-Addressing or some other well-known method I will be happy. As a last resort I will be writing something like you did.
>>
>> Thanks,
>>
>> Jeff
>>
>
> Can you use a light weigh orchestration/workflow system? This seems to
> be what BPEL was designed for.
>
> -- bk
>
>
>
>
RE: Tacking messages across several SOAP Request
Posted by Je...@cox.com.
I will talk to our design team about a lightweight workflow system. I really want a unique transactionID generated by the client to follow the SOAP calls throughout our backend provisioning systems. I just don't know how to embed it in the SOAP message. We had an XML over HTTP architecture and we embedded a transactionID in *every* XML schema we passed around. I could add a transactionID to *every* SOAP call but that is not a good solution. I really want it outside of the content.
I could use the MessageID in WS-Addressing if I can set it programmatically but I have not found a way to intercept the MessageID creation. I can read it before it goes out but I don't see how to set it prior to sending the SOAP message. Is this possible?
Thanks for the ideas,
jeff
-----Original Message-----
From: Bryan Kearney [mailto:bkearney@redhat.com]
Sent: Tuesday, March 17, 2009 4:32 PM
To: users@cxf.apache.org
Subject: Re: Tacking messages across several SOAP Request
Jeffrey.Constantin@cox.com wrote:
> Thanks Andrew.
>
> I am attempting to do this without a "home-grown" solution. If this can be done using WS-Addressing or some other well-known method I will be happy. As a last resort I will be writing something like you did.
>
> Thanks,
>
> Jeff
Can you use a light weigh orchestration/workflow system? This seems to
be what BPEL was designed for.
-- bk
Re: Tacking messages across several SOAP Request
Posted by Bryan Kearney <bk...@redhat.com>.
Jeffrey.Constantin@cox.com wrote:
> Thanks Andrew.
>
> I am attempting to do this without a "home-grown" solution. If this can be done using WS-Addressing or some other well-known method I will be happy. As a last resort I will be writing something like you did.
>
> Thanks,
>
> Jeff
Can you use a light weigh orchestration/workflow system? This seems to
be what BPEL was designed for.
-- bk
RE: Tacking messages across several SOAP Request
Posted by Je...@cox.com.
Thanks Andrew.
I am attempting to do this without a "home-grown" solution. If this can be done using WS-Addressing or some other well-known method I will be happy. As a last resort I will be writing something like you did.
Thanks,
Jeff
-----Original Message-----
From: andrew.clegg@gmail.com [mailto:andrew.clegg@gmail.com] On Behalf Of Andrew Clegg
Sent: Tuesday, March 17, 2009 11:48 AM
To: users@cxf.apache.org
Subject: Re: Tacking messages across several SOAP Request
2009/3/17 <Je...@cox.com>:
> a. Is this the right thing to do?
> 3. Is there an easier way to track a SOAP request across multiple calls?
I've built a system with a very similar topology to this without using
WS-Addressing: http://funcnet.eu/
When the front-end server receives a request, it generates a unique ID
for it and returns that to the user immediately. It also creates a
database record for the session which contains the job ID, user's
email address and some metadata.
It then calls each of the prediction services synchronously but in
parallel, using a separate thread for each one. As each one returns,
the front-end stores the results in the database, and when the last
one returns, it sets a 'COMPLETE' flag in the database.
The user gets MonitorJob (get current status), CancelJob and
RetrieveScores operations -- obviously the latter results in an error
unless the job is COMPLETE.
Whether this is easier than using WS-A or not, I dunno :-)
Andrew.
--
:: http://biotext.org.uk/ ::
Re: Tacking messages across several SOAP Request
Posted by Andrew Clegg <an...@nervechannel.com>.
2009/3/17 <Je...@cox.com>:
> a. Is this the right thing to do?
> 3. Is there an easier way to track a SOAP request across multiple calls?
I've built a system with a very similar topology to this without using
WS-Addressing: http://funcnet.eu/
When the front-end server receives a request, it generates a unique ID
for it and returns that to the user immediately. It also creates a
database record for the session which contains the job ID, user's
email address and some metadata.
It then calls each of the prediction services synchronously but in
parallel, using a separate thread for each one. As each one returns,
the front-end stores the results in the database, and when the last
one returns, it sets a 'COMPLETE' flag in the database.
The user gets MonitorJob (get current status), CancelJob and
RetrieveScores operations -- obviously the latter results in an error
unless the job is COMPLETE.
Whether this is easier than using WS-A or not, I dunno :-)
Andrew.
--
:: http://biotext.org.uk/ ::