Re: Pax products and JPMS of Java 9

[Pavel Kastornyy]

Hi Achim

The problem is that there is no solution how to work with JPMS together
with OSGi (one module = one bundle) at the current time and there is
no information when such solution will appear. For details see
https://mail.osgi.org/pipermail/osgi-dev/2017-September/thread.html

I've read many articles in internet about possible solution and all
they say that "suggested solution is not for production".

So, I started to think that static JPMS will not allow us to use OSGi
dynamism. I very much hope that I am wrong because all our projects
are on OSGi.

Best regards, Pavel

On 09.09.2017 09:08, 'Achim Nierbeck' via OPS4J wrote:

Hi Pavel,

as all those projects are targeted to run in an  OSGi environment.
I don't see anything special to handle JPMS.
The goal is to have these bundles as OSGi bundles, so the OSGi framework
will take care of that.
JPMS does have a complete different goal (at least to my understanding)
Therefore I don't see any special handling is needed.

Besides maybe the pax-url project. It's the only one also capable of
running outside of a container.
Though as it's just another jar it should work right away on top of any
jdk.

regards, Achim

2017-09-08 19:56 GMT+02:00 Pavel :


Hello, everyone

Pax products are well known (pax-logging, pax-cdi, pax-web, pax-exam etc)
in OSGi world.
I think that pax products are among the most important products for
building infrastructure
for OSGi. Thanks to community.

Now Java 9 with its own module system (JPMS) is about to be released.
Could anyone
give any information about pax products future and possible plans for
creating products for JPMS
infrastructure.

Best regards, Pavel

--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

---
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.






--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pax-web] Osgi + Pax-web + Spring - is there any sense

[Pavel Kastornyy]

Achim, then if Spring is not good for osgi why apache
builds Spring for osgi in project servicemix? The question
is related to another my question.

On 06.06.2017 15:11, 'Achim Nierbeck' via OPS4J wrote:

Hi Pavel,

kind of. If you want to have something similar to Spring, Blueprint is to
the rescue.
The downside of it, it's purely XML, that's where Declarative Services (DS)
come in handy,
as they support annotations, also for configurations.
Downside on DS, no inner-bundle wiring, only wiring of Services.

regards, Achim



2017-06-06 13:00 GMT+02:00 Pavel :


Hi all

I had an idea to make a soltuion Osgi+Pax-web+Spring. But after reading
some information,
for example https://stackoverflow.com/a/25001220/5057736 and some work
it seems that such configuration
has no future. Am I right?

Best regards, Pavel




--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

---
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.






--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pax-web] JSP are not rendered with pax-web and Spring

[Pavel Kastornyy]

mework.util;version="3.2.
  3.RELEASE";uses:="org.apache.commons.logging",org.springframework.uti
  l.comparator;version="3.2.3.RELEASE",org.springframework.util.xml;ver
  sion="3.2.3.RELEASE";uses:="javax.xml.namespace,javax.xml.stream,java
  x.xml.stream.util,javax.xml.transform,javax.xml.transform.sax,org.apa
  che.commons.logging,org.w3c.dom,org.xml.sax,org.xml.sax.ext"
Bundle-Vendor: SpringSource
Implementation-Title: spring-core
Implementation-Version: 3.2.3.RELEASE
Bundle-Version: 3.2.3.RELEASE
Tool: Bundlor 1.0.0.RELEASE
Bundle-Name: Spring Core
Bundle-ManifestVersion: 2
Created-By: 1.7.0_11 (Oracle Corporation)
Bundle-SymbolicName: org.springframework.core
Import-Package: javax.xml.namespace;version="0";resolution:="optional"
  ,javax.xml.stream;version="0";resolution:="optional",javax.xml.stream
  .events;version="0",javax.xml.stream.util;version="0",javax.xml.trans
  form;version="0";resolution:="optional",javax.xml.transform.sax;versi
  on="0",javax.xml.transform.stax;version="0",joptsimple;version="[3.0.
  0, 4.0.0)";resolution:="optional",net.sf.cglib.beans;version="[3.0.0,
   4.0.0)";resolution:="optional",net.sf.cglib.core;version="[3.0.0, 4.
  0.0)";resolution:="optional",net.sf.cglib.proxy;version="[3.0.0, 4.0.
  0)";resolution:="optional",net.sf.cglib.reflect;version="[3.0.0, 4.0.
  0)";resolution:="optional",net.sf.cglib.transform;version="[3.0.0, 4.
  0.0)";resolution:="optional",net.sf.cglib.util;version="[3.0.0, 4.0.0
  )";resolution:="optional",org.apache.commons.logging;version="[1.1.1,
   2.0.0)",org.apache.log4j;version="[1.2.15, 2.0.0)";resolution:="opti
  onal",org.apache.log4j.xml;version="[1.2.15, 2.0.0)";resolution:="opt
  ional",org.apache.tools.ant;version="[1.7.0, 2.0.0)";resolution:="opt
  ional",org.apache.tools.ant.types;version="[1.7.0, 2.0.0)";resolution
  :="optional",org.aspectj.bridge;version="[1.7.1, 2.0.0)";resolution:=
  "optional",org.aspectj.weaver;version="[1.7.1, 2.0.0)";resolution:="o
  ptional",org.aspectj.weaver.bcel;version="[1.7.1, 2.0.0)";resolution:
  ="optional",org.aspectj.weaver.patterns;version="[1.7.1, 2.0.0)";reso
  lution:="optional",org.eclipse.core.runtime;common="split";version="0
  ";resolution:="optional",org.jboss.vfs;version="[3.0.0, 4.0.0)";resol
  ution:="optional",org.jboss.virtual;version="[2.1.0.GA, 3.0.0)";resol
  ution:="optional",org.objectweb.asm;version="[3.2.0, 4.0.0)";resoluti
  on:="optional",org.springframework.asm.tree;version="[3.2.3.RELEASE,
  3.2.3.RELEASE]";resolution:="optional",org.w3c.dom;version="0";resolu
  tion:="optional",org.xml.sax;version="0";resolution:="optional",org.x
  ml.sax.ext;version="0";resolution:="optional",org.xml.sax.helpers;ver
  sion="0";resolution:="optional"



2017-06-04 18:26 GMT+02:00 Pavel Kastornyy <pavelkastor...@gmail.com>:


Hi Achim

Thank you for your answer.

I am now trying to resolve all these dependencies and I can't
understand one thing. The half of the dependencies are not
osgi bundles. How to explain it? I mean the following are
not osgi bundles (version 3.2.3.RELEASE):

 mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.beans").versionAsInProject().start(true),
 mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.core").versionAsInProject().start(true),
 mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.context").versionAsInProjec
t().start(true),
 mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.context.support").
versionAsInProject().start(true),
 mavenBundle().groupId("org.aopalliance")
.artifactId("com.springsource.org.aopalliance").versionAsInP
roject().start(true),
 mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.aop").versionAsInProject().start(true),
 mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.expression").versionAsInPro
ject().start(true),
 mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.web").versionAsInProject().start(true),
  

Re: [pax-web] JSP are not rendered with pax-web and Spring

[Pavel Kastornyy]

Hi Achim

Thank you for your answer.

I am now trying to resolve all these dependencies and I can't
understand one thing. The half of the dependencies are not
osgi bundles. How to explain it? I mean the following are
not osgi bundles (version 3.2.3.RELEASE):

mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.beans").versionAsInProject().start(true),
mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.core").versionAsInProject().start(true),
mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.context").versionAsInProject().start(true),
mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.context.support").versionAsInProject().start(true),
mavenBundle().groupId("org.aopalliance")
.artifactId("com.springsource.org.aopalliance").versionAsInProject().start(true),
mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.aop").versionAsInProject().start(true),
mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.expression").versionAsInProject().start(true),
mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.web").versionAsInProject().start(true),
mavenBundle().groupId("org.springframework")
.artifactId("org.springframework.web.servlet").versionAsInProject().start(true),


On 04.06.2017 15:46, 'Achim Nierbeck' via OPS4J wrote:

Hi Pavel,

you'll need a setup like the one in the Karaf based Integration test.
This sample can only be run in an environment like that one [1].

So make sure you have the bundles like the following installed [2],
but keep in mind, Karaf will bring a lot Out-Of-The-Box features and
bundles which might not be listed here
but still required. So it might not be enough for your own application
solely based on Pax-Web.

regards, Achim

[1] -
https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-karaf/src/test/java/org/ops4j/pax/web/itest/karaf/SpringOsgiKarafTest.java
[2] -
https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-karaf/src/test/java/org/ops4j/pax/web/itest/karaf/SpringOsgiKarafTest.java#L58-L85

2017-06-04 14:40 GMT+02:00 Pavel :


Hi all

