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 Krishnendu Kunti <Kr...@infosys.com> on 2004/10/18 08:39:36 UTC
Serialization Problems
Hi
I tried serializing org.apache.axis.AxisEngine and
org.apache.axis.Message from a MessageContext and storing the same in a
databse a blob. Though both these classes implements
java.io.Serializable but internally they use some classes which are not
Serializable.... and hence effectively are non serilalizable.
In case of org.apache.axis.AxisEngine , it references
org.apache.axis.utils.cache.ClassCache class which is non serializable.
In case of org.apache.axis.Message , it contains a private variable
MessageContext which is non serializable.
Please suggest if it should be reported as Bug ..
Thanks
Regards
Krishnendu
Re: Serialization Problems
Posted by Srinath Perera <he...@gmail.com>.
you do not need to serialize the engine as the engine is stateless.
Serializing the MessageContext and runing in with the correct
EngineConfiguration (the deployment Info) and message context should
do.
There are problems seralizing MessageContext, since it store anything
in the form of properties.
On Mon, 18 Oct 2004 12:09:36 +0530, Krishnendu Kunti
<kr...@infosys.com> wrote:
>
> Hi
>
> I tried serializing org.apache.axis.AxisEngine and
> org.apache.axis.Message from a MessageContext and storing the same in a
> databse a blob. Though both these classes implements
> java.io.Serializable but internally they use some classes which are not
> Serializable.... and hence effectively are non serilalizable.
>
> In case of org.apache.axis.AxisEngine , it references
> org.apache.axis.utils.cache.ClassCache class which is non serializable.
>
> In case of org.apache.axis.Message , it contains a private variable
> MessageContext which is non serializable.
>
> Please suggest if it should be reported as Bug ..
> Thanks
> Regards
> Krishnendu
>
Re: Serialization Problems
Posted by Srinath Perera <he...@gmail.com>.
you do not need to serialize the engine as the engine is stateless.
Serializing the MessageContext and runing in with the correct
EngineConfiguration (the deployment Info) and message context should
do.
There are problems seralizing MessageContext, since it store anything
in the form of properties.
On Mon, 18 Oct 2004 12:09:36 +0530, Krishnendu Kunti
<kr...@infosys.com> wrote:
>
> Hi
>
> I tried serializing org.apache.axis.AxisEngine and
> org.apache.axis.Message from a MessageContext and storing the same in a
> databse a blob. Though both these classes implements
> java.io.Serializable but internally they use some classes which are not
> Serializable.... and hence effectively are non serilalizable.
>
> In case of org.apache.axis.AxisEngine , it references
> org.apache.axis.utils.cache.ClassCache class which is non serializable.
>
> In case of org.apache.axis.Message , it contains a private variable
> MessageContext which is non serializable.
>
> Please suggest if it should be reported as Bug ..
> Thanks
> Regards
> Krishnendu
>
RE: Serialization Problems
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi,
I don't think it is a bug, but a possible improvement that we can do.
Axis is on its way to the new version that is Axis2 and it is better if we
can eliminate this issue in the new version.
Thanks,
Jaliya
-----Original Message-----
From: Krishnendu Kunti [mailto:Krishnendu_Kunti@infosys.com]
Sent: Monday, October 18, 2004 12:40 PM
To: fx-dev@ws.apache.org; axis-dev@ws.apache.org
Cc: Jaliya Ekanayake
Subject: Serialization Problems
Hi
I tried serializing org.apache.axis.AxisEngine and
org.apache.axis.Message from a MessageContext and storing the same in a
databse a blob. Though both these classes implements
java.io.Serializable but internally they use some classes which are not
Serializable.... and hence effectively are non serilalizable.
In case of org.apache.axis.AxisEngine , it references
org.apache.axis.utils.cache.ClassCache class which is non serializable.
In case of org.apache.axis.Message , it contains a private variable
MessageContext which is non serializable.
Please suggest if it should be reported as Bug ..
Thanks
Regards
Krishnendu
RE: Serialization Problems
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi,
I don't think it is a bug, but a possible improvement that we can do.
Axis is on its way to the new version that is Axis2 and it is better if we
can eliminate this issue in the new version.
Thanks,
Jaliya
-----Original Message-----
From: Krishnendu Kunti [mailto:Krishnendu_Kunti@infosys.com]
Sent: Monday, October 18, 2004 12:40 PM
To: fx-dev@ws.apache.org; axis-dev@ws.apache.org
Cc: Jaliya Ekanayake
Subject: Serialization Problems
Hi
I tried serializing org.apache.axis.AxisEngine and
org.apache.axis.Message from a MessageContext and storing the same in a
databse a blob. Though both these classes implements
java.io.Serializable but internally they use some classes which are not
Serializable.... and hence effectively are non serilalizable.
In case of org.apache.axis.AxisEngine , it references
org.apache.axis.utils.cache.ClassCache class which is non serializable.
In case of org.apache.axis.Message , it contains a private variable
MessageContext which is non serializable.
Please suggest if it should be reported as Bug ..
Thanks
Regards
Krishnendu