Eclipse Community Forums: BPEL Designer » pattern attribute of correlation implicitly always set

Home » Modeling » BPEL Designer » pattern attribute of correlation implicitly always set(How to check then the explicit usage of "pattern"?)

pattern attribute of correlation implicitly always set [message #647627]

Fri, 07 January 2011 08:15

Eclipse User

As always, this is a question to the developers

SA00046 of App. B in the BPEL spec asks to check whether the pattern attribute of a correlation is set in some cases. As it points out, the pattern attribute is implicitly ALWAYS set in the model of the process. Thus, asking for correlation.getPattern() == null is useless (the value of pattern is always request, as long as not explicitly set to response or requestresponse).

So I'm keen on the answer how to check then whether the correlation uses the attribute.
The BPEL Validator uses an own model, I know. But I'm committed to the task to develop another validator, just if you ask.

[Updated on: Fri, 07 January 2011 12:53] by Moderator

Re: pattern attribute of correlation implicitly always set [message #647690 is a reply to message #647627]

Fri, 07 January 2011 13:52

Eclipse User

Hi Christoph,

I'm not sure if you are asking about the interpretation of SA00046 or about how the BPEL Designer's validator handles this validation rule.

Re: pattern attribute of correlation implicitly always set [message #648105 is a reply to message #647627]

Tue, 11 January 2011 04:10

Eclipse User

Hi Bob,

I know how the BPEL validator handles this rule, but I cannot go the same way (building an own tree of the process and using this for validation).

SA00046 says that one MUST NOT use the pattern attribute if the invoked operation is one-way. But since the attribute is always implicitly set, I cannot programmatically decide, whether the attribute is used or not. I wonder whether this (implicitly set attribute) is a violation of the specification.

[Updated on: Tue, 11 January 2011 04:10] by Moderator

Re: pattern attribute of correlation implicitly always set [message #648643 is a reply to message #648105]

Thu, 13 January 2011 13:39

Eclipse User

Ah, I think I understand what you're saying now: you are suggesting that the CorrelationImpl class should NOT be initializing the pattern attribute to "request" on construction and should simply leave it as null, right? You probably have a point here, but I would have to see what, if anything, is affected by a change like this.

Can you please file a bugzilla here so that we can track this?

Thanks!
Bob

Re: pattern attribute of correlation implicitly always set [message #648752 is a reply to message #648643]

Fri, 14 January 2011 07:18

Eclipse User

Yes. I suggest not to initialize the pattern attribute.

Bug filed.

Previous Topic:	Missing attribute in EMF model for FROM element
Next Topic:	Link to CVS on developer page broken

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 06 07:30:03 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter