You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Scott Heaberlin (JIRA)" <ji...@apache.org> on 2009/08/07 04:17:14 UTC

[jira] Created: (WSS-205) WSS4J Handler passes null to MessageContext.setProperty

WSS4J Handler passes null to MessageContext.setProperty
-------------------------------------------------------

                 Key: WSS-205
                 URL: https://issues.apache.org/jira/browse/WSS-205
             Project: WSS4J
          Issue Type: Bug
          Components: WSS4J Handlers
    Affects Versions: 1.5.7, 1.5.8
         Environment: IBM WebSphere Application Server v6, IBM WebServices Engine
            Reporter: Scott Heaberlin
            Assignee: Ruchith Udayanga Fernando
         Attachments: wss4jhandler1_5_8_patch_sheaberlin.txt

WSS4JHandler cannot be used in an IBM WebSphere web services engine runtime because it attempts to set a MessageContext property to null instead of calling MessageContext.removeProperty().  Doing so raises an exception while using UsernameToken (perhaps more) functionality with the WebSphere error "WSWS3211E: Error: Null property value specified."

I was able to track this down in a debugger session to (WSS4J 1.5.7, 1.5.8) WSS4JHandler, line 314:

mc.setProperty(WSHandlerConstants.SND_SECURITY, null);

As it turns out, the WebSphere implementation of MessageContext is a descendant of java.util.Hashtable, which does not allow null values.

I will attach a patch (passes all unit tests in the maven2 build) with a proposed fix, which is to use MessageContext.removeProperty() instead of setProperty(..., null).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


[jira] Updated: (WSS-205) WSS4J Handler passes null to MessageContext.setProperty

Posted by "Scott Heaberlin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Heaberlin updated WSS-205:
--------------------------------

    Attachment: wss4jhandler1_5_8_patch_sheaberlin.txt

patch vs tag 1_5_8

> WSS4J Handler passes null to MessageContext.setProperty
> -------------------------------------------------------
>
>                 Key: WSS-205
>                 URL: https://issues.apache.org/jira/browse/WSS-205
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.5.7, 1.5.8
>         Environment: IBM WebSphere Application Server v6, IBM WebServices Engine
>            Reporter: Scott Heaberlin
>            Assignee: Ruchith Udayanga Fernando
>         Attachments: wss4jhandler1_5_8_patch_sheaberlin.txt
>
>
> WSS4JHandler cannot be used in an IBM WebSphere web services engine runtime because it attempts to set a MessageContext property to null instead of calling MessageContext.removeProperty().  Doing so raises an exception while using UsernameToken (perhaps more) functionality with the WebSphere error "WSWS3211E: Error: Null property value specified."
> I was able to track this down in a debugger session to (WSS4J 1.5.7, 1.5.8) WSS4JHandler, line 314:
> mc.setProperty(WSHandlerConstants.SND_SECURITY, null);
> As it turns out, the WebSphere implementation of MessageContext is a descendant of java.util.Hashtable, which does not allow null values.
> I will attach a patch (passes all unit tests in the maven2 build) with a proposed fix, which is to use MessageContext.removeProperty() instead of setProperty(..., null).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


[jira] Updated: (WSS-205) WSS4J Handler passes null to MessageContext.setProperty

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated WSS-205:
------------------------------------

    Fix Version/s: 1.6
                   1.5.9

> WSS4J Handler passes null to MessageContext.setProperty
> -------------------------------------------------------
>
>                 Key: WSS-205
>                 URL: https://issues.apache.org/jira/browse/WSS-205
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.5.7, 1.5.8
>         Environment: IBM WebSphere Application Server v6, IBM WebServices Engine
>            Reporter: Scott Heaberlin
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.5.9, 1.6
>
>         Attachments: wss4jhandler1_5_8_patch_sheaberlin.txt
>
>
> WSS4JHandler cannot be used in an IBM WebSphere web services engine runtime because it attempts to set a MessageContext property to null instead of calling MessageContext.removeProperty().  Doing so raises an exception while using UsernameToken (perhaps more) functionality with the WebSphere error "WSWS3211E: Error: Null property value specified."
> I was able to track this down in a debugger session to (WSS4J 1.5.7, 1.5.8) WSS4JHandler, line 314:
> mc.setProperty(WSHandlerConstants.SND_SECURITY, null);
> As it turns out, the WebSphere implementation of MessageContext is a descendant of java.util.Hashtable, which does not allow null values.
> I will attach a patch (passes all unit tests in the maven2 build) with a proposed fix, which is to use MessageContext.removeProperty() instead of setProperty(..., null).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


