[
http://jira.amdatu.org/jira/browse/AMDATU-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10168#comment-10168
]
Ivo Ladage - van Doorn edited comment on AMDATU-128 at 10/27/10 11:11 AM:
--------------------------------------------------------------------------
It seems that Apache Sling is a bad choice. Sling is a web framework in itself
and the compile and runtime JSP bundles cannot easily be deployed solely on an
OSGi container. You will need to deploy many other Sling bundles, introducing
unwanted dependencies and increased footprint. The most important unwanted
dependency is the availability of a JCR storage.
Basically Sling is a web framework which internally uses OSGi for flexibility
and SOA support, it was not designed as independent components running in an
arbitrary OSGi container.
Equinox also has some compile/runtime JSP bundles, but like many other Equinox
bundles these bundles cannot be deployed in an arbitrary OSGi container; they
need the Equinox-OSGi runtime.
Another option may using the Jasper libraries. I'll try that first.
was (Author: ivol):
It seems that Apache Sling is a bad choice. Sling is a web framework in
itself can the compile and runtime JSP bundles cannot easily be deployed solely
on an OSGi container. You will need to deploy many other Sling bundles,
introducing unwanted dependencies and increased footprint. The most important
unwanted dependency is the availability of a JCR storage.
Basically Sling is a web framework which internally uses OSGi for flexibility
and SOA support, it was not designed as independent components running in an
arbitrary OSGi container.
Equinox also has some compile/runtime JSP bundles, but like many other Equinox
bundles these bundles cannot be deployed in an arbitrary OSGi container; they
need the Equinox-OSGi runtime.
Another option may using the Jasper libraries. I'll try that first.
> Replace Pax JSP bundle with an implementation that could work with any
> implementation of the OSGi HTTP service specification
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMDATU-128
> URL: http://jira.amdatu.org/jira/browse/AMDATU-128
> Project: Amdatu
> Issue Type: Improvement
> Components: Platform - HTTP Context
> Affects Versions: 0.0.6
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.0.6
>
>
> Pax Web implements the OSGi HTTP Service specification, but on top of that
> provides an extended API. The bundle 'OPS4J Pax Web - Jsp Support' depends on
> the availability of this extended HTTP service. This means that currently we
> are stuck to the Pax implementation of the HTTP Service; we cannot simply
> replace the http bundle by any implementation of the HTTP Service.
> To resolve this unwanted dependency, the first step is to replace the Pax JSP
> bundle with an implementation that does not depend on Pax Web. We might use
> the Apache Sling Scripting project for this, see
> http://sling.apache.org/site/servlet-resolution.html
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
