You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2009/03/27 03:34:51 UTC
[jira] Created: (CXF-2135) JAXB binding files with no
schemaLocation don't work
JAXB binding files with no schemaLocation don't work
----------------------------------------------------
Key: CXF-2135
URL: https://issues.apache.org/jira/browse/CXF-2135
Project: CXF
Issue Type: Bug
Components: Tooling
Reporter: Benson Margulies
Fix For: 2.2.1
In order to clean up other code and prevent other bugs, I am breaking the code that allows JAXB binding files with no schemaLocation attribute to work.
In 2.2 and earlier, this worked because we fed all the schemas to JAXB under the same key. This is contrary to the doc and likely to cause other more confusing problems, such as mis-applied customizations.
The correct solution seems to be to just leave off the schemaLocation, but as of JAXB 2.1.10, that doesn't work, since JAXB doesn't handle this case for outboard customization files. Heck, perhaps recycling outboard customization files with JAXB is just not a good idea, period.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CXF-2135) JAXB binding files with no
schemaLocation don't work
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reopened CXF-2135:
------------------------------
Assignee: Daniel Kulp
Kind of a regression as this feature was specifically added for CXF-1094.
Semi-easy to add back in, but with a small performance penalty, but the penalty is really just hit for binding files with no schemaLocation so not a big deal for most use cases.
> JAXB binding files with no schemaLocation don't work
> ----------------------------------------------------
>
> Key: CXF-2135
> URL: https://issues.apache.org/jira/browse/CXF-2135
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
> Fix For: Invalid
>
>
> In order to clean up other code and prevent other bugs, I am breaking the code that allows JAXB binding files with no schemaLocation attribute to work.
> In 2.2 and earlier, this worked because we fed all the schemas to JAXB under the same key. This is contrary to the doc and likely to cause other more confusing problems, such as mis-applied customizations.
> The correct solution seems to be to just leave off the schemaLocation, but as of JAXB 2.1.10, that doesn't work, since JAXB doesn't handle this case for outboard customization files. Heck, perhaps recycling outboard customization files with JAXB is just not a good idea, period.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2135) JAXB binding files with no
schemaLocation don't work
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2135.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
Marking this invalid. Per JAXB spec, the schemaLocation is required so not accepting it is OK.
> JAXB binding files with no schemaLocation don't work
> ----------------------------------------------------
>
> Key: CXF-2135
> URL: https://issues.apache.org/jira/browse/CXF-2135
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Reporter: Benson Margulies
> Fix For: Invalid
>
>
> In order to clean up other code and prevent other bugs, I am breaking the code that allows JAXB binding files with no schemaLocation attribute to work.
> In 2.2 and earlier, this worked because we fed all the schemas to JAXB under the same key. This is contrary to the doc and likely to cause other more confusing problems, such as mis-applied customizations.
> The correct solution seems to be to just leave off the schemaLocation, but as of JAXB 2.1.10, that doesn't work, since JAXB doesn't handle this case for outboard customization files. Heck, perhaps recycling outboard customization files with JAXB is just not a good idea, period.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2135) JAXB binding files with no
schemaLocation don't work
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2135.
------------------------------
Resolution: Fixed
Fix Version/s: (was: Invalid)
2.2.6
> JAXB binding files with no schemaLocation don't work
> ----------------------------------------------------
>
> Key: CXF-2135
> URL: https://issues.apache.org/jira/browse/CXF-2135
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
> Fix For: 2.2.6
>
>
> In order to clean up other code and prevent other bugs, I am breaking the code that allows JAXB binding files with no schemaLocation attribute to work.
> In 2.2 and earlier, this worked because we fed all the schemas to JAXB under the same key. This is contrary to the doc and likely to cause other more confusing problems, such as mis-applied customizations.
> The correct solution seems to be to just leave off the schemaLocation, but as of JAXB 2.1.10, that doesn't work, since JAXB doesn't handle this case for outboard customization files. Heck, perhaps recycling outboard customization files with JAXB is just not a good idea, period.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.