This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 81034 - validation problem in bpel
Summary: validation problem in bpel
Status: VERIFIED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-25 04:28 UTC by Ritesh Adval
Modified: 2007-08-15 19:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
bpel (3.41 KB, application/octet-stream)
2006-07-25 04:30 UTC, Ritesh Adval
Details
wsdl (5.05 KB, application/octet-stream)
2006-07-25 04:30 UTC, Ritesh Adval
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ritesh Adval 2006-07-25 04:28:46 UTC
Getting following error see attached bpel:

C:\Documents and Settings\radval\BpelModule4
\src\correlation\CorrelationOnMessageN5.bpel:33: column:12 ERROR: A "start 
activity" is a <receive> or <pick> activity that is annotated with a 
createInstance="yes" attribute. Activities other than the following: start 
activities, <scope>, <flow>, <sequence>, and <empty> MUST NOT be performed 
prior to or simultaneously with start activities.

The bpel has flow as start activity which has <pick> as one of parallel activity
so there is a <pick> and we need to do above check inside <flow> as well
and allow <flow> to be start activity.
Comment 1 Ritesh Adval 2006-07-25 04:30:14 UTC
Created attachment 32165 [details]
bpel
Comment 2 Ritesh Adval 2006-07-25 04:30:28 UTC
Created attachment 32166 [details]
wsdl
Comment 3 Ritesh Adval 2006-07-25 04:31:06 UTC
This is failing the build in a bpel project.
Comment 4 Michael Frisino 2006-07-25 07:53:47 UTC
Adding to Ritesh comment. Not just flow, but all the "allowed" activities need
to be handled similarly - i.e. check inside the allowed activity for the
presence of one of the mandatory activities. 

i.e. you need a mandatory "start" actitivity (receive or pick with create
instance = yes) INSIDE an allowed actitity (<scope>, <flow>, <sequence> )

AND algorithm must disregard <empty> activities as irrelevant to this order.
Comment 5 Denis Anisimov 2006-07-25 11:41:25 UTC
May be I'm wrong , but please see at this example ( just part from example ):  
     <flow>
            <pick createInstance="yes">
                <onMessage partnerLink="OneWayLink"
                           portType="ns0:correlationOnMessageFirstN5PortType1"
                           operation="correlationOnMessageFirstN5Operation1"
                           variable="correlationOnMessageFirstN5Operation1_Output">
                    <correlations>
                        <correlation set="corrSetN"
                                     initiate="yes"/>
                    </correlations>
                    <empty />
                </onMessage>
            </pick>
            <receive name="correlationOnMessageFirstN5Operation"
                     partnerLink="TwoWayLink"
                     portType="ns0:correlationOnMessageFirstN5PortType"
                     operation="correlationOnMessageFirstN5Operation"
                     variable="correlationOnMessageFirstN5Operation_Output">
                <correlations>
                    <correlation set="corrSetN"/>
                </correlations>
            </receive>
        </flow>

In this case flow have two activities : pick and receive.
Pick have createInstance set to "yes" BUT receive don't have this attribute.
It means that pick and receive will be performed simultaneously but
receive is not START ACTIVITY.

Here is the specification rule :
A "start activity" is a <receive> or <pick> activity that is 
annotated with a createInstance="yes" attribute. 
Activities other than the following: start activities, <scope>, 
<flow>, <sequence>, and <empty> MUST NOT be performed prior to 
or simultaneously with start activities.
Comment 6 _ hong_lin 2007-08-15 19:53:01 UTC
Close INVALID issue against previous releases