hi,
I am trying out some examples with JMS and AXIS.
I send a soap request over JMS to a web service. And I get the response
also back thru the JMS. Now I have a handler at the client end which
takes the SOAP message from the JMS message and places it in the
MessageContext Object so that AXIS
Total newbie here, I will confess that up front.
I am trying to deploy a java-based webservice on axis 1.1, but appear to
have something wrong somewhere.
When I run the admin client, I get this message:
==
Processing file
Funny,
I was just getting this error yesterday. I'm still using Axis 1.1, and the
IncompatableClassChangeError was due to a compiled version of a .jar file (not
necessarily the axis jar) using newer API's than the JVM it was running in.
I believe that is one of the main reasons for
To answer your second question first:
The easy/fun/pretty solution is to write out the wsdl for the array
container and then use the WSDL2Java tool(using the generate stubs and
skeletons option... Read about it in the axis user guide) to have axis
libraries automatically generate all the classes
i have created a very simple web service using doc/literal encoding to try to test
string arrays. my very simple example as a single method:
public Bean execute(Bean bean) {
return bean;
}
a Bean is simply:
public class Bean {
private
Try putting the jar file (and if that fails... The class files
themselves) with com.mwt.bean.BookInfoResponseType (and other classes
your implementation uses) into
webapps/axis/WEB-INF/classes/nameofyourwebservice/
This seems to be the place that axis looks for any and all classes
having to do
Actually, I think I shot myself in the foot. :-(
I am trying to deploy to a context other than /axis/, but did not tell
the AdminClient that.
Duh! Heheh, oh well, at least it is Friday, right?
I will try again at lunch time and post the results...hopefully this
will save some other poor idiot
can someone please explain to me the interop issues with rpc vs. doc literal.
specifically, what datatypes (arrays, nested complex types, etc) will interop.
i am writing some web services and need to support .net and gsoap clients. rpc seems
a lot easier, but not if it won't interop with all
The issues are basically this:
1. With rpc/enc there are many valid ways to say the same thing. If
the soap stacks you are interested in have implemented the same subset
of these options your all set - kind of.
2. With doc lit there is one way to serialize a message and its
described
Whilst everything Jim said is true, rpc/enc has been around the longest
in the current tools and I think interop is pretty good. Doc/lit is the
way to go long term, but I think interop today for doc/lit sucks,
because every tools supports different subsets of XML Schema.
Cheers
Simon
Hi,
I get the following exception on the client which uses proxies.
I have created a constructor on the Person class mentioned below.
What else can I do on the client to get my client working?
The server does not show any exceptions. In fact the SOAP monitor shows
that the response message
Apologies up front - I'm still new to Axis...
I've been folowing the Axis / Castor write up over on IBM's web site. I've
done everything in the writeup and understand (I think) up thru the deploy
step.
My environment:
Linux
Tomcat 5.0.25
Axis 1.2 beta 3
I've put together a WSDL for a User
Hmmm, it does seem that you have everything reference and such, which is
cool, and you say you have all the serializing worked out...
You have an extra wsdl:types element in your wsdl... But it might not
be the problem
The problem might be that axis doesn't seem to like upper-case starting
Whilst everything Jim said is true, rpc/enc has been around the longest
in the current tools and I think interop is pretty good. Doc/lit is the
way to go long term, but I think interop today for doc/lit sucks,
because every tools supports different subsets of XML Schema.
I can second this. In
Hi, All,
There has been discussion about the wrapper style and the attributes
in the past. And Axis does not support wrapper element attributes since
JAX-RPC spec says that the wrapper element should not have attributes. I
have no problem with it. But I do like people to clarify the following
A speculation (I'm not an expert):
If you have
wrapper someatt=somevalue
part1.../part1
part2.../part2
/wrapper
being converted to a method call on the server:
ServiceClass.someMethod(part1, part2)
the attributes are lost. There is no way in wsdl to specify parts
16 matches
Mail list logo
