You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "sit (JIRA)" <ji...@apache.org> on 2015/11/20 15:56:11 UTC
[jira] [Commented] (SANTUARIO-433) IBM JVM does not support null
for NameSpace prefix
[ https://issues.apache.org/jira/browse/SANTUARIO-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018116#comment-15018116 ]
sit commented on SANTUARIO-433:
-------------------------------
I submitted a pull request on XMLSecurityStreamWriter.
https://github.com/SitChenNam/santuario-java
> IBM JVM does not support null for NameSpace prefix
> --------------------------------------------------
>
> Key: SANTUARIO-433
> URL: https://issues.apache.org/jira/browse/SANTUARIO-433
> Project: Santuario
> Issue Type: Improvement
> Components: Java
> Affects Versions: Java 2.0.5
> Environment: IBM WebSphere 8.5.5
> Reporter: sit
> Assignee: Colm O hEigeartaigh
> Priority: Minor
>
> When running under WAS 8.5.5.5 under Windows 7,
> 1. XMLSecurityStreamWriter.writeDefaultNamespace() fails with null pointerException at line 296: this.openStartElement.getElementPrefix() return null
> 2. XMLSecurityStreamWriter$Element.getQName (XMLSecurityStreamWriter.java:538) Caused by: java.lang.IllegalArgumentException: prefix cannot be "null" when creating a QName
> at javax.xml.namespace.QName.<init>(Unknown Source)
> at org.apache.xml.security.stax.impl.XMLSecurityStreamWriter $Element.getQName(XMLSecurityStreamWriter.java:538)
> Both are due to the fact that IBM JVM 1.6 deos not allow NS prefix = null
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)