|
From: Bruce M. <br...@mc...> - 2003-04-04 02:58:15
|
On Thursday 03 April 2003 06:57 pm, ek...@ba... wrote:
No, its not worth it - just copy your own copy of the sqlconfig object. I
mean I can do this but these classes are really not intended for extending.
Bruce.
> I would like to create an interface as follows:
>
> package com.babeldoc.sql.config;
> import com.babeldoc.core.config.IConfigService;
> public interface ISqlConfigService extends IConfigService { }
>
> It's purpose would be to replace the following method signature in
> com.babeldoc.sql.SqlConfig
>
> public SqlConfig(String name, SqlConfigService service)
>
> with
>
> public SqlConfig(String name, ISqlConfigService service)
>
>
> My reason is that I have created a new class
> com.bankofny.iecc.alt.sql.config.SqlConfigService (which does NOT extend
> com.babeldoc.sql.config.SqlConfigService) and this cannot be passed as an
> argument to the constructor of SqlConfig (as seen above) because it is
> from a different package.
>
> By having both My SqlConfigService and the Standard Babeldoc
> SqlConfigService implementing ISqlConfigService (which just extends
> IConfigService), I could change the method signature for the constructor
> of SqlConfig to take an ISqlConfigService argument, rather than a
> SqlConfigService argument which ties it only to the babeldoc
> implementation.
>
> Please advise.
>
> Erik
|