Upayavira wrote:
Sylvain Wallez wrote:
Seconded. We will *all* need to run Cocoon as a servlet in whatever
J2EE server our customers require us to run it on (for example, we
recently were asked to deploy on an SAP app server). Saying that we
can't deploy on an app server because it's not available as an OSGi
HttpService will just make people throw away Cocoon, and us with it.
So although I clearly admit that using the OSGi HttpService is easier
to run Cocoon as a set of bundles, we shouldn't forget that we also
need to run Cocoon in a war file.
Yes, and, just to make it clear, no-one, including Daniel, suggested
that we wouldn't do so, only that doing it within the framework is easier.
Great!
And this requires to run the OSGi framework within a webapp
classloader. I understand this may prevent the use of the URL
service, and we have to find out if there are other issues as well.
This discussion clearly belongs to felix-dev.
Yup. When someone steps forward to solve that problem, that is the
place they should go.
I just sent our concerns to felix-dev. That's where we will have answers.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