There is a sample https://github.com/ops4j/org.ops4j.pax.web/tree/master/
samples/war-spring for spring.
  When I run it with pax-web 6.1.0 - SNAPSHOT and jetty-9.3.11 (spring libs
are inside sample jar)
I get the following in my *browser*:

<%@ page language="java" contentType="text/html; charset=UTF-8"
pageEncoding="UTF-8"%> I've been called by the controller Controller send
me the following message: ${message}

So we see that JSP pages are not rendered as JSP, but are placed as simple
text files.
Could anyone give any suggestions? Did anyone try to make this sample work?

Best regards, Pavel

--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

---
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.






--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pax-cdi] How to inject beans from another bundle?

[Pavel Kastornyy]

I think many people had this problem and many people will have.

On 22.05.2017 18:54, Marc Schlegel wrote:

Aaaah that one: I've fallen for that one several times in JEE projects too
:-)
The file is used as a marker for CDI so it doesnt have to scan all JARs

Am Montag, 22. Mai 2017 16:28:42 UTC+2 schrieb Pavel:

It was necessary to put in bundlA META-INF folder beans.xml file.
I thought that beans.xml is required only in bundle for which container
is created. However, it turned out that this file is also required
for bundles for which container is not created but which contain
CDI beans.

On 22.05.2017 16:55, Marc Schlegel wrote:

What was the problem?

Maybe somebody else has the same issue and could learn from this thread.

Am Montag, 22. Mai 2017 13:26:34 UTC+2 schrieb Pavel:

Hi Marc

Thank you for your suggestion. I have solved that problem.

Best regards, Pavel

понедельник, 22 мая 2017 г., 13:39:24 UTC+3 пользователь Marc Schlegel
написал:

I remember that I had a example which pretty much covered your

use-case

and it was working with RC1.

Maybe you can share your two Beans as well as your manifest.

regards
Marc

Am Samstag, 20. Mai 2017 20:16:16 UTC+2 schrieb Pavel:

Hi all

I have two bundles - A and B.

In bundleA I have an cdi Bean (@Dependent) in package com.temp. For
bundleA cdi container is not created.

For bundleB cdi container is created. BundleB imports package

com.temp.

However, bundleB cdi container
doesn't find bean from bundleA.

Could anyone say if it is possible to do and if possible then how?

Best regards, Pavel





--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pax-cdi] How to inject beans from another bundle?

[Pavel Kastornyy]

It was necessary to put in bundlA META-INF folder beans.xml file.
I thought that beans.xml is required only in bundle for which container
is created. However, it turned out that this file is also required
for bundles for which container is not created but which contain
CDI beans.

On 22.05.2017 16:55, Marc Schlegel wrote:

What was the problem?

Maybe somebody else has the same issue and could learn from this thread.

Am Montag, 22. Mai 2017 13:26:34 UTC+2 schrieb Pavel:

Hi Marc

Thank you for your suggestion. I have solved that problem.

Best regards, Pavel

понедельник, 22 мая 2017 г., 13:39:24 UTC+3 пользователь Marc Schlegel
написал:

I remember that I had a example which pretty much covered your use-case
and it was working with RC1.

Maybe you can share your two Beans as well as your manifest.

regards
Marc

Am Samstag, 20. Mai 2017 20:16:16 UTC+2 schrieb Pavel:

Hi all

I have two bundles - A and B.

In bundleA I have an cdi Bean (@Dependent) in package com.temp. For
bundleA cdi container is not created.

For bundleB cdi container is created. BundleB imports package com.temp.
However, bundleB cdi container
doesn't find bean from bundleA.

Could anyone say if it is possible to do and if possible then how?

Best regards, Pavel



--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
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 ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PAX:WEB How many war bundles do pax-web support?

[Pavel Kastornyy]

Ok, Achim. Thank you for detailed answers.

I currently need and use only the following subprojects:

pax-web-api-6.0.0-SNAPSHOT.jar
pax-web-deployer-6.0.0-SNAPSHOT.jar
pax-web-descriptor-6.0.0-SNAPSHOT.jar
pax-web-extender-war-6.0.0-SNAPSHOT.jar
pax-web-extender-whiteboard-6.0.0-SNAPSHOT.jar
pax-web-jetty-6.0.0-SNAPSHOT.jar
pax-web-jsp-6.0.0-SNAPSHOT.jar
pax-web-runtime-6.0.0-SNAPSHOT.jar
pax-web-spi-6.0.0-SNAPSHOT.jar

