axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: General Approach
Date Thu, 17 Apr 2003 00:59:36 GMT

Another way to approach this might be to create a wrapper for the class
that you want to expose and ensure that the wrapper does comply with the
standards required for Axis to correctly generate the RPC code.  Then you
don't need to maintain the generated code (it should just work).

My own SOAP RPC client code does not use any kind of axis code at all.  I
use JAX-RPC (with axis as the underlying implementation) and can make a
call to a web service in around 3 lines of code.




There is no magic.

                    Frank Apap                                                           
                    <fsa3@optonlin       To:              
          >               cc:                                          
                                         Subject:     RE: General Approach               
                    12:31 PM                                                             
                    Please respond                                                       
                    to axis-user                                                         

Well I'm kind of new to this myself.  Here are my thoughts (if I am
wrong please tell me I'm interested in learning the 'right' way):

#3 - I had trouble using ?WSDL method for generating the WSDL.  It
didn't seem to correctly create it (at least for a client applications
use).  It seemed to create different namespace then java2Wsdl (which is
what I now use.)

#4 - The use of wsdl2java is/was a source of great confusion for me.  I
don't see its benefits at least for my use.  It was much easier for met
to create my own client code with about 20 lines of code then have to
figure out what the generated code was doing.  That's just my opinion;
maybe I was using it wrong.


-----Original Message-----
From: Airline Pedestal []
Sent: Wednesday, April 16, 2003 3:05 PM
Subject: General Approach

Hi All,

   I've been hoping to use Apache Axis to make
my Java application available via the web.  I have
one class with several methods.  Many of the
in, out, and return parameters do not conform
to the standard (i.e. primitives, Java beans)
data types that Axis handles.  I have a XML
schema, and I plan to code custom (de)serlizers
for my data types.  My question is...  How
should I approach making this a web service with
Axis?  Following, is the steps that I've compiled
based on my research.

1. Develop a deploy.wsdd for my service.
   This specifies XML schema and custom
2. Use deploy.wsdd to deploy service into tomcat/axis.
3. Use
   to generate the wsdl file.
4. Use the generated wsdl with WSDL2Java to generate
   the client stubs, etc.
5. Modify the generated stubs as necessary.

Does this seem like a good approach?



Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo

Have you seen our website?....

CAUTION: This correspondence is confidential and intended for the named recipient(s) only.
If you are not the named recipient and receive this correspondence in error, you must not
distribute or take any action in reliance on it and you should delete it from your system
notify the sender immediately.  Thank you.

Unless otherwise stated, any views or opinions expressed are solely those of the author and
not represent those of Vodafone New Zealand Limited.

Vodafone New Zealand Limited
21 Pitt Street, Private Bag 92161, Auckland, 1020, New Zealand
Telephone + 64 9 357 5100
Facsimile + 64 9 377 0962

View raw message