Nathaniel Alfred wrote:
-----Original Message-----
From: Daniel Fagerstrom [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 26. Mai 2005 15:42
To: [email protected]
Subject: Re: [RT] Block usage
a block deployer block
Basically the block deployer will be a stand-alone application (Ant
task, Maven plug-in, Eclipse plug-in, ...). Of course somebody could
write a web interface for it which could be a cocoon block.
As you can see in my original message I proposed: a block deployer
block, a block depoyer webapp block. Web interface and functinality
should cleary be kept separately.
Having read the OSGi whitepaper but not having followed in detail the
discussion about the vision of "real blocks", I am confused now.
Aren't OSGi bundles already what Cocoon blocks want to be? "Just"
package each block into a bundle with the right dependencies and
deploy it into the OSGi kernel.
true for the classloading part
What am I missing?
... but there needs some work to enable the blocks:/ protocol, component
management and block-aware flowscript (e.g. cocoon.blocks.blockA.myFunc())
Additionally we have to integrate Torsten's classloader to ease development and
we need to work on block building and deploying.
--
Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