Firstly I will take some time to study them. If after analysis I can 
find and suggest some

solution which will require not so much time I will discuss it with you.

But I say in advance that if I will do something, it will be linked only 
with subprojects

I need and use. I think the reason can be easily understood.

Best regards,

On 02.10.2016 19:35, 'Achim Nierbeck' via OPS4J wrote:

About a person year, with the prerequisite that the current implementation
is well known.

1) Not really, certain people working on the code are paid to do so.
2) Nope, it's an open source project most people working on this do this in
their private time.
 Sometimes those people (like me) don't even work on any related stuf
anymore.
3) Hard to tell ... as we have people which get engaged for certain topics
which move off after a certain amount of time
 Here's a complete list of recent developers [1]


regards, Achim

[1] - https://github.com/ops4j/org.ops4j.pax.web/graphs/contributors

2016-10-02 18:20 GMT+02:00 Pavel Kastornyy <pavelkastor...@gmail.com>:


Achim, thank you for the information. So about one person year
if I understand you right.

Could you also shortly answer the following questions:

1) is there any financial help from any companies?
2) has the community tried to draw investments into the product?
3) how many active developers are there at this time?

Best regards,



On 02.10.2016 18:47, 'Achim Nierbeck' via OPS4J wrote:


wow, that's a tough one ... :D

if you take a look at Openhub [1] ... it'll tell you it took about 57
years
[2], or at least it's the amount of work worth it ;)

Anyway it's hard to estimate as I've spent the last 6 years improving on
it. Never the less if I would work on it full time 8h day
with the knowledge I have right now. One person could redo it within maybe
a year. But it's a wild guess ... might be faster, might take longer ...
Of course I would expect it to have the same features and possibilities it
has which makes it different to other implementations of the HttpService
etc. Right now we have about 500 unit and integration tests running with
every build [3].
That functionality I would expect to be available after the re-write ;)

BUT, the nice thing is. We can always start with a new branch and work on
that in parallel.
If there are enough people to work on it it should work.

[1] - https://www.openhub.net/p/pax-web
[2] - https://www.openhub.net/p/pax-web/estimated_cost
[3] - http://ci.ops4j.org/jenkins/job/org.ops4j.pax.web/1028/testReport/




2016-10-02 15:39 GMT+02:00 iJava <pavelkastor...@gmail.com>:

Hi Achim

Could you say (from the top of your head) approximatively how many hours
may these changes need - 100/1000/5000/1?

Best regards,

воскресенье, 2 октября 2016 г., 15:40:23 UTC+3 пользователь Achim
Nierbeck
написал:


Sounds like a good and interesting idea ...
Right now only from the top of my head:
The Pax-Web Runtime and therefore the different Implementations aren't
made for this right now. So this would need a complete rewrite of how
we're
handling it. Another point would be how would web and white-board
extender
work with it. We could think about wiring those two closer to the core.
Never the less an application deploying servlets will always need to add
the virtual host environment, working with defaults could take care of
that.

We could consider to start this with a complete rewrite of Pax-Web and
therefore aim for a 7.0.

BUT ... I fear I won't have enough time to takle this. Considering the
amount of time I spent in the past and about what it would take to have
all
the functionalities of Pax-Web re-written, and especially with my
$dayJob +
Family.

regards, Achim



2016-10-02 5:35 GMT+02:00 Niclas Hedhman <nic...@hedhman.org>:

Honestly, if this is to be fixed, I think Pax Web should support Managed

Service Factory, and instantiate separate virtual host services
according
to a provided configuration. That configuration should contain which
WAB(s)
goes into that virtual host, together with any other virtual host
configuration.

To me, that seems to be the right solution forward, maintains OSGi
compatibility, doesn't introduce new config args on WABs and doesn't
treat
"one domain" different than another.

I think the tricky bit is to make the default case and the MSF
instantiations play nicely with each other, but that is an design
implementation detail at this stage.

Cheers
Niclas

On Sat, Oct 1, 2016 at 4:49 PM, iJava <pavelka...@gmail.com> wrote:

I analyzed situation again and I

Re: PAX:WEB How many war bundles do pax-web support?

[Pavel Kastornyy]

benefits of those underlying servers in the
same way. If you're not satisfied because you expect something
different. I'm sorry to hear
but nothing we can do about.

regards, Achim


2016-09-30 17:04 GMT+02:00 Achim Nierbeck <bcan...@googlemail.com>:


