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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

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

Subject: Re: [ebxml-dev] re BPSS: how can I identify DocumentEnvelopefromreceivedmessage


Thank you for your reply!

I did't know the specificationElement attribute of BusinessDocument ... 
Ah, It is in the class diagram on page 22! (I'm reading 1.04 draft - I 
understand it is wip) I couldn't find any description for 
specificationElement, even on page 59 (the specificationID attribute is 
missing in BusinessDocument class in the diagram, too). Coudld you tell 
me what should I specify in specificationElement?

If it points to message schema (I'm not sure because there is 
specificationLocation attribute), I have to validate the received 
message against all possible schemas to identify DocumentEnvelope. This 
sounds like a costly implementation. It would be lightweight if I could 
use some short identifier I can get without parsing the payload.

If it is an identifier, question remains: in which MSH information I can 
find the identifier?

Sorry if I missed something in other related ebXML specs.

Kenji Nagahashi

> DocumentEnvelope references the BusinessDocument
> which points to a specificationElement.
> Based on the specificationElement in the document received
> over the messaging layer, this identifies the DocumentEnvelope
> corresponding to isPositiveResponse=false
> You could use the conditionExpression in the BusinessDocument, if for 
>  same Schema is used for different BusinessDocuments but
> based on the conditionExpression, like presence or absence
> of a specific Element, they derive different DocumentEnvelopes.
> -hima
> nagahashi@jp.fujitsu.com wrote:
> > Hi
> >
> > I have a (possibly silly) question about BPSS. Anybody has 
> > this problem? Could anybody give me an answer to it?
> > ----
> > Please assume I'm developing ebXML gateway which is configurable 
> > BPSS and do some business process management staff for me.
> >
> > BusinessTransaction/RespondingActivity can have more than one
> > DocumentEnvelope. If the gateway receives a message for 
> > with isPositiveResponse="false", the BusinessTransaction must fail.
> > In order to determine completion state of a BusinessTransaction, the
> > gateway must identify which DocumentEnvelope it received.
> >
> > Question is, which information from BPSS gives me a key to identify
> > DocumentEnvelope? Transport (ebMS) can pass many information up to 
> > manager. Which of them are used to identify DocumentEnvelope and 
> > is it specified in the BPSS? This is so important that there should 
> > some 'standard' way.
> >
> > I found that BusinessDocument has conditionExpression. BPSS spec 
> > this conditionExpression "determines whether this is a valid 
> > document for its envelope." Is this it?
> >
> > Thanks in advance
> >
> > Kenji Nagahashi
> >
> > ----------------------------------------------------------------
> > The ebxml-dev list is sponsored by OASIS.
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.ebxml.org/ob/adm.pl>
> ----------------------------------------------------------------
> The ebxml-dev list is sponsored by OASIS.
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.ebxml.org/ob/adm.pl>

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC