axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Davis" <...@us.ibm.com>
Subject RE: faults
Date Thu, 06 Dec 2001 17:49:59 GMT
unless I'm doing something totally wrong, it still fails with the latest
alpha-3 and HEAD.
-Dug


Glen Daniels <gdaniels@macromedia.com> on 12/06/2001 12:13:04 PM

Please respond to axis-dev@xml.apache.org

To:   "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
cc:
Subject:  RE: faults




Already backported to a3 in the tree, but Sam probably hasn't cut a new
release zip yet.

--G

> -----Original Message-----
> From: Doug Davis [mailto:dug@us.ibm.com]
> Sent: Thursday, December 06, 2001 12:12 PM
> To: axis-dev@xml.apache.org
> Subject: RE: faults
>
>
> Try it on the alpha - that's what i'm using and have to use right now.
> If you have fixed it since the alpha then we need to migrate that fix
> back.
> -Dug
>
>
> Glen Daniels <gdaniels@macromedia.com> on 12/06/2001 12:08:28 PM
>
> Please respond to axis-dev@xml.apache.org
>
> To:   "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
> cc:
> Subject:  RE: faults
>
>
>
>
> This was definitely working (returning a ClassNotFound wrapped in an
> AxisFault) yesterday, still works for me today.  I did do
> some work on it
> at
> some point recently, though - try updating.
>
> I'm still cleaning up a few things wrt faults, but I know this works.
>
> --G
>
> > -----Original Message-----
> > From: Doug Davis [mailto:dug@us.ibm.com]
> > Sent: Thursday, December 06, 2001 11:54 AM
> > To: axis-dev@xml.apache.org
> > Subject: RE: faults
> >
> >
> > Try using:
> >  <deployment    name="test" xmlns="http://xml.apache.org/axis/wsdd/"
> >                         xmlns:java
> > ="http://xml.apache.org/axis/wsdd/providers/java"
> >                         xmlns:xsi
> > ="http://www.w3.org/2000/10/XMLSchema-instance">
> >   <typeMapping xmlns:echo="http://soapinterop.org/xsd"
> >     qname="echo:SOAPStruct" languageSpecificType
> > ="java:samples.echo.SOAPStruc11t"
> >     serializer="org.apache.axis.encoding.BeanSerializer"
> deserializer
> > ="org.apache.axis.encoding.BeanSerializer$BeanSerFactory"/>
> > </deployment>
> >
> > Notice the "11" in the classname.  I don't think this is the
> > exact thing I
> > was doing but this does show the problem.
> > -Dug
> >
> > Tom Jordahl <tomj@macromedia.com> on 12/06/2001 11:40:10 AM
> >
> > Please respond to axis-dev@xml.apache.org
> >
> > To:   "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
> > cc:
> > Subject:  RE: faults
> >
> >
> >
> >
> > Glen and I did some reworking of AxisFault this week.
> > Perhaps we missing something?
> >
> > How can I duplicate it?  I am tied up most of today, but I
> > can try to check
> > it.
> > --
> > Tom Jordahl
> >
> >
> > -----Original Message-----
> > From: Doug Davis [mailto:dug@us.ibm.com]
> > Sent: Thursday, December 06, 2001 11:33 AM
> > To: axis-dev@xml.apache.org
> > Subject: Re: faults
> >
> >
> > Stuck looking at another bug - but has anyone worked on
> > how faults are returned recently?  I think I've seen over
> > cases where faults are being thrown but all we get back
> > in a 500 + empty body.
> > -Dug
> >
> >
> > James M Snell/Fresno/IBM@IBMUS@IBMUS on 12/06/2001 11:30:17 AM
> >
> > Please respond to axis-dev@xml.apache.org
> >
> > To:   axis-dev@xml.apache.org
> > cc:
> > Subject:  Re: faults
> >
> >
> >
> > I don't know about now, but a few days ago (Saturday) I was
> > getting the
> > class not found error back.
> >
> > - James M Snell/Fresno/IBM
> >     Web services architecture and strategy
> >     Internet Emerging Technologies, IBM
> >     544.9035 TIE line
> >     559.587.1233 Office
> >     919.486.0077 Voice Mail
> >     jasnell@us.ibm.com
> > =================================================================
> > Have I not commanded you?  Be strong and courageous.  Do not
> > be terrified,
> >
> > do not be discouraged, for the Lord your God will be with you
> > wherever you
> > go.
> > - Joshua 1:9
> >
> > Please respond to axis-dev@xml.apache.org
> > To:     axis-dev@xml.apache.org
> > cc:
> > Subject:        faults
> >
> >
> >
> > When I deploy a service or handler that uses a class that it
> > can't find I
> > *think* I used to be able to see the "class not found" error
> > back on the
> > client - now I just get a soap-env with an empty body back
> > from the server
> > - is anyone else seeing this?
> > -Dug
> >
> >
> >
> >
> >
> >
>
>



Mime
View raw message