You live and learn! Thanks, Michael.
But I guess this demonstrates that they're
not really designed for stand-alone use, despite the fact that they can
be used that way. I don't know if the SerializationContext constructor
is a "public" API that won't change.
Tony
"Michael Schuerig" <[EMAIL PRO
On Tuesday 23 November 2004 09:27, [EMAIL PROTECTED] wrote:
> I don't think that the BeanSerializer, or any Axis serializer, can be
> used on its own. It works via callbacks from Axis, in a particular
> serialization context. I don't think it has an methods that can
> simply serialize an object to
I don't think that the BeanSerializer, or
any Axis serializer, can be used on its own. It works via callbacks from
Axis, in a particular serialization context. I don't think it has an methods
that can simply serialize an object to an XML string, or an XML document.
Tony
-Original Message---
Title: BeanSerializer
If you
just want to serialise java objects to xml, you could look at
java.beans.XMLEncoder.
However, if you want to see how axis does it this won't
help.
-Original Message-From: Levy, Avi
[mailto:[EMAIL PROTECTED]Sent: Tuesday, 23 November 2004
9:54 AMTo
The following code posted by Michael
Binz could help you.
-- START--
package .util;
import java.io.IOException;
import java.io.StringReader;
import java.io.StringWriter;
import java.io.ByteArrayInputStream;
import java.lang.reflect.Method;
e: Mon, 6 Sep 2004 09:42:44 +0200
Subject: Re: BeanSerializer
To: [EMAIL PROTECTED]
hi Mahen,
thanks for your comment... one more question... what about if the
"sub-bean" is an abstract bean-class or the root
of a inheritance-hierarchie? Is this a problem or transparent for the
devep
hen Perera <[EMAIL PROTECTED]>
06.09.2004 08:21
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: BeanSerializer
Hi Sandro,
if the sub beans are also specified using the tag,
then
there should be no problem. No need to use Custom
Serialization
Hi Sandro,
if the sub beans are also specified using the tag, then
there should be no problem. No need to use Custom
Serialization/Deserialization
Hope this answers ur Q.
Mahen
- Original Message -
From: Sandro Ruch <[EMAIL PROTECTED]>
Date: Mon, 6 Sep 2004 08:18:36 +0200
Subject
MAIL PROTECTED]
Sent: Monday, June
28, 2004 1:01 PM
To: [EMAIL PROTECTED]
Subject: RE: BeanSerializer and
xml attributes
Per the definition of
"wrapped" in JAX-RPC (and in the way .NET works), wrapped does not
support attributes - only a sequence of elements.
From: We
AIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: BeanSerializer and xml attributes
Date: Mon, 28 Jun 2004 13:01:06 -0700
Per the definition of "wrapped" in JAX-RPC (and in the way .NET works),
wrapped does not support attributes - only a sequence of
Per the definition of “wrapped”
in JAX-RPC (and in the way .NET works), wrapped does not support attributes –
only a sequence of elements.
From: Wei Hsu
[mailto:[EMAIL PROTECTED]
Sent: Monday, June 28, 2004 11:56
AM
To: [EMAIL PROTECTED]
Subject: BeanSerializer and xml
attribut
EMAIL PROTECTED]'
Subject: RE: BeanSerializer
Hi Tom
I think what I was really asking was if there was a way to turn off
serialization in Java2WSDL for certain properties? Is it
something that other users have requested? It would help me as I have a lot
of prexisting classes, some of which
:47 PM
To: '[EMAIL PROTECTED]'
Subject: RE: BeanSerializer
All the data in the Bean is serialized, so all the element show up in the
Schema. It's the other sides responsibility to deserialize the data in to a
data type. The thing on the other end of the wire may not be Java,
All the data in the Bean is serialized, so all the element show up in the Schema.
It's the other sides responsibility to deserialize the data in to a data type. The
thing on the other end of the wire may not be Java, or may not have access to the
original Java type. For instance WSDL2Java wi
Joel,
Creating complex object graphs is the most difficult part of Java/XML
serialization and deserialization (no duh right :-). Well, in your case it
looks like, unless MyObject also conforms to the JavaBean paradigm, you
need to write some classes to handle serialization. Classes like
MyObjec
Title: RE: BeanSerializer support array properties?
i had a similar problem and adding a no argument constructor seemed to fix it. it seems that the BeanSerializer is perhaps not very good at letting you know if your bean does not comply with the java beans spec.
-Original Message
To answer my own question, yes, apparently it expects both getters and setters, so
I've added the appropriate setters.
It's still not quite there, though because now it creates the type definition for the
main object, but it's not creating type definitions for the contained classes.
For exampl
oops... its BeanDeserializer that throws the exception. The serializer
seems to work fine.
Vikram Rayabhari wrote:
> I have a property in a bean that is declared as
>
> private MyInterface intf;
>
> This property is always null and will never change in my application.
> Currently the BeanSeriali
18 matches
Mail list logo