Well, in that case try to use GlassFish again.
GlassFish uses a complete different strategy.

Regards, Achim


2016-09-30 17:02 GMT+02:00 iJava <pavelka...@gmail.com>:


Something is wrong here. I worked with glassfish. Everything starts
with glassfish domain.
In one domain you usually have one http connector and one https
connector. After that in
one domain you can have multiple virtual hosts. When you deploy
osgi bundle you
in manifest have Web-ContextPath and VirtualServers. So you can
have N sites
(example.com, boo.org, blablabla.net) with WebContextPath / and it
is not necessary
  to create new connectors for new ports.

I know it well, because I remember it took me some time to make it
work.
And I was very glad because it is easy to work with one port then
with N.

Now you suggest me to go back and again work with N ports. I am
shocked and killed.


пятница, 30 сентября 2016 г., 17:49:30 UTC+3 пользователь Achim
Nierbeck написал:

Hi,

yes, you can only have one Web-ContextPath per WAB. "/" is
especially tricky since you can also have HttpService servlets listening on
that one.

regards, Achim


2016-09-30 16:46 GMT+02:00 iJava <pavelka...@gmail.com>:


Hi Achim

Thank you for the links, I wil study them now. So, do I
understand it right -
accroding to specs I can have only one bundle with
web-contextpath / for one port ?

Best regards,


пятница, 30 сентября 2016 г., 17:37:55 UTC+3 пользователь Achim
Nierbeck написал:

It's in the spec ...


Now, if you want to run virtual hosts, take a look at the links
below.

regards, Achim

[1] - https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax
-web-itest/pax-web-itest-container/pax-web-itest-container-
jetty/src/test/java/org/ops4j/pax/web/itest/jetty/JettyConfi
gurationExtendedIntegrationTest.java
[2] - https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax
-web-itest/pax-web-itest-container/pax-web-itest-container-
jetty/src/test/java/org/ops4j/pax/web/itest/jetty/JettyConfi
gurationExtendedTwoIntegrationTest.java
[3] - http://notizblog.nierbeck.de/2013/01/bind-certain-web-appl
ications-to-specific-httpconnectors/


2016-09-30 16:23 GMT+02:00 Pavel Kastornyy <pavelka...@gmail.com

:
Achim, I understand you, but why? If the domains are different
why must I change web-contextpath? For example, lets suppose
I have five different sites on one osgi and for every site I
have
separate wab (which is logical) and every wab has only one
context
- /. It is normal situation - take a look at any web server.

Best regards,



On 30.09.2016 17:19, 'Achim Nierbeck' via OPS4J wrote:


The Manifest entry Web-ContextPath is the one in charge of
where the
application resides in.
So in that case you need to make sure of different
Web-ContextPaths.

regards, Achim


2016-09-30 16:09 GMT+02:00 iJava <pavelka...@gmail.com>:

Hi Achim,

Yes, you are right. The same web-contextpath in both bundles:
/

But it seems to be a bug because in bundle A I have
jetty-web.xml


  
  
example.com
www.example.com
  
  


and in bundle B I have jetty-web.xml


  
  
foo.example.com
www.foo.example.com
  
  






пятница, 30 сентября 2016 г., 16:54:24 UTC+3 пользователь
Achim Nierbeck
написал:


Hi,

this seems to be a rather strange bug. Do both of the war
maybe have the
same web-contextpath?

regards, Achim


2016-09-30 14:09 GMT+02:00 iJava <pavelka...@gmail.com>:

Hi all

It may seem to be funny question but I have the following
situation. I
have two war bundles A and B.
When I start and install only bundle A - it works ok. When
I start and
install only bundle B it works ok.

When I try to install both of them always only the first
works. The
servlet in the second bundle is not
instantiated. I tried to add 0
to
servlet config
in web.xml but it didn't help.

Any ideas? Does anyone try to deploy more then one war
bundle on the same
osgi framework with pax-web 6.0?

Best regards,


--
--
--
OPS4J - http://www.ops4j.org - op...@googlegroups.com

---
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 ops4j+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

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

--


--
-

Re: Pax-web says it is available but it not available.

[Pavel Kastornyy]

Thank you. I solved the problem. Could you give a hint to another my 
thread - why jasper compiles jsp again and again?


On 09.08.2016 17:55, 'Achim Nierbeck' via OPS4J wrote:

Hi,

As I'm still on vacation only a quick hint.
Take a look at the PAX Web integration tests. They do use all of the
samples and show which bundles to use.

Regards, Achim

sent from mobile device

Am 09.08.2016 10:05 vorm. schrieb "iJava" :


Ok. I finally made it working: I added two bundles:
pax-web-extender-war-4.2.7.jar
pax-web-extender-whiteboard-4.2.7.jar

And the server started listen port. However, when I do
http://127.0.0.1:8080/wab-jetty-web/
I get
HTTP ERROR 403  Problem accessing /wab-jetty-web/. Reason:  Forbidden

Could anyone help me solve it? I doubt that I can solve this problem
without help.

My full log is:

org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling SLF4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Jakarta Commons Logging API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Log4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Avalon Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling JULI Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Log4J v2 API support. Ignored FQCN: org.apache.logging.log4j.spi.
AbstractLogger
[main] INFO org.ops4j.pax.web.service.internal.Activator - EventAdmin
support enabled, servlet events will be postet to topics.
[main] INFO org.ops4j.pax.web.service.internal.Activator - LogService
support enabled, log events will be created.
[main] INFO org.ops4j.pax.web.service.internal.Activator - Pax Web started
2016-08-09 10:58:10.915:INFO::pool-28-thread-1: Logging initialized
@1184ms
[pool-28-thread-1] INFO 
org.ops4j.pax.web.service.jetty.internal.JettyFactoryImpl
- SPDY not available, creating standard ServerConnector for Http
[pool-28-thread-1] INFO org.ops4j.pax.web.service.jetty.internal.JettyServerImpl
- Pax Web available at [0.0.0.0]:[8080]
[pool-28-thread-1] INFO 
org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl
- Binding bundle: [org.ops4j.pax.web.samples.wab-jetty-web [41]] to http
service
[pool-28-thread-1] INFO 
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper
- will add org.apache.jasper.servlet.JasperInitializer to
ServletContainerInitializers
[pool-28-thread-1] INFO 
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper
- Skipt org.apache.jasper.servlet.JasperInitializer, because specialized
handler will be present
[pool-28-thread-1] INFO 
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext
- registering context WebAppHttpContext{org.ops4j.pax.web.samples.wab-jetty-web
- 41}, with context-name: wab-jetty-web
[pool-28-thread-1] INFO 
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext
- registering JasperInitializer
org.ops4j.pax.web.pax-web-jsp[org.apache.tomcat.util.digester.Digester] :
addRuleSet() with no namespace URI
org.ops4j.pax.web.pax-web-jsp[org.apache.tomcat.util.digester.Digester] :
addRuleSet() with no namespace URI
2016-08-09 10:58:11.372:WARN:oejs.ServletContextHandler:pool-28-thread-1:
ServletContextHandler.setHandler should not be called directly. Use
insertHandler or setSessionHandler etc.
[pool-28-thread-1] ERROR org.ops4j.pax.web.jsp.JspServletWrapper -
Ignored exception
java.lang.NullPointerException
 at org.ops4j.pax.web.jsp.JspServletWrapper$1.call(
JspServletWrapper.java:101)
 at org.ops4j.pax.web.jsp.JspServletWrapper$1.call(
JspServletWrapper.java:97)
 at org.ops4j.pax.swissbox.core.ContextClassLoaderUtils.
doWithClassLoader(ContextClassLoaderUtils.java:60)
 at org.ops4j.pax.web.jsp.JspServletWrapper.init(
JspServletWrapper.java:96)
 at org.eclipse.jetty.servlet.ServletHolder.initServlet(
ServletHolder.java:640)
 at org.eclipse.jetty.servlet.ServletHolder.initialize(
ServletHolder.java:419)
 at org.eclipse.jetty.servlet.ServletHandler.initialize(
ServletHandler.java:875)
 at org.eclipse.jetty.servlet.ServletContextHandler.startContext(
ServletContextHandler.java:349)
 at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.
startContext(HttpServiceContext.java:590)
 at org.eclipse.jetty.server.handler.ContextHandler.
doStart(ContextHandler.java:772)
 at org.eclipse.jetty.servlet.ServletContextHandler.doStart(
ServletContextHandler.java:262)
 at org.ops4j.pax.web.service.jetty.internal.
HttpServiceContext.doStart(HttpServiceContext.java:249)
 at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
 at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(
JettyServerImpl.java:273)
 at org.ops4j.pax.web.service.internal.HttpServiceStarted.