[jira] Assigned: (WSS-205) WSS4J Handler passes null to MessageContext.setProperty

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh reassigned WSS-205:
---------------------------------------

    Assignee: Colm O hEigeartaigh  (was: Ruchith Udayanga Fernando)

> WSS4J Handler passes null to MessageContext.setProperty
> -------------------------------------------------------
>
>                 Key: WSS-205
>                 URL: https://issues.apache.org/jira/browse/WSS-205
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.5.7, 1.5.8
>         Environment: IBM WebSphere Application Server v6, IBM WebServices Engine
>            Reporter: Scott Heaberlin
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.5.9, 1.6
>
>         Attachments: wss4jhandler1_5_8_patch_sheaberlin.txt
>
>
> WSS4JHandler cannot be used in an IBM WebSphere web services engine runtime because it attempts to set a MessageContext property to null instead of calling MessageContext.removeProperty().  Doing so raises an exception while using UsernameToken (perhaps more) functionality with the WebSphere error "WSWS3211E: Error: Null property value specified."
> I was able to track this down in a debugger session to (WSS4J 1.5.7, 1.5.8) WSS4JHandler, line 314:
> mc.setProperty(WSHandlerConstants.SND_SECURITY, null);
> As it turns out, the WebSphere implementation of MessageContext is a descendant of java.util.Hashtable, which does not allow null values.
> I will attach a patch (passes all unit tests in the maven2 build) with a proposed fix, which is to use MessageContext.removeProperty() instead of setProperty(..., null).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


[jira] Closed: (WSS-205) WSS4J Handler passes null to MessageContext.setProperty

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh closed WSS-205.
-----------------------------------


> WSS4J Handler passes null to MessageContext.setProperty
> -------------------------------------------------------
>
>                 Key: WSS-205
>                 URL: https://issues.apache.org/jira/browse/WSS-205
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.5.7, 1.5.8
>         Environment: IBM WebSphere Application Server v6, IBM WebServices Engine
>            Reporter: Scott Heaberlin
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.5.9, 1.6
>
>         Attachments: wss4jhandler1_5_8_patch_sheaberlin.txt
>
>
> WSS4JHandler cannot be used in an IBM WebSphere web services engine runtime because it attempts to set a MessageContext property to null instead of calling MessageContext.removeProperty().  Doing so raises an exception while using UsernameToken (perhaps more) functionality with the WebSphere error "WSWS3211E: Error: Null property value specified."
> I was able to track this down in a debugger session to (WSS4J 1.5.7, 1.5.8) WSS4JHandler, line 314:
> mc.setProperty(WSHandlerConstants.SND_SECURITY, null);
> As it turns out, the WebSphere implementation of MessageContext is a descendant of java.util.Hashtable, which does not allow null values.
> I will attach a patch (passes all unit tests in the maven2 build) with a proposed fix, which is to use MessageContext.removeProperty() instead of setProperty(..., null).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


[jira] Resolved: (WSS-205) WSS4J Handler passes null to MessageContext.setProperty

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh resolved WSS-205.
-------------------------------------

    Resolution: Fixed


Fixed, thanks.

Colm.

> WSS4J Handler passes null to MessageContext.setProperty
> -------------------------------------------------------
>
>                 Key: WSS-205
>                 URL: https://issues.apache.org/jira/browse/WSS-205
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.5.7, 1.5.8
>         Environment: IBM WebSphere Application Server v6, IBM WebServices Engine
>            Reporter: Scott Heaberlin
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.5.9, 1.6
>
>         Attachments: wss4jhandler1_5_8_patch_sheaberlin.txt
>
>
> WSS4JHandler cannot be used in an IBM WebSphere web services engine runtime because it attempts to set a MessageContext property to null instead of calling MessageContext.removeProperty().  Doing so raises an exception while using UsernameToken (perhaps more) functionality with the WebSphere error "WSWS3211E: Error: Null property value specified."
> I was able to track this down in a debugger session to (WSS4J 1.5.7, 1.5.8) WSS4JHandler, line 314:
> mc.setProperty(WSHandlerConstants.SND_SECURITY, null);
> As it turns out, the WebSphere implementation of MessageContext is a descendant of java.util.Hashtable, which does not allow null values.
> I will attach a patch (passes all unit tests in the maven2 build) with a proposed fix, which is to use MessageContext.removeProperty() instead of setProperty(..., null).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org