You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Chris McClelland (JIRA)" <ji...@apache.org> on 2008/04/28 17:39:55 UTC
[jira] Created: (CXF-1553) TunedDocumentLoader fails to resolve xsi
prefix properly when not using WSTX.
TunedDocumentLoader fails to resolve xsi prefix properly when not using WSTX.
-----------------------------------------------------------------------------
Key: CXF-1553
URL: https://issues.apache.org/jira/browse/CXF-1553
Project: CXF
Issue Type: Bug
Components: Configuration
Affects Versions: 2.1
Reporter: Chris McClelland
Fix For: 2.1
I want to use Xerces, not WSTX. But if I remove WSTX from the CLASSPATH, the fallback mechanism at line 75 of TunedDocumentLoader fails. I believe WSTX defaults the "http://xml.org/sax/features/namespaces" property to true, whereas Xerces defaults it to false. As a result, you get a cryptic error:
NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces
The fix is to add this line:
nsasaxParserFactory.setFeature("http://xml.org/sax/features/namespaces", true);
After line 85 of org.apache.cxf.bus.spring.TunedDocumentLoader.
On a side note, what is the reason for the fallback mechanism at org.apache.cxf.bus.spring.TunedDocumentLoader.java:75? Why not just rely on the JAXP mechanism to find implementations?
- Chris
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1553) TunedDocumentLoader fails to resolve
xsi prefix properly when not using WSTX.
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592836#action_12592836 ]
Daniel Kulp commented on CXF-1553:
----------------------------------
You're probably write about the property. I'll add that to the namespace-prefix property that we DO set on that factory.
The basic reason is that we want to use Woodstox if it's available. Woodstox is a LOT faster than xerces to do this. Benson has done quite a bit of benchmarking on application startup and making sure we use woodstox when it's there is a huge help with application startup time. However, it should work if woodstox isn't there.
Dan
> TunedDocumentLoader fails to resolve xsi prefix properly when not using WSTX.
> -----------------------------------------------------------------------------
>
> Key: CXF-1553
> URL: https://issues.apache.org/jira/browse/CXF-1553
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.1
> Reporter: Chris McClelland
> Assignee: Daniel Kulp
> Fix For: 2.1
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> I want to use Xerces, not WSTX. But if I remove WSTX from the CLASSPATH, the fallback mechanism at line 75 of TunedDocumentLoader fails. I believe WSTX defaults the "http://xml.org/sax/features/namespaces" property to true, whereas Xerces defaults it to false. As a result, you get a cryptic error:
> NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces
> The fix is to add this line:
> nsasaxParserFactory.setFeature("http://xml.org/sax/features/namespaces", true);
> After line 85 of org.apache.cxf.bus.spring.TunedDocumentLoader.
> On a side note, what is the reason for the fallback mechanism at org.apache.cxf.bus.spring.TunedDocumentLoader.java:75? Why not just rely on the JAXP mechanism to find implementations?
> - Chris
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1553) TunedDocumentLoader fails to resolve
xsi prefix properly when not using WSTX.
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-1553:
--------------------------------
Assignee: Daniel Kulp
> TunedDocumentLoader fails to resolve xsi prefix properly when not using WSTX.
> -----------------------------------------------------------------------------
>
> Key: CXF-1553
> URL: https://issues.apache.org/jira/browse/CXF-1553
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.1
> Reporter: Chris McClelland
> Assignee: Daniel Kulp
> Fix For: 2.1
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> I want to use Xerces, not WSTX. But if I remove WSTX from the CLASSPATH, the fallback mechanism at line 75 of TunedDocumentLoader fails. I believe WSTX defaults the "http://xml.org/sax/features/namespaces" property to true, whereas Xerces defaults it to false. As a result, you get a cryptic error:
> NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces
> The fix is to add this line:
> nsasaxParserFactory.setFeature("http://xml.org/sax/features/namespaces", true);
> After line 85 of org.apache.cxf.bus.spring.TunedDocumentLoader.
> On a side note, what is the reason for the fallback mechanism at org.apache.cxf.bus.spring.TunedDocumentLoader.java:75? Why not just rely on the JAXP mechanism to find implementations?
> - Chris
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1553) TunedDocumentLoader fails to resolve xsi
prefix properly when not using WSTX.
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-1553:
-----------------------------
Fix Version/s: (was: 2.1)
2.1.1
> TunedDocumentLoader fails to resolve xsi prefix properly when not using WSTX.
> -----------------------------------------------------------------------------
>
> Key: CXF-1553
> URL: https://issues.apache.org/jira/browse/CXF-1553
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.1
> Reporter: Chris McClelland
> Assignee: Daniel Kulp
> Fix For: 2.1.1
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> I want to use Xerces, not WSTX. But if I remove WSTX from the CLASSPATH, the fallback mechanism at line 75 of TunedDocumentLoader fails. I believe WSTX defaults the "http://xml.org/sax/features/namespaces" property to true, whereas Xerces defaults it to false. As a result, you get a cryptic error:
> NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces
> The fix is to add this line:
> nsasaxParserFactory.setFeature("http://xml.org/sax/features/namespaces", true);
> After line 85 of org.apache.cxf.bus.spring.TunedDocumentLoader.
> On a side note, what is the reason for the fallback mechanism at org.apache.cxf.bus.spring.TunedDocumentLoader.java:75? Why not just rely on the JAXP mechanism to find implementations?
> - Chris
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1553) TunedDocumentLoader fails to resolve
xsi prefix properly when not using WSTX.
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1553.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.7
> TunedDocumentLoader fails to resolve xsi prefix properly when not using WSTX.
> -----------------------------------------------------------------------------
>
> Key: CXF-1553
> URL: https://issues.apache.org/jira/browse/CXF-1553
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.1
> Reporter: Chris McClelland
> Assignee: Daniel Kulp
> Fix For: 2.1.1, 2.0.7
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> I want to use Xerces, not WSTX. But if I remove WSTX from the CLASSPATH, the fallback mechanism at line 75 of TunedDocumentLoader fails. I believe WSTX defaults the "http://xml.org/sax/features/namespaces" property to true, whereas Xerces defaults it to false. As a result, you get a cryptic error:
> NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces
> The fix is to add this line:
> nsasaxParserFactory.setFeature("http://xml.org/sax/features/namespaces", true);
> After line 85 of org.apache.cxf.bus.spring.TunedDocumentLoader.
> On a side note, what is the reason for the fallback mechanism at org.apache.cxf.bus.spring.TunedDocumentLoader.java:75? Why not just rely on the JAXP mechanism to find implementations?
> - Chris
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.