Use case: User opens a .bpel file containing BPEL 1.0 source code *i.e. based on
BPEL 1.0 xsd)

xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" 
   

Problem - when user runs the Validate XML action user receives the following erorr:

XML validation started.

C:/Documents and
Settings/Mike/TravelReservationService9/TravelReservationService9/src/Test1.0.bpel:2,660
cvc-elt.1: Cannot find the declaration of element 'process'.

1 Error(s),  0 Warning(s).
XML validation finished.

--------------

This is not an appropriate message. This file is a valid BPEL 1.0 file. It
should be validated against the BPEL 1.0 schema as expressed in its namespace
declaration.

The problem is that our Validate XML action is trying to validate the object
model and the object model is based on assumption that user is working with BPEL
2.0 source. Since this is not a valid BPEL 2.0 source, it will not be possible
to create a BPEL 2.0 object model. This is why validation is failing today.
However, I think this is wrong behavior for IDE. Users should be allowed to edit
and validate BPEL 1.0 source code. It is valid XML and the Validate XML should
respect this. Therefore, I believe our current behavior is a defect. Yes, the
user will not be able to edit this BPEL visually. Yes, they will not be able to
deploy this to Sun BPEL SE. But they should be able to edit it at a source code
level and receive expected validation from XML source editor.

Recommendation - IDE should recognize that user is working with BPEL 1.0 source.
The Validate XML action should be adjusted to simply pass the file to the
default validate xml utility. This may require that the action be conditionalized:

if ( isBPEL2() ) {
  // use existing OM based validation story
}
else ( isBPEL1() ) {

 // fall back to standard XML validation story
}


Note: This solution may require that the BPEL 1.0 schema be added to the
NetBeans xsd catalog.