Hi Sandro,

If the abstract class or root of an inheritance hierachy is specified
in the WSDD correctly, there should be no problem i guess.

If u explain using some examples, i think i can give a better answer

Mahen


----- Original Message -----
From: Sandro Ruch <[EMAIL PROTECTED]>
Date: 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
deveploper and just a question of correct specification in the
wsdd-file?

Sandro




Mahen Perera <[EMAIL PROTECTED]> 

06.09.2004 08:21 

Please respond to
[EMAIL PROTECTED]


[EMAIL PROTECTED] 

cc

SubjectRe: BeanSerializer











Hi Sandro,

if the sub beans are also specified using the <beanMapping> 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: BeanSerializer
To: [EMAIL PROTECTED]


Hi all, 

Does the beanserializer / deserializer also work if the bean-class has
its "sub-beans"?
We have specified the bean-class unsing the <beanMapping> tag in the
wsdd... but now
we get a saxexception for the next "sub-bean"... 

Is it better in this case to use customized serializer/deserializer? 

Thx, 
Sandro

Reply via email to