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.
Summary: | xsd validation fails due to use of import schema in bpel schema and no internnet connection | ||
---|---|---|---|
Product: | soa | Reporter: | Ritesh Adval <radval> |
Component: | BPEL Project | Assignee: | Praveen Savur <praveensavur> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | praveensavur |
Priority: | P1 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Ritesh Adval
2006-07-20 21:03:18 UTC
i have commented this test till it is fixed. 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. 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. 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. Added EntityResolver in BPELSchemavalidator to supply a bundled xml.xsd file. Uncommented the unit test commented out earlier by Ritesh. Tested with a simple scenario when BPEL imports the schema with some unreachable namespace. Seem to work fine |