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 80761 - xsd validation fails due to use of import schema in bpel schema and no internnet connection
Summary: xsd validation fails due to use of import schema in bpel schema and no intern...
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Praveen Savur
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-20 21:03 UTC by Ritesh Adval
Modified: 2006-10-01 15:58 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ritesh Adval 2006-07-20 21:03:18 UTC 
testValidationPositive is failing in daily report under bpel project.

This test is failing due to problem in bpel schema validator.
Looks like tests are run on a machine which does not have internet connection. 
In this case it fails to load imported schema

http://www.w3.org/XML/1998/namespace 
in wsbpel_2_0.xsd.


This could be fixed in org.netbeans.modules.xml.xam.spi.XsdBasedValidator by 
getting EntityReslover from subclasses and using local schema for 
http://www.w3.org/XML/1998/namespace. if this not possible due respin of beta2 
then Praveen can fix this by overriding validate or createXMLReader in 
BPELSchemaValidator

The test to look is testValidationPositive.
Comment 1 Ritesh Adval 2006-07-20 22:58:11 UTC 
i have commented this test till it is fixed.
Comment 2 Nam Nguyen 2006-07-21 00:19:16 UTC 
Ritesh, my understanding is that xsd-based jdk validation should first try
resolving based on systemid and relative position.  xsdbased validation works
fine on multi-files with Schema validator.  Please review
XsdBasedValidator.getSource() and its usage in validate method.  Make sure the
ModelSource does provide javax.xml.transform.Source in its lookup.
Comment 3 Praveen Savur 2006-07-21 01:36:55 UTC 
Chris, Nam and me verified that BPEL schema validation fails if there is no
internet connection.

XsdBasedValidator has to be overridden to supply the imported schema file.
Comment 4 Ritesh Adval 2006-07-21 17:57:06 UTC 
Even a better approach would be use catalog in XsdBasedValidator and let 
individual implementation provide a catalog with all their external references 
locally and mapped into catalog.

Or EntityResolver works as well. Let individual implementation provide an 
EntityResolver to resolve external reference like <import> etc.
Comment 5 Praveen Savur 2006-07-21 22:57:34 UTC 
Added EntityResolver in BPELSchemavalidator to supply a bundled xml.xsd file.

Uncommented the unit test commented out earlier by Ritesh.
Comment 6 Mikhail Kondratyev 2006-10-01 15:58:13 UTC 
Tested with a simple scenario when BPEL imports the schema with some unreachable
namespace. Seem to work fine