Don't you mean:
edu.usf.acomp.axis.AxisLMSServer
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
James Black [EMAIL PROTECTED]
06/05/2002 02:44 PM
Please respond to axis-user
To:[EMAIL PROTECTED]
cc:
Subject:re: java2wsdl
(1) The Holder java class is emitted as defined by JSR 101. Probably should remove the // ?++? comment from the emitted code.
(2) I don't have enough information to determine the problem. Please send more info.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
method implementations for my operations.
Am I missing something obvious? Shouldn't the stub compile right away without further modification?
Thank you,
Bryan
P.S. My WSDL file is attached.
xmlacl.wsdl has been removed from this note on June 04 2002 by R J Scheuerle Jr
You forgot the wsdl namespace prefixes on the elements in you binding. For example operation ... should be wsdl:operation
After making the changes, the stub was generated correctly.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Bryan Field-Elliot [EMAIL
There is a problem with calling a service that has an abstract complex type as a parameter. I am working on this right now.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
St-Germain, Sylvain [EMAIL PROTECTED]
05/30/2002 08:31 AM
Please respond to axis-user
The fault contents currently are not passed across the wire.
Use AxisFault.getFaultCode() to get the fault code.
Hope this helps.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Schwartz, Brenton [EMAIL PROTECTED]
05/29/2002 05:03 PM
Please respond to
that this is a deeper problem...
Brent
-Original Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 5:07 PM
To: [EMAIL PROTECTED]
Subject: Re: AxisFault vs SOAP Fault
The fault contents currently are not passed across the wire.
Use AxisFault.getFaultCode
Shinde,
I will try and re-create this problem with the latest version of the code.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Vaishakhi,
Are you using a new version of Axis and perhaps are your fields public?
I see from the original error message that the problem was with field
password and your bean accessors are (apparently) setPasswd and
getPasswd. So if password is sent over the wire and the bean property
is
)
R J Scheuerle
Jr/Austin/IBM@IBMTo: [EMAIL PROTECTED]
US cc
There have been 2 bugzilla defects and some user notes concerning
the new hashCode method generated in the bean classes for
complexTypes. If the bean contains a boolean field, the hashCode method
would not compile.
The problem has been fixed and will be available in the 4/23 build.
Thanks,
Good stuff!
-Original Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 20, 2002 9:26 AM
To: [EMAIL PROTECTED]
Subject: RE: Array deserialization problem
Russell and I talked about
I might have some time Thursday to look at this problem.
Thanks,
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
xsd:nonNegativeInteger is not supported yet.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Alex Krotov
The Java classes generated from your wsdl is correct and compliant with JSR
101.
WSDL2Java only generates classes for the xml constructs that are
referenced, which may be your missing classes problem.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 15, 2002 11:05 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Array complexType
Simon,
Your schema is correct. WSDL2Java will correctly interpret the type as
an
Option[].
However, when the Axis runtime
Simon,
Your schema is correct. WSDL2Java will correctly interpret the type as an
Option[].
However, when the Axis runtime serializes the Option[], it does not know
the name
of the array component element (in your case option).The axis runtime
always uses
the name item when serializing the
- Original Message -
From: R J Scheuerle Jr
Sent: Friday, March 15, 2002 11:14 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: wsdl2java works with all XMLSchema?
Axis does not support all of the XMLSchema primitives. It supports the
ones explicitly listed in JSR 101.
You should
Java2WSDL currently generates mangled operation names when it encounters
overloaded java names.
I don't think your problem is entirely limited to the name attribute on the
input/output parts.
Russell and I will revisit the overloading question...including
roundtripping...after the beta release.
Carsten,
I don't know what level of Axis you are using, but there have been a number
of improvements
to the code associated with the serialization of byte[]. You may want to
checkout a nightly build.
Hope this helps.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
)
R J Scheuerle
Jr/Austin/IBM@IBMTo: [EMAIL PROTECTED]
US
Use the axis wsdl2java tool.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Stefan Taubenberger
Rania,
There have been quite a few changes to the serialization framework.
The multi-referencing support is done in the DeserializerImpl and
DeserializationContext, and should
work without intervention.
Why do you need you need the name of the element in these cases ?
(Please contact me
Egger,
I don't understand your question.
I have done quite a bit of work in the array deserializer and bean
deserializer.
Please send me your wsdl and detailed problem and I can address it.
Thanks for supporting Axis!
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL
before, .NET stubs fail too), it's with the axis service. I've attached as
much of the source code as I can provide.
Dave Dunkin
-Original Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 3:07 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject
Dunkin
-Original Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 3:07 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: array serialization problem (user error ?)
I took a serious look your ServiceOne.wsdl document
use a
sequence compositor instead of an all, but why not use the soap array
encoding? I believe the the schema in the original wsdl was correct. The
problem is with the way axis builds the response. (btw, the wsdl is from
?wsdl).
Dave
-Original Message-
From: R J Scheuerle Jr [mailto
I took a serious look your ServiceOnewsdl document, and it doesn't appear
to match your response files
Here's a snippet of the response file:
multiRef id=id1 SOAP-ENC:root=0
xsi:type=ns3:ScreenOutputs__Table
xmlns:ns3=http://outputgetOrderDataServiceOneserviceone;
on the
service class when any of its methods use a List as a parameter.
Vikram
R J Scheuerle Jr wrote:
Great observation!
It makes sense to me that the component types of a List object should
always be considered as an Object.
The code should not look at the actual data to determine the type
Could you send me the wsld generated from the classes and the wsdl
generated from ?wsdl.
Are you using the latest axis code?
Also send me your deploy.wsdd file and the java class that implements the
service.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
It is intended to support the requirements of JSR 101.
Other enhancements have been made per user request.
If you have any specific requirements, please post them to the list (or
send me the list offline).
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
)
at org.apache.axis.client.Call.invoke(Call.java:1392)
at org.apache.axis.client.Call.invoke(Call.java:1008)
at localhost.ServiceOneSoapBindingStub.getOrderData(Unknown
Source)
at Test.main(Unknown Source)
On Tuesday, February 26, 2002, at 03:25 PM, R J Scheuerle Jr wrote:
It would help me a lot if I had
Send me the wsdl and I will debug the problem.
Thanks
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Luis Novais
R J Scheuerle Jr wrote:
If I have time on Monday I will try and debug this situation.
Any help/hints are appreciated. If I can be of assistance, let me know!
Are you using the latest version of Axis
Try quotes around the package and namespace.
-p com.ecofin.vk.beans=urn:ecofin.quoteserver.types
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
SOAPStruct.java
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
R J Scheuerle
Here's a couple ideas.
1) Look at the samples.echo.TestClient code. There are some examples in
the code for sending and receiving arrays.
2) If you have the wsdl for the service, run WSDL2Java to generate client
side stubs. Even if you don't use the stubs, you can
see how the stubs invoke the
Here's an idea.
1) Take your interface/implementation class and run it through Java2WSDL to
create a wsdl file.
2) Take the wsdl file and run WSDL2Java to generate the client and server
side stubs/skeletons.
3) Study the stubs and skeletons...
A couple of things that I do know:
a) The Axis
This sounds like a bug. Have you tried the latest Axis code ?
If there is a bug, I can look into it on Monday.
If you don't want to install a deserializer, you *should* be able to:
1) not specify deserializer in the TypeMapping, or
2) specify deserializer with an empty string, or
3)
Yes the serializer/deserializer handle complexTypes.
I would suggest that you run your wsdl through WSDL2Java to build your
stubs.
Thanks
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
1) Why don't you use the WSDL2Java tool to discover which typeMapping
elements are needed? Run it with -d Session.
2) How are you determining the qnames for the mapping ?
3) If you are dealing with non-axis clients/servers, it is possible that
arrays can be received that use the type=qname of
Thomas,
If you would like to send me a patch to set the service stanza name, I
would be happy to commit it.
Please make the options named serviceStanzaName with the one letter
option as S, and
portTypeName with the one letter option as P. (Please make sure the
help messages, etc.
are changed.)
The encoding framework has changed substantially. The code has been split
into interfaces and classes (classes end with Impl). The actual
serializers and deserializers are now under org.apache.axis.encoding.ser.
It appears that you have an old ArraySerializer class in your tree ?
You may want
(current build).
Thomas
-Original Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Montag, 11. Februar 2002 19:08
To: [EMAIL PROTECTED]
Subject: Re: WSDL-Emitter: No parameter names for arrays
Could you supply an example.
Rich Scheuerle
XML Web Services
.
Steve Pannier
Jacada, Inc.
(763) 268-6382
[EMAIL PROTECTED]
http://www.jacada.com
banking.wsdl has been removed from this note on February 12 2002 by R
J Scheuerle Jr
The ArrayListExtension object should not be propogated outside of the
deserialization framework.
I will change the code to fix this.
Note that the Axis deserialization has been recently changed to return an
array instead of a List.
Could you update your version of Axis and tell me if this fixes
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
I agree Glen. But don't we need this support for any output parameter ?
Maybe we should move further discussion to axis-dev.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
Let me think about this some more. There may be a way to fix this now in
the array deserializer.
Rich Scheuerle
XML Web Services Development
512-838-5115 (IBM TL 678-5115)
49 matches
Mail list logo
