You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Oliver Geisser <ol...@gmail.com> on 2007/11/05 12:49:39 UTC

Tapestry and OSGi (was: DISCUSS Remove Module autoloading)

Hi.

On Nov 5, 2007 10:12 AM, Kristian Marinkovic <
kristian.marinkovic@porsche.co.at> wrote:

> [...]
> maybe T5 IoC should work on top of OSGi. Along with module handling
> (autoload, access control) we could take advantage of OSGis runtime
> behaviour.  (Eclipse Equinox does support many of the concepts found
> in T5 IoC like extension-points and extensions aka. configurations and
> features an autoload bundle)
> [...]


To make Tapestry work on top of OSGi would be a killer feature. Currently
there is
a lot of activity related to OSGi to use OSGi on the server side, especialy
for
Web Development. From my point of view OSGi and Tapestry are similar in the
spirit they want ot achieve: strong component modularizaton and highly
dynamic
environment.

There is also the "marketing" point. Tapestry 5 would be the first
webframework
with native OSGi support.


Greetings, Olli

-- 
og