OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: WS-CAF Article


Hi Eric,

	Are we looking to add a separate namespaces each child context?

Regards,
Krishna

-----Original Message-----
From: Newcomer, Eric [mailto:Eric.Newcomer@iona.com] 
Sent: Monday, January 05, 2004 4:59 AM
To: krishna@inventicasystems.com
Subject: RE: WS-CAF Article

Hi Krishna,

That's a good point, right now it's kind of the entire context, or a
subset that doesn't have the "must understand" attribute defined for it.
Maybe each child should have a separate namespace.

Eric

-----Original Message-----
From: krishna@inventicasystems.com [mailto:krishna@inventicasystems.com]
Sent: Monday, January 05, 2004 1:21 AM
To: Newcomer, Eric
Subject: WS-CAF Article


Hi Eric,

    I was going through the WS-CAF article you wrote on webservices.org.
First I appreciate you for writing such a great article. Secondly, I
have some questions:

In your example, once the user is authenticated or logged in, WS-CTX
adds <AuthToken> to <child-context>. If you are going through WS-BPEL
flow how would you relate each WS in the flow to each of the
child-contexts? Do we need to put all the <child-contexts> in the same
sequence as the BPEL flow? In order to be able to use the information
WS-CTX has collected at the first step (ex: user authentication), I
think there should be a relation that needs to be stablished in some way
between the WS and the <child-context> it is reffering to. But from what
I see, <child-context>s do not have any names associated with them. 

Regards,
Krishna



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]