Re: WSDL2Java http://util.java
No Ollie, it's more than that. wsdl2java is expecting to find a
complex type definition with a name of Properties in a schema with a
targetNamespace of http://util.java;. You can't use namespace
declarations and schema imports to import JAR files. All elements and
complex types must be defined using XML Schema.
Anne
On 6/21/05, Michael Oliver [EMAIL PROTECTED] wrote:
I am trying to run WSDL2Java I won't post the WSDL file here unless someone
thinks I should. I don't think the problem is with the WSDL file itself.
When I run WSDL2Java from ant, both with an ant task and with an ant Java
task I am getting an error similar to:
[axis-wsdl2java] java.io.IOException: Type {http://util.java}Properties is
referenced but not defined.
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:663)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:493)
[axis-wsdl2java] at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)
[axis-wsdl2java] at java.lang.Thread.run(Unknown Source)
BUILD FAILED:
C:\Java\eclipse\workspace\AlariusUser\ant\build.xml:76:
WSDL processing error for
C:\Java\eclipse\workspace\AlariusUser\WebContent\pages\AlariusUser.wsdl
:
Type {http://util.java}Properties is referenced but not defined.
I am assuming the part of the wsdl it is looking at is
wsdl:definitions
targetNamespace=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:intf=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:tns1=http://contentclient.alariusj.com;
xmlns:tns2=http://util.java;
xmlns:tns3=http://action.struts.apache.org;
xmlns:tns4=http://upload.struts.apache.org;
xmlns:tns5=http://registries.alariusj.com;
xmlns:tns6=http://io.java;
xmlns:tns7=http://httpclient.commons.apache.org;
xmlns:tns8=http://lib.webdav.apache.org;
xmlns:tns9=http://user.alariusj.com;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
and
complexType name=AJCSConfig
sequence
element name=configuration nillable=true type=tns2:Properties/
/sequence
/complexType
and this all points to having rt.jar in the classpath so it can find
java.util.Properties, right?
So what do I do to get this working? Or what more do you need to know?
WSDL?
Ollie
Loosely Coupled
Mike Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd
Apt 1096
Las Vegas, NV 89156
[EMAIL PROTECTED]
[EMAIL PROTECTED]
IM: [EMAIL PROTECTED]
http://www.alariussystems.com/
tel:
fax:
mobile:
(702)643-7425
(702)974-0341
(518)378-6154
Add me to your address book...
Want a signature like this?
No serializer found for return-type
Hi, I am getting the following exception: java.io.IOException: No serializer found for class com.somecompany.stockquote.Quote in registry [EMAIL PROTECTED] Basically, the Service gets invoked (I see this from the log), but for some reason it cannot find a serializer even though a serializer is set in the .wsdd! typeMapping xmlns:ns=http://www.somecompany.com/schemas/services/stockquote; qname=ns:quote type=java:com.somecompany.stockquote.Quote serializer=org.apache.axis.encoding.ser.castor.CastorSerializerFactory deserializer=org.apache.axis.encoding.ser.castor.CastorDeserializerFactory encodingStyle= / To give a bit more detail: I am using castor for serialization and deserialization on a document-service (style=wrapped use=literal) for which I have provided a WSDL myself. It all works perfectly fine when deploying the exact same code into a web-container, but when I try to create my own jvm-based transport it throws this Exception. And yes, I do have to make my own transport, as once I get this spike working I need to elaborate the transport and do some routing and other stuff with the requests and responses (but that is not in there now). What could be the problem when it throws this Exception when a service has been invoked and it works in one transport but not the other? This is the code used to invoke the Service (some other methods omitted): AxisEngine engine = getAxisEngine(); MessageContext ctx = new MessageContext(engine); Message serverRequest = new Message(soapRequest); ctx.setRequestMessage(serverRequest); ctx.setTargetService(cls); engine.invoke( ctx ); Message responseMsg = ctx.getResponseMessage(); SOAPEnvelope envelope = responseMsg.getSOAPEnvelope(); Element envElement = envelope.getAsDOM(); String strSOAPBody = XMLUtils.ElementToString(envElement); return strSOAPBody; Any help would be greatly appreciated! regards Wille Faler
Re: Does Axis support polymorphism?
Yes -- for interoperability reasons. Axis and other Java-based systems can handle abstract types pretty easily, but other languages have a lot more trouble with them. Web services should work with concrete XML structures. Anne On 6/20/05, Steven Smith [EMAIL PROTECTED] wrote: Anne, Why should you avoid abstract types? Is it because of interoperability with other Web Service implementations? I have implemented a service that uses GML (Geographic Markup Language) to pass Spatial objects around. The GML specification uses abstract types heavily and I can't avoid that (without implementing my own). I have tested my service from an Axis client and it works fine as is, so I was wondering why abstract types should be avoided. -- Steven Smith [EMAIL PROTECTED] Software Developer / Analyst Telephone: 03 6223 1999 Facsimile: 03 6223 1988 Web : www.geometry.com.au Address : 31 Salamanca Square, Battery Point, TAS 7004, Australia Postal : PO Box 844, Sandy Bay, TAS 7006, Australia -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Tuesday, 21 June 2005 6:28 AM To: axis-user@ws.apache.org Subject: Re: Does Axis support polymorphism? Avoid polymorphism and abstract types. Flatten your objects. Anne On 6/20/05, Amihai Fuks [EMAIL PROTECTED] wrote: Hi, I am new to Axis (and SOAP in general...). Does Axis support polymorphism in the service's methods? I'll give an example: is it a good practice to expose a method like: public void addShape(Shape shape); Where Shape is an abstract type and there are several implementations for the type like: Square and Rectangle (as you may guess). Or maybe try avoid it through flattening my objects resulting in duplication of logic applied to all Shapes and having as much Shapes I have addShape methods. Notice that I have no idea who my clients are and how they handle the SOAP on their side. Thanks, Amihai
Can a classcast exception be caused by a malformed WSDL?
Hi Posting this again as it didn't seem to show up last time round. Pat -Original Message- From: Patrick Quinn Sent: 21 June 2005 17:41 To: 'axis-user@ws.apache.org' Subject: Can a classcast exception be caused by a malformed WSDL? Hi I'm receiving a java.lang.ClassCastException as an exception when attempting a 'wrapped' style service call. Could this be a WSDL problem, or is it more likely to be down to other factors? Any help gratefully received again - as I am dealing with a customer's WSDL, and am not that familiar with AXIS, it is very difficult to spot what is wrong. Thanks previously to Anne for fixing the last WSDL - much appreciated. The WSDL looks like this: ?xml version=1.0 encoding=utf-8? wsdl:definitions xmlns:s1=http://ProvidentConnector.ProvidentResponseToOrch; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:s=http://www.w3.org/2001/XML Schema xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns=http://namespace.accent.com/ xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; targetNamespace=http://namespace.accent.com/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; wsdl:types s:schema elementFormDefault=qualified targetNamespace=http://namespace.accent.com/; s:import namespace=http://ProvidentConnector.ProvidentResponseToOrch; / s:element name=SOPResponse s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 ref=s1:ProvidentResponse / /s:sequence /s:complexType /s:element s:element name=SOPResponseResponse s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 name=part type=s:string / /s:sequence /s:complexType /s:element /s:schema s:schema elementFormDefault=qualified targetNamespace=http://ProvidentConnector.ProvidentResponseToOrch; s:element name=ProvidentResponse type=s1:ProvidentResponse / s:complexType name=ProvidentResponse s:sequence s:element minOccurs=0 maxOccurs=1 form=unqualified name=REQUESTID type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=SO_RESULT_CODE type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=SO_PROV_DATE type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=SO_ERR_DESC type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=XML_SORESULT type=s:string / /s:sequence /s:complexType /s:schema /wsdl:types wsdl:message name=SOPResponseSoapIn wsdl:part name=parameters element=tns:SOPResponse / /wsdl:message wsdl:message name=SOPResponseSoapOut wsdl:part name=parameters element=tns:SOPResponseResponse / /wsdl:message wsdl:portType name=ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap wsdl:operation name=SOPResponse wsdl:input message=tns:SOPResponseSoapIn / wsdl:output message=tns:SOPResponseSoapOut / /wsdl:operation /wsdl:portType wsdl:binding name=ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap type=tns:ProvidentConnector _ProvidentReceiver_ProvidentWSPortSoap soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document / wsdl:operation name=SOPResponse soap:operation soapAction=http://namespace.accenture.com/ProvidentConnector_ProvidentR eceiver_ProvidentWSPort/SOPResponse style=document / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=ProvidentConnector_ProvidentReceiver_ProvidentWSPort documentation xmlns=http://schemas.xmlsoap.org/wsdl/;BizTalk assembly ProvidentConnector, Version=1.0.0.0, Culture=neutral, PublicKeyToken=ae7c9e263f196bff published web service./documentation wsdl:port name=ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap binding=tns:ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap soap:address location=http://localhost/ProvidentConnector/ProvidentWSPort.asmx; / /wsdl:port /wsdl:service /wsdl:definitions __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Bug with Arrays as Return Types
Title: Bug with Arrays as Return Types Hi, I've got a Problem with web service methods returning an array. I have found the example from http://wiki.apache.org/ws/DotNetInteropArrays and it says: At one point, there was a bug in AXIS dealing with an operation that returns an array directly, rather than a structure containing an array (ie, an operation like String[] getInfo() rather than Container getInfo()). This may still be present in AXIS V1.2RC3. Dims? Another thread in the archive says: Also make sure that you've applied the fix for the bug that Dino talks about. I have installed AXIS 1.2.1 and the bug still seems to be present. Is this true? If so: Where can I find a patch or a workaround? Please help! Mit freundlichen Grüßen Dipl. Ing. Oliver Wolters (Systementwickler Auftragsentwicklung) -- ProCom Systemhaus und Ingenieurunternehmen GmbH Luisenstr. 41 - D-52070 Aachen Tel. +49 241 51804-175 Fax +49 241 51804-30 http://www.procom.de mailto:[EMAIL PROTECTED]
Signature creation failed exception with WSS4J and AXIS
Hi All,
I want to try a simple handson on how to implement X509 Certificate
Token Profile with WSS4J and AXIS. I just want to use a X509
Certificate as token and no username/password token , no encryption
but just signing and verifying the signature using wss4j and axis.
I am following the code in the ***ws-fx\wss4j\interop*** directory of
wss4j binary and found that Ping5 web service is suitable for my
purpose (not so confident whether Ping5 example is the right one for
me).
When I run my web service client program to connect to the service I
am getting below exception. In my TCPMonitor I am not seeing any
request soap message either and can anyone please suggest what am I
missing here.
Exception in thread main AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: WSDoAllSender: Signature: error during message
procesingorg.apache.ws.security.WSSecurityException: Signature c
reation failed; nested exception is:
java.security.UnrecoverableKeyException: Cannot recover key
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:WSDoAllSender:
Signature: error during message procesingorg.apache.ws.securit
y.WSSecurityException: Signature creation failed; nested exception is:
java.security.UnrecoverableKeyException: Cannot recover key
at
org.apache.ws.axis.security.WSDoAllSender.performSIGNAction(WSDoAllSender.java:414)
at
org.apache.ws.axis.security.WSDoAllSender.invoke(WSDoAllSender.java:320)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:121)
at org.apache.axis.client.Call.invokeEngine(Call.java:2754)
at org.apache.axis.client.Call.invoke(Call.java:2737)
at org.apache.axis.client.Call.invoke(Call.java:2413)
at org.apache.axis.client.Call.invoke(Call.java:2336)
at org.apache.axis.client.Call.invoke(Call.java:1793)
at ping.PingBindingStub.ping(PingBindingStub.java:154)
at ping.Client.main(Client.java:87)
{http://xml.apache.org/axis/}hostname:hyddl0337
WSDoAllSender: Signature: error during message
procesingorg.apache.ws.security.WSSecurityException: Signature
creation failed
; nested exception is:
java.security.UnrecoverableKeyException: Cannot recover key
at
org.apache.ws.axis.security.WSDoAllSender.performSIGNAction(WSDoAllSender.java:414)
at
org.apache.ws.axis.security.WSDoAllSender.invoke(WSDoAllSender.java:320)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:121)
at org.apache.axis.client.Call.invokeEngine(Call.java:2754)
at org.apache.axis.client.Call.invoke(Call.java:2737)
at org.apache.axis.client.Call.invoke(Call.java:2413)
at org.apache.axis.client.Call.invoke(Call.java:2336)
at org.apache.axis.client.Call.invoke(Call.java:1793)
at ping.PingBindingStub.ping(PingBindingStub.java:154)
at ping.Client.main(Client.java:87)
Thanks Regards,
Kumar
ComplexTypes Costum (De)Serializer / ANT / WSDL2JAVA / JAVA2WSDL
Hy everybody
I 've following problem:
I hava a nonBean-complinet WSType.class
and a Webservice WS_Test.class using WSType
So I hav a Writen a (De)Serializer and the corresponding Factory, using XStream do serialize and deserialize
when I call java2wsdl via ant (
java2wsdl
output=${local.wsdl}
location=http://${target.server}:${target.port}/axis/services/WS-Test
namespace=urn:sms
classname=at.co.ksg.ws_test.WSTest_org
style=rpc
use=encoded
serviceelementname=WSTest
classpath=${bin.dir}
complexType
classname=at.co.ksg.ws_test.WSType
namespace=urn:ws_test
serializer=at.co.ksg.ws_test.WSSerFactory
deserializer=at.co.ksg.ws_test.WSDeSerFactory
/
/java2wsdl
) every thing work fine!
but when I call
wsdl2java
I have troubles ( cause the urn:ws_test isn't found! )
no my question:
is there somthing like the completype statement ( where I tell (de)serializer ) in the wsdl2java task?
best regard harry!
The requested method POST is not allowed for the URL - (405)Method Not Allowed
Hi there, i have troubles using a service with AXIS. I got a faultString: (405)Method Not Allowed Exception when i run my client. I got this additional message The requested method POST is not allowed for the URL /index.html.lt;Pgt; How can I change the request to GET? I thought POST is the common request, isnt it? Thanks for any help, Christian
Re: Bug with Arrays as Return Types
Oliver, Can you please open a bug report and upload the WSDL you use to generate the server/client. thanks, dims On 6/22/05, Wolters, Oliver [EMAIL PROTECTED] wrote: Hi, I've got a Problem with web service methods returning an array. I have found the example from http://wiki.apache.org/ws/DotNetInteropArrays and it says: At one point, there was a bug in AXIS dealing with an operation that returns an array directly, rather than a structure containing an array (ie, an operation like String[] getInfo() rather than Container getInfo()). This may still be present in AXIS V1.2RC3. Dims? Another thread in the archive says: Also make sure that you've applied the fix for the bug that Dino talks about. I have installed AXIS 1.2.1 and the bug still seems to be present. Is this true? If so: Where can I find a patch or a workaround? Please help! Mit freundlichen Grüßen Dipl. Ing. Oliver Wolters (Systementwickler Auftragsentwicklung) -- ProCom Systemhaus und Ingenieurunternehmen GmbH Luisenstr. 41 - D-52070 Aachen Tel. +49 241 51804-175 Fax +49 241 51804-30 http://www.procom.de mailto:[EMAIL PROTECTED] -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
AW: Bug with Arrays as Return Types
Hi Dims, thanks for your answer. I think that there is already a bug report for this bug (if it's stil present). I'm not sure but maybe I'm doing something bad with my deployment. The problem is: The webservices I'm working on are generated from CORBA-IDL - not from a WSDL as I have explained in my mail AXIS 1.2 and MS VB interop (arrays) So the way it goes is CORBA-IDL - idlj- Java-Stubs - deploy as WS - generate WSDL - generate Client-Stub. The generated WSDL is (the getUserDomainsByName-Methode returning an Array of TDomain makes trouble): wsdl:definitions targetNamespace=http://gateway.bofit.enw.procom.de/gatekeeper; - !-- WSDL created by Apache Axis version: 1.2.1 Built on Jun 14, 2005 (09:15:57 EDT) -- - wsdl:types - schema elementFormDefault=qualified targetNamespace=http://gateway.bofit.enw.procom.de/gatekeeper; import namespace=http://gateway.bofit.enw.procom.de/ import namespace=http://CORBA.omg.org/ - element name=logoutWebservice complexType/ /element - element name=logoutWebserviceResponse complexType/ /element element name=fault type=tns1:EInternalError/ - element name=createServiceManager - complexType - sequence element name=in0 type=xsd:string/ element name=in1 type=xsd:string/ element name=in2 type=xsd:short/ /sequence /complexType /element - element name=createServiceManagerResponse - complexType - sequence element name=createServiceManagerReturn type=xsd:anyType/ /sequence /complexType /element element name=fault1 type=tns1:EUnknownUser/ element name=fault2 type=tns1:EUserLoggedIn/ element name=fault3 type=tns1:EWrongPassword/ element name=fault4 type=tns1:EUnknownDomain/ - element name=getUserDomainsByName - complexType - sequence element name=in0 type=xsd:string/ /sequence /complexType /element - element name=getUserDomainsByNameResponse - complexType - sequence element maxOccurs=unbounded name=getUserDomainsByNameReturn type=tns1:TDomain/ /sequence /complexType /element element name=fault5 type=tns1:EDbError/ /schema - schema elementFormDefault=qualified targetNamespace=http://CORBA.omg.org; import namespace=http://gateway.bofit.enw.procom.de/gatekeeper/ import namespace=http://gateway.bofit.enw.procom.de/ - complexType abstract=true name=UserException sequence/ /complexType /schema - schema elementFormDefault=qualified targetNamespace=http://gateway.bofit.enw.procom.de; import namespace=http://gateway.bofit.enw.procom.de/gatekeeper/ import namespace=http://CORBA.omg.org/ - complexType name=EInternalError - complexContent - extension base=tns2:UserException sequence/ /extension /complexContent /complexType - complexType name=EUnknownUser - complexContent - extension base=tns2:UserException sequence/ /extension /complexContent /complexType - complexType name=EUserLoggedIn - complexContent - extension base=tns2:UserException sequence/ /extension /complexContent /complexType - complexType name=EWrongPassword - complexContent - extension base=tns2:UserException sequence/ /extension /complexContent /complexType - complexType name=EUnknownDomain - complexContent - extension base=tns2:UserException sequence/ /extension /complexContent /complexType - complexType name=TDomain - sequence element name=id type=xsd:int/ element name=transaktion type=xsd:int/ element name=name nillable=true type=xsd:string/ /sequence /complexType - complexType name=EDbError - complexContent - extension base=tns2:UserException - sequence element name=reason nillable=true type=xsd:string/ /sequence /extension /complexContent /complexType /schema /wsdl:types - wsdl:message name=logoutWebserviceResponse wsdl:part element=impl:logoutWebserviceResponse name=parameters/ /wsdl:message - wsdl:message name=EDbError wsdl:part element=impl:fault5 name=fault/ /wsdl:message - wsdl:message name=EUnknownDomain wsdl:part element=impl:fault4 name=fault/ /wsdl:message - wsdl:message name=getUserDomainsByNameResponse wsdl:part element=impl:getUserDomainsByNameResponse name=parameters/ /wsdl:message - wsdl:message name=logoutWebserviceRequest wsdl:part element=impl:logoutWebservice name=parameters/ /wsdl:message - wsdl:message name=getUserDomainsByNameRequest wsdl:part element=impl:getUserDomainsByName name=parameters/ /wsdl:message - wsdl:message name=EInternalError wsdl:part element=impl:fault name=fault/ /wsdl:message - wsdl:message name=EWrongPassword wsdl:part element=impl:fault3 name=fault/ /wsdl:message - wsdl:message name=createServiceManagerResponse wsdl:part element=impl:createServiceManagerResponse name=parameters/ /wsdl:message - wsdl:message name=EUnknownUser wsdl:part element=impl:fault1 name=fault/
TypeMapping problem for different transports
Hi all. I posted earlier today about my problems with serializing on return from a service-invocation from different transports: I have since chased it down further and found out that it is the TypeMapping returned by SerializationContext.getTypeMapping() that is different between http (which works) and other transports (that do not work). At what point and where does this configuration get set? My config is exactly the same between transports, but the getTypeMapping() returns a TypeMapping with no Serializer on other transports than http implemented by me. I am using CastorSerializers, here is the code for my custom transport: AxisEngine engine = getAxisServer(); MessageContext ctx = new MessageContext(engine); Message serverRequest = new Message(soapRequest); // Message String ctx.setRequestMessage(serverRequest); ctx.setTargetService(serviceName); engine.invoke( ctx ); Message responseMsg = ctx.getResponseMessage(); SOAPEnvelope envelope = responseMsg.getSOAPEnvelope(); Element envElement = envelope.getAsDOM(); // this is where the exception is thrown String strSOAPBody = XMLUtils.ElementToString(envElement); return strSOAPBody; Am I missing something that I shouuld set on the MessageContext for the TypeMappings to be set up correctly for the response? As I said, it works fine on http, but this particular implementation does not work. regards Wille Faler
Re: Signature creation failed exception with WSS4J and AXIS
Hi Werner All,
Thank you for pointing the problem. It works . Now I am able to see
below soap request message in TCPMonitor .
Request SOAP Message
POST /axis/services/SparePartInfo HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.2RC1
Host: 127.0.0.1:
Cache-Control: no-cache
Pragma: no-cache
SOAPAction:
Content-Length: 2443
?xml version=1.0 encoding=UTF-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header
wsse:Security
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
soapenv:mustUnderstand=1
wsse:UsernameToken
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
wsu:Id=usernameTokenId-5294604
wsse:Usernamealice/wsse:Username
wsse:Password
Type=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText;password/wsse:Password
wsu:Created2005-06-22T13:52:43Z/wsu:Created
wsse:NoncejJk9swcs+hN460RCJNOFxg==/wsse:Nonce
/wsse:UsernameToken
ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
ds:SignedInfo
ds:CanonicalizationMethod
Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#;
ec:InclusiveNamespaces
xmlns:ec=http://www.w3.org/2001/10/xml-exc-c14n#; PrefixList=soapenv
xsd xsi/ec:InclusiveNamespaces
/ds:CanonicalizationMethod
ds:SignatureMethod
Algorithm=http://www.w3.org/2000/09/xmldsig#hmac-sha1;/ds:SignatureMethod
ds:Reference URI=#id-16625677
ds:Transforms
ds:Transform
Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#;
ec:InclusiveNamespaces
xmlns:ec=http://www.w3.org/2001/10/xml-exc-c14n#; PrefixList=xsd
xsi/ec:InclusiveNamespaces
/ds:Transform
/ds:Transforms
ds:DigestMethod
Algorithm=http://www.w3.org/2000/09/xmldsig#sha1;/ds:DigestMethod
ds:DigestValueIEnmBTVOR4+F8ogoCoeeTJO+KDk=/ds:DigestValue
/ds:Reference
/ds:SignedInfo
ds:SignatureValue62NTqelpmGcSmOUfgcll1woekZM=/ds:SignatureValue
ds:KeyInfo Id=KeyId-30408372
wsse:SecurityTokenReference
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
wsu:Id=STRId-29689095
wsse:Reference URI=#usernameTokenId-5294604
ValueType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken;/wsse:Reference
/wsse:SecurityTokenReference
/ds:KeyInfo
/ds:Signature
/wsse:Security
/soapenv:Header
soapenv:Body
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
wsu:Id=id-16625677
getPartInfo xmlns=http://Chapter4.wroxaxis;
in0 xmlns=SKU-123/in0
/getPartInfo
/soapenv:Body
/soapenv:Envelope
Now I have 2 issues here :
1. I get below exception on the client side and hence a axis fault
response from the server.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: WSDoAllReceiver: security processing failed (actions
number mismatch)
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:hyddl0337
WSDoAllReceiver: security processing failed (actions number mismatch)
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1077)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
Axis1.1 / Axis 1.2 IllegalArgumentException
Hello, I am trying to run some tests to upgrade from Axis 1.1 to Axis 1.2 and have run into a problem. My WSDL has the following: xs:complexType name="OntSearchResponseType" xs:sequence xs:element name="id" type="ifis:SearchIdType"/ xs:element name="result" type="ifis:OntResultType"/ /xs:sequence /xs:complexType xs:simpleType name="SearchIdType" xs:annotation xs:documentationPer provider unique search id./xs:documentation /xs:annotation xs:restriction base="xs:positiveInteger"/ /xs:simpleType When I run WSDL2Java under 1.1 a SearchIdType object is created but under Axis 1.2 it is not. In my test I have my client still running under Axis 1.1 with the Axis 1.1 WSDL2Java generated objects (can't convert the client just yet because other modules are out of my control). I have two servers running. One is running the Axis 1.1 stuff and the other server is running Axis 1.2 with the Axis 1.2 WSDL2Java generated objects. When I make a web service call from my client to the Axis 1.1 server the SOAP body being returned is: soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="id-30999846" searchResponse xmlns="urn:ifis-wsdl" id xmlns=""1/id result xmlns="" xmlns:ns1="http://www.dod.mil/ifis/1.0/ifis#" ns1:isStillProcessing="false" ns1:timestamp="2005-06-22T12:45:52.020Z"/ /searchResponse /soapenv:Body When I make a web service call from my client to the Axis 1.2 server the SOAP body being returned is: soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="id-1132857" searchResponse xmlns="urn:ifis-wsdl" id xmlns="" xsi:type="xsd:positiveInteger"1/id result xmlns="" xmlns:ns1="http://www.dod.mil/ifis/1.0/ifis#" ns1:isStillProcessing="false" ns1:timestamp="2005-06-22T12:54:28.191Z"/ /searchResponse /soapenv:Body You can see that the Axis 1.2 server returned a slightly different version of the "id" element. When hitting the Axis 1.2 server, my client ends up throwing an "IllegalArgumentException: argument type mismatch" error. My thought is that when Axis (1.1) deserializes the SOAP Body on my client, it is having problems with this new version of the "id" element. Can anyone verify that this is what is causing the error? Thanks - Peter
REST again
Following the 'Start with the WSDL!' principle of web service development, I have produced a successful service which works in both Axis .net, greatly helped by the classes produced by wsdl2java. So far so good. Now I have a requirement to provide the same service via REST. Being lazy I don't want to recreate all the functionality so intend to directly call the service method in the auto-generated xxSoapBindingImpl class. I can easily create the correct Object to pass as a parameter. The problem I next have is to be able to create a response XML Document from the Object returned from the method. Axis must do this when it is creating the response SOAP Body. Does anyone know how I can easily access this functionality. Richard. Register your interest now Insight 2005 : 15th 16th November Register your interest now http://www.talis.com/events Any views or personal opinions expressed within this email may not be those of Talis Information Ltd. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
RE: WSDL2Java http://util.java
Thanks Anne,
The problem is simple enough, I used Java2WSDL to generate the wsdl file
from a class that had a getter and setter for java.util.Properties and I
took a snippet from the wsdl and showed it in my original message. Then
when I ran WSDL2Java to get the server side sources, I got the error message
related to java.util.Properties.
So, it isn't enough to have java.util.Properties in the classpath, got it. I
guess I was presuming too much about the generated wsdl.
What DOES it need? One would think that WSDL2Java would be able to consume
a Java2WSDL generated file that was unmodified and in the same environment.
Is there something in the Java2WSDL task I need to change?
The current Java2WSDL task looks like
axis-java2wsdl
classname=com.ajcs.services.AJCCUserServices
style= DOCUMENT
namespace= urn:http://alariussystemsllc.com/AlariusUser/;
location=
http://localhost:8080/AlariusUser/services/AlariusUserServices;
output=${local.wsdl}
classpath
pathelement path =${webinf.dir}/classes/
/classpath
classpath refid=EPCLASSPATH/
/axis-java2wsdl
I suppose that it isn't enough that java.util.Properties is serializable,
and that it is still too complex to be interoperable and that we need to
provide a mapping to support it when we generate the wsdl? Or another
option would be to simplify the AlariusUserServices?
Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from [EMAIL PROTECTED]
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 21, 2005 11:08 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: WSDL2Java http://util.java
No Ollie, it's more than that. wsdl2java is expecting to find a
complex type definition with a name of Properties in a schema with a
targetNamespace of http://util.java;. You can't use namespace
declarations and schema imports to import JAR files. All elements and
complex types must be defined using XML Schema.
Anne
On 6/21/05, Michael Oliver [EMAIL PROTECTED] wrote:
I am trying to run WSDL2Java I won't post the WSDL file here unless
someone
thinks I should. I don't think the problem is with the WSDL file itself.
When I run WSDL2Java from ant, both with an ant task and with an ant Java
task I am getting an error similar to:
[axis-wsdl2java] java.io.IOException: Type {http://util.java}Properties is
referenced but not defined.
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.j
ava:663)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:493)
[axis-wsdl2java] at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)
[axis-wsdl2java] at java.lang.Thread.run(Unknown Source)
BUILD FAILED:
C:\Java\eclipse\workspace\AlariusUser\ant\build.xml:76:
WSDL processing error for
C:\Java\eclipse\workspace\AlariusUser\WebContent\pages\AlariusUser.wsdl
:
Type {http://util.java}Properties is referenced but not defined.
I am assuming the part of the wsdl it is looking at is
wsdl:definitions
targetNamespace=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:intf=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:tns1=http://contentclient.alariusj.com;
xmlns:tns2=http://util.java;
xmlns:tns3=http://action.struts.apache.org;
xmlns:tns4=http://upload.struts.apache.org;
xmlns:tns5=http://registries.alariusj.com;
xmlns:tns6=http://io.java;
xmlns:tns7=http://httpclient.commons.apache.org;
xmlns:tns8=http://lib.webdav.apache.org;
xmlns:tns9=http://user.alariusj.com;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
and
complexType name=AJCSConfig
sequence
element name=configuration nillable=true
type=tns2:Properties/
/sequence
/complexType
and this all points to having rt.jar in the classpath so it can find
java.util.Properties, right?
So what do I do to get this working? Or what more do you need to know?
WSDL?
Ollie
Loosely Coupled
Mike Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd
Apt 1096
Las Vegas, NV 89156
[EMAIL PROTECTED]
[EMAIL PROTECTED]
IM: [EMAIL PROTECTED]
http://www.alariussystems.com/
Re: WSDL2Java http://util.java
Actually, JAX-RPC doesn't permit you to map java.util.Properties to
XML. You should wrap this class with a JavaBean to make it work.
Anne
On 6/22/05, Michael Oliver [EMAIL PROTECTED] wrote:
Thanks Anne,
The problem is simple enough, I used Java2WSDL to generate the wsdl file
from a class that had a getter and setter for java.util.Properties and I
took a snippet from the wsdl and showed it in my original message. Then
when I ran WSDL2Java to get the server side sources, I got the error message
related to java.util.Properties.
So, it isn't enough to have java.util.Properties in the classpath, got it. I
guess I was presuming too much about the generated wsdl.
What DOES it need? One would think that WSDL2Java would be able to consume
a Java2WSDL generated file that was unmodified and in the same environment.
Is there something in the Java2WSDL task I need to change?
The current Java2WSDL task looks like
axis-java2wsdl
classname=com.ajcs.services.AJCCUserServices
style= DOCUMENT
namespace= urn:http://alariussystemsllc.com/AlariusUser/;
location=
http://localhost:8080/AlariusUser/services/AlariusUserServices;
output=${local.wsdl}
classpath
pathelement path =${webinf.dir}/classes/
/classpath
classpath refid=EPCLASSPATH/
/axis-java2wsdl
I suppose that it isn't enough that java.util.Properties is serializable,
and that it is still too complex to be interoperable and that we need to
provide a mapping to support it when we generate the wsdl? Or another
option would be to simplify the AlariusUserServices?
Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from [EMAIL PROTECTED]
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 21, 2005 11:08 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: WSDL2Java http://util.java
No Ollie, it's more than that. wsdl2java is expecting to find a
complex type definition with a name of Properties in a schema with a
targetNamespace of http://util.java;. You can't use namespace
declarations and schema imports to import JAR files. All elements and
complex types must be defined using XML Schema.
Anne
On 6/21/05, Michael Oliver [EMAIL PROTECTED] wrote:
I am trying to run WSDL2Java I won't post the WSDL file here unless
someone
thinks I should. I don't think the problem is with the WSDL file itself.
When I run WSDL2Java from ant, both with an ant task and with an ant Java
task I am getting an error similar to:
[axis-wsdl2java] java.io.IOException: Type {http://util.java}Properties is
referenced but not defined.
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.j
ava:663)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
[axis-wsdl2java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:493)
[axis-wsdl2java] at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)
[axis-wsdl2java] at java.lang.Thread.run(Unknown Source)
BUILD FAILED:
C:\Java\eclipse\workspace\AlariusUser\ant\build.xml:76:
WSDL processing error for
C:\Java\eclipse\workspace\AlariusUser\WebContent\pages\AlariusUser.wsdl
:
Type {http://util.java}Properties is referenced but not defined.
I am assuming the part of the wsdl it is looking at is
wsdl:definitions
targetNamespace=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:intf=urn:http://alariussystemsllc.com/AlariusUserServices/;
xmlns:tns1=http://contentclient.alariusj.com;
xmlns:tns2=http://util.java;
xmlns:tns3=http://action.struts.apache.org;
xmlns:tns4=http://upload.struts.apache.org;
xmlns:tns5=http://registries.alariusj.com;
xmlns:tns6=http://io.java;
xmlns:tns7=http://httpclient.commons.apache.org;
xmlns:tns8=http://lib.webdav.apache.org;
xmlns:tns9=http://user.alariusj.com;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
and
complexType name=AJCSConfig
sequence
element name=configuration nillable=true
type=tns2:Properties/
/sequence
/complexType
and this all points to having rt.jar in the classpath so it can find
java.util.Properties, right?
So what do I do to get this working? Or what more do you need to know?
WSDL?
Ollie
Loosely Coupled
Mike
TCP Monitoring on the client side
Title: TCP Monitoring on the client side Does tcpmon support monitoring on the client side? I wish to connect to a web service and log out the request xml and the response xml. I'm using Axis1.2. Thanks for any help. ___ Jeremy Nix Senior Application Developer Southwest Financial Services, LTD. (513) 621-6699 x1158 www.sfsltd.com
Re: Tutorial or docs on WSDD and WSDL
See http://www.osmoticweb.com/axis-wsdd/ On 6/22/05, Gary Zhu [EMAIL PROTECTED] wrote: Hi all, Your direction to docs on WSDD and WSDL is needed to speed up my attempt to deploy a web service using AXIS. Thanks. Gary
Re: Axis1.1 / Axis 1.2 IllegalArgumentException
Solved... Even though the SearchIdType did not exist as an object after running WSDL2Java using Axis 1.2, there still was a typeMapping entry that got created (in the deploy.wsdd file) which I failed to add to my server-config.wsdd file. Once I did that all was well. Developer error. Thanks - Peter Peter Len wrote: Hello, I am trying to run some tests to upgrade from Axis 1.1 to Axis 1.2 and have run into a problem. My WSDL has the following: xs:complexType name="OntSearchResponseType" xs:sequence xs:element name="id" type="ifis:SearchIdType"/ xs:element name="result" type="ifis:OntResultType"/ /xs:sequence /xs:complexType xs:simpleType name="SearchIdType" xs:annotation xs:documentationPer provider unique search id./xs:documentation /xs:annotation xs:restriction base="xs:positiveInteger"/ /xs:simpleType When I run WSDL2Java under 1.1 a SearchIdType object is created but under Axis 1.2 it is not. In my test I have my client still running under Axis 1.1 with the Axis 1.1 WSDL2Java generated objects (can't convert the client just yet because other modules are out of my control). I have two servers running. One is running the Axis 1.1 stuff and the other server is running Axis 1.2 with the Axis 1.2 WSDL2Java generated objects. When I make a web service call from my client to the Axis 1.1 server the SOAP body being returned is: soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="id-30999846" searchResponse xmlns="urn:ifis-wsdl" id xmlns=""1/id result xmlns="" xmlns:ns1="http://www.dod.mil/ifis/1.0/ifis#" ns1:isStillProcessing="false" ns1:timestamp="2005-06-22T12:45:52.020Z"/ /searchResponse /soapenv:Body When I make a web service call from my client to the Axis 1.2 server the SOAP body being returned is: soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="id-1132857" searchResponse xmlns="urn:ifis-wsdl" id xmlns="" xsi:type="xsd:positiveInteger"1/id result xmlns="" xmlns:ns1="http://www.dod.mil/ifis/1.0/ifis#" ns1:isStillProcessing="false" ns1:timestamp="2005-06-22T12:54:28.191Z"/ /searchResponse /soapenv:Body You can see that the Axis 1.2 server returned a slightly different version of the "id" element. When hitting the Axis 1.2 server, my client ends up throwing an "IllegalArgumentException: argument type mismatch" error. My thought is that when Axis (1.1) deserializes the SOAP Body on my client, it is having problems with this new version of the "id" element. Can anyone verify that this is what is causing the error? Thanks - Peter
Re: Correct usage of wsdl:part/@element for doc/literal
Thanks for your help Anne, I think I got it straightened out now.
As an aside, it turns out that along with my ignorance, some of the
tools that I've been trying to leverage to supplement my WSDL
knowledge (or lack thereof) have a few problems. For example, I took
this example a step closer to my real problem and changed it to
import multiple schemas using xsd:import. In this scenario, I found
that:
- Axis wsdl2java works
- CapeClear SOA Editor validation succeeds
- Eclipse WTF (M7) WSDL validation fails
- MindReef SOAP Scop validation fails
To make matters worse, when I take things a step further towards my
real problem and import the 3rd party schemas I'm trying to use
(OTA), CapeClear SOA Editor hangs on validation.
Perhaps I'm doing something wrong, but it seems that the tools support
for this case is buggy and inconsistent. Hopefully when I get my
enterprise license for XMLSpy Enterprise the experience will be
better.
On 6/21/05, Anne Thomas Manes [EMAIL PROTECTED] wrote:
You need to define an element in your schema (rather than just a
type), and reference this element from your part description. You
need to do the same for your input message. And rather than using the
unwrapped document style, I recommend that you use the wrapped
document style, which means that you should define input and output
wrapper elements
xsd:schema targetNamespace=urn:listing2
xmlns:listing3=urn:listing3
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xsd:import namespace=urn:listing3 schemaLocation=listing3.xsd /
xsd:element name=getPhone
xsd:complexType
xsd:sequence
xsd:element name=name type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=getPhoneReturn
xsd:complexType
xsd:sequence
xsd:element name=phone type=listing3:Phone/
/xsd:sequence
/xsd:complexType
/xsd:element
/xsd:schema
wsdl:message name=GetPhoneRequest
wsdl:part name=parameters element=tns:getPhone /
/wsdl:message
wsdl:message name=GetPhoneResponse
wsdl:part name=parameters element=tns:getPhoneReturn /
/wsdl:message
Anne
On 6/21/05, Z Ellmy [EMAIL PROTECTED] wrote:
I'm trying to compose a valid doc/literal WSDL but I'm having trouble.
If I use:
wsdl:part name=phone type=listing3:Phone/
this works and I can generate stubs and bindings but SOAPScope and
other tools clue me that this violates WS-I Basic Profile:
Missing element attribute - Wsdl:part phone does not have an element
attribute defined and is referred to by a document style soap:body.
So, if I change this to:
wsdl:part name=phone element=listing3:Phone/
then I get an error with wsdl2java:
WSDL processing error for AddressBook.wsdl : Element {urn:listing3}Phone
is referenced but not defined.
So I guess my question is what is the correct way to import this type
from another schema file and still satisfy the WS-I requirements? This
is just a basic example, my real problem involves creating a WSDL
for an existing set of complex schemas.
I've attached my WSDL and my XSD.
I'll be the first to admit any ignorance and/or misunderstand of the
concepts here -- but I'd really appreciate some help :
AW: WSDL2Java Bug?
I got the same exception when i use polymorphism.
I definded an interface and used it as a method parameter. The wsdl creation
with java2wsdl succeeded but wsdl2java failed.
Do you use interfaces too?
Christian
-Ursprüngliche Nachricht-
Von: Antonio Ruiz Martínez [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 22. Juni 2005 21:02
An: axis-user@ws.apache.org
Betreff: WSDL2Java Bug?
Hello!
I have a problem with Axis 1.2.1. I thing that it is a bug because
the wsdl is very simple and I think is correct.
Here is the error:
java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy true
-t -p validate simple.wsdl
java.io.IOException: Type {http://www.w3.org/2000/09/xmldsig#}Reference
is referenced but not defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
Table.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
Could you tell me how I can solve it, please?
Regards,
Antonio.
--
--
Antonio Ruiz Martínez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
e-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es
--
Re: WSDL2Java Bug?
Hello!
Sorry I forgot attach the wsld, here is:
definitions xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:conv=http://www.openuri.org/2002/04/soap/conversation/;
xmlns:cw=http://www.openuri.org/2002/04/wsdl/conversation/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:jms=http://www.openuri.org/2002/04/wsdl/jms/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:ns0=http://ea.carm.es/schemas/basicos/seguridad/certificados/respuestaCertificado.xsd;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:s0=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.xsd;
xmlns:s1=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
targetNamespace=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl;
types
s:schema targetNamespace=mitarjet.xsd
s:import namespace=http://www.w3.org/2000/09/xmldsig#;
schemaLocation=http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd/
/s:schema
/types
message name=validaSigSoapIn
part name=parameters element=ds:Signature/
/message
message name=validaSigSoapOut
part name=parameters element=ds:Signature/
/message
portType name=ValidaSigWSSoap
operation name=validaSig
input message=s1:validaSigSoapIn/
output message=s1:validaSigSoapOut/
/operation
/portType
binding name=ValidaSigWSSoap type=s1:ValidaSigWSSoap
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
operation name=validaSig
soap:operation
soapAction=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl/validaSig;
style=document/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
/operation
/binding
service name=ValidaSigWS
port name=ValidaSigWSSoap binding=s1:ValidaSigWSSoap
soap:address
location=http://miip:80/servicios/basicos/seguridad/certificados/ValidaCertificadoWS.jws/
/port
/service
/definitions
Regards,
Antonio
Antonio Ruiz Martínez wrote:
Hello!
I have a problem with Axis 1.2.1. I thing that it is a bug because
the wsdl is very simple and I think is correct.
Here is the error:
java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy
true -t -p validate simple.wsdl
java.io.IOException: Type
{http://www.w3.org/2000/09/xmldsig#}Reference is referenced but not
defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
Table.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
Could you tell me how I can solve it, please?
Regards,
Antonio.
--
--
Antonio Ruiz Martínez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
e-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es
--
AW: WSDL2Java Bug?
..The paramter Signatur of method validaSig is not defined anywhere.
-Ursprüngliche Nachricht-
Von: Antonio Ruiz Martínez [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 22. Juni 2005 21:13
An: axis-user@ws.apache.org
Betreff: Re: WSDL2Java Bug?
Hello!
Sorry I forgot attach the wsld, here is:
definitions xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:conv=http://www.openuri.org/2002/04/soap/conversation/;
xmlns:cw=http://www.openuri.org/2002/04/wsdl/conversation/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:jms=http://www.openuri.org/2002/04/wsdl/jms/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:ns0=http://ea.carm.es/schemas/basicos/seguridad/certificados/respuestaCertificado.xsd;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:s0=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.xsd;
xmlns:s1=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
targetNamespace=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl;
types
s:schema targetNamespace=mitarjet.xsd
s:import namespace=http://www.w3.org/2000/09/xmldsig#;
schemaLocation=http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd/
/s:schema
/types
message name=validaSigSoapIn
part name=parameters element=ds:Signature/
/message
message name=validaSigSoapOut
part name=parameters element=ds:Signature/
/message
portType name=ValidaSigWSSoap
operation name=validaSig
input message=s1:validaSigSoapIn/
output message=s1:validaSigSoapOut/
/operation
/portType
binding name=ValidaSigWSSoap type=s1:ValidaSigWSSoap
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
operation name=validaSig
soap:operation
soapAction=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl/validaSig;
style=document/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
/operation
/binding
service name=ValidaSigWS
port name=ValidaSigWSSoap binding=s1:ValidaSigWSSoap
soap:address
location=http://miip:80/servicios/basicos/seguridad/certificados/ValidaCertificadoWS.jws/
/port
/service
/definitions
Regards,
Antonio
Antonio Ruiz Martínez wrote:
Hello!
I have a problem with Axis 1.2.1. I thing that it is a bug because
the wsdl is very simple and I think is correct.
Here is the error:
java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy
true -t -p validate simple.wsdl
java.io.IOException: Type
{http://www.w3.org/2000/09/xmldsig#}Reference is referenced but not
defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
Table.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
Could you tell me how I can solve it, please?
Regards,
Antonio.
--
--
Antonio Ruiz Martínez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
e-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es
--
Re: AW: WSDL2Java Bug?
Hello!
Christian Kunert wrote:
..The paramter Signatur of method " validaSig " is not defined anywhere.
But it imported from xmldsig, with
s:import namespace="http://www.w3.org/2000/09/xmldsig#"
schemaLocation="http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd"/
Regards,
Antonio.
-Ursprngliche Nachricht-
Von: Antonio Ruiz Martnez [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 22. Juni 2005 21:13
An: axis-user@ws.apache.org
Betreff: Re: WSDL2Java Bug?
Hello!
Sorry I forgot attach the wsld, here is:
definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/"
xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:ns0="http://ea.carm.es/schemas/basicos/seguridad/certificados/respuestaCertificado.xsd"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:s0="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.xsd"
xmlns:s1="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
targetNamespace="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl"
types
s:schema targetNamespace="mitarjet.xsd"
s:import namespace="http://www.w3.org/2000/09/xmldsig#"
schemaLocation="http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd"/
/s:schema
/types
message name="validaSigSoapIn"
part name="parameters" element="ds:Signature"/
/message
message name="validaSigSoapOut"
part name="parameters" element="ds:Signature"/
/message
portType name="ValidaSigWSSoap"
operation name="validaSig"
input message="s1:validaSigSoapIn"/
output message="s1:validaSigSoapOut"/
/operation
/portType
binding name="ValidaSigWSSoap" type="s1:ValidaSigWSSoap"
soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/
operation name="validaSig"
soap:operation
soapAction="http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl/validaSig"
style="document"/
input
soap:body use="literal"/
/input
output
soap:body use="literal"/
/output
/operation
/binding
service name="ValidaSigWS"
port name="ValidaSigWSSoap" binding="s1:ValidaSigWSSoap"
soap:address
location="http://miip:80/servicios/basicos/seguridad/certificados/ValidaCertificadoWS.jws"/
/port
/service
/definitions
Regards,
Antonio
Antonio Ruiz Martnez wrote:
Hello!
I have a problem with Axis 1.2.1. I thing that it is a bug because
the wsdl is very simple and I think is correct.
Here is the error:
java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy
true -t -p validate simple.wsdl
java.io.IOException: Type
{http://www.w3.org/2000/09/xmldsig#}Reference is referenced but not
defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
Table.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
Could you tell me how I can solve it, please?
Regards,
Antonio.
--
--
Antonio Ruiz Martnez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
e-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es
--
AW: AW: WSDL2Java Bug?
Okay.. i have no other ideas, sorry, but it sounds like a namespace problem.
Good luck,
christian
-Ursprüngliche
Nachricht-
Von: Antonio Ruiz Martínez
[mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 22. Juni 2005
21:31
An: axis-user@ws.apache.org
Betreff: Re: AW: WSDL2Java Bug?
Hello!
Christian Kunert wrote:
..The paramter Signatur of method validaSig is not defined anywhere.
But it imported from
xmldsig, with
s:import namespace=http://www.w3.org/2000/09/xmldsig# schemaLocation=http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd/Regards,Antonio.
-Ursprüngliche Nachricht-Von: Antonio Ruiz Martínez [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 22. Juni 2005 21:13An: axis-user@ws.apache.orgBetreff: Re: WSDL2Java Bug?Hello!Sorry I forgot attach the wsld, here is:definitions xmlns=http://schemas.xmlsoap.org/wsdl/ xmlns:conv=http://www.openuri.org/2002/04/soap/conversation/ xmlns:cw=http://www.openuri.org/2002/04/wsdl/conversation/ xmlns:http=http://schemas.xmlsoap.org/wsdl/http/ xmlns:jms=http://www.openuri.org/2002/04/wsdl/jms/ xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/ xmlns:ns0=http://ea.carm.es/schemas/basicos/seguridad/certificados/respuestaCertificado.xsd xmlns:s=http://www.w3.org/2001/XMLSchema xmlns:s0=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.xsd xmlns:s1=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/ xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:ds=http://www.w3.org/2000/09/xmldsig# targetNamespace=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl types s:schema targetNamespace=mitarjet.xsd s:import namespace=http://www.w3.org/2000/09/xmldsig# schemaLocation=http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd/ /s:schema /types message name=validaSigSoapIn part name=parameters element=ds:Signature/ /message message name=validaSigSoapOut part name=parameters element=ds:Signature/ /message portType name=ValidaSigWSSoap operation name=validaSig input message=s1:validaSigSoapIn/ output message=s1:validaSigSoapOut/ /operation /portType binding name=ValidaSigWSSoap type=s1:ValidaSigWSSoap soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ operation name=validaSig soap:operation soapAction=http://ea.carm.es/schemas/basicos/seguridad/certificados/ValidaCertificadoWS.wsdl/validaSig style=document/ input soap:body use=literal/ /input output soap:body use=literal/ /output /operation /binding service name=ValidaSigWS port name=ValidaSigWSSoap binding=s1:ValidaSigWSSoap soap:address location=http://miip:80/servicios/basicos/seguridad/certificados/ValidaCertificadoWS.jws/ /port /service/definitionsRegards,AntonioAntonio Ruiz Martínez wrote:
Hello! I have a problem with Axis 1.2.1. I thing that it is a bug because the wsdl is very simple and I think is correct.Here is the error:java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy true -t -p validate simple.wsdljava.io.IOException: Type {http://www.w3.org/2000/09/xmldsig#}Reference is referenced but not defined. at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:665) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTablejava:518) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Unknown Source)Could you tell me how I can solve it, please?Regards,Antonio.
-- --Antonio Ruiz MartínezFaculty of Computer Science-University of Murcia30071 Murcia - Spaine-mail: [EMAIL PROTECTED] or arm [at] dif [dot] um [dot] es--
Re: Bug with Arrays as Return Types
I've put together two webapps for comparision: one using Axis 1.1, the other using Axis 1.2. They can be downloaded here: http://www.public.iastate.edu/~andrewv/axis/webapps.zip They each have one service, StringArrayServer. In each case, the service is implemented by a Java class with one method: String[] getStringArray(); Each service is deployed via the AdminClient with the following deploy.wsdd: deployment name=test xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; xmlns:xsi=http://www.w3.org/2000/10/XMLSchema-instance; service name=StringArrayServer provider=java:RPC parameter name=scope value=request/ parameter name=className value=StringArrayServer/ parameter name=allowedMethods value=*/ /service /deployment The two versions of Axis generate nearly identical WSDL files for the services via the ?wsdl query in the URL. When a request is made, Axis 1.1 returns this XML: ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ns1:getStringArrayResponse soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=http://DefaultNamespace; ns1:getStringArrayReturn xsi:type=soapenc:Array soapenc:arrayType=xsd:string[3] xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; itemstring 1/item itemstring 2/item itemstring 3/item /ns1:getStringArrayReturn /ns1:getStringArrayResponse /soapenv:Body /soapenv:Envelope Axis 1.2 returns this XML, which fails to work with a .NET client built from the WSDL generated by the ?wsdl comand: ?xml version=1.0 encoding=utf-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ns1:getStringArrayResponse soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=http://DefaultNamespace; getStringArrayReturn soapenc:arrayType=soapenc:string[3] xsi:type=soapenc:Array xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; getStringArrayReturn xsi:type=soapenc:stringstring 1/getStringArrayReturn getStringArrayReturn xsi:type=soapenc:stringstring 2/getStringArrayReturn getStringArrayReturn xsi:type=soapenc:stringstring 3/getStringArrayReturn /getStringArrayReturn /ns1:getStringArrayResponse /soapenv:Body /soapenv:Envelope Is this considered a bug or just the new intended behavior? Thanks, Andrew At 10:48 AM 6/22/2005, you wrote: Oliver, I think I have a problem similar to yours. I had an RPC service written in Java from which I generated WSDL that was consumed by a .NET client. The client is in use, so I can't change the interface now. Upgrading to Axis 1.2 from 1.1 changes how arrays of Strings get returned to the .NET client--so I can't upgrade to Axis 1.2 without breaking the current system and making changes on the client. Like you, I know I'm doing things somewhat backward (going from Java to WSDL rather than the other way around). Is backward compatibility for this sort of scenario simply not a goal of Axis? Can any developers comment? Thanks, Andrew ***original message*** Hi Dims, thanks for your answer. I think that there is already a bug report for this bug (if \ it's stil present). I'm not sure but maybe I'm doing something bad with my \ deployment. The problem is: The webservices I'm working on are generated from \ CORBA-IDL - not from a WSDL as I have explained in my mail AXIS 1.2 and MS VB \ interop (arrays) So the way it goes is CORBA-IDL - idlj- Java-Stubs - deploy as \ WS - generate WSDL - generate Client-Stub. The generated WSDL is (the getUserDomainsByName-Methode returning an Array of \ TDomain makes trouble):
Problem calling AdminClient
Hello,
I am trying to call the AdminClient utility to process a wsdd file and am getting the exception below. Any ideas on how I an resolve this? I am running axis 1.2.1 on Jboss 4.01. In the jboss console I get a message that its unable to find the config and its creating a /web-inf/server-config.wsdd, which is followed by
-- in jboss console ---
18:35:01,436 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd18:36:34,620 INFO [AxisServlet] org.apache.axis.AxisFault: No HTTP SOAPAction property in context
-- from batch file --
Processing file deploy.wsddException: AxisFaultfaultCode: {http://xml.apache.org/axis/}HTTPfaultSubcode:faultString: (404)/axis/servicesfaultActor:faultNode:faultDetail: {}:return code: 404lt;htmlgt;lt;headgt;lt;titlegt;Apache Tomcat/5.0.28 - Error reportlt;/tit
thanks in Advance
Leslie.
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
Best IDE to use for Axis
I'm currently using NetBeans 4.1 as my Java IDE, but I have no idea how to use it with Axis. Are there any instructions on how to do this, or should I use another preferred IDE to develop web services?
