You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Grant McDonald (JIRA)" <ji...@apache.org> on 2006/08/06 05:35:23 UTC
[jira] Created: (SM-514) ValidateComponent does not create
StreamSource with a SystemId which breaks schema includes and imports
ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
-------------------------------------------------------------------------------------------------------
Key: SM-514
URL: https://issues.apache.org/activemq/browse/SM-514
Project: ServiceMix
Issue Type: Bug
Components: servicemix-components
Affects Versions: 3.0
Environment: Windows XP SP2, Ubuntu Linux 5.10, ServiceMix HEAD
Reporter: Grant McDonald
Assigned To: Grant McDonald
Fix For: 3.0
Attachments: servicemix-components.zip
When creating a new schema object with a Source object the only way for Xalan/Xerces to resolve schema imports is via a SystemId which is an attribute on Source objects. Without this attribute being set schema imports and includes are not resolved correctly and an obscure message is returned:
org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'USAddress' to a(n) 'type definition' component.
This is actually because the import/include failed. It is unfortunate that the error message is not more informative. A patch has been provided to fix this error and the ValidationTest test case updated to use a simple hierarchical directory layout.
NOTE: the attached zip file has two patches and a new directory and xsd. The layout is as from the servicemix-components directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: [jira] Commented: (SM-514) ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
Posted by Hofri Yehuda <Ye...@comverse.com>.
Granted!
-----Original Message-----
From: Grant M [mailto:clearvertigo@gmail.com]
Sent: Wednesday, July 11, 2007 1:44 PM
To: servicemix-dev@geronimo.apache.org
Cc: servicemix-users@geronimo.apache.org
Subject: Re: [jira] Commented: (SM-514) ValidateComponent does not
create StreamSource with a SystemId which breaks schema includes and
imports
Archana,
Can you provide be the exact error and some more information about your
schemas? Hierarchical layout? Relative imports etc...
Grant
On 7/11/07, archana (JIRA) <ji...@apache.org> wrote:
>
>
> [
> https://issues.apache.org/activemq/browse/SM-514?page=com.atlassian.ji
> ra.plugin.system.issuetabpanels:comment-tabpanel#action_39642]
>
> archana commented on SM-514:
> ----------------------------
>
> i dont think issue is resolved.. coz i tried all possible ways as
> suggested but i am still facing same problem and getting same
error..
>
> > ValidateComponent does not create StreamSource with a SystemId which
> breaks schema includes and imports
> >
> ----------------------------------------------------------------------
> ---------------------------------
> >
> > Key: SM-514
> > URL:
https://issues.apache.org/activemq/browse/SM-514
> > Project: ServiceMix
> > Issue Type: Bug
> > Components: servicemix-components
> > Affects Versions: 3.0.1
> > Environment: Windows XP SP2, Ubuntu Linux 5.10, ServiceMix
HEAD
> > Reporter: Grant McDonald
> > Assignee: Grant McDonald
> > Fix For: 3.0
> >
> > Attachments: servicemix-components.zip
> >
> > Original Estimate: 15 minutes
> > Remaining Estimate: 15 minutes
> >
> > When creating a new schema object with a Source object the only way
> > for
> Xalan/Xerces to resolve schema imports is via a SystemId which is an
> attribute on Source objects. Instantiating a StreamSource with an
> InputStream does not set this attribute and without this attribute
> being set schema imports and includes are not resolved correctly and
> an obscure message is returned:
> > org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name
> 'USAddress' to a(n) 'type definition' component.
> > This is actually because the import/include failed. It is
> > unfortunate
> that the error message is not more informative. A patch has been
> provided to fix this error and the ValidationTest test case updated to
> use a simple hierarchical directory layout.
> > NOTE: the attached zip file has two patches and a new directory and
> xsd. The layout is as from the servicemix-components directory.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [jira] Commented: (SM-514) ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
Posted by Grant M <cl...@gmail.com>.
Archana,
Can you provide be the exact error and some more information about your
schemas? Hierarchical layout? Relative imports etc...
Grant
On 7/11/07, archana (JIRA) <ji...@apache.org> wrote:
>
>
> [
> https://issues.apache.org/activemq/browse/SM-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39642]
>
> archana commented on SM-514:
> ----------------------------
>
> i dont think issue is resolved.. coz i tried all possible ways as
> suggested but i am still facing same problem and getting same error..
>
> > ValidateComponent does not create StreamSource with a SystemId which
> breaks schema includes and imports
> >
> -------------------------------------------------------------------------------------------------------
> >
> > Key: SM-514
> > URL: https://issues.apache.org/activemq/browse/SM-514
> > Project: ServiceMix
> > Issue Type: Bug
> > Components: servicemix-components
> > Affects Versions: 3.0.1
> > Environment: Windows XP SP2, Ubuntu Linux 5.10, ServiceMix HEAD
> > Reporter: Grant McDonald
> > Assignee: Grant McDonald
> > Fix For: 3.0
> >
> > Attachments: servicemix-components.zip
> >
> > Original Estimate: 15 minutes
> > Remaining Estimate: 15 minutes
> >
> > When creating a new schema object with a Source object the only way for
> Xalan/Xerces to resolve schema imports is via a SystemId which is an
> attribute on Source objects. Instantiating a StreamSource with an
> InputStream does not set this attribute and without this attribute being set
> schema imports and includes are not resolved correctly and an obscure
> message is returned:
> > org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name
> 'USAddress' to a(n) 'type definition' component.
> > This is actually because the import/include failed. It is unfortunate
> that the error message is not more informative. A patch has been provided
> to fix this error and the ValidationTest test case updated to use a simple
> hierarchical directory layout.
> > NOTE: the attached zip file has two patches and a new directory and
> xsd. The layout is as from the servicemix-components directory.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [jira] Commented: (SM-514) ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
Posted by Grant M <cl...@gmail.com>.
Archana,
Can you provide be the exact error and some more information about your
schemas? Hierarchical layout? Relative imports etc...
Grant
On 7/11/07, archana (JIRA) <ji...@apache.org> wrote:
>
>
> [
> https://issues.apache.org/activemq/browse/SM-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39642]
>
> archana commented on SM-514:
> ----------------------------
>
> i dont think issue is resolved.. coz i tried all possible ways as
> suggested but i am still facing same problem and getting same error..
>
> > ValidateComponent does not create StreamSource with a SystemId which
> breaks schema includes and imports
> >
> -------------------------------------------------------------------------------------------------------
> >
> > Key: SM-514
> > URL: https://issues.apache.org/activemq/browse/SM-514
> > Project: ServiceMix
> > Issue Type: Bug
> > Components: servicemix-components
> > Affects Versions: 3.0.1
> > Environment: Windows XP SP2, Ubuntu Linux 5.10, ServiceMix HEAD
> > Reporter: Grant McDonald
> > Assignee: Grant McDonald
> > Fix For: 3.0
> >
> > Attachments: servicemix-components.zip
> >
> > Original Estimate: 15 minutes
> > Remaining Estimate: 15 minutes
> >
> > When creating a new schema object with a Source object the only way for
> Xalan/Xerces to resolve schema imports is via a SystemId which is an
> attribute on Source objects. Instantiating a StreamSource with an
> InputStream does not set this attribute and without this attribute being set
> schema imports and includes are not resolved correctly and an obscure
> message is returned:
> > org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name
> 'USAddress' to a(n) 'type definition' component.
> > This is actually because the import/include failed. It is unfortunate
> that the error message is not more informative. A patch has been provided
> to fix this error and the ValidationTest test case updated to use a simple
> hierarchical directory layout.
> > NOTE: the attached zip file has two patches and a new directory and
> xsd. The layout is as from the servicemix-components directory.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Resolved: (SM-514) ValidateComponent does not create
StreamSource with a SystemId which breaks schema includes and imports
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-514?page=all ]
Guillaume Nodet resolved SM-514.
--------------------------------
Fix Version/s: 3.0-M3
(was: 3.0)
Resolution: Fixed
Author: gnodet
Date: Mon Aug 7 01:48:49 2006
New Revision: 429279
URL: http://svn.apache.org/viewvc?rev=429279&view=rev
Log:
SM-514: ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
Patch provided by Grant McDonald, thx !
Added:
incubator/servicemix/trunk/servicemix-components/src/test/resources/org/apache/servicemix/components/validation/address/
incubator/servicemix/trunk/servicemix-components/src/test/resources/org/apache/servicemix/components/validation/address/address.xsd
Modified:
incubator/servicemix/trunk/servicemix-components/src/main/java/org/apache/servicemix/components/validation/ValidateComponent.java
incubator/servicemix/trunk/servicemix-components/src/test/resources/org/apache/servicemix/components/validation/schema.xsd
> ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
> -------------------------------------------------------------------------------------------------------
>
> Key: SM-514
> URL: https://issues.apache.org/activemq/browse/SM-514
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-components
> Affects Versions: 3.0
> Environment: Windows XP SP2, Ubuntu Linux 5.10, ServiceMix HEAD
> Reporter: Grant McDonald
> Assigned To: Grant McDonald
> Fix For: 3.0-M3
>
> Attachments: servicemix-components.zip
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> When creating a new schema object with a Source object the only way for Xalan/Xerces to resolve schema imports is via a SystemId which is an attribute on Source objects. Instantiating a StreamSource with an InputStream does not set this attribute and without this attribute being set schema imports and includes are not resolved correctly and an obscure message is returned:
> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'USAddress' to a(n) 'type definition' component.
> This is actually because the import/include failed. It is unfortunate that the error message is not more informative. A patch has been provided to fix this error and the ValidationTest test case updated to use a simple hierarchical directory layout.
> NOTE: the attached zip file has two patches and a new directory and xsd. The layout is as from the servicemix-components directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-514) ValidateComponent does not create
StreamSource with a SystemId which breaks schema includes and imports
Posted by "archana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39642 ]
archana commented on SM-514:
----------------------------
i dont think issue is resolved.. coz i tried all possible ways as suggested but i am still facing same problem and getting same error..
> ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
> -------------------------------------------------------------------------------------------------------
>
> Key: SM-514
> URL: https://issues.apache.org/activemq/browse/SM-514
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-components
> Affects Versions: 3.0.1
> Environment: Windows XP SP2, Ubuntu Linux 5.10, ServiceMix HEAD
> Reporter: Grant McDonald
> Assignee: Grant McDonald
> Fix For: 3.0
>
> Attachments: servicemix-components.zip
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> When creating a new schema object with a Source object the only way for Xalan/Xerces to resolve schema imports is via a SystemId which is an attribute on Source objects. Instantiating a StreamSource with an InputStream does not set this attribute and without this attribute being set schema imports and includes are not resolved correctly and an obscure message is returned:
> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'USAddress' to a(n) 'type definition' component.
> This is actually because the import/include failed. It is unfortunate that the error message is not more informative. A patch has been provided to fix this error and the ValidationTest test case updated to use a simple hierarchical directory layout.
> NOTE: the attached zip file has two patches and a new directory and xsd. The layout is as from the servicemix-components directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-514) ValidateComponent does not create
StreamSource with a SystemId which breaks schema includes and imports
Posted by "Grant McDonald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-514?page=all ]
Grant McDonald updated SM-514:
------------------------------
Description:
When creating a new schema object with a Source object the only way for Xalan/Xerces to resolve schema imports is via a SystemId which is an attribute on Source objects. Instantiating a StreamSource with an InputStream does not set this attribute and without this attribute being set schema imports and includes are not resolved correctly and an obscure message is returned:
org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'USAddress' to a(n) 'type definition' component.
This is actually because the import/include failed. It is unfortunate that the error message is not more informative. A patch has been provided to fix this error and the ValidationTest test case updated to use a simple hierarchical directory layout.
NOTE: the attached zip file has two patches and a new directory and xsd. The layout is as from the servicemix-components directory.
was:
When creating a new schema object with a Source object the only way for Xalan/Xerces to resolve schema imports is via a SystemId which is an attribute on Source objects. Without this attribute being set schema imports and includes are not resolved correctly and an obscure message is returned:
org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'USAddress' to a(n) 'type definition' component.
This is actually because the import/include failed. It is unfortunate that the error message is not more informative. A patch has been provided to fix this error and the ValidationTest test case updated to use a simple hierarchical directory layout.
NOTE: the attached zip file has two patches and a new directory and xsd. The layout is as from the servicemix-components directory.
> ValidateComponent does not create StreamSource with a SystemId which breaks schema includes and imports
> -------------------------------------------------------------------------------------------------------
>
> Key: SM-514
> URL: https://issues.apache.org/activemq/browse/SM-514
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-components
> Affects Versions: 3.0
> Environment: Windows XP SP2, Ubuntu Linux 5.10, ServiceMix HEAD
> Reporter: Grant McDonald
> Assigned To: Grant McDonald
> Fix For: 3.0
>
> Attachments: servicemix-components.zip
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> When creating a new schema object with a Source object the only way for Xalan/Xerces to resolve schema imports is via a SystemId which is an attribute on Source objects. Instantiating a StreamSource with an InputStream does not set this attribute and without this attribute being set schema imports and includes are not resolved correctly and an obscure message is returned:
> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'USAddress' to a(n) 'type definition' component.
> This is actually because the import/include failed. It is unfortunate that the error message is not more informative. A patch has been provided to fix this error and the ValidationTest test case updated to use a simple hierarchical directory layout.
> NOTE: the attached zip file has two patches and a new directory and xsd. The layout is as from the servicemix-components directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira