Thanks for your reply.
I am using Axis 2 only.
Regards-
Sanjeev.
Deepal Jayasinghe wrote:
Hello Experts,
I have a webservice implemented in Java and Axis. This webservice works
just
fine. Now I have added another method as a part of this webservice. Made
an
entry for this method in
Michael,
If you use Maven to build your application, you can use the maven-
assembly-plugin with the built-in jar-with-dependencies descriptor to
achieve this:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptorRefs
I'm trying to generate the Java code from a document-literal WSDL.
Initailly I was able to write a fulli WS-I compiant WSDL and generate
the code with wsdl2java without any problem.
I then modified a portion of the wsdl from:
wsdl:message name=editGeneralSubscriptionResponse
wsdl:part
There is no element named boolean in the XML Schema namespace, only
a type named boolean. You have to provide an element QName for the
message part in a doc/lit web service, so you must define an element
that is of type boolean if that's the type you want. It must be in
some namespace you
Axis 1.3 has known problems with arrays.
I suggest you upgrade to Axis 1.4, although it has other issues with arrays.
Anne
On Thu, Sep 4, 2008 at 10:31 AM, Roy Barman, Shashwata
[EMAIL PROTECTED] wrote:
Problem Summary-
There is a WS-I compliant valid WSDL ( attached). When consumed via
The latest version of ADB no longer imposes the limitations described
in the documentation. It offers pretty comprehensive support for XML
Schema now.
Anne
On Tue, Sep 2, 2008 at 2:53 PM, Peter Conrey [EMAIL PROTECTED] wrote:
I have been developing web services and web service clients in a
Andrea
if you could display your full wsdl we could see what your xsd maps to..
Molte Grazie
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission
If we have a wsdl:fault element declared in the wsdl for an operation, the
wsdl2java (from Axis2) would create a java artifact for the fault message
that extends the java.lang.Exception. Is it possible that the the fault
exception extends a business exception instead of java.lang.Exception?
For
