Hi,
we're facing two problems that seems different but also related, with
typeMapping and beanMapping in a WSDD file.
The second one will be in another mail ;)
We're trying to expose, in RPC/Literal style, the following java class :
public class BusinessStructImpl {
public SimpleBean
Hi,
and now, the second problem !
It's more like a problem with arrays.
We're still trying to expose, in RPC/Literal style, the following java
class :
public class BusinessStructImpl {
public String[] echoStringArray(String[] param) {
return param;
}
public ArrayBean
Frank-Ralph Reiser a écrit :
One of my web service classes deployed with axis has e.g. a method
public Data findCityByName(String name) {...}
which returns a Data object containing an array of City objects.
Consuming that webservice using an JSP client with generated stubs by wsdl2java
and either
Ellecer Valencia a écrit :
(i'll probably be told to create WSDL first... but if so, why then do
we have java2wsdl?)
You can generate a first draft with java2wsdl, modify it according to
your needs, and use wsdl2java afterwards :)
--
Julien
Robert Bateman a écrit :
I tried that Karim. I can see my service, but it appears I have something
mis-configured in my service as I can't seem to get the WSDL to display.
I think you have to specify the wsdl file in your wsdd.
http://www.osmoticweb.com/axis-wsdd/wsdlFile.htm
also in
Axel Bock a écrit :
Keith Hatton wrote:
Try not using long directory names with spaces in them when you're
setting
the CLASSPATH. I think your AXIS_HOME variable (C:\Programme\Apache
Software Foundation\Axis1.2b) or TOMCAT_HOME is the problem. The Java
interpreter is having a problem with the
Martin Kuba a écrit :
Hi,
However it is much slower than Axis 1.1. I have a simple
webservice for measuring the speed, and it show that
1.2 is about three times slower. The exact results are:
Axis1.1 server / Axis1.1 client - 192 calls/sec
Axis1.2 server / Axis1.2 client - 67 calls/sec
Michael Schuerig a écrit :
I'm still pretty new to web services in general and Axis in particular.
I have a case, where I don't want to generate the value returned from a
call not from objects. I have the ResultSet from a database query and
would like to avoid first binding its rows to objects
Maybe, you can try to generate a service skeleton from your modified
wsdl file... ?
Jairam, Roopnaraine a crit :
Please help.
*From:* Jairam, Roopnaraine
*Sent:* Monday, October 18, 2004 10:03 AM
*To:* [EMAIL PROTECTED]
Koney, Satish a écrit :
If I develop a web service using axis, SHOULD the axis be deployed as web
application in the server ??
or is there any other way?
It's the way it works. It's a servlet, so you need a servlet container,
such as tomcat.
--
Julien
Vy Ho a écrit :
Also, unzip the axis.jar file, I do not see the package there either.
It's only on the CVS trunk :
http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/constants/
You must either :
- wait for the next Axis release
- checkout the CVS version
--
Julien
Hi,
We have a strange bug in axis 1.2RC2, dealing with array of beans.
There is a method whose signature is :
public ArrayBean echoArrayBean(ArrayBean param);
ArrayBean is defined like this :
public class ArrayBean implements Serializable {
private String stringData;
private SimpleBean[]
Christian Kalkhoff a crit :
Hi,
i want to use the axis soap client to connect to php 5.0.2. soap server.
Unfortunally the server is not in may hand, so i cannot change it to
java.
It seems that php soap library doesn't understand the id href tags in
axis generated messages.
Do you mean
and setter from simpleBeanArrayData
but also a getter and setter by index, getSimpleBeanArrayData(int i) and
setSimpleBeanArrayData(int i, SimpleBean bean).
This keeps Axis from generating the ArrayOf_ type (which is not valid based
on the WS-I spec).
-Original Message-
From: WAJSBERG Julien RD-BIZZ
Tim Dev a écrit :
Hi,
I have a simple test method:
Long foo(Long bar)
Java2WSDL maps the Long to xsd:long and the client stub contains the
method as:
long foo(long bar)
How does the WSDL look like ? The parameter and return value should have
a nillable='true' attribute, otherwise I guess it's
Montabert, Olivier a écrit :
Hi,
The problem is that you have a WSDL with multiple parts in doc/lit
mode, which is not WS-I compliant.
Either change your operation, or use rpc/literal instead.
or rather wrapped/literal.
--
Julien
Daniel Beland a écrit :
I had the same problem, and someone gave the answer earlier in another
thread.
You need a class that contains only the array and no more attributes with
the standard get/set methods + getX(int i) and setX(int i, X x) methods.
And your MyService class can return this class
Tim Gmane a écrit :
WAJSBERG Julien RD-BIZZ wrote:
Tim Dev a écrit :
Hi,
I have a simple test method:
Long foo(Long bar)
Java2WSDL maps the Long to xsd:long and the client stub contains the
method as:
long foo(long bar)
How does the WSDL look like ? The parameter and return value should
have
Simon Fell a écrit :
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tim K. (Gmane)
Sent: Monday, November 29, 2004 7:20 PM
To: [EMAIL PROTECTED]
Subject: Re: long vs. Long
If anyone else has an example on how to get the Long stuff to
work end-to-end and to
Vy Ho a écrit :
Looking at the reference for Java2Wsdl, there's this line:
-y, --styleThe style of binding in the WSDL, either
DOCUMENT, RPC, or WRAPPED.
That means you can pass in DOCUMENT as the style when generating the
wsdl to say that you want DOCUMENT style messaging.
Be
I also have a service returning byte[], and it is correctly serialized
as xsd:base64Binary (both in wrapped/literal and rpc/encoded styles) .
James Black a écrit :
I am using Axis 1.2RC2 and I have a function:
public byte[] lookupSelectLocationsString(Item input)
~From the wsdl file I have this:
Eyad Garelnabi a crit :
Hi,
Im interested in having the client call one of two (or three) methods
that are within the same web service. Im using currently using
message style webservices and through the research Ive done so far
it seems to me that with message style I cant have multiple methods
yes
otherwise, you can configure another variable with this specific
classpath (like AXISCLASSPATH), and use this one when you launch the
java interpreter :
java -cp %AXISCLASSPATH% AdminClient ...
(or java -cp $AXISCLASSPATH with unix).
(maybe double quotes if you have spaces in your
Hi,
I found once that interoperability for HashMap of Strings is good
between axis 1.1 and Perl, using RPC/Encoded.
using literal encoding, it doesn't work anymore.
The problem is that you will need wrapped/literal mode for
interoperability with .Net :)
So, Anne is right, you should avoid
Ephemeris Lappis a écrit :
Thanks for your feedback. Bad news !...
I'd like to have a point of view from the Axis team about this issue. I'm
not currently working a lot in web services domains, but according to what
i've been reading in this list and others, document/literal seems to be
often
Ephemeris Lappis a écrit :
I'm not a SOAP expert ! I think i had understood the difference between
document and wrapped styles, and i suppose tools that will process the
repective wsdl files will not generate similar codes : both use xml messages
without soap encoding, but in document mode the
Daniel Beland a écrit :
In fact, to be more precise, it means that there is a schema element, with
the same name as the operation, that contains (wraps) the actual document
element representing all the parameters.
ie:
wrapped
A
AElement/ (of type X)
/A
document
AElement/ (of type X)
I believe
Jian J Zhang a écrit :
Does AXIS supports WS-RM?
Thanks,
A first implementation exists :
http://ws.apache.org/ws-fx/sandesha/
But I don't know if it's mature.
--
Julien
Ephemeris Lappis a écrit :
Hello.
I'm not sure i have understood it all. Sincerly, i remember, years ago, i
had a look at the CORBA/GIOP/IIOP marshalling protocols, and finished the
day with the same headache ! But, once more, we were lucky : we had IDL to
write our interfaces...
As i understand,
For the difference between wrapped and non-wrapped document-style web
services, you can read the weblog of Anne Thomas Manes :
http://www.burtongroup.com/weblogs/annethomasmanes/archives/2004/04/000187.html
Maybe it will make you better understand :)
(this little article helped me also in the
Vy Ho a écrit :
In client-side stub code, look for the call object and try:
Call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();
--
Lyndon Tiu
I can choose not to use the application scope for now. However, this
shows a very serious problem with the generated
M Litherland a écrit :
Hi all,
I'm new to Axis and I am trying to create a SOAP client to communicate
with a vendor. They have supplied me with the WSDL and I ran
WSDL2Java against it to create my stubs. There are custom headers, so
I specified the '-a' option for WSDL2Java to produce a stub
32 matches
Mail list logo
