On Mon, Sep 30, 2002 at 12:08:41AM +0200, Stephen McConnell wrote:
>
> > + ECM remains JDK1.2 compatible. Look, the damn thing is legacy
> >legacy legacy.
> > It works fine, but I'd rather have it remain A4.0 instead of trying
> >to mutate
> > it to A4.1, unless that mutation can be done without JDK1.3.
> >Branching is
> > another possiblity. Under JDK1.2, the lookup of a non-Component
> >implementing
> > component would throw a ComponentException, under 1.3 it would be
> >solved
> > via the proxy generator.
> >
>
> Is the ECM (CVS version) support for Serviceable based on proxying the
> interface? Is so, is there any reason why the ECM cannot simply be
> updated to handle serviceable components the good old fashined way (if x
> instanceof Serviceable ... )?
I think the issue why proxies were used is because Serviceable
components may not necessarily implement Component, so looking them
up in ECM will cause a ClassCastException due to the return type of
lookup().
The proxy adds Component to the list of implemented interfaces so the
return cast succeeds.
It's an interesting situation - but as far as Cocoon is concerned,
they don't have any Servicable (ie. non-Component implementing)
components, so they probably don't need this feature right now.
Maybe in the future, but in the future they'll most likely be looking
to move away from ECM and to the newer Containers anyway.
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
