You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2019/04/26 07:58:00 UTC

[jira] [Resolved] (SANTUARIO-503) Updating to xmlsec 2.0.4: setSignatureSpecNSprefix not available.

     [ https://issues.apache.org/jira/browse/SANTUARIO-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh resolved SANTUARIO-503.
-------------------------------------------
    Resolution: Not A Problem

> Updating to xmlsec 2.0.4: setSignatureSpecNSprefix not available.
> -----------------------------------------------------------------
>
>                 Key: SANTUARIO-503
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-503
>             Project: Santuario
>          Issue Type: Bug
>          Components: Java
>            Reporter: Alejandro Carlstein
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>              Labels: xmlsec
>
> We are updating from Java 7 to 8 and from Weblogic 10 to 12.
> Therefore, we updated from xmlsec 1.2.0 to 2.0.4.
> Some of our unit test utilize:
> {code:java}
> import org.apache.xml.security.utils.Constants;
> ...
> Constants.setSignatureSpecNSprefix("");
> {code}
> However, it seems that setSignatureSpecNSprefix has being removed in the version 2.0.4.
> We can't find any documentation that help us to replace it or find a way around it.
> If this is not the place for asking this kind of question, please guide us to where we can. 
> Thank you for you time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)