Thanks. I have the general problem that I'm trying to bring the world of
apache axis (soap) genereated objects for together with castor. I would like
to use the same objects for both mapping to soap rpc and usual xml instance
documents.
What I mean is that I want to be able to both serialize the objects in to soap
messages and xml confirming to the schema.
Any hints?
-David
On Wednesday 30 July 2003 20:17, Keith Visco wrote:
> Because Castor assumes that if you are marshalling an object, you are
> probably going to also want to unmarshal.
>
> You can get around this by disabling the constructor check for a
> specific class...but then you may not be able to unmarshal.
>
> <class name="foo" verify-constructable="false">
>
> --Keith
>
> David Kocher wrote:
> > Hi castor users,
> > I would like to write some objects to an xml which do not have a
> > constructor with no arguments.
> >
> > >From castor I get the following exception:
> >
> > org.exolab.castor.mapping.MappingException: The Java class
> > ch.itserve.MyClass is not constructable -- it does not contain a default
> > public constructor
> >
> > Why does castor attempt to make new instances of the class? I assumed all
> > it needs to to is fetching the values with the getter methods.
> >
> > Thanks for clarification!
> > - David
> >
> > -----------------------------------------------------------
> > If you wish to unsubscribe from this mailing, send mail to
> > [EMAIL PROTECTED] with a subject of:
> > unsubscribe castor-dev
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
