axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Jordahl <t...@macromedia.com>
Subject RE: Service interface
Date Mon, 04 Feb 2002 15:20:32 GMT

Here is a suggestion: Check for "Service" at the end of the name, and don't append it if it's
already there.  This prevents the stupid name. Still avoids name clashes.

--
Tom Jordahl


-----Original Message-----
From: Russell Butek [mailto:butek@us.ibm.com]
Sent: Monday, February 04, 2002 10:09 AM
To: axis-dev@xml.apache.org
Subject: Service interface


JAX-RPC 0.6 discussed generating a service interface and a service
implementation.  The interface was optional.  In the interests of
minimizing generated files, AXIS opted to NOT generate the interface.

In JAX-RPC 0.7 the service interface is no longer optional.  If the service
is named X, the service interface is named X.  That's the name we'd been
using for the implementation.  I would like to rename the implementation to
XServiceImpl.  I will not simply rename it XImpl because I've occasionally
seen a binding and a service share the same name and we already generate an
implementation template called <bindingName>Impl.  Of course, most often
the service name is something like XService, so we'd be generating the
rather strangely named class XServiceServiceImpl.  I'd be happy to hear
better suggestions if folks have them.

Russell Butek
butek@us.ibm.com

Mime
View raw message