Hi Steve,
In order to help you I need some info on how you need to use the runtime
and on your environment.
What is the environment your application run ? An application server
like JBoss or
directly on a web container like tomcat ?
Regarding the target platform you need to know that nuxeo runtime works
by default in any OSGi platform,
on JBoss, on Glassfish and as a standalone java application.
If you need to run nuxeo runtime on other platform you need an adapter.
How do you plan to use nuxeo runtime?
Nuxeo runtime is primarily designed to define an extensible component
model and a runtime environment
that can be run on any host framework as long as an adapter exists.
Roughly nuxeo runtime uses the same concepts as OSGi - installable java
modules (JARs) are named bundles
and each bundle has a context created when the bundle is loaded by the
framework.
So the bundle context is the link between the bundle and the underlying
framework and it is responsible to load and locate classes and resources
inside the bundle it manage.
Each bundle may declare zero or more nuxeo components.
Nuxeo components are managed components that are started and stopped by
the run time when the containing bundle is installed / uninstalled
Each component is described by an XML file that is referenced from the
MANIFEST.MF using Nuxeo-Component: header
Components are usually driven by an implementation class but this is not
required.
Also components may declare extension points and/or contribute
extensions to other components (through the extension points they expose)
Extensions are described as XML and are transformed in java objects
using XMap (see org.nuxeo.commons.xmap)
Thus, you may have plain xml component without any implementation that
is only contributing some extensions to other components
(this is one of the differences between nuxeo components and osgi
components)
Also componentys may declare zero or more services. Runtime components
and services can be retrieved at runtime using the runtime framework API.
When loading components the parent bundle context is used to resolve
classes and resources that the component may use.
The context used to load components is named "runtime context" and
usually it wraps the bundle context.
The class loading model is dependent on the underlying framework. This
means the runtime context should hide
the differences between host frameworks class loading mechanisms.
The default implementation of the nuxeo runtime is assuming it is
running on a OSGi framework and provides an implementation of
the run time context that delegates its task to the OSGi bundle context.
So, the correct approach to port nuxeo runtime on other host frameworks
is to write a minimal OSGi adapter for the framework
and use the default nuxeo runtime implementation (which is assuming to
be on top of an OSGi framework)
I will help you more if you give me more info about your environment and
what exactly are your needs
Bogdan
[EMAIL PROTECTED] wrote:
>I will let Bogdan give you more information.
Thanks! I'm looking forward to any help I can get. :-)
> The pluggable deployemnt system of the Runtime that is used to
construct
> one JSF/Seam app from several jars can be used for JSP too.
> For example, it lets you contribute the web.xml and application.xml
from
> several separated components.
OK...a code crawling I shall go....again.
> The action and View system can be used in plain JSP but it will need
> some modifications.
Not the happiest words I could have heard.
> The pluggable authentification system should be directly reusable too.
OK. That might help.
> All other web related features are tied to JSF and Seam in the default
> implementation : Default webapp + ui-web + client plugins (wf, audit,
> relations, ...)
Back to the unhappy part. We aren't using JSF (Deemed it to unstable
and not quite ready for primetime for now...plus too few people using
it well.)
Seam...haven't even touched it yet.
> Are you only interested in the Runtime or also in Nuxeo5 Core and
> Services ?
The Runtime for now. I'm fairly new at the company I work for
now....and we are in the process of upgrading a current application.
Part of that process is the introduction of a decent web framework for
plugin functionality. The first step is a relatively simple
introduction of customer centric specializations - XSLT, SQL, &
Groovy scripts.
> Are you using JSF or plain JSP ?
JSP for now. Looking at revamping the framework. It's several years
old and a bit long in the tooth.
Thanks for the information so far.
Steve
**************************************
See what's free at http://www.aol.com.
------------------------------------------------------------------------
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
