You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@sling.apache.org by Guillaume Lucazeau <gl...@gmail.com> on 2015/11/23 14:01:28 UTC
Deploy Sling to JBoss EAP 6.4.0
Hello,
I am trying to run Sling on JBoss. Following this article
http://bobpaulin.com/home/computer_science/tutorials/setting_up_sling_jboss.html
I've just added the "sling.home" parameter and copied sling.war to
jboss/standalone.deployments, but when starting JBoss I get this error:
13:44:15,206 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
(FelixStartLevel) ERROR: Error starting
slinginstall:org.apache.felix.http.bridge-3.0.0.jar
(org.osgi.framework.BundleException: Unable to resolve
org.apache.felix.http.bridge [6](R 6.0): missing requirement
[org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
org.osgi.framework.BundleException: Unable to resolve
org.apache.felix.http.bridge [6](R 6.0): missing requirement
[org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
at
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4114)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2111)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1365)
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
And http://localhost:8080/sling returns a 503 error.
If I try to follow the article and add this to sling.properties :
sling.bootdelegation.org.apache.xerces=org.apache.xerces.*
I just get more errors.
I'm not sure whih package is actually missing, is it javax.servlet.*?
Any clue on how to fix this?
Thank you,
Guillaume
Re: Deploy Sling to JBoss EAP 6.4.0
Posted by Guillaume Lucazeau <gl...@gmail.com>.
Hello Carsten,
> Just to be sure, does that JBoss version support servlet 3.1?
That was a good question, actually JBoss EAP 6.4.0 doesn't:
https://access.redhat.com/articles/113373
I don't know if JBoss EAP 7 will support it, but WildFly 9.0.2 (the
community version) supports it and I've successfully deployed Sling to it.
So I'll just go with that for now, and maybe switch back to Sling 7 if the
client is using JBoss EAP, as I also have to figure out how to connect
Jackrabbit or Oak to Oracle DB.
Once again, thank you very much for your help
Regards,
Guillame
On Mon, Nov 23, 2015 at 5:25 PM, Carsten Ziegeler <cz...@apache.org>
wrote:
> Hi Guillaume,
>
> I changed it to:
> <web-app version="3.1"
> xmlns="http://xmlns.jcp.org/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
> http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
>
> (Oracle changed the url of the schema...)
>
> If you checkout the latest and build base and then builder, the
> resulting war will have the correct web.xml. (But of course editing by
> hand should give you the same).
> Just to be sure, does that JBoss version support servlet 3.1?
>
> Regards
> Carsten
>
> Guillaume Lucazeau wrote
> > Hello Carsten,
> >
> > Did you change the file like this?
> > web-app version="3.1"
> > xmlns="http://java.sun.com/xml/ns/j2ee"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> > http://java.sun.com/xml/ns/j2ee/web-app_3_1.xsd">
> >
> > I've changed it in "sling/launchpad/base/src/main/webapp/WEB-INF/web.xml"
> > but the web.xml in the war generated by Maven was still containing 3.0,
> and
> > actually none of my changes (i.e. sling.home property)
> >
> > So I've just edit the war manually with the above line and redeployed it
> > but it seems I still have the same issue:
> >
> > 16:40:07,287 ERROR
> >
> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
> > (FelixStartLevel) ERROR: Error starting
> > slinginstall:org.apache.felix.http.bridge-3.0.2.jar
> > (org.osgi.framework.BundleException: Unable to resolve
> > org.apache.felix.http.bridge [10](R 10.0): missing requirement
> > [org.apache.felix.http.bridge [10](R 10.0)] osgi.wiring.package;
> > (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> > Unresolved requirements: [[org.apache.felix.http.bridge [10](R 10.0)]
> > osgi.wiring.package;
> >
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
> > org.osgi.framework.BundleException: Unable to resolve
> > org.apache.felix.http.bridge [10](R 10.0): missing requirement
> > [org.apache.felix.http.bridge [10](R 10.0)] osgi.wiring.package;
> > (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> > Unresolved requirements: [[org.apache.felix.http.bridge [10](R 10.0)]
> > osgi.wiring.package;
> >
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
> > at
> > org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111)
> > at org.apache.felix.framework.Felix.startBundle(Felix.java:2117)
> > at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
> > at
> >
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
> > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> >
> > On Mon, Nov 23, 2015 at 3:02 PM, Carsten Ziegeler <cz...@apache.org>
> > wrote:
> >
> >> I've just updated launchpad base to require 3.1 servlet in the web.xml
> >> and tested this with Tomcat. I hope/guess this should work in jboss as
> well
> >>
> >> Carsten
> >>
> >> Carsten Ziegeler wrote
> >>> Hi,
> >>>
> >>> launchpad is searching for servlet API 3.1 and I assume your webapp
> gets
> >>> started with 3.0.
> >>> This seems to be due to the web.xml just requiring 3.0.
> >>>
> >>> Could you please check by
> >>> a) Changing the version to 3.1 in
> >>> sling/launchpad/base/src/main/webapp/WEB-INF/web.xml
> >>> b) Rebuilding launchpad/base
> >>> c) Rebuilding launchpad/builder
> >>> d) Redeploying the war file
> >>>
> >>> Thanks
> >>> Carsten
> >>>
> >>> Guillaume Lucazeau wrote
> >>>> Hello,
> >>>>
> >>>> I am trying to run Sling on JBoss. Following this article
> >>>>
> >>
> http://bobpaulin.com/home/computer_science/tutorials/setting_up_sling_jboss.html
> >>>> I've just added the "sling.home" parameter and copied sling.war to
> >>>> jboss/standalone.deployments, but when starting JBoss I get this
> error:
> >>>>
> >>>> 13:44:15,206 ERROR
> >>>>
> >>
> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
> >>>> (FelixStartLevel) ERROR: Error starting
> >>>> slinginstall:org.apache.felix.http.bridge-3.0.0.jar
> >>>> (org.osgi.framework.BundleException: Unable to resolve
> >>>> org.apache.felix.http.bridge [6](R 6.0): missing requirement
> >>>> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
> >>>>
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> >>>> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
> >>>> osgi.wiring.package;
> >>>>
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
> >>>> org.osgi.framework.BundleException: Unable to resolve
> >>>> org.apache.felix.http.bridge [6](R 6.0): missing requirement
> >>>> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
> >>>>
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> >>>> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
> >>>> osgi.wiring.package;
> >>>>
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
> >>>> at
> >>>>
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4114)
> >>>> at org.apache.felix.framework.Felix.startBundle(Felix.java:2111)
> >>>> at
> >> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1365)
> >>>> at
> >>>>
> >>
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
> >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> >>>>
> >>>> And http://localhost:8080/sling returns a 503 error.
> >>>>
> >>>> If I try to follow the article and add this to sling.properties :
> >>>> sling.bootdelegation.org.apache.xerces=org.apache.xerces.*
> >>>>
> >>>> I just get more errors.
> >>>>
> >>>> I'm not sure whih package is actually missing, is it javax.servlet.*?
> >>>>
> >>>> Any clue on how to fix this?
> >>>>
> >>>> Thank you,
> >>>> Guillaume
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Carsten Ziegeler
> >> Adobe Research Switzerland
> >> cziegeler@apache.org
> >>
> >
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>
Re: Deploy Sling to JBoss EAP 6.4.0
Posted by Carsten Ziegeler <cz...@apache.org>.
Hi Guillaume,
I changed it to:
<web-app version="3.1"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
(Oracle changed the url of the schema...)
If you checkout the latest and build base and then builder, the
resulting war will have the correct web.xml. (But of course editing by
hand should give you the same).
Just to be sure, does that JBoss version support servlet 3.1?
Regards
Carsten
Guillaume Lucazeau wrote
> Hello Carsten,
>
> Did you change the file like this?
> web-app version="3.1"
> xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_3_1.xsd">
>
> I've changed it in "sling/launchpad/base/src/main/webapp/WEB-INF/web.xml"
> but the web.xml in the war generated by Maven was still containing 3.0, and
> actually none of my changes (i.e. sling.home property)
>
> So I've just edit the war manually with the above line and redeployed it
> but it seems I still have the same issue:
>
> 16:40:07,287 ERROR
> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
> (FelixStartLevel) ERROR: Error starting
> slinginstall:org.apache.felix.http.bridge-3.0.2.jar
> (org.osgi.framework.BundleException: Unable to resolve
> org.apache.felix.http.bridge [10](R 10.0): missing requirement
> [org.apache.felix.http.bridge [10](R 10.0)] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> Unresolved requirements: [[org.apache.felix.http.bridge [10](R 10.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.felix.http.bridge [10](R 10.0): missing requirement
> [org.apache.felix.http.bridge [10](R 10.0)] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> Unresolved requirements: [[org.apache.felix.http.bridge [10](R 10.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2117)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
>
> On Mon, Nov 23, 2015 at 3:02 PM, Carsten Ziegeler <cz...@apache.org>
> wrote:
>
>> I've just updated launchpad base to require 3.1 servlet in the web.xml
>> and tested this with Tomcat. I hope/guess this should work in jboss as well
>>
>> Carsten
>>
>> Carsten Ziegeler wrote
>>> Hi,
>>>
>>> launchpad is searching for servlet API 3.1 and I assume your webapp gets
>>> started with 3.0.
>>> This seems to be due to the web.xml just requiring 3.0.
>>>
>>> Could you please check by
>>> a) Changing the version to 3.1 in
>>> sling/launchpad/base/src/main/webapp/WEB-INF/web.xml
>>> b) Rebuilding launchpad/base
>>> c) Rebuilding launchpad/builder
>>> d) Redeploying the war file
>>>
>>> Thanks
>>> Carsten
>>>
>>> Guillaume Lucazeau wrote
>>>> Hello,
>>>>
>>>> I am trying to run Sling on JBoss. Following this article
>>>>
>> http://bobpaulin.com/home/computer_science/tutorials/setting_up_sling_jboss.html
>>>> I've just added the "sling.home" parameter and copied sling.war to
>>>> jboss/standalone.deployments, but when starting JBoss I get this error:
>>>>
>>>> 13:44:15,206 ERROR
>>>>
>> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
>>>> (FelixStartLevel) ERROR: Error starting
>>>> slinginstall:org.apache.felix.http.bridge-3.0.0.jar
>>>> (org.osgi.framework.BundleException: Unable to resolve
>>>> org.apache.felix.http.bridge [6](R 6.0): missing requirement
>>>> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
>>>>
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
>>>> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
>>>> osgi.wiring.package;
>>>>
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
>>>> org.osgi.framework.BundleException: Unable to resolve
>>>> org.apache.felix.http.bridge [6](R 6.0): missing requirement
>>>> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
>>>>
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
>>>> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
>>>> osgi.wiring.package;
>>>>
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
>>>> at
>>>> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4114)
>>>> at org.apache.felix.framework.Felix.startBundle(Felix.java:2111)
>>>> at
>> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1365)
>>>> at
>>>>
>> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
>>>>
>>>> And http://localhost:8080/sling returns a 503 error.
>>>>
>>>> If I try to follow the article and add this to sling.properties :
>>>> sling.bootdelegation.org.apache.xerces=org.apache.xerces.*
>>>>
>>>> I just get more errors.
>>>>
>>>> I'm not sure whih package is actually missing, is it javax.servlet.*?
>>>>
>>>> Any clue on how to fix this?
>>>>
>>>> Thank you,
>>>> Guillaume
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Carsten Ziegeler
>> Adobe Research Switzerland
>> cziegeler@apache.org
>>
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: Deploy Sling to JBoss EAP 6.4.0
Posted by Guillaume Lucazeau <gl...@gmail.com>.
Hello Carsten,
Did you change the file like this?
web-app version="3.1"
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_3_1.xsd">
I've changed it in "sling/launchpad/base/src/main/webapp/WEB-INF/web.xml"
but the web.xml in the war generated by Maven was still containing 3.0, and
actually none of my changes (i.e. sling.home property)
So I've just edit the war manually with the above line and redeployed it
but it seems I still have the same issue:
16:40:07,287 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
(FelixStartLevel) ERROR: Error starting
slinginstall:org.apache.felix.http.bridge-3.0.2.jar
(org.osgi.framework.BundleException: Unable to resolve
org.apache.felix.http.bridge [10](R 10.0): missing requirement
[org.apache.felix.http.bridge [10](R 10.0)] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
Unresolved requirements: [[org.apache.felix.http.bridge [10](R 10.0)]
osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
org.osgi.framework.BundleException: Unable to resolve
org.apache.felix.http.bridge [10](R 10.0): missing requirement
[org.apache.felix.http.bridge [10](R 10.0)] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
Unresolved requirements: [[org.apache.felix.http.bridge [10](R 10.0)]
osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
at
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2117)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
On Mon, Nov 23, 2015 at 3:02 PM, Carsten Ziegeler <cz...@apache.org>
wrote:
> I've just updated launchpad base to require 3.1 servlet in the web.xml
> and tested this with Tomcat. I hope/guess this should work in jboss as well
>
> Carsten
>
> Carsten Ziegeler wrote
> > Hi,
> >
> > launchpad is searching for servlet API 3.1 and I assume your webapp gets
> > started with 3.0.
> > This seems to be due to the web.xml just requiring 3.0.
> >
> > Could you please check by
> > a) Changing the version to 3.1 in
> > sling/launchpad/base/src/main/webapp/WEB-INF/web.xml
> > b) Rebuilding launchpad/base
> > c) Rebuilding launchpad/builder
> > d) Redeploying the war file
> >
> > Thanks
> > Carsten
> >
> > Guillaume Lucazeau wrote
> >> Hello,
> >>
> >> I am trying to run Sling on JBoss. Following this article
> >>
> http://bobpaulin.com/home/computer_science/tutorials/setting_up_sling_jboss.html
> >> I've just added the "sling.home" parameter and copied sling.war to
> >> jboss/standalone.deployments, but when starting JBoss I get this error:
> >>
> >> 13:44:15,206 ERROR
> >>
> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
> >> (FelixStartLevel) ERROR: Error starting
> >> slinginstall:org.apache.felix.http.bridge-3.0.0.jar
> >> (org.osgi.framework.BundleException: Unable to resolve
> >> org.apache.felix.http.bridge [6](R 6.0): missing requirement
> >> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> >> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
> >> osgi.wiring.package;
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
> >> org.osgi.framework.BundleException: Unable to resolve
> >> org.apache.felix.http.bridge [6](R 6.0): missing requirement
> >> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> >> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
> >> osgi.wiring.package;
> >>
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
> >> at
> >> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4114)
> >> at org.apache.felix.framework.Felix.startBundle(Felix.java:2111)
> >> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1365)
> >> at
> >>
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
> >> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> >>
> >> And http://localhost:8080/sling returns a 503 error.
> >>
> >> If I try to follow the article and add this to sling.properties :
> >> sling.bootdelegation.org.apache.xerces=org.apache.xerces.*
> >>
> >> I just get more errors.
> >>
> >> I'm not sure whih package is actually missing, is it javax.servlet.*?
> >>
> >> Any clue on how to fix this?
> >>
> >> Thank you,
> >> Guillaume
> >>
> >
> >
> >
> >
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>
Re: Deploy Sling to JBoss EAP 6.4.0
Posted by Carsten Ziegeler <cz...@apache.org>.
I've just updated launchpad base to require 3.1 servlet in the web.xml
and tested this with Tomcat. I hope/guess this should work in jboss as well
Carsten
Carsten Ziegeler wrote
> Hi,
>
> launchpad is searching for servlet API 3.1 and I assume your webapp gets
> started with 3.0.
> This seems to be due to the web.xml just requiring 3.0.
>
> Could you please check by
> a) Changing the version to 3.1 in
> sling/launchpad/base/src/main/webapp/WEB-INF/web.xml
> b) Rebuilding launchpad/base
> c) Rebuilding launchpad/builder
> d) Redeploying the war file
>
> Thanks
> Carsten
>
> Guillaume Lucazeau wrote
>> Hello,
>>
>> I am trying to run Sling on JBoss. Following this article
>> http://bobpaulin.com/home/computer_science/tutorials/setting_up_sling_jboss.html
>> I've just added the "sling.home" parameter and copied sling.war to
>> jboss/standalone.deployments, but when starting JBoss I get this error:
>>
>> 13:44:15,206 ERROR
>> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
>> (FelixStartLevel) ERROR: Error starting
>> slinginstall:org.apache.felix.http.bridge-3.0.0.jar
>> (org.osgi.framework.BundleException: Unable to resolve
>> org.apache.felix.http.bridge [6](R 6.0): missing requirement
>> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
>> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
>> osgi.wiring.package;
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
>> org.osgi.framework.BundleException: Unable to resolve
>> org.apache.felix.http.bridge [6](R 6.0): missing requirement
>> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
>> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
>> osgi.wiring.package;
>> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
>> at
>> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4114)
>> at org.apache.felix.framework.Felix.startBundle(Felix.java:2111)
>> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1365)
>> at
>> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
>>
>> And http://localhost:8080/sling returns a 503 error.
>>
>> If I try to follow the article and add this to sling.properties :
>> sling.bootdelegation.org.apache.xerces=org.apache.xerces.*
>>
>> I just get more errors.
>>
>> I'm not sure whih package is actually missing, is it javax.servlet.*?
>>
>> Any clue on how to fix this?
>>
>> Thank you,
>> Guillaume
>>
>
>
>
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: Deploy Sling to JBoss EAP 6.4.0
Posted by Carsten Ziegeler <cz...@apache.org>.
Hi,
launchpad is searching for servlet API 3.1 and I assume your webapp gets
started with 3.0.
This seems to be due to the web.xml just requiring 3.0.
Could you please check by
a) Changing the version to 3.1 in
sling/launchpad/base/src/main/webapp/WEB-INF/web.xml
b) Rebuilding launchpad/base
c) Rebuilding launchpad/builder
d) Redeploying the war file
Thanks
Carsten
Guillaume Lucazeau wrote
> Hello,
>
> I am trying to run Sling on JBoss. Following this article
> http://bobpaulin.com/home/computer_science/tutorials/setting_up_sling_jboss.html
> I've just added the "sling.home" parameter and copied sling.war to
> jboss/standalone.deployments, but when starting JBoss I get this error:
>
> 13:44:15,206 ERROR
> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sling]]
> (FelixStartLevel) ERROR: Error starting
> slinginstall:org.apache.felix.http.bridge-3.0.0.jar
> (org.osgi.framework.BundleException: Unable to resolve
> org.apache.felix.http.bridge [6](R 6.0): missing requirement
> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]):
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.felix.http.bridge [6](R 6.0): missing requirement
> [org.apache.felix.http.bridge [6](R 6.0)] osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))
> Unresolved requirements: [[org.apache.felix.http.bridge [6](R 6.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=javax.servlet)(version>=3.1.0)(!(version>=4.0.0)))]
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4114)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2111)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1365)
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
>
> And http://localhost:8080/sling returns a 503 error.
>
> If I try to follow the article and add this to sling.properties :
> sling.bootdelegation.org.apache.xerces=org.apache.xerces.*
>
> I just get more errors.
>
> I'm not sure whih package is actually missing, is it javax.servlet.*?
>
> Any clue on how to fix this?
>
> Thank you,
> Guillaume
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org