also am not a fan of having 2 "Impl" files. But I don't have any really
good replacement names off the top of my head. Can we change one of the
other file names to be called "Interface" and drop the Impl from its
corresponding concrete java class?
--
Tom Jordahl
-Orig
;Impl" files. But I don't have any really
good replacement names off the top of my head. Can we change one of the
other file names to be called "Interface" and drop the Impl from its
corresponding concrete java class?
--
Tom Jordahl
-Original Message-
From: Russel
an we change one of the other file names
to be called "Interface" and drop the Impl from its corresponding concrete java class?
--
Tom Jordahl
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 5:08 PM
To: [EMAIL PROTECTED]
Subje
ppy. Any ideas?
binding impl: Template
service impl: Impl
binding impl: Impl
service impl: Concrete
binding impl: Impl
service impl: Factory
Russell Butek
[EMAIL PROTECTED]
Richard Sitze/Charlotte/IBM@IBMUS on 02/04/2002 09:39:46 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PRO
/2002 09:20 Subject: RE: Service interface
AM
Please respond
uot; <[EMAIL PROTECTED]>
cc:
Subject: RE: Service interface
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---
Russell,
Is JAX-RPC 0.7 public yet? URL?
Thanks,
dims
--- Russell Butek <[EMAIL PROTECTED]> wrote:
> 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
February 04, 2002 10:09 AM
To: [EMAIL PROTECTED]
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
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
