You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/14 23:12:51 UTC

[jira] Created: (AXIS-1610) Serialization outside the context of sending a message could throw an exception

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1610

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1610
    Summary: Serialization outside the context of sending a message could throw an exception
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis
 Components: 
             Serialization/Deserialization
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Steve Green

    Created: Thu, 14 Oct 2004 2:11 PM
    Updated: Thu, 14 Oct 2004 2:11 PM

Description:
Calling toString() or getAsDOM() on a MessageElement involves serialization.  Sometimes it is usefull to use these methods when working with 3rd party libraries that use DOM.  In this case, it is common to call getAsDOM before sending a message.  When trying to serialize a bean that is not in the type mapping, Axis will invoke getSerializer() on the bean.  That call will result in a nullPointerException trying to get the encoding style from the message context because the message context is null.

Attached is patch that uses the default encoding style when the message context is null.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Closed: (AXIS-1610) Serialization outside the context of sending a message could throw an exception

Posted by ax...@ws.apache.org.
Message:

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Thu, 14 Oct 2004 3:10 PM

invalid as per Steve Green's comments.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1610

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1610
    Summary: Serialization outside the context of sending a message could throw an exception
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: INVALID

    Project: Axis
 Components: 
             Serialization/Deserialization
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Steve Green

    Created: Thu, 14 Oct 2004 2:11 PM
    Updated: Thu, 14 Oct 2004 3:10 PM

Description:
Calling toString() or getAsDOM() on a MessageElement involves serialization.  Sometimes it is usefull to use these methods when working with 3rd party libraries that use DOM.  In this case, it is common to call getAsDOM before sending a message.  When trying to serialize a bean that is not in the type mapping, Axis will invoke getSerializer() on the bean.  That call will result in a nullPointerException trying to get the encoding style from the message context because the message context is null.

Attached is patch that uses the default encoding style when the message context is null.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXIS-1610) Serialization outside the context of sending a message could throw an exception

Posted by ax...@ws.apache.org.
The following comment has been added to this issue:

     Author: Steve Green
    Created: Thu, 14 Oct 2004 2:25 PM
       Body:
Just as I sent this report, I see that the same bug was fixed as of today.  Because of that, I am not attaching my patch, however I wonder if it makes more sense to use Use.DEFAULT.getEncoding(), rather than Use.ENCODED.getEncoding().
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1610?page=comments#action_54109

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1610

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1610
    Summary: Serialization outside the context of sending a message could throw an exception
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis
 Components: 
             Serialization/Deserialization
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Steve Green

    Created: Thu, 14 Oct 2004 2:11 PM
    Updated: Thu, 14 Oct 2004 2:25 PM

Description:
Calling toString() or getAsDOM() on a MessageElement involves serialization.  Sometimes it is usefull to use these methods when working with 3rd party libraries that use DOM.  In this case, it is common to call getAsDOM before sending a message.  When trying to serialize a bean that is not in the type mapping, Axis will invoke getSerializer() on the bean.  That call will result in a nullPointerException trying to get the encoding style from the message context because the message context is null.

Attached is patch that uses the default encoding style when the message context is null.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira