Not sure what's so special about an exception. My boolean situations
is as follows:
bean:
public void setPrimary(Boolean arg0) {
generates:
Doc Lit - <element name="primary" nillable="true" type="xsd:boolean"/>
RPC Enc - <element name="primary" nillable="true" type="soapenc:boolean"/>
>From what I've seen java2wsdl will generate a nillable attribute only
if the argument is non-primitive. So, Axis must be seeing your
argument as a boolean when it converts it. If you can absolutely
verify that your java2wsdl will not produce the nillable attribute,
file a bug request.
On 1/10/06, Jarmo Doc <[EMAIL PROTECTED]> wrote:
> I do have a typeMapping for my exception. It was generated for me by
> wsdl2java, as follows:
>
> <typeMapping
> xmlns:ns="x.y.z"
> qname="ns:MyException"
> type="java:x.y.z.MyException"
> serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> encodingStyle=""
> />
>
> I'm assuming that this is perfectly reasonable alternative to a beanmapping.
>
> What I don't understand is why java2wsdl reports that I should register a
> typemapping/beanmapping (does that mean oneor the other? Or both?) for this
> exception when it does not report that for any other user-defined class.
> What's so special about an exeption?
>
>
> >From: Todd Orr <[EMAIL PROTECTED]>
> >Reply-To: [email protected]
> >To: [email protected]
> >Subject: Re: Axis 1.3 suitable for production env?
> >Date: Tue, 10 Jan 2006 10:25:43 -0800
> >
> >#1 - I have been able to avoid all the Exception trouble you mention by
> >simply creating a beanMapping for my custom exception.
> >
> >On 1/10/06, Jarmo Doc <[EMAIL PROTECTED]> wrote:
> > >
> > > I do use document/literal.
> > >
> > > On the #1 issue below, I see the following from java2wsdl:
> > >
> > > - Please register a typemapping/beanmapping for 'xyz.myexception'
> > > - The class java.lang.Throwable is defined in a java or javax package
> >and
> > > cannot be converted into an xml schema type. An xml schema anyType will
> > > be
> > > used to define this class in the wsdl file.
> > >
> > > How do I 'tweak' the WSDL to correct these issues?
> > >
> > >
> > > > > 1. exceptions descending from java.rmi.RemoteException (as per the
> > > Axis
> > > > > sample NoSuchEmployeeFault) cause java2wsdl to report "The class
> > > > > java.lang.Throwable is defined in a java or javax package and cannot
> > > be
> > > > > converted into an xml schema type. An xml schema anyType will be
> >used
> > > >to
> > > > > define this class in the wsdl file."
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
