Well, there are errors in the originally generated WSDL-- The type
definitions are defined as SOAP Encoding types (tns2 namespace) rather
than XSD types (default namespace), and I suspect that .NET would barf
on these types.
I can't tell you why RC3 is generating the funky > values
Java2WSDL tool as follows:
java org.apache.axis.wsdl.Java2WSDL -X"./build" -o
SAPSync.wsdl -l"http://localhost:8080/axis/services/SAPSync"; -n"http://www.b
og.com/wsdl" -p"com.bog.sync.ws" "http://www.bog.com/wsdl"; -yWRAPPED
com.bog.sync.
gt; > Sent: Tuesday, February 15, 2005 11:15 AM
> > To: [EMAIL PROTECTED]
> > Subject: Is there a way to get the auto-generated WSDL
> > document at compile time?
> >
> > Hello all.
> >
> > We have a web application that is configured through the
> >
Just checking to see if anyone had an answer for this question ...
JDG
> From: Jay Glanville [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 15, 2005 11:15 AM
> To: [EMAIL PROTECTED]
> Subject: Is there a way to get the auto-generated WSDL
> document at compile time?
equivalent
below is handled properly:
I've no idea why this change should make a difference, but ?wsdl is
working again for me.
Cheers,
Michael
Michael Thome wrote:
As an in-progress followup, the lack of a stack dump is due to java bug
4872096 (see
Hello. I've found a workaround to the problem stated below.
Tracing through the Axis code i found out that the WSDL Emitter gets
confused with namespaces.
I've removed all simpleType's like
Hi,
I implemented a webservice which works fine. The WSDL was defined by a third
party so I shouldn't change it. One problem occures however, when I try to get
the WSDL in the Browser with
http://localhost:8080/axis/services/SubjectList?wsdl.
The error messa
to be any logging hooks in this code... guess it is
time to move over to the -dev list...
cheers,
-mik
Jay Glanville wrote:
I've got a deployed service which is perfectly functional,
but for which
the ?wsdl option fails with a simple "Exception -
java.lang.StackOv
Hi There!
I have seen a couple of people with the same problem but there seems to be
no answer so far:
The problem relates to WSDL generation of deployed services in Axis 1.2RC2 .
The error is:
BEGIN
AXIS error
Sorry
> I've got a deployed service which is perfectly functional,
> but for which
> the ?wsdl option fails with a simple "Exception -
> java.lang.StackOverflowError" message (without a stack dump
> or any other
> information). The tomcat/catalina logs
I've got a deployed service which is perfectly functional, but for which
the ?wsdl option fails with a simple "Exception -
java.lang.StackOverflowError" message (without a stack dump or any other
information). The tomcat/catalina logs are similarly unhelpful. Also
inte
sounds good
On Wed, 16 Feb 2005 19:10:45 +0100, Carsten Ziegeler
<[EMAIL PROTECTED]> wrote:
> Davanum Srinivas wrote:
> > Carsten,
> >
> > Do you want to share it? Please open a JIRA request for enchancement :)
> >
> Hmm, sure, I' not against sharing - but my solution currently runs
> outside of
Davanum Srinivas wrote:
Carsten,
Do you want to share it? Please open a JIRA request for enchancement :)
Hmm, sure, I' not against sharing - but my solution currently runs
outside of Axis
and alters for example the incomming message in order to append the
schema information etc.
But I could open
Carsten,
Do you want to share it? Please open a JIRA request for enchancement :)
thanks,
dims
On Wed, 16 Feb 2005 14:18:25 +0100, Carsten Ziegeler
<[EMAIL PROTECTED]> wrote:
> Carsten Ziegeler wrote:
> > I'm searching for an easy way of validating an XML document against a
Carsten Ziegeler wrote:
I'm searching for an easy way of validating an XML document against a
WSDL file. This is in order to test if the document is a valid request
for the service.
Does Axis provide some classes/functionalitity I could use? Or is there
something else I can do?
I
d returns XML.
> I
> don't want to use that as the basis for the reports
> because it requires knowing XML and knowing the
> system's schema.)
>
> I'd rather each report was exposed as an operation,
> so
> a developer (or tool) could look at the WSDL and
>
Hello all.
We have a web application that is configured through the
server-config.wsdd file. The resulting WSDL file is auto-generated for
us by Axis (i.e.: http://localhost/app_ctx/services/webservice?wsdl).
So far, everything is working out rather well for us.
What we would like to do next is
Bill Keese wrote:
AFAIK Axis doesn't support this but if you write in document/literal or
wrapped/literal mode, and separate out your schema definition into a
separate XSD file, then you can use Castor to verify schemas. Haven't
tried it though.
See http://www-106.ibm.com/developerworks/webser
library/ws-castor/
Carsten Ziegeler wrote:
I'm searching for an easy way of validating an XML document against a
WSDL file. This is in order to test if the document is a valid request
for the service.
Does Axis provide some classes/functionalitity I could use? Or is
there something else I
I'm searching for an easy way of validating an XML document against a
WSDL file. This is in order to test if the document is a valid request
for the service.
Does Axis provide some classes/functionalitity I could use? Or is there
something else I can do?
I read somewhere that Axis curr
Nothing wrong with using "item" for elements of different types of
arrays. I think your WSDL is OK but AXIS' output is wrong. You
probably need Eric Chijoke's famous Axis array patch to the bug http://issues.apache.org/jira/browse/AXIS-1547
Eric's patch to this is
I have a service that references 2 bean arrays. One
is Object[] and another is String[]. Looks like WSDL generated by Axis is
slightly incorrect. Well .NET complains about it.
Here is the snippet of WSDL:
<complexType name="ArrayOf_xsd_string">
<sequence>
Hi all,
I wanted to make sure the the "service?wsdl" is generated with method param names from the
interface. I've been able find:
http://marc.theaimsgroup.com/?l=axis-user&m=109031639800225&w=2
Which says the my problem is that the method parameter doesn't seem t
he basis for the reports
because it requires knowing XML and knowing the
system's schema.)
I'd rather each report was exposed as an operation, so
a developer (or tool) could look at the WSDL and
invoke the operations they wished, passing the
necessary parms and understanding what was return
Does axis need 'service' class (actual web service
class) to generate wsdl? Can it generate
wsdl just from a custom service descriptor (For example: XSDServiceDescriptor)
?
-Aseem
Fiorano MailServer
All incoming and outgoing mails are scanned for Virus
http://www.fiorano.com
Bill,
If you use the WSDD file when you change machines, you don't have to bother
with the WSDL. Just re-deploy the WSDD file (which doesn't contain
machine-specific information) on whatever machine you like and voila, you'll
get a WSDL that contains that machine's information
Using Axis RC2 it automatically substitutes the correct url of the
machine it is running on, regardless of what the actual value is in
the wsdl. This works even if you specify in the deploy.wsdd
/xxx.wsdlunder element for you service.
Regards,
Patrick.
On Thu, 27 Jan 2005 09:10:18 +0900, Bill
Hi everybody,
I generated a WSDL for a .NET Web Service. In the WSDL there are two
operations by the same name under one Port type tag. however in the
binding section these two operations are attacjed to two different
Soap actions.
When I try to generate the java client using this WSDL,,, it
On Jan 26, 2005, at 4:10 PM, Bill Keese wrote:
It's inconvenient having the host name / port number in the WSDL file,
like below, because every time you setup your service on a new machine
you have to manually modify the WSDL file with the new machine's name.
Look at the filtering=&quo
It's inconvenient having the host name / port number in the WSDL file,
(Blike below, because every time you setup your service on a new machine
(Byou have to manually modify the WSDL file with the new machine's name.
(BDo other people have a trick for dealing w/this inconvenience? Are
I also feel like the WSDL contains a lot of duplicated code, but I don't
know how to avoid it. The message definitions (in document/literal
mode) are also pretty useless, since each message just points to a
single element (with the same name).
I've thought about generating the W
Greetings,
I have a WSDL document that describes the services of my client. I am no
expert at web services so I have a question that might be seen as a
little silly so please excuse me.
In the document I have SEVERAL places where I have the same string over
and over again. A prime example is
I mapped the Axis servlet to a custom URL (e.g. /app/ws) rather than the
default /axis/services/ or whatever it is.
Now if I simply go to: http://server:port/app/ws I see a bunch of links
to the (wsdl) files for each service, but the link is wrong, it is of
the form /app/services/Foo?wsdl
When I go to http://localhost:8080/calendar3/services/calendar the page says:
calendar
Hi there, this is an AXIS service!
However, when I try to have Axis generate the wsdl for this service by going to
http://localhost:8080/calendar3/services/calendar?wsdl I get the following
exception:
Eugene's point is that he attempted to do deploy a wrapped style
service using only an implementation and a WSDD file (which Axis claim
to do), but the generated WSDL document produced errors.
It did, in fact generate a doc/literal "wrapped" style service (not
rpc/encoded), but
We're having a bit of an odd problem.
If we read the WSDL online (using the ?wsdl parameter) before calling
the web service then the web service gives an error back to the client
and will not work again until restarting the axis (1.2) context under
Tomcat (ver 5). If we do not read the
e -
From:
Simon
Fell
To: [EMAIL PROTECTED] ; Eugene Shershnev
Sent: Thursday, January 20, 2005
5:01p
Subject: RE: WS-I compliancy problem for
generated wrapped WSDL
The first one is a false assertion from the WS-I tools,
if you read the WS-I BP erata, you'l
be doc/literal
(probably wrapped) to be WS-I compliant.
Cheers
Simon
From: Eugene Shershnev
[mailto:[EMAIL PROTECTED] Sent: Thursday, January 20, 2005 1:58
PMTo: [EMAIL PROTECTED]Subject: WS-I compliancy
problem for generated wrapped WSDL
Hi All,
The WSDL generated from a si
Hi All,
The WSDL generated from a simple class does not go though
SOAPscope WS-I test.
It fails in 3 different points:
Assertion: WSI2102 Message: An XML schema import element
references something other than an XML schema definition: the referenced element
does not have "schema"
Title: RE: Is Axis generating bad WSDL, or is .NET's wsdl.exe broken?
I had the same error today and the problem was caused by the fact that there were two methods with the same name in the XSoapBindingImpl class. I didn't think this would cause a problem as I only defined
Hi all,
Wanted to find out the need for keeping ws addressing
as abstract and then defining the wsdl binding for ws
addressing.
Consider this
web services addressing : abstract/core
web service addresing : soap binding
web services addressing: wsdl binding
wsdl : abstract
wsdl :soap binding
OAP service(?). Is this true?
>
> e.g.
>
> Originally names were Companies, CompanyData, SearchString, .
>
> .
>
>
> name="companyData" type="s1:companiesCompanyData"/>
>
>
>
>
>
> .
>
> I get from another organizatio
, I will get an error. When I manually change all names to
start with lower case, I will get working SOAP service(?). Is this true?
e.g.
Originally names were Companies, CompanyData, SearchString, .
.
.
I get from another organization Microsoft SOAP Toolkit compatible WSDL
Hi!
Is it at ALL possible to ged SOAP headers declared in
the WSDL for an Axis Web Service?
Preferably declaratively (like in the WSDD), and if
not, by pointing out a custom made WSDL to use for the
Web Service..
Surely this must be possible somehow, or there is a
major deficiency in the
rpc/encoded fud.
Cheers
Simon
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 04, 2005 7:46 AM
> To: [EMAIL PROTECTED]
> Subject: Re: WSDL critique?
>
> Well...
>
> You're using RPC/encoded, and you'
It looks like a bug in RC2. check Jira and log a new bug if needed.
Cheers
Simon
> -Original Message-
> From: Donnie Hale [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 01, 2005 8:42 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Is Axis generating bad WSDL, or is .NE
It's a bug. Please file a bug report.
- Anne
On Sat, 1 Jan 2005 11:41:40 -0500, Donnie Hale
<[EMAIL PROTECTED]> wrote:
> Simon,
>
> I appreciate the response. If you know, how do I get Axis to not insert that
> prefix when it auto-generates the WSDL? Is it a bug, and
e.
Anne
On Sun, 02 Jan 2005 21:22:21 -0700, Larry Meadors
<[EMAIL PROTECTED]> wrote:
> Duh. Here is the WSDL.
>
> >>> Larry Meadors 01/02/05 9:18 PM >>>
> OK, I am new at this, but want to create a web service that is easy to
> use from both .net and java
>>> [EMAIL PROTECTED] 01/02/05 10:35 PM >>>
>Quoting Larry Meadors <[EMAIL PROTECTED]>:
>
>> OK, I am new at this, but want to create a web service that is easy
to
>> use from both .net and java clients.
>>
>> I took a look at the WSDL, and d
Barz i also thought the same, i am sure Larry meant
something else..
--- [EMAIL PROTECTED] wrote:
> Quoting Larry Meadors <[EMAIL PROTECTED]>:
>
> > OK, I am new at this, but want to create a web
> service that is easy to
> > use from both .net and java clients.
> &
Quoting Larry Meadors <[EMAIL PROTECTED]>:
> OK, I am new at this, but want to create a web service that is easy to
> use from both .net and java clients.
>
> I took a look at the WSDL, and do not see anything that looks java
> specific, but am afraid that it would need t
Duh. Here is the WSDL.
>>> Larry Meadors 01/02/05 9:18 PM >>>
OK, I am new at this, but want to create a web service that is easy to
use from both .net and java clients.
I took a look at the WSDL, and do not see anything that looks java
specific, but am afraid that it would
OK, I am new at this, but want to create a web service that is easy to
use from both .net and java clients.
I took a look at the WSDL, and do not see anything that looks java
specific, but am afraid that it would need to bite me on the nose before
I would. :-)
Anyone willing to take a look and
Simon,
I appreciate the response. If you know, how do I get Axis to not insert that
prefix when it auto-generates the WSDL? Is it a bug, and should I submit a
new bug entry? Or is there a deployment/configuration mechanism that will
prevent this?
Thanks again,
Donnie
-Original Message
Simon,
I appreciate the response. If you know, how do I get Axis to not insert that
prefix when it auto-generates the WSDL? Is it a bug, and should I submit a
new bug entry? Or is there a deployment/configuration mechanism that will
prevent this?
Thanks again,
Donnie
-Original Message
As far as I can see, .NET is correct, this is not valid value for name
attribute.
Cheers
Simon
> -Original Message-
> From: Donnie Hale [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 31, 2004 12:13 PM
> To: [EMAIL PROTECTED]
> Subject: Is Axis generating bad WSD
er, hexadecimal value
0x3A, cannot be included in a name..
In the wsdl:types element (see end of message), notice the elements. If I hand-edit the WSDL, taking out the 2
appearances of the "tns1:" prefixes from those elements, then wsdl.exe
doesn't complain and generates the proxies.
er, hexadecimal value
0x3A, cannot be included in a name..
In the wsdl:types element (see end of message), notice the elements. If I hand-edit the WSDL, taking out the 2
appearances of the "tns1:" prefixes from those elements, then wsdl.exe
doesn't complain and generates the proxies.
Regards,
Anne
On Wed, 22 Dec 2004 13:58:23 +0200, Ilkka Heinonen
<[EMAIL PROTECTED]> wrote:
>
>
> Hello everyone. Because of my lack of skills, I simply can't start any
> web-service if I have valid schema in wsdl-file and wsdl2java.
>
>
>
&
Hi Andy,
The namespace defeintions are exactly same, they match letter to
letter. I see this issue was reported back in june 2003, but there are
no replies posted for that.
http://marc.theaimsgroup.com/?l=axis-user&m=105525355225192&w=2
Appreticate any inputs on this.
Thanks,
Shain
On Wed, 22
m. The clients on the .net platform is having trouble
with the wsdl that is generated by Axis, though other Axis based
clients and some perl based clients are running fine.
This Axis generated wsdl for our service has duplicate namespace
declarations and the .net client
is faling with the erro
Hello everyone. Because of my lack of skills, I simply
can’t start any web-service if I have valid schema in wsdl-file and
wsdl2java.
WSDL2Java works fine as long as I use e.g. xsd:string and
apachesoap:Element in requests and responses.
Above are the examples that I can easily
Hello,
We have an Axis based WebService Server with some of the consumers on
the .net platform. The clients on the .net platform is having trouble
with the wsdl that is generated by Axis, though other Axis based
clients and some perl based clients are running fine.
This Axis generated wsdl for
n for reusability. Once it's done, a first pass WSDL can
be generated from the business implementation. That can be used as the
starting point for developing a fixed WSDL. It might need nothing more
than adding some comments and separating out the XML schema. But you might
need to do more work for intero
Hi Everybody,
Is there a way to specify minOccurs / maxOccurs for elements in the wsdl
when we generate the wsdl from java using Java2WSDL?
Or does it have to be done manually only?
Thanks
Vikas
I am trying to change our webservice from type RPC encoded to
Doc/Literal. =3D20
We are running AXIS 1.2 RC2. ...I was hoping all I would need to do is
change in the deployment the attributes on the service. However when I
do this the wsdl generation fails with an error " Please regis
You can specify the file path of the WSDL
in the server-config.wsdd configuration file.
/yourService.wsdl
The file is not a URL but a resource location.
I can't remember exactly how it looks for the file but if you specify it
as above and place it in your classpath (for exampl
Does anyone know how to include the documentation tag in the automatic wsdl
generation in axis?
What I actually want is when my web service endpoint is called via
http://...?wsdl that the returned wsdl will include documentation about the web
service with a documentation tag that I told axis
; eric
>
> -Original Message-
> From: Jason Bodnar [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 14, 2004 2:30 PM
> To: [EMAIL PROTECTED]
> Subject: java.lang.NoClassDefFoundError: javax/wsdl/OperationType
>
> Hi,
>
> I'm trying to go through the
0 PM
To: [EMAIL PROTECTED]
Subject: java.lang.NoClassDefFoundError: javax/wsdl/OperationType
Hi,
I'm trying to go through the installation documentation found here:
http://ws.apache.org/axis/java/install.html
I successfully completed every step and tried to test the Stock Quote sample.
The sample d
k web service I get:
$ /usr/java/j2sdk1.4.2_06/bin/java -cp .:$AXISCLASSPATH samples.stock.GetQuote
-lhttp://localhost:8080/axis/servlet/AxisServlet -uuser1 -wpass1 XXX
Exception in thread "main" java.lang.NoClassDefFoundError:
javax/wsdl/OperationType
at
org.apache.axis.descriptio
Hi all,
I have created a new issue (improvement) in JIRA (AXIS-1719) that
contains a preliminary implementation for generation of documentation in
a wsdl file generated by java2wsdl. Documentation will be extracted
from implementation class source code comments written in javadoc.
Comments
ader
as a "part" in my message. What I had incorrectly done instead, was
create a separate message for the header. That works with other wsdl
parsers, but not Axis 1.2.
So to complete the thread for anybody else who has this problem, to get
headers to show up in the wsdl (e.g. http://?
Not sure why the generated WSDL is inconsistant but as a workaround you can
add a "" tag to the WSDD and point to your WSDL. I usually do that to
let my clients see the WSDL I coded, instead of an Axis generated one.
TMG <[EMAIL PROTECTED]> wrote:
I would like to add a header
I would like to add a header to several of my services to require some
simple authorization (using CVS tree of Axis 1.2RC2).
An example of one of the service's wsdl binding is a follows:
http://schemas.xmlsoap.org/soap
I've just found that my problem was actually a bug in Axis (#Axis-346).
-Original Message-
From: Damir Suban [mailto:[EMAIL PROTECTED]
Sent: Friday, December 10, 2004 10:54 AM
To: [EMAIL PROTECTED]
Subject: WSDL problem
Hi all!
I have installed Axis 1.1, and I am pretty new to
Hi all!
I have installed Axis 1.1, and I am pretty new to Axis. It has worked well
for me so far, but I have found something that looks strange to me.
In the following WSDL file fragment,
I have put
FilterCriteriaSOAPRequest.class,
> qn2), new
>
org.apache.axis.encoding.ser.BeanDeserializerFactory(FilterCriteriaSOAPRequest.class,
> qn2));
>
> However when I try to use the stub created from my
> WSDL it complains of:
> org.xml.sax.SAXException: Deserializing parameter
&
2));
However when I try to use the stub created from my
WSDL it complains of:
org.xml.sax.SAXException: Deserializing parameter
'listObjectsSOAPRequest': could not find deserializer
for type {http://soap.miscy}ListObjectsSOAPRequest
I'm assuming this must be a problem with my WSDD not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
WAJSBERG Julien RD-BIZZ wrote:
| I also have a service returning byte[], and it is correctly serialized
| as xsd:base64Binary (both in wrapped/literal and rpc/encoded styles) .
~ I don't know how I am going to troubleshoot this problem. I will work
on
the .wsdd file with
serialization data for those unused classes.
However, the WSDL as then shown by hitting the ?WSDL URL for my service shows
the dummy version of BigParam, not the real version.
Question #1: Would there be a way to have that ?WSDL URL provide a reference to
the real version of B
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am using Axis 1.2RC2 and I have a function:
public byte[] lookupSelectLocationsString(Item input)
~From the wsdl file I have this:
This is causing me a problem in .net, as this is converted to an sbyte,
rather than being a byte array.
It used to
Axis error messages.
Tim
[EMAIL PROTECTED] wrote:
You can also specify the methods to expose, using the -m option.
Tony
Tim K. wrote on 01/12/2004 19:21:04:
> Vy Ho wrote:
> > I wonder if you declare an interface for this service, then use it to
> > generate wsdl.
> >
>
You can also specify the methods to expose,
using the -m option.
Tony
Tim K. wrote on 01/12/2004 19:21:04:
> Vy Ho wrote:
> > I wonder if you declare an interface for this service, then use
it to
> > generate wsdl.
> >
> > This shields you from how you implement yo
Vy Ho wrote:
I wonder if you declare an interface for this service, then use it to
generate wsdl.
This shields you from how you implement your service.
Right, that's the way to do it, just create an interface for only the
methods you want exposed. The class can have a lot more stuff in it
I wonder if you declare an interface for this service, then use it to
generate wsdl.
This shields you from how you implement your service.
uch
types, therefore the WSDL cannot be dynamically generated.
-David
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tim K. (Gmane)
Sent: Tuesday, November 30, 2004 5:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem generating WSDL from Java
David Song wrote:
> Hi
Brian,
Thanks for sharing the solution. And for working it out yourself in the
first place!
Tony
"Brian J. Sayatovic" <[EMAIL PROTECTED]>
wrote on 01/12/2004 02:45:45:
> I finally figured out how to set the targetNamespace of the wsdl:
> definitions. The WSDD service
yatovic wrote:
I'm
trying to use the ?WSDL generating capabilities of Axis to generate a
WSDL Consumable by a non-Axis client, Laszlo. However is limited in
that it expects the targetNamespace of the schema to be the same as the
targetNamespace of the wsdl:definitions.
The wsdl:definitio
to match what I had coded in my serializers, I was able to
eliminate the second name space and keep everything in the first.
I still would like to know how to change the target namespace of the
whole wsdl:definitions.
Regards,
Brian.
Brian J. Sayatovic wrote:
I'm
trying to use the ?WSD
. The class cannot
be converted into
an xml schema type. An xml schema anyType will be used to define this
class in the wsdl file.
- The class javax.servlet.ServletContext is defined in a java or javax
package and cannot be converted into an xml schema type. An xml schema
anyType will be used to
be converted into
an xml schema type. An xml schema anyType will be used to define this
class in the wsdl file.
- The class javax.servlet.ServletContext is defined in a java or javax
package and cannot be converted into an xml schema type. An xml schema
anyType will be used to define this class
I'm
trying to use the ?WSDL generating capabilities of Axis to generate a
WSDL Consumable by a non-Axis client, Laszlo. However is limited in
that it expects the targetNamespace of the schema to be the same as the
targetNamespace of the wsdl:definitions.
The wsdl:definitions targetName
> -Original Message-
> From: James Ludlow
> That's great for the server, but you also have to take
> that into account for the command line too. I used
> the following switch to fix this.
>
> C:\axis>java -Djava.endorsed.dirs=/axis/lib
> samples.userguide.example2.CalcClient -p8081 add 5
I still see this next error, but the example runs now,
and it's no longer complaining about not being able to
find classes in the wsdl4.jar packages.
"- Unable to find required classes
(javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support
is disabled."
You need a
--- David Werner <[EMAIL PROTECTED]> wrote:
> OK, here's my problem. After following the steps
> described in the
> installation guide, I successfully tried the
> examples mentioned in the user
> guide with Axis 1.1. But I'm running into problems
> when I try th
Axis 1.1. But I'm running into problems when I try the samples of
section "Using WSDL with Axis". I also tried using Axis 1.2 RC2, but it
didn't help. BTW, I'm using Windows XP, Tomcat 5.0 and JDK 1.4.
Here's the error message for the AddressBook example (WSDL2Java)
calls).
When I enter the url "http://localhost/api"; the Axis servlet shows the
following response:
And now... Some Services
Deziro (wsdl)
doFoo
If I follow the wsdl link I get a 404. Searching around I got the vaque
clue that I should do "something" with a qs:wsdl, but w
http://dante.acomp.usf.edu:8080/ws_test/template/AxisLMSServerStub.jws?wsdl
- -
- -
A valid version is seen at
http://data.acomp.usf.edu:8080/axis/services/AxisLMSServer?wsdl
- -
- -
- -
- --
"Love is mutual self-giving that ends in sel
1 - 100 of 1534 matches
Mail list logo
