Re: Using AXIS for java web services

Thu, 07 Jul 2005 09:24:31 -0700

Hi Neelam,
I'll make my help attempt in 2 parts. once for the novice (such as myself) and the other is a bit more axis configuration related.

Have you tried accessing the .jws file first, from a web browser?
You need to do this in order for the Axis to compile and generate the required classes (the service and the descriptor). Untill you don't do that, you won't have a service and a description available.
You should do that first and access it (using a browser) and see it gives you an indication there's a web service running there (a message in the html page you'll view).

If you get an error there, you should try and find out if your Axis deployment is good. Have you tried running happyaxis?
Running happyaxis is very important, as i've discovered. It gives  you a very good listing of what libraries are installed and what are not. Of which, what libraries are mandatory.
I suggest you install all libraries in this listing, even the not mandatory ones.
Having the jar files and compiler jars and other related lib files in the right place is very very important.

i missed a step or two on my first attempts and i needed to read real good the installation and development guide in order to make it all work.

If my silly questions were dealt by you, already, to your satisfaction, you might consider trying and just compiling the original class (named as .java file) using the javac command. You may have errors there.

I think these could be some good pointers for beginning.

I'm sorry, again, if my questions seem silly for you. It's not disrespect. I just had to learn those in the hard way :)

Having all that said and done... here comes the hard part.
When importing other packages, have you kept the directory structure? Have you put them in the righr comman separated order in the director structure?
Are the other classes compiled?
Try putting the external classes in your CLASSPATH system variable or AXISCLASSPATH. The importance of defining the axis environment (or system) variables is crucial.

I hope i was able to help a little.

Moshe

Neelam Bhatnagar wrote: 
Hello,

We are using AXIS 1.2 for developing Java Web services. We have a java program which is needed to be deployed as a web service. This program uses methods from classes which are in a different package. Hence we have an import <package name> statement in this program. This java program is saved as a JWS file under the AXIS folder. But when we try to access the WSDL for the JWS, the following error comes:


AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - Error while compiling:  /data/jakarta_tomcat_4.0.6/jakarta-tomcat-4.0.6/webapps/axis/WEB-INF/jwsClasses/OcwCleanDirectory.java

