Created attachment 34549 [details]
loanRequestor.zip

Created attachment 34550 [details]
enb.zip

link to the loan tutorial
http://bookshelf.sfbay.sun.com/jets/JavaStudio/Coke/postbeta/loanprocessing4.htm

This problem is because of bug 85837.  However, the qustion is why the BPEL
module builds successfully?
I change it to P2. But, I still think if there is any problem with the BPEL
module it should come up when the BPEL Module is build.

Ritesh pointed out that this bug has been fixed in 9/25 build. However, the 
bpel project build validation did not pick this error up. 

Ritesh,

Can you evaluate this and assign it to the appropriate module responsible for 
the validation of this error?

Thanks,

When I try to build LoanRequestor project it does fail with errors,
and those are due to importing xsd which are non existent.

<xsd:import namespace="http://xml.netbeans.org/schema/LoanRequestor" 
schemaLocation="../../../../Demo/LoanRequestor/src/LoanRequestor.xsd"/>

See attached.

Though error does not say anything about importing a non existent xsd.

We should fix this in wsdl validation to have a more meaningful error reporting
for this error, it should say 
that "../../../../Demo/LoanRequestor/src/LoanRequestor.xsd" is not found or 
something like that.

Kini,

see if this can be fixed now, this is not a showstopper and can be dealt later 
as well. 

Created attachment 34648 [details]
project did fail to build

My observation is that the validation done from wsdl ui doesnt show the errors,
because it is able to resolve the part element or type. (I mean the wsdlmodel is
able to resolve the part from the correct schema)

When this is run from the ant task, the model is not able to resolve the part
element or type, so it shows the errors.

This needs more evaluation as to what is different between the two ways.

Also the JAXP validator doesnt throw a exception if the schemaLocation cannot be
resolved, so there are no errors relating to invalid schema location. This
occurs in the schema editor too.
I think its better to fix this post FCS.

assigning to model for evaluation, why does model resolve the schema when run
from wsdl editor and why not from the ant task.

Chris,

Any reason for this reassign? Thanks,

User cwebster changed the following:

                What    |Old value                 |New value
===============================================================================
=
             Assigned to|nnguyen                   |issues@enterprise
-------------------------------------------------------------------------------
-
               Component|xml                       |enterprise
-------------------------------------------------------------------------------
-
              QA contact|issues@xml                |issues@enterprise
-------------------------------------------------------------------------------
-
            Subcomponent|wsdl tools                |compapp project
-------------------------------------------------------------------------------
-

The issue is regarding catalog resolution from the build. The issue mentions
that things resolve as expected in the IDE but not from build. 

So, you consider the wsdl with the bad schemaLocation is valid? 

I opened LoanRequestor did a clean build -- no errors, did a ui validation on
LoanRequestor -- no errors

Then I changed the imports for the embedded schema to reference a non existent
LoanRequestor.xsd document. An error was raised when using the validate action,
but no error during build. 

Looks like we are in a loop... Chris, plese see my comments made on 9/27. 

I think this is a bpel project validation issue and assigned it to the bpel 
project. Ritesh think it was a wsdl issue assigned to Kini. Kini assigned to 
xml... and you assigned it back to compapp project. If you think this is a 
bepl build validation error, then assign it to the bpel project, not the 
compapp project.

The reason is same as http://www.netbeans.org/issues/show_bug.cgi?id=84652
The fixes to http://www.netbeans.org/issues/show_bug.cgi?id=84652
 http://www.netbeans.org/issues/show_bug.cgi?id=85179 will fix this issue.

Checked into release55_dev branch

sreenigv, Please update the "Status" and "Target milestone" field, so QE can 
verify the fix. Thanks.

fix for 85179 fixes this.
The change for 85179 looks fine to me.

validation during bpel build is in synch with editor validation. Fixed. Please use
next release build to test. ( Ent pack )

With build 070530 the build of LoanRequestor fails with the following output:

pre-init:
init-private:
init-userdir:
init-user:
init-project:
do-init:
post-init:
init-check:
init-taskdefs:
init:
pre-dist:
D:\sss\LoanRequestor\nbproject\build-impl.xml:155: java.lang.NullPointerException
BUILD FAILED (total time: 0 seconds)

Reproduced. The attached project uses the obsolete namespaces for BPEL, and the validator reports correctly saying it
can not find the element "process". Although, when it tries to build, it gets NPE from the ant task which is defined by
class org.netbeans.modules.bpel.project.anttasks.ValidateBPELProjectTask.
Needs further investigation.

In my last comment I've confused the class name, it's really IDEValidateBPELProject.
Fixed in trunk:
Checking in IDEValidateBPELProject.java;
/cvs/enterprise/bpel/project/antsrc/org/netbeans/modules/bpel/project/anttasks/IDEValidateBPELProject.java,v  <-- 
IDEValidateBPELProject.java
new revision: 1.14; previous revision: 1.13

Close "FIXED" issue against previous releases