I am new to the axis and I have a problem with Java2WSDL. I've created a
simple service (1 method, returns int, no params) and deployed it. It's
listed as one of available services.
I want to create wsdl file and running Java2WSDL produces the following:
C:\devWS\testjava
run it from C:\devWS directory like
java -classpath test ..
regards,
kiran pathuru
-Original Message-
From: Danko Desancic [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 25, 2004 4:26 PM
To: [EMAIL PROTECTED]
Subject: Java2WSDL problem
I am new to the axis
]
Subject: Java2WSDL problem
I am new to the axis and I have a problem with Java2WSDL. I've created a
simple service (1 method, returns int, no params) and deployed it. It's
listed as one of available services.
I want to create wsdl file and running Java2WSDL produces the following:
C:\devWS
braio 2004
18.01A: [EMAIL PROTECTED]Oggetto: Re: java2wsdl
problem with axis1.2 alfa
Roberto,
The java2WSDL and WSDL2java not always work as one expected. They always
work molto bene with those interfaces that contain simple type such as String,
int, float and so on.
The
ds
Roberto
-Messaggio originale-Da: Tony Blair [mailto:[EMAIL PROTECTED]Inviato: lunedì 16 febbraio 2004 18.01A: [EMAIL PROTECTED]Oggetto: Re: java2wsdl problem with axis1.2 alfa
Roberto,
The java2WSDL and WSDL2java not always work as one expected. They always work molto bene with those interfaces th
Hi everybody
...since 1 month I'm hanging on the following problem: I want to generate with
Axis 1.1 a pure document/literal wsdl (starting from a Java Interface ) without any
reference to SoapEncoding. For example, when, the interface refers to an array of
Objects (ex: public User[]
Roberto,
The java2WSDL and WSDL2java not always work as one expected. They always work molto bene with those interfaces that contain simple type such as String, int, float and so on.
The listUsers() interfaceseems simple, try to write the deploy.wsdd and the client code yourself and deploy the
I am having a problem with Java2WSDL
in Axis 1.0.
The problem is when I declare an exception
in my EJB interface and when Java2WSDL generates corresponding WSDL, in
the binding information it does not generate name attribute
for the SOAP fault. Because of this sproxy tool from .NET is not able
PROTECTED]
Subject: RE: Java2WSDL problem for vandana
Date: Mon, 10 Mar 2003 11:26:21 +0530
Hi,
What is the exception that you're getting while deploying the service?
rgds,
Vandana.
-Original Message-
From: parmod mehta [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 08, 2003 9:42 PM
Hi,
Am trying to generate a WSDL file from my deployed service. The command I give is as
follows:
D:\xml-axis-10\samples\CustomClaimManagerjava org.apache.axis.wsdl.Java2WSDL -o
ClaimManager.wsdl -lhttp://localhost:9080/axis/services/ClaimManage;
-nurn:ClaimManager
to compile the SoapBindings. It gave me errors.
Could you please help me in solving my problem?
Thanks,
Parmod Mehta
From: Balakrishna, Vandana (Cognizant) [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Java2WSDL problem.
Date: Sat, 8 Mar 2003 16:37:52 +0530
Hi
Title: Java2WSDL Problem
I have found the following problem using Java2WSDL utility.
It seems that the utility doesnt generate correct WSDL for the TestInterface interface: the WSDL part for the 2°nd superInterface (002) is missing, and only the first superinterface method is generated
I cannot deploy wsdl file, that was generated with Java2WSDL.
During deployment I'm getting the follow exception:
- Exception:
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: java.lang.Exception: FIXME
faultActor: null
faultDetail:
stackTrace:
Message-
From: Bihani, Swastik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 22, 2002 6:43 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Java2WSDL problem in namespace for bindings
Hi
I am running the WSDL2Java on the following class that comes along with the
Apache Soap 2.2 samples
Hi
I am running the WSDL2Java on the following class that comes along with the Apache
Soap 2.2 samples.
samples.mime.MimeTest
However, in the bindings, I'm getting a wrong output:
wsdl:binding name=MimeTestSoapBinding type=intf:MimeTest
wsdlsoap:binding style=rpc
15 matches
Mail list logo