But the problem still remains:
interface DataSourceComponent {
String ROLE =
"org.apache.avalon.excalibur.datasources.DataSourceComponentSelector";
Connection getConnection();
}
Shouldn't the role be
"org.apache.avalon.excalibur.datasources.DataSourceComponent"? According to
the general rule?
Maybe:
interface DataSourceComponent {
String ROLE =
"org.apache.avalon.excalibur.datasources.DataSourceComponent";
String SELECTORROLE =
"org.apache.avalon.excalibur.datasources.DataSourceComponentSelector";
String MULTIPLEROLEROOT = "org.apache.avalon.excalibur.datasources.";
Connection getConnection();
}
I'll wait for the paper, but I still see problems with your approach.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- RE: [Proposal] Should we introduce a new idiom for Compo... Leo Simons
- Re: [Proposal] Should we introduce a new idiom for Compo... Charles Benett
- RE: [Proposal] Should we introduce a new idiom for ... Stephen McConnell
- Re: [Proposal] Should we introduce a new idiom for Compo... Harmeet Bedi
- Re: [Proposal] Should we introduce a new idiom for Compo... Peter Donald
- Re: [Proposal] Should we introduce a new idiom for Compo... Harmeet Bedi
- RE: [Proposal] Should we introduce a new idiom for Compo... Leo Sutic
- Re: [Proposal] Should we introduce a new idiom for Compo... Berin Loritsch
- Re: [Proposal] Should we introduce a new idiom for Compo... Berin Loritsch
- Re: [Proposal] Should we introduce a new idiom for Compo... Leo Sutic
- Re: [Proposal] Should we introduce a new idiom for Compo... Berin Loritsch
- Re: [Proposal] Should we introduce a new idiom for Compo... Peter Donald
- Re: [Proposal] Should we introduce a new idiom for ... Berin Loritsch
- RE: [Proposal] Should we introduce a new idiom for Compo... Leo Simons
- RE: [Proposal] Should we introduce a new idiom for Compo... Ricardo Rocha
