The problem with the Java->WSDL approach is that you can design code/objects
that either do not inter-operate well or do not distribute well, because of
this you *should* always use the WSDL->Java approach. The major drawback of
starting with WSDL is one of tooling. Starting with Java (or C#, VB/Net, .)
is easy because we are all familiar with the environment and the language,
whereas WSDL is complicated and there are not many good tools that let us
create and manage WSDL. One solution to this is to start with Java, create
the initial WSDL to get the 'outline', then throw away the Java and work
solely at the WSDL level,
Kevin Jones
http://kevinj.develop.com/weblog
_____
From: Fraser Crichton [mailto:fraser.crichton_at_solnetsolutions.co.nz]
Sent: 07 September 2005 02:50
To: users_at_jax-rpc.dev.java.net
Subject: WSDL > Java or Java > WSDL
Hi,
I've recently read a lot of best practice articles that suggests generating
Java artefacts from WSDL is the best approach to creating code for web
services. However, I've also heard that most people do not do this in
practice and still rely on the Java > WSDL approach. I'm trying to get an
idea of if there is anybody out there using the WSDL > Java approach and
what problems / issues people have with this?
Cheers,
Fraser
--
Fraser Crichton
XML Developer
SolNet Solutions Limited
L12, SolNet House, 70 The Terrace
PO Box 397, Wellington, Aotearoa / New Zealand
http://www.solnetsolutions.co.nz
DDI: 04-462-5078
Mob: 027-278-3392
Fax: 04-462-5011
email: fraser.crichton_at_solnetsolutions.co.nz
Attention: This email may contain information intended for the sole use of
the original recipient. Please respect this when sharing or disclosing this
email's contents with any third party. If you believe you have received this
email in error, please delete it and notify the sender or
postmaster_at_solnetsolutions.co.nz as soon as possible. The content of this
email does not necessarily reflect the views of SolNet Solutions Ltd.