Hi Dheeraj,
I think the top-down approach assumes that you know sufficiently about 
web services.  I think .jws -> java2wsdl -> handcode is the way to go 
about with top-down approach (assuming that you started with web 
services 1 month back).  This way you are not exposed to details in the 
beginning and as your understanding increases you can start tweaking 
and then finally move to handcode WSDL. 

True, java2WSDL wouldn't create the complex type hierarchy. When I 
suggested possible ways of generating WSDL I thought of simpler(normal) 
cases. 
And to add further .jws would also fail with complex class hierarchy.
 
I am responding even though the discussion has gone far because I felt 
that I should clear certain assumptions. 

DISCLAIMER:  
 Any Information contained or transmitted in this e-mail and / or 
attachments may contain confidential data, proprietary to Majoris 
Systems Pvt Ltd., and / or the authors of the information and is  
intended for use only by the individual or entity to which it is 
addressed. If you are not the intended recipient or email appears 
to have been sent to you by error, you are not authorised to access, 
read, disclose, copy, use or otherwise deal with it. If you 
have received this e-mail in error, please notify us immediately at 
mail to: [EMAIL PROTECTED] and delete this mail from your records.

This is to notify that Majoris Systems Pvt Limited shall have no  
liability or obligation, legal or otherwise, for any errors, 
omissions, viruses or computer problems experienced as a result of  
this transmission since data over the public Internet cannot be  
guaranteed to be secure or error-free. 

----- Original Message -----
From: "Soti, Dheeraj" <[EMAIL PROTECTED]>
Date: Thursday, March 24, 2005 0:19 am
Subject: RE: possible ways of creating WSDL file

> Sunil,
> 
> Will java2wsdl create the complex type hierarchies correctly? I 
> have a complex
> class hierarchy (using inheritance and nested classes) and finally 
> I ended up
> handcoding the wsdl from scratch. Did I miss something? I've also 
> read some best
> practice articles talking about top down approach where u write 
> your wsdl first
> and then proceed.
> 
> Thanks
> 
> Dheeraj
> 
> -----Original Message-----
> From: Sunil Kothari [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, March 23, 2005 1:20 AM
> To: [email protected]
> Cc: [EMAIL PROTECTED]
> Subject: Re:possible ways of creating WSDL file
> 
> 
> I think of 3 ways of creating WSDL
> 1) Using java2wsdl tool
> 2) Using .jws facility 
> 3) Handcode WSDL
> 
> I think 3) is error-prone and requires high level of understanding 
> of 
> WSDL. 2) is also not recommended for various reasons like 
> a) No deployment descriptors are created 
> b) WSDL is not persistent and prone to changes 
> c) (This I am not sure) For overloaded methods this way of 
> creation 
> causes problems.
> 
> I hope this helps.
> 
> Sunil Kothari
> Valtech India 
> 
> DISCLAIMER:  
> Any Information contained or transmitted in this e-mail and / or 
> attachments may contain confidential data, proprietary to Majoris 
> Systems Pvt Ltd., and / or the authors of the information and is  
> intended for use only by the individual or entity to which it is 
> addressed. If you are not the intended recipient or email appears 
> to have been sent to you by error, you are not authorised to 
> access, 
> read, disclose, copy, use or otherwise deal with it. If you 
> have received this e-mail in error, please notify us immediately 
> at 
> mail to: [EMAIL PROTECTED] and delete this mail from your records.
> 
> This is to notify that Majoris Systems Pvt Limited shall have no  
> liability or obligation, legal or otherwise, for any errors, 
> omissions, viruses or computer problems experienced as a result of 
> 
> this transmission since data over the public Internet cannot be  
> guaranteed to be secure or error-free. 
> 

Reply via email to