cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Sutic" <leo.su...@inspireinfrastructure.com>
Subject RE: [Kernel22] How to develop a component?
Date Thu, 08 Apr 2004 14:29:17 GMT


> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
> Sent: den 8 april 2004 16:24
> To: dev@cocoon.apache.org
> Subject: RE: [Kernel22] How to develop a component?
> 
> 
> > 
> > > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> > >
> > > How does the working code look like?
> > 
> > The working code of what?
> > 
> > The adapter / sandbox / compatibility layer?
> > 
> The working code with some cocoon interfaces. I guess the 
> component interface for the stateful component is the same. 
> So, the different should be in the client.java code. Or am I wrong?

The new code would be very similar.

The new "Block" code uses Wirings instead of a
ComponentManager/ServiceManager,
but they are *very* similar. You should also include a
comp.ensureWired() call
at the top, to test if the block whose components you are using hasn't
been 
reloaded since you last checked. (This call will also reload the block
if it is
scheduled for reload, but not yet reloaded).

***The biggest change however***, is that you have to be prepared for
the
event that a component that you have looked up may disappear due to
block reloading.

This simply did not happen with Avalon. So you may get an exception
where 
you didn't get one before.

Otherwise you should be fine.

/LS


Mime
View raw message