#x27;s and
> other test cases ?
>
>
> Please execuse me if I am really dumb !,
> Kumar.
>
>
> On Wed, 9 Feb 2005 14:34:01 +0100, Bouche Paul
> <[EMAIL PROTECTED]> wrote:
> > yes as fas as I understand this is where the test cases and
> wsdd's
Download the axis source distribution from the latest cvs or better a stable
source (1.2rc2) so it will compile.
-- Paul
> -Original Message-
> From: babloosony [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 9. Februar 2005 14:18
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re
I am amazed to see that other are also interested in doing enumerations. But I
guess you are coming for the XML presepctive. The answer to your questions is
yes. See the following for detials.
I am still wondering if Axis will ever support Java 1.5 Enums.
-- Paul
snip JAX-RPC Spec
First of you cannot automatically serialized any arbritrary java object with
Axis (it wouldn't know how). For Axis to automatically serialize/deserialize
your objects they need to be Java Bean compatible (if you don't know what that
is google for java beans). One of the requirements for a java b
Hi,
I habe the following problem
I have an interface similar to this
public interface IWebService
{
public RequestSearchResult requestSearch(SearchRequestBase[]
searchRequests);
}
and the classes look the following
the ReqeustSearchResult is not the problem
public abstract class SearchReq
Is the wsdl correct?
I remember seeing the problem and its discussion before on this list. You
might want to search the archives at the list. I just did that and check this
out http://issues.apache.org/jira/browse/AXIS-1331.
-- Paul
> -Original Message-
> From: Antonio Ruiz Martínez [
Hi,
I habe the following problem
I have an interface similar to this
public interface IWebService
{
public RequestSearchResult requestSearch(SearchRequestBase[]
searchRequests);
}
and the classes look the following
the ReqeustSearchResult is not the problem
public abstract class SearchReq
Does anyone know how to include the documentation tag in the automatic wsdl
generation in axis?
What I actually want is when my web service endpoint is called via
http://...?wsdl that the returned wsdl will include documentation about the web
service with a documentation tag that I told axis be
According to the axis doc and the jax-rpc spec. The following is true
XML <-> Java Data Mapping in Axis
How your Java types map to SOAP/XML types
Interoperability, interop, is an ongoing challenge between SOAP
implementations. If you want your service to work with other platforms and
implement
Hi,
> Upon further review, I discovered that the
> org.w3c.com.Node interface has the new method
> "getUserData(String key)" in Java 1.5. I'm sure this
> is the reason for all the errors - interfaces not
> fully implemented.
I also got these errors when trying to build axis with Java 1.5. Yet thi
I am using Axis 1.2rc2 and am talking to a Web Service using Axis 1.1 final
which I have no control over.
I noticed that the detail information of the Axisfault was lost, not
deserialized correctly by Axis 1.2rc2.
The service is a RPC style service.
Did anyone notice similiar behaviour?
-- Pau
Dalibor,
response see below...
> -Original Message-
> From: Dalibor Dostál [mailto:[EMAIL PROTECTED]
> Sent: Dienstag, 19. Oktober 2004 14:51
> To: [EMAIL PROTECTED]
> Subject: Re: HashMap problem
[...]
> What kind of service style do you use? - I don´t understand this
> question. We j
What kind of client do you use? What kind of service style do you use?
java.util.HashMaps are not all that interoperable. They only work with modifications
to generated code. Does Axis maybe serialize the request is gets in into a different
object?
-- Paul
> -Original Message-
> From
Does anyone here know here when and if AXIS will support Java 5 esp. serialization of
enum types?
Thanks for any input,
paul
.
Tami, what version of AXIS are you using? AXIS 1.1 final has very poor support for
doc/lit.
Maybe this creates the different view.
> -Original Message-
> From: Nelson Minar [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 30. September 2004 01:42
> To: [EMAIL PROTECTED]
> Subject: RE: Arra
Does anyone here know here when and if AXIS will support Java 5 esp. serialization of
enum types?
Thanks for any input,
paul
.
>
> Hi,
>
> I am also using HashMaps, but only in AXIS - so I am
> interessted in your
> solution for Interoperability reasons
>
> Thanks Tomi
>
> ------
> --
> ---
> T-Systems
; at
> org.apache.axis.encoding.DeserializationContextImpl.startEleme
> nt(Deseria
> lizationContextImpl.java:963)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventReco
> rder.java:
> 198)
> at
> org.apache.axis.message.MessageElement
I have been reading the recent discussions about interoperability esp. with .NET
sending arrays, using WSDL and so forth and the suggested method was to write
interfaces use java2wsdl to get a starting wsdl then edit it and generate the actually
service stubs and skeletons with wsdl2java.
Now a
If anyone is interested I have managed to receive a java.lang.util.HashMap with .NET
returned by an AXIS web service. During the process of trying to work that out I also
found out that the root of the problem was a namespace differrency: .NET interpreted
the namespaces of the WSDL false and ad
Hello,
from my understanding I think you don't have to specify the wsdl you can. AXIS should
automatically generate it. It seems to me like you did not copy the .class files or
the package into the WEB-INF\classes directory of axis. Maybe you also did not
specify the right value for
in your
The latest releace of Java AXIS has been Java AXIS 1.2 beta 3
(http://www.apache.org/dist/ws/axis/1_2beta3/) and this folders date is August 17th
2004. They must have forgotten to post this at the web site (either intendend or
unintended ;-). But I am wondering about the same thing: AXIS C++ s
TED]
> > Sent: Mittwoch, 22. September 2004 17:08
> > To: [EMAIL PROTECTED]
> > Subject: Re: "Strange" format of RPC/encoded messages
> >
> > Yes I agree with all this. I would ask if you are interested
> > in readability why not chose to implement
Patrick,
What I write know is what I understand from talking to others (credit be to them ;-)
and reading the spec.
The references you see are the normal behaviour of the /encoded use of the parameters
(here RPC/encoded). This is to allow serialization of complex object graphs (with
cyclic ref
Hello,
from
my understanding to previous posts and reading the bug data
base:
There
is a bug in Axis 1.2 beta 3, work in progress respectively sending arrays of
simple types in Axis 1.2 beta 3 with document/lit encoding. I also
understand that the developers are working on this with high
Hi,
what exactly do you need to do? When you encode the AXIS service with DOC / lireral
then that creates a lof of problems on the AXIS side, sometimes AXIS creates DOC /
encoded types which is not valid (in a DOC/literal context) and .NET does not handle
them. When you encode the AXIS servic
Hello,
I use this list for
the first time and maybe this problem has been posted before, if so then please
point me to a solution.
when trying to return an array of integers for
intance there is the following problem trying to generate a DOC style
service. AXIS still generates a WSDL do
27 matches
Mail list logo
