embedlets-developer

[Embedlets-dev] Re: A few release 003 questions

[Andrzej J. T. <an...@ch...>]

Ted:

> Here are a few questions that came up as I have been looking through the
> release 003 code:

Too bad version 0.04 just got posted. <grins>

> 1) In the core Embedlet build.xml file, if the 'compile' target depends on
> > the 'init' target, why are the 'build.dir' and 'build.classes'
> directories being made in both of these targets? 

Compile didn't used to depend on init, so it's just a historical artifact is 
all.  If you try to create a directory in Ant that already exists, nothing 
happens, so it's not a big deal.

> 2) The org.embedlet.Adapter class's Javadoc page states that 'The Adapter
> class is the base class for all Embedlets'.  Should 'Embedlets' here be
> 'Adapters'?

Yes.  I fixed that and posted a new version to the CVS source tree.  It is 
NOT fixed in the 0.04 release zip file.  That's what happens when you 
copy/paste files sometimes. ;-)

> 3) Looking at the org.embedlet.container class the following question occurred
> to me:  Will Embedlets be able to contain Embedlets? 

Nope!  An embedlet has to extend the org.embedlet.Embedlet abstract class 
(which in turn extends org.embedlet.Component).  An Embedlet is a component, 
which lives in and is managed by an Embedlet-compliant Container.  An 
Embedlet does not extend org.embedlet.Container which it would have to do to 
contain other components (which doesn't make much sense).  Only Outpost 
extends the Container contract.

Hope this helps!

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

[Embedlets-dev] Re: A few release 003 questions

[Ted K. <tk...@ya...>]

Andrzej,

> 
> > 3) Looking at the org.embedlet.container class the following question
> occurred
> > to me:  Will Embedlets be able to contain Embedlets? 
> 
> Nope!  An embedlet has to extend the org.embedlet.Embedlet abstract class 
> (which in turn extends org.embedlet.Component).  An Embedlet is a component, 
> which lives in and is managed by an Embedlet-compliant Container.  An 
> Embedlet does not extend org.embedlet.Container which it would have to do to 
> contain other components (which doesn't make much sense).  Only Outpost 
> extends the Container contract.

I know this is somewhat of an esoteric idea which probably does not have a
practical use but the thought that occurred to me was that if an Embedlet
container could be implemented practically anywhere, was it possible for one to
be implemented inside of an Embedlet (not by extending org.embedlet.Container
itself but by containing an object that did)?  Aside from whether it is
reasonable or not, is it possible?


Ted

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/