You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Johan Mörén (Created JIRA)" <ji...@apache.org> on 2012/01/09 15:56:39 UTC
[jira] [Created] (CAMEL-4877) API-breaking changes in
Validator-component
API-breaking changes in Validator-component
-------------------------------------------
Key: CAMEL-4877
URL: https://issues.apache.org/jira/browse/CAMEL-4877
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.9.0
Reporter: Johan Mörén
Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
{code}
...
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
...
{code}
I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4877.
--------------------------------
Resolution: Fixed
Thanks for reporting. Your use-case works now in an unit test.
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Assignee: Claus Ibsen
> Fix For: 2.9.1, 2.10.0
>
> Attachments: xsd-import_example.zip
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Johan Mörén (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Mörén updated CAMEL-4877:
-------------------------------
Attachment: (was: xsd-import_example.zip)
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Fix For: 2.9.1, 2.10.0
>
> Attachments: xsd-import_example.zip
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187659#comment-13187659 ]
Claus Ibsen commented on CAMEL-4877:
------------------------------------
Johan, can you re-attach the example, and grant [x] in give license to Apache (or what the checkbox says). We need this due legal, to be able to use any of your work/example for fixing this.
The attached file should have an Apache feather at the icon logo.
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Fix For: 2.9.1, 2.10.0
>
> Attachments: xsd-import_example.zip
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-4877:
-------------------------------
Fix Version/s: 2.10.0
2.9.1
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Fix For: 2.9.1, 2.10.0
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Claus Ibsen (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-4877:
----------------------------------
Assignee: Claus Ibsen
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Assignee: Claus Ibsen
> Fix For: 2.9.1, 2.10.0
>
> Attachments: xsd-import_example.zip
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Johan Mörén (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Mörén updated CAMEL-4877:
-------------------------------
Attachment: xsd-import_example.zip
attatched simple maven project. Just switch the pom-property camel.version between 2.9.0 and 2.8.0 to verify the difference in behaviour.
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Fix For: 2.9.1, 2.10.0
>
> Attachments: xsd-import_example.zip
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186522#comment-13186522 ]
Claus Ibsen commented on CAMEL-4877:
------------------------------------
Can you attach a little example of this, such as the velocity template which refer to the other template. Just to be sure, so we can use that for an unit test.
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Fix For: 2.9.1, 2.10.0
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Claus Ibsen (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186522#comment-13186522 ]
Claus Ibsen edited comment on CAMEL-4877 at 1/15/12 3:30 PM:
-------------------------------------------------------------
Can you attach a little example of this, such as the template file which refer to the other template. Just to be sure, so we can use that for an unit test.
was (Author: davsclaus):
Can you attach a little example of this, such as the velocity template which refer to the other template. Just to be sure, so we can use that for an unit test.
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Fix For: 2.9.1, 2.10.0
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Johan Mörén (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Mörén updated CAMEL-4877:
-------------------------------
Attachment: xsd-import_example.zip
Attached file again with flag.
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Fix For: 2.9.1, 2.10.0
>
> Attachments: xsd-import_example.zip, xsd-import_example.zip
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4877) API-breaking changes in
Validator-component
Posted by "Johan Mörén (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188966#comment-13188966 ]
Johan Mörén commented on CAMEL-4877:
------------------------------------
Thanks Claus! Looking forward to 2.9.1.
> API-breaking changes in Validator-component
> -------------------------------------------
>
> Key: CAMEL-4877
> URL: https://issues.apache.org/jira/browse/CAMEL-4877
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Johan Mörén
> Assignee: Claus Ibsen
> Fix For: 2.9.1, 2.10.0
>
> Attachments: xsd-import_example.zip
>
>
> Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.
> Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error
> {code}
> ...
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
> ...
> {code}
> I can see in the new documentation for the validator-component that there is an new property that you can set called *resourceResolver*. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.
> I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira