Nice tip, but this then raises the question, why doesn't wsdl2java
automagically fill this tag since he's the
one responsible for generating the deployment descriptors...
WH
Weicheng Peng wrote:
try this
just add wsdlFilec:/xmloutput.wsdl/wsdlFile into service in wsdd.
service
This works, but only for a given value of works!
I want the WSDL to be part of my web app, so I've added
wsdlFileMathService.wsdl/wsdlFile
to my wsdd file.
I've put the MathService.wsdl file in every directory in the webapp but
I get the 'Unable to find WSDL file' fault.
So how do I reference
Hi!
Im new to axis and i
started to install a helloworld-service on my axis server.
The axis server is running on
a tomcat 4 and validate is working. I was trying to run the
Client. I have 2 questions:
why does the client need to have an javax.servlet-import? Is not a
Server isnt
You need to set fullpath file name, axis doesn't use relative path for this
case.
there are such code snippet in axis source codes,
WSDDService.java
public WSDDService(Element e){
...
Element wsdlElem = getChildElement(e, ELEM_WSDD_WSDLFILE);
if (wsdlElem != null) {
You need to set fullpath file name, axis doesn't use relative path
for this
case.
Which means it's broken. Setting the full path is useless for several
reasons:
If I want to deploy the app as a WAR file I won't have a full path.
Different Servers will have differnet paths
Windows vs Linux!
I
Looks
like you have an old XML parser being picked up, given that lexical handler
feature not supported error.
Try
picking up the latest Xerces and making sure it's in your classpath before any
older XML parsers in the classpath that might be picked up at
runtime...
-Original
I agree .
Weicheng
- Original Message -
From: Kevin Jones [EMAIL PROTECTED]
To: Weicheng Peng [EMAIL PROTECTED]
Cc: Axis User [EMAIL PROTECTED]
Sent: Saturday, December 21, 2002 11:58 AM
Subject: Re: Returning my own WSDL from ?wsdl
You need to set fullpath file name, axis doesn't
Ok. But the problem is when I try to use WSDL2Java to then build my Java
classes (including bindings), I get the following exception (and none of the
files are generated):
java.io.IOException: Type MBeanServer is referenced but not defined.
at
Tom,
Looks like something wrong in the WSDL file. The MBeanServer type is
used in one of the message and it is not found.Most likely cause for
these kinds of error would be the namespace issues. Make sure that
MBeanServer is defined in the proper namespace and the referencing part
in the WSDL
