You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Marc Giger (JIRA)" <ji...@apache.org> on 2015/11/29 18:25:10 UTC
[jira] [Resolved] (SANTUARIO-433) IBM WAS 8.5.5 JVM does not
support null for NameSpace prefix
[ https://issues.apache.org/jira/browse/SANTUARIO-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marc Giger resolved SANTUARIO-433.
----------------------------------
Resolution: Fixed
Assignee: Marc Giger (was: Colm O hEigeartaigh)
Fix Version/s: Java 2.0.6
Fixed in trunk.
> IBM WAS 8.5.5 JVM does not support null for NameSpace prefix
> ------------------------------------------------------------
>
> Key: SANTUARIO-433
> URL: https://issues.apache.org/jira/browse/SANTUARIO-433
> Project: Santuario
> Issue Type: Bug
> Components: Java
> Affects Versions: Java 2.0.5
> Environment: IBM WebSphere 8.5.5
> Reporter: sit
> Assignee: Marc Giger
> Priority: Minor
> Fix For: Java 2.0.6
>
>
> 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)