AxisFault
 faultCode: {http://xml.apache.org/axis/}Server.compileError
 faultSubcode: 
 faultString: Error while compiling:  /data/jakarta_tomcat_4.0.6/jakarta-tomcat-4.0.6/webapps/axis/WEB-INF/jwsClasses/OcwCleanDirectory.java
 faultActor: 
 faultNode: 
 faultDetail: 
	{}Errors:Error compiling /data/jakarta_tomcat_4.0.6/jakarta-tomcat-4.0.6/webapps/axis/WEB-INF/jwsClasses/OcwCleanDirectory.java:
Line 0, column 0: could not parse error message:  Note: sun.tools.javac.Main has been deprecated.
/data/jakarta_tomcat_4.0.6/jakarta-tomcat-4.0.6/webapps/axis/WEB-INF/jwsClasses/OcwCleanDirectory.java:17: Package Common not found in import.
import Common.*;


How can we solve this problem? Any help will be greatly appreciated.

Thanks and regards
Neelam Bhatnagar
 



-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, July 07, 2005 8:41 PM
To: axis-user
Subject: Re: Error seen on BizTalk client request to my web service

There's an error in this WSDL. When I validate it with the Cape Clear
SOA Editor, I get the following errors:

Warning : 1004 : There is no schema component of the name
[ProvidentResponse] defined in the WSDL either via imported or
embedded schema.

Warning : 1003 : WSDLException: faultCode=PARSER_ERROR: failed parsing
schemas into object model - validation error: missing prefix mapping
for value 'tns1:ProvidentResponse' in attribute type:
/wsdl:definitions/wsdl:types/schema/element[1]/complexType/sequence/element:
validation error: missing prefix mapping for value
'tns1:ProvidentResponse' in attribute type:
/wsdl:definitions/wsdl:types/schema/element[1]/complexType/sequence/element

Anne

On 7/7/05, Patrick Quinn <[EMAIL PROTECTED]> wrote:
  
Hi Anne

Below is the WSDL found at:
http://192.168.1.150:8880/axis/services/ProvidentConnector_ProvidentRece
iver_ProvidentWSPortSoap?WSDL

Patrick




 <?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions targetNamespace="http://namespace.accenture.com/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://namespace.accenture.com/"
xmlns:intf="http://namespace.accenture.com/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <wsdl:types>
- <schema targetNamespace="http://namespace.accenture.com/"
xmlns="http://www.w3.org/2001/XMLSchema">
- <element name="SOPResponse">
- <complexType>
- <sequence>
 <element name="ProvidentResponse" type="tns1:ProvidentResponse" />
 </sequence>
 </complexType>
 </element>
- <element name="SOPResponseResponse">
- <complexType>
- <sequence>
 <element name="part" type="xsd:string" />
 </sequence>
 </complexType>
 </element>
 </schema>
 </wsdl:types>
- <wsdl:message name="SOPResponseResponse">
 <wsdl:part element="impl:SOPResponseResponse" name="parameters" />
 </wsdl:message>
- <wsdl:message name="SOPResponseRequest">
 <wsdl:part element="impl:SOPResponse" name="parameters" />
 </wsdl:message>
- <wsdl:portType
name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
- <wsdl:operation name="SOPResponse" parameterOrder="">
 <wsdl:input message="impl:SOPResponseRequest"
name="SOPResponseRequest" />
 <wsdl:output message="impl:SOPResponseResponse"
name="SOPResponseResponse" />
 </wsdl:operation>
 </wsdl:portType>
- <wsdl:binding
name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoapSoapBindin
g" type="impl:ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
 <wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="SOPResponse">
 <wsdlsoap:operation
soapAction="http://namespace.accenture.com/ProvidentConnector_ProvidentR
eceiver_ProvidentWSPort/SOPResponse" />
- <wsdl:input name="SOPResponseRequest">
 <wsdlsoap:body namespace="http://namespace.accenture.com/"
use="literal" />
 </wsdl:input>
- <wsdl:output name="SOPResponseResponse">
 <wsdlsoap:body namespace="http://namespace.accenture.com/"
use="literal" />
 </wsdl:output>
 </wsdl:operation>
 </wsdl:binding>
- <wsdl:service
name="ProvidentConnector_ProvidentReceiver_ProvidentWSPort">
- <wsdl:port
binding="impl:ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoapSo
apBinding"
name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
 <wsdlsoap:address
location="http://192.168.1.150:8880/axis/services/ProvidentConnector_Pro
videntReceiver_ProvidentWSPortSoap" />
 </wsdl:port>
 </wsdl:service>
 </wsdl:definitions>



-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: 07 July 2005 14:57
To: [email protected]
Subject: Re: Error seen on BizTalk client request to my web service


Patrick,

This obviously isn't the WSDL file for your test Axis service. Because
that WSDL file will specify the correct location URI. Please send me the
WSDL that you obtain by adding the ?wsdl to the location URI.

Anne

On 7/7/05, Patrick Quinn <[EMAIL PROTECTED]> wrote:
    
Hi Anne

The client soap request, client code, error message, WSDL, and WSDD
are
below:

Thanks

Pat

*CLIENT SOAP REQUEST*

<?xml version="1.0" encoding="UTF8"?>
<soapenv:Envelope
xmlsn: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>
   <SOPResponse xmlns="http://namespace.accenture.com/">
     nsl:ProvidentResponse
xmlns:nsl="http://ProvidentConnector.ProvidentResponseToOrch">
       <REQUESTID xmlns="">1</REQUESTID>
       <SO_RESULT_CODE xmlns="">2</SO_RESULT_CODE>
       <SO_ERR_DESC xmlns="">blank</SO_ERR_DESC>
       <XML_SORESULT xmlns="">0</XML_SORESULT>
     </nsl:ProvidentResponse>
   </SOPResponse>
 </soapenv:Body>
</soapenv:Envelope>


*client code*


com.accenture.namespace.ProvidentConnector_ProvidentReceiver_Provident
WS
Port wsPort = new

      
com.accenture.namespace.ProvidentConnector_ProvidentReceiver_ProvidentWS
    
PortLocator();

ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap pt =
wsPort.getProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap(ser
vi
ceURL);

Where serviceURL is configurable, and set currently to:
http://192.168.1.150:8880/axis/services/ProvidentConnector_ProvidentRe
ce
iver_ProvidentWSPortSoap



*error*


ERROR!!!!org.xml.sax.SAXException: Deserializing parameter
'ProvidentResponse':  could not find deserializer for type
{http://ProvidentConnector.ProvidentResponseToOrch}ProvidentResponse


*WSDD file*

<deployment
   xmlns="http://xml.apache.org/axis/wsdd/"
   xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">

 <!-- Services from
ProvidentConnector_ProvidentReceiver_ProvidentWSPort WSDL service -->

 <service
name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap"
provider="java:RPC" style="wrapped" use="literal">
     <parameter name="wsdlTargetNamespace"
value="http://namespace.accenture.com/"/>
     <parameter name="wsdlServiceElement"
value="ProvidentConnector_ProvidentReceiver_ProvidentWSPort"/>
     <parameter name="schemaQualified"
value="http://ProvidentConnector.ProvidentResponseToOrch,http://namesp
ac
e.accenture.com/"/>
     <parameter name="wsdlServicePort"
value="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap"/>
     <parameter name="className"

      
value="com.accenture.namespace.ProvidentConnector_ProvidentReceiver_Prov
    
identWSPortSoapSkeleton"/>
     <parameter name="wsdlPortType"
value="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap"/>
     <parameter name="typeMappingVersion" value="1.2"/>
     <parameter name="allowedMethods" value="*"/>

     <typeMapping
       xmlns:ns="http://ProvidentConnector.ProvidentResponseToOrch"
       qname="ns:ProvidentResponse"


      
type="java:ProvidentResponseToOrch.ProvidentConnector.ProvidentResponse"
    
       serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"

deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
       encodingStyle=""
     />
 </service>
</deployment>




* WSDL file *

<?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/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://namespace.accenture.com/"
xmlns:tm="http://microsoft.com/wsdl/mime/textM
atching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
targetNamespace="http://namespace.accenture.com/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
 <wsdl:types>
   <s:schema elementFormDefault="qualified"
targetNamespace="http://namespace.accenture.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 e-mail and any attachments may be confidential and/or legally
privileged. If you have received this e-mail and you are not a named
addressee, please inform Evolving Systems TIS at [EMAIL PROTECTED] and
then delete the e-mail from your system. If you are not a named
addressee you must not use, disclose, distribute, copy, print or rely
on this e-mail. To ensure regulatory compliance and for the protection
      
of our clients and business, Evolving Systems may monitor and read
e-mails sent to and from its servers. Although Evolving Systems
routinely screens for viruses, addressees should scan this e-mail and
any attachments for viruses. Evolving Systems makes no representation
or warranty as to the absence of viruses in this e-mail or any
attachments.

Registered Office: One Angel Square, Torrents Street, London. EC1V
1PL. Registered number 2325854

      
This e-mail and any attachments may be confidential and/or legally privileged. If you have received this e-mail and you are not a named addressee, please inform Evolving Systems TIS at [EMAIL PROTECTED] and then delete the e-mail from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this e-mail. To ensure regulatory compliance and for the protection of our clients and business, Evolving Systems may monitor and read e-mails sent to and from its servers. Although Evolving Systems routinely screens for viruses, addressees should scan this e-mail and any attachments for viruses. Evolving Systems makes no representation or warranty as to the absence of viruses in this e-mail or any attachments.

Registered Office: One Angel Square, Torrents Street, London. EC1V 1PL. Registered number 2325854

Reply via email to