http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19682
http://marc.theaimsgroup.com/?l=axis-dev&m=105354748107569&w=2
-- dims
--- Dan Kamins <[EMAIL PROTECTED]> wrote:
>
> How specifically has this problem been fixed? I'm looking at the samples/faults
> example in v1.1
> and I can see now tha
How specifically has this problem been fixed? I'm looking at the samples/faults
example in v1.1 and I can see now that a RemoteException (not AxisFault) is being
thrown, and that it has a bean typeMapping in the wsdd. But what control does a
developer have over this mapping? This should be e
We are NOT going to change the way wsdl2java generates code...In 1.1, you can register
your own
exceptions and throw/catch them. Look at samples\faults
-- dims
--- Peter Landmann <[EMAIL PROTECTED]> wrote:
>
> Dear Dvanum,
>
> Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> > Dan,
> >
> > This p
Dear Dvanum,
Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Dan,
>
> This problem has been fixed already in 1.1
I am using the 1.1 release version (I never tried it with 1.0). Last week I
even tried one of the nightly builds, but the problem is still the same,
and wsdl2java generates the same exc
Dan,
This problem has been fixed already in 1.1
thanks,
dims
--- Dan Kamins <[EMAIL PROTECTED]> wrote:
>
> I faced the same problem (can't throw app-specific exceptions) and solved it by
> subclassing
> AxisFault for all of my exceptions. It allows me to explicitly set text for the
> actor,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
I faced the same problem (can't throw app-specific exceptions) and solved it by
subclassing AxisFault for all of my exceptions. It allows me to explicitly set text
for the actor, code, details, etc. fields of the SOAP fault fairly easily in the
constructors of the exceptions.
That being said,
Hi,
Once again, as no one replied: Did really no one else face this problem up
to now? Don't you use exceptions in your service interfaces?
I took a look on the JAX-RPC specification 1.0 now: It defines that service
specific exceptions must extend java.lang.Exception - and not something
like Remo
Hello all,
I use Axis 1.1 and would like to work with custom exceptions. I generated
the client side code with wsdl2java, and the generated client stub
correctly declares these exceptions, but unfortunately the deserialization
doesn't seem to work: I get an AxisFault instead of my self-defined
exc
Hi all,
I took a look on the exception classes generated by wsdl2java and got it to
work now: The point seems to be that the exception class needs to be
derivated from AxisFault, then the deserialization works.
I'm not happy at all to have to derivate my exceptions from AxisFault, as I
want to k
12 matches
Mail list logo
