You mean method overloading.
I think, in general, this should work; it may well be a bug in Axis.
-- Oliver
Jim Hazen wrote:
>
> I have a simple class (listed below). I would expect it to be a trivial
> case to determine which method to call. After all the signature is
> nothing alike (eithe
Could this be added?
-- Oliver
Tom Jordahl wrote:
>
> I believe you can deploy a service with document style and we will generate doc/lit
>WSDL. I don't think there are switch in Java2WSDL to do this.
>
> --
> Tom Jordahl
> Macromedia
>
> -Original Message-
> From: OBRADOVIC,PETAR (
iscussion on why on the dotnet list hosted at
> discuss.develop.com.
>
> Anyhow I think I've ranged far enough off topic now. Sorry for the
> diversion.
>
> -Original Message-
> From: Oliver Suciu [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 19, 2002 1:30
ual java class name of the
>exception in the faultDetails element, but this is non-standard (i.e. we made this
>up).
>
> --
> Tom Jordahl
> Macromedia
>
> -Original Message-
> From: Oliver Suciu [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 19, 2002 4:30 PM
&g
ment (IIRC).
>
> -----Original Message-
> From: Oliver Suciu [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 19, 2002 10:49 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: .Net ignores ?
>
> Hi all,
>
> (Sorry, this one is somewhat geared towards
Hi all,
(Sorry, this one is somewhat geared towards .Net...)
I've got an Axis service that throws an exception, and WSDL2Java
correctly generates a for the .
However, the .Net wsdl.exe seems to completely ignore the ,
and no corresponding client-side code is generated.
Has anybdoy got this wo
Hi all,
(This may be a FAQ, not sure...)
How can I get a service-specific exception passed back properly
(proper type, etc) to the invoking client?
My service interface looks somewhat like this:
> public TestType test(TestType data) throws TestExc;
The generated WSDL contains the proper typede
Not sure about "List", but if you can live with an "Object[]",
the attached WSDL works (your WSDL hacked so that .Net wsdl
compiles it).
Maybe it even works with "List", give it try, you never know.
In any case you'll get an "object[]" on the .Net side.
Why this WSDL works and not the one genera
It works for me (.Net Framework 1.0.3705.0)...
-- Oliver
Russell Butek wrote:
>
> soap-enc:Array is a SOAP 1.2 creature. MS probably only supports SOAP 1.1.
> Try creating WSDL using Java2WSDL with the following option:
> --typeMappingVersion 1.1.
>
> Russell Butek
> [EMAIL PROTECTED]
>
> "E
Hi all,
Has anybody managed to get a .Net client talk to an Axis service,
using a session context?
I've got an Axis (beta1) web service talking successfully
with both an Axis and a .Net (beta2, C#) client.
I've also added session management on the server side:
- MessageContext.getCurrentContex
SoapTypeAttribute("Book", "urn:SomeUniqueThing")]
> [System.Xml.Serialization.SoapIncludeAttribute(typeof(Novel))]
> public abstract class Book {
>
> ///
> public BookId bookId;
> }
>
> ///
> [System.Xml.Serialization.SoapTypeAttribute("Novel",
Hi all,
Would the following work in Axis? And in JAX-RPC?
// the service to be exposed:
public interface MyServiceProvider extends java.rmi.Remote {
public MyData doSomething(MyData someData) throws java.rmi.RemoteException;
}
// the interface that all data objects must implement:
public inte
Quite the opposite -- it rather seems that Axis is emerging
as the standard Java web service container, with support for
Sun's JAX-RPC API.
To me, it seems more like Axis is starting to become to
web services (and JAX-RPC) what Tomcat is today for JSP &
servlets -- the reference implementation.
Hi,
Is there a target date for the beta release?
Thx,
-- Oliver
Thanks.
Let's hope this (or something similar) makes it into JAX-RPC as well...
-- Oliver
"Adam.Leggett" wrote:
>
> See Glens reponse to this post
>
> http://marc.theaimsgroup.com/?l=axis-user&m=101413005300555&w=2
>
> -Original Message-
>
I am with you -- every non-trivial (web) app requires session management.
And just as servlets have added HttpSession on top of the stateless
HTTP, *something* should be added on top of SOAP (SoapSession?).
Note that this is *not* addressed by the current JAX-RPC spec.
But perhaps in Axis? (I'm
16 matches
Mail list logo