cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (CXF-2135) JAXB binding files with no schemaLocation don't work
Date Mon, 04 Jan 2010 19:45:54 GMT

     [ 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.


Mime
View raw message