Hello

I'm concerned about several things:

1. 18|Active     |    4|Apache Felix Framework (5.6.10)

do you really need another OSGi system bundle? Felix Framework is simply
another alternative to Equinox - you don't need it.

2. 12|Active     |    4|OPS4J Pax Web - Jetty Bundle (7.2.3)

This bundle was created to make it easy to deploy/run jetty w/ pax-web. You
should not need separate Jetty bundles.

I can recommend one thing - run clean instance of Karaf, check the bundles
(`la -l`) then install pax-web jetty (`feature:install pax-web-jetty`)
feature and check bundles again - the difference should be the list of
bundles you need to run Jetty with pax-web.

best regards
Grzegorz Grzybek

śr., 31 paź 2018 o 01:27 Jared Stofflett <[email protected]>
napisał(a):

> Apparently Eclipse was behaving badly, I restarted it and can now access
> the server. When I try to access a jsp I get 500 server JSP support not
> configured. Below is my OSGI console output, note I'm not currently getting
> any logs. I would expect to see errors in the console since my launch
> configuration runs with the "-consoleLog -console" program argument.
>
> log4j:WARN No appenders could be found for logger
> (org.eclipse.jetty.util.log).
> log4j:WARN Please initialize the log4j system properly.
> osgi> felix:lb
> START LEVEL 6
>    ID|State      |Level|Name
>     0|Active     |    0|OSGi System Bundle (3.12.100.v20180210-1608)
>     1|Active     |    4|SLF4J API (1.7.2.v20121108-1250)
>     2|Active     |    4|JAXP XML (1.3.4.v201005080400)
>     3|Active     |    4|OSGi Release 4.2.0 Utility Classes
> (3.4.0.v20170111-1608)
>     4|Active     |    4|OSGi Release 4.2.0 Services (3.6.0.v20170228-1906)
>     6|Active     |    4|OPS4J Pax Web - API (7.2.3)
>     7|Active     |    4|javax.annotation API (1.2.0)
>     8|Active     |    4|OPS4J Pax Web - Jsp Support (7.2.3)
>     9|Active     |    4|org.apache.tomcat.embed.tomcat-embed-logging-juli
> (8.0.52)
>    10|Active     |    4|Apache XBean OSGI Bundle Utilities (4.6.0)
>    11|Active     |    4|Java Servlet API (3.1.0)
>    12|Active     |    4|OPS4J Pax Web - Jetty Bundle (7.2.3)
>    13|Active     |    4|org.objectweb.asm.commons (6.2.0)
>    14|Active     |    4|org.objectweb.asm (6.2.0)
>    15|Active     |    4|OPS4J Pax Web - Service SPI (7.2.3)
>    16|Active     |    4|Apache Jakarta log4j Plug-in (1.2.15.v201012070815)
>    17|Active     |    4|SampleWeb (19.3.1.qualifier)
>    18|Active     |    4|Apache Felix Framework (5.6.10)
>    19|Active     |    4|org.objectweb.asm.tree (6.2.0)
>    20|Resolved   |    4|SLF4J LOG4J-12 Binding (1.7.2.v20131105-2200)
>    21|Active     |    4|OPS4J Pax Swissbox :: Optional JCL (1.8.2)
>    22|Active     |    4|Expression Language 3.0 API (3.0.0)
>    23|Active     |    4|Apache Felix Gogo Runtime (0.10.0.v201209301036)
>    24|Active     |    4|Apache XBean :: Classpath Resource Finder (4.6.0)
>    25|Active     |    4|Apache Felix Gogo Command (0.10.0.v201209301215)
>    28|Active     |    4|Jetty :: JAAS (9.4.11.v20180605)
>    29|Active     |    4|Jetty Http Service (3.4.0.v20170503-2025)
>    30|Active     |    4|Jetty :: Utilities :: Ajax(JSON) (9.4.11.v20180605)
>    31|Active     |    4|Jetty :: Server Core (9.4.11.v20180605)
>    32|Active     |    4|Jetty :: JASPI Security (9.4.11.v20180605)
>    33|Active     |    4|Jetty :: Asynchronous HTTP Client
> (9.4.11.v20180605)
>    34|Active     |    4|geronimo-jta_1.1_spec (1.1.1)
>    35|Active     |    4|Jetty :: Http Utility (9.4.11.v20180605)
>    36|Active     |    4|Jetty :: XML utilities (9.4.11.v20180605)
>    37|Active     |    4|Jetty :: JNDI Naming (9.4.11.v20180605)
>    38|Active     |    4|Jetty :: Rewrite Handler (9.4.11.v20180605)
>    39|Active     |    4|Jetty :: Security (9.4.11.v20180605)
>    40|Active     |    4|Jetty :: Utilities (9.4.11.v20180605)
>    41|Active     |    4|Jetty :: Plus (9.4.11.v20180605)
>    42|Active     |    4|Jetty :: Servlet Handling (9.4.11.v20180605)
>    43|Active     |    4|Http Services Servlet (1.4.0.v20170524-1452)
>    44|Active     |    4|Jetty :: Utility Servlets and Filters
> (9.4.11.v20180605)
>    45|Active     |    4|Jetty :: IO Utility (9.4.11.v20180605)
>    46|Active     |    4|Jetty :: Webapp Application Support
> (9.4.11.v20180605)
>    47|Active     |    4|Apache Commons IO (2.2.0.v201405211200)
>    48|Active     |    4|Apache Commons FileUpload (1.3.2.v20170320-2229)
>    49|Active     |    4|Jetty :: JMX Management (9.4.11.v20180605)
>    50|Active     |    4|Java Authentication SPI for Containers (1.1.0)
>    51|Active     |    4|Jetty :: Continuation (9.4.11.v20180605)
>    52|Active     |    4|Jetty :: Deployers (9.4.11.v20180605)
>   129|Active     |    4|Apache Felix Gogo Shell (0.10.0.v201212101605)
>   130|Active     |    4|Console plug-in (1.1.300.v20170512-2111)
>   131|Active     |    4|Jetty :: OSGi :: Boot (9.4.11.v20180605)
>
>
> On Tuesday, October 30, 2018 at 2:21:18 PM UTC-4, Grzegorz Grzybek wrote:
>>
>> Hello
>>
>> There's no ops4j p2 update site - pax-web (and other pax-* projects)
>> provide only Karaf-style feature XML files.
>>
>> I can however try helping with your actual problem - not started jetty.
>> Can you show me list of bundles / logs?
>>
>> regards
>> Grzegorz Grzybek
>>
>> wt., 30 paź 2018 o 17:47 Jared Stofflett <[email protected]>
>> napisał(a):
>>
>>> The application I'm working on uses Equinox as the OSGI container and
>>> Tycho as the build and packaging tool. I'm hoping to replace an embedded
>>> Jetty server running in a plain Equinox framework with Pax Web to allow for
>>> easier maintenance and updates in the future. Does Pax Web offer a P2
>>> update site so Tycho could pull in all the required dependencies? I've
>>> attempted to grab dependencies listed in the Pax Web feature.xml for the
>>> following features and create my own update site.
>>>
>>> pax-jetty
>>>
>>> pax-http-jetty
>>>
>>> pax-war
>>>
>>> Although I get my bundles to resolve in an eclipse run configuration
>>> when I run my OSGI container nothing happens.
>>>
>>> felix:lb
>>>
>>> shows all the bundles have started, but I am unable to access the jetty
>>> server.
>>>
>>>
>>>
>>> --
>>> --
>>> ------------------
>>> OPS4J - http://www.ops4j.org - [email protected]
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OPS4J" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> ------------------
> OPS4J - http://www.ops4j.org - [email protected]
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to