[ https://issues.apache.org/jira/browse/SLING-11783 ]
Prasad Shembekar deleted comment on SLING-11783:
------------------------------------------
was (Author: JIRAUSER298546):
Hi,
We are currently using Apache Sling 6 as a war. While trying to upgrade the
version from 6 to 7,, changed the attached *pom.xml* to use
"{*}defaultBundleList=7{*}" for the
*org.apache.sling:maven-launchpad-plugin:2.3.4 (upgraded from 2.0.10 to 2.3.4).*
Updated the dependency for *org.apache.sling:org.apache.sling.launchpad.base
(from 2.3.0 to 2.5.0).*
In addition to the default bundles, we are explicitly packaging additional
bundles using the attached *list.xml.*
The war builds successfully after making the above changes.
But when, the war with the *apache sling 7* is deployed to {*}JBOSS EAP
7.4.0{*}, the war fails to deploy and exceptions related to bundle dependencies
are seen. Please see the attached *server.log* file for the errors.
{code:java}
2023-02-20 10:26:05,271 ERROR [io.undertow.servlet] (FelixStartLevel) ERROR:
Error starting
slinginstall:E:\cover-all\cms\sling\startup\0\org.apache.sling.engine-2.3.6.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.sling.engine [39]: Unable to resolve 39.0: missing requirement
[39.0] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=2.3.0)(!(version>=4.0.0)))):
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.sling.engine [39]: Unable to resolve 39.0: missing requirement
[39.0] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=2.3.0)(!(version>=4.0.0)))
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4002)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2045)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1299)
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:748) {code}
The war for *apache sling 6* is successfully deployed on the same *JBOSS EAP
7.4.0* server.
We tried explicitly adding the *javax.servlet* bundle to the *list.xml* at
{*}level=0{*}, but it also didn't work. Not sure what is missing.
*Note:* We are upgrading the sling version, in order to update the Jackrabbit
version. We are seeing some Jackrabbit & database connection leak related
issues, and thus trying to upgrade the jackrabbit version to the latest. Let us
know, if Jackrabbit can be directly upgraded instead. It will be really helpful
> Issue while upgrading version 6 to 7
> -------------------------------------
>
> Key: SLING-11783
> URL: https://issues.apache.org/jira/browse/SLING-11783
> Project: Sling
> Issue Type: Bug
> Components: App CMS, Launchpad
> Reporter: Prasad Shembekar
> Priority: Major
> Attachments: list.xml, pom.xml, server.log
>
>
> We are currently using Apache Sling 6 as a war. While trying to upgrade the
> version from 6 to 7,, changed the attached *pom.xml* to use
> "{*}defaultBundleList=7{*}" for the
> *org.apache.sling:maven-launchpad-plugin:2.3.4 (upgraded from 2.0.10 to
> 2.3.4).*
> Updated the dependency for *org.apache.sling:org.apache.sling.launchpad.base
> (from 2.3.0 to 2.5.0).*
> In addition to the default bundles, we are explicitly packaging additional
> bundles using the attached *list.xml.*
> The war builds successfully after making the above changes.
> But when, the war with the *apache sling 7* is deployed to {*}JBOSS EAP
> 7.4.0{*}, the war fails to deploy and exceptions related to bundle
> dependencies are seen. Please see the attached *server.log* file for the
> errors.
> {code:java}
> 2023-02-20 10:26:05,271 ERROR [io.undertow.servlet] (FelixStartLevel) ERROR:
> Error starting
> slinginstall:E:\cover-all\cms\sling\startup\0\org.apache.sling.engine-2.3.6.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.sling.engine [39]: Unable to resolve 39.0: missing requirement
> [39.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=2.3.0)(!(version>=4.0.0)))):
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.sling.engine [39]: Unable to resolve 39.0: missing requirement
> [39.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=2.3.0)(!(version>=4.0.0)))
> at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4002)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2045)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1299)
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
> at java.lang.Thread.run(Thread.java:748) {code}
> The war for *apache sling 6* is successfully deployed on the same *JBOSS EAP
> 7.4.0* server.
>
> We tried explicitly adding the *javax.servlet* bundle to the *list.xml* at
> {*}level=0{*}, but it also didn't work. Not sure what is missing.
> *Note:* We are upgrading the sling version, in order to update the Jackrabbit
> version. We are seeing some Jackrabbit & database connection leak related
> issues, and thus trying to upgrade the jackrabbit version to the latest. Let
> us know, if Jackrabbit can be directly upgraded instead. It will be really
> helpful
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
