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 76443 - BPEL source is not valid
Summary: BPEL source is not valid
Status: VERIFIED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Michael Frisino
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-16 16:33 UTC by Alexander Pepin
Modified: 2006-08-31 02:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Pepin 2006-05-16 16:33:45 UTC
Steps to reproduce:
- create a new BPEL module project
- open BPEL for editing
- drag IF activity from palette to the diagram
- drag SEQUENCE activity into the IF 
- switch to source view
- right-click on source code and choose Validate XML from the context menu
Result: Validating finished with errors. One of them is: Invalid content was
found starting with element 'sequence'. One of (:then) is expected.

Obviously the source does not match bundled wsbpel_2_0.xsd schema or bundled
schema is obsolete.
Comment 1 _ hong_lin 2006-06-22 22:11:47 UTC
move this bug to "enterprise" component
Comment 2 Michael Frisino 2006-07-16 21:21:28 UTC

One of the new features is eager / automatic validation and error reporting.
This means that as the user develops or modifies a BPEL process they will be
informed of invalid (warning and error) conditions in their process.

It is perfectly natural that a process will contain many invalid elements during
the design phase. The IDE cannot create completely valid BPEL for the user at
every single moment. There are intermediary stages where things are invalid
until the user initiates the remining design steps. This is no different than
other programming models where the IDE does what it can, but it must await user
input on anything that truly program specific.

Therefore, this is not a bug if the validation message is correct.

It is only a bug if the validation is incorrect.
Comment 3 Alexander Pepin 2006-07-27 15:10:08 UTC
verified in build 060725