Achim,

I mistook "the extra module" you were referring to as the pax-http-undertow
one.  My bad.  I think the amount of jetty libraries that pax-jsf-support
ends up installing making me think it's necessary for Jetty.  I'll give a
try deploying a JSF application without that pax-jsf-support.

Thanks!
Ryan

On Mon, Feb 26, 2018 at 1:11 PM Achim Nierbeck <[email protected]>
wrote:

> As I already tried to tell you, with Jetty you don't need to install the
> pax-jsf-support feature, as it is for undertow only.
>
> regards, Achim
>
> 2018-02-26 17:43 GMT+01:00 Ryan Moquin <[email protected]>:
>
>> I don't want to use undertow, if I try to install the pax-jsf-support
>> feature, it says pax-http-undertow is required.  I don't know if maybe it's
>> an error that it requires undertow since when you install the jsf support
>> feature, a lot of Jetty bundles get installed.....  I personally am fine
>> with only jetty, if I can install the jsf support without undertow :)
>>
>> Also, to JB's suggestion.  I was running with a clean karaf and when I
>> install the features, I end up with the problem above.  I am wondering if
>> this whole problem is because I keep getting an error that undertow is a
>> requirement for the pax-jsf-support feature (I think if I look at the
>> feature info, it is listed as a requirement, which would make sense based
>> on the error.)
>>
>> I'll see if maybe an older pax version is getting referenced somehow?
>>
>> Ryan
>>
>>
>> On Mon, Feb 26, 2018, 10:36 AM Achim Nierbeck <[email protected]>
>> wrote:
>>
>>> Hi,
>>>
>>> you need to differentiate, if you want to do JSF with jetty there is no
>>> extra module needed, if you want to use undertow instead of Jetty, you'll
>>> need that extra module.
>>>
>>> regards, Achim
>>>
>>> 2018-02-26 16:08 GMT+01:00 Jean-Baptiste Onofré <[email protected]>:
>>>
>>>> We did a lot of improvements for 4.2.x around that and in new Pax
>>>> CDI/Pax Web
>>>> releases (just out couple of days ago).
>>>>
>>>> Anyway, it seems there's a mix between undertow and jetty. It should be
>>>> one or
>>>> the other (changing the HTTP provider).
>>>>
>>>> Can you please try from a cleanup instance ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 02/26/2018 03:30 PM, Ryan Moquin wrote:
>>>> > I wanted to try out JSF support in Karaf, but seem to get a lot of
>>>> problems
>>>> > originating between undertow and jetty.  When I try to install
>>>> pax-jsf-support,
>>>> > it says I need pax-http-undertow.  I can install pax-http-undertow
>>>> fine.  When I
>>>> > install pax-jsf-support, it installs jetty (which seems odd if it
>>>> depends on the
>>>> > feature for a different servlet container)and then I see the
>>>> following error (if
>>>> > I install pax-war, then pax-http-undertow, jetty and undertow seem to
>>>> install
>>>> > without any problems, but if I then add pax-jsf-support, I also get
>>>> the
>>>> > following error as well as a bunch related to CDI after it):
>>>> >
>>>> > 2018-02-26 09:03:10,917 | WARN  | onfig-1-thread-1 | JettyServerImpl
>>>>
>>>> >       | 154 - org.ops4j.pax.web.pax-web-jetty - 6.0.9 | No
>>>> configuration file
>>>> > found with name jetty.xml. Filename given: undertow.properties, will
>>>> read this
>>>> > one instead.
>>>> > 2018-02-26 09:03:10,954 | INFO  | tures-1-thread-1 |
>>>> FeaturesServiceImpl
>>>> >       | 8 - org.apache.karaf.features.core - 4.1.5 |
>>>> >  org.apache.xbean.asm5-shaded/4.4.0
>>>> > 2018-02-26 09:03:10,957 | INFO  | tures-1-thread-1 |
>>>> FeaturesServiceImpl
>>>> >       | 8 - org.apache.karaf.features.core - 4.1.5 |
>>>>  openwebbeans-impl/1.6.3
>>>> > 2018-02-26 09:03:10,962 | INFO  | tures-1-thread-1 |
>>>> FeaturesServiceImpl
>>>> >       | 8 - org.apache.karaf.features.core - 4.1.5 |
>>>> >  org.ops4j.pax.cdi.extension/1.0.0
>>>> > 2018-02-26 09:03:10,968 | WARN  | onfig-1-thread-1 | XmlParser
>>>>
>>>> >       | 117 - org.eclipse.jetty.util - 9.3.21.v20170918 |
>>>> > FATAL@file:/C:/dev/karaf/etc/undertow.properties line:1 col:1 :
>>>> > org.xml.sax.SAXParseException; systemId:
>>>> > file:/C:/dev/karaf/etc/undertow.properties; lineNumber: 1;
>>>> columnNumber: 1;
>>>> > Content is not allowed in prolog.
>>>> > 2018-02-26 09:03:10,969 | ERROR | onfig-1-thread-1 | JettyServerImpl
>>>>
>>>> >       | 154 - org.ops4j.pax.web.pax-web-jetty - 6.0.9 | Exception
>>>> while starting
>>>> > Jetty
>>>> > org.xml.sax.SAXParseException: Content is not allowed in prolog.
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:994)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327)
>>>> > ~[?:?]
>>>> >         at org.eclipse.jetty.xml.XmlParser.parse(XmlParser.java:201)
>>>> ~[?:?]
>>>> >         at org.eclipse.jetty.xml.XmlParser.parse(XmlParser.java:221)
>>>> ~[?:?]
>>>> >         at
>>>> >
>>>> org.eclipse.jetty.xml.XmlConfiguration.<init>(XmlConfiguration.java:137)
>>>> ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.start(JettyServerImpl.java:151)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:478)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:81)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerFactoryImpl$1.start(ServerControllerFactoryImpl.java:164)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:787)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:97)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:347)
>>>> ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.internal.Activator.lambda$scheduleUpdateFactory$2(Activator.java:291)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>>> [?:?]
>>>> >         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>> [?:?]
>>>> >         at
>>>> >
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>> > [?:?]
>>>> >         at
>>>> >
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>> > [?:?]
>>>> >         at java.lang.Thread.run(Thread.java:748) [?:?]
>>>> > 2018-02-26 09:03:10,980 | ERROR | onfig-1-thread-1 | Activator
>>>>
>>>> >       | 75 - org.ops4j.pax.web.pax-web-runtime - 6.0.9 | Unable to
>>>> start pax web
>>>> > server: Exception while starting Jetty
>>>> > java.lang.RuntimeException: Exception while starting Jetty
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.start(JettyServerImpl.java:197)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:478)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:81)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerFactoryImpl$1.start(ServerControllerFactoryImpl.java:164)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:787)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:97)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:347)
>>>> ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.internal.Activator.lambda$scheduleUpdateFactory$2(Activator.java:291)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>>> [?:?]
>>>> >         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>> [?:?]
>>>> >         at
>>>> >
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>> > [?:?]
>>>> >         at
>>>> >
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>> > [?:?]
>>>> >         at java.lang.Thread.run(Thread.java:748) [?:?]
>>>> > Caused by: org.xml.sax.SAXParseException: Content is not allowed in
>>>> prolog.
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:994)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
>>>> > ~[?:?]
>>>> >         at
>>>> >
>>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327)
>>>> > ~[?:?]
>>>> >         at org.eclipse.jetty.xml.XmlParser.parse(XmlParser.java:201)
>>>> ~[?:?]
>>>> >         at org.eclipse.jetty.xml.XmlParser.parse(XmlParser.java:221)
>>>> ~[?:?]
>>>> >         at
>>>> >
>>>> org.eclipse.jetty.xml.XmlConfiguration.<init>(XmlConfiguration.java:137)
>>>> ~[?:?]
>>>> >         at
>>>> >
>>>> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.start(JettyServerImpl.java:151)
>>>> > ~[?:?]
>>>> >         ... 12 more
>>>> >
>>>> > Is there a particular way to be able to get jsf running successfully
>>>> in Karaf?
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> [email protected]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Apache Member
>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>>> & Project Lead
>>> blog <http://notizblog.nierbeck.de/>
>>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>>>
>>> Software Architect / Project Manager / Scrum Master
>>>
>>>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
>

Reply via email to