;>> A side topic we already discussed a bit with Greg is about the effort to
>>> have more "isolated" bundles for jetty, tomcat and undertow. Today, we are
>>> suffering a lot to maintain at same level the Pax Web API with the three
>>> containers. Clearly
w. Today, we are
>> suffering a lot to maintain at same level the Pax Web API with the three
>> containers. Clearly some methods of the API are mostly Jetty related and
>> not easy to implement with other containers.
>> So, I wonder at some point if we should not have pure
> regards
> Grzegorz Grzybek
>
> wt., 23 cze 2020 o 15:46 Jean-Baptiste Onofré > napisał(a):
>
>> Hi,
>>
>> It sounds good. Tomcat 8.x should be easy, Tomcat 9 probably needs API
>> updates.
>>
>> Regards
>> JB
>>
>>
>>
Hi,
It has been quite a while since the Tomcat version was updated in Pax-Web.
The 7.2.x branch references Tomcat 8.5.32 and the 3.x and master branches
references Tomcat 9.0.16.
These versions are from June 2018 and February 2019, so I think we should
update to more recent versions 8.5.56 and
him
>
>
> Am Di., 2. Juli 2019 um 14:49 Uhr schrieb Jean-Baptiste Onofré <
> jeanbapti...@gmail.com >:
>
>> +1 to create a Jira related to undertow.
>>
>> Regards
>> JB
>> On 02/07/2019 13:51, Stephan Siano wrote:
>>
>> Hi,
>>
&g
st regards
Stephan
Am Montag, 1. Juli 2019 20:33:58 UTC+2 schrieb Jean-Baptiste Onofré:
>
> Thanks Stephan
>
> I will take a look.
>
> Regards
> JB
>
> Le mer. 26 juin 2019 à 14:32, Stephan Siano > a écrit :
>
>> OK, I created a first pull request that only co
happy to work with you on this one ;)
>>
>> Regards
>> JB
>> On 26/06/2019 11:33, Stephan Siano wrote:
>>
>> Hi,
>>
>> I did some further work on the topic. Here are my results:
>>
>> 1. I have some changes that are required to get the tests
twoch, 26. Juni 2019 13:25:01 UTC+2 schrieb Jean-Baptiste Onofré:
>
> +1 to reuse PAXWEB-1027, and happy to work with you on this one ;)
>
> Regards
> JB
> On 26/06/2019 11:33, Stephan Siano wrote:
>
> Hi,
>
> I did some further work on the topic. Here are my results:
rds, Achim
>
>
> Am Di., 25. Juni 2019 um 16:49 Uhr schrieb Jean-Baptiste Onofré <
> jeanbapti...@gmail.com >:
>
>> I mean that it's a similar pattern we use for other "connector".
>>
>> By the way, did you take a look on the websocket example in
ean-Baptiste Onofré wrote:
>
> Hi,
>
> AFAIR, it's not yet fully supported.
>
> But easy to add/fix, I will tackle that.
>
> Regards
> JB
> On 25/06/2019 15:25, Stephan Siano wrote:
>
> Hi,
>
> I have a question concerning web sockets in Pax-Web:
>
Hi,
I have a question concerning web sockets in Pax-Web:
A colleague of mine is trying to deploy a war on a Pax-Web container that
contains some annotated websocket server endpoints. This works with other
web containers but not on Pax web (he is getting a 404 response when he is
trying to upgr
Hi,
Is it possible that the ops4j jenkins ci.ops4j.org is down? I get a
connection timeout if I try to access it.
Best regards
Stephan
--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
---
You received this message because you are subscribed to the Google Groups
aware of events inside a subsystem at all? is it correct
> semantic for information to leak out of the region?
>
> On Thu 24 May, 2018, 12:02 PM Stephan Siano, > wrote:
>
>> Hi,
>>
>> I had a look into the OSGi enterprise spec (134.9). It says that the
>> bun
bundle's
bundleContext if bundle 0 is unreachable.
Best regards
Stephan
Am Mittwoch, 23. Mai 2018 15:20:59 UTC+2 schrieb Stephan Siano:
>
> Hi,
>
> One problem with the bundleContext.getBundle(0) call is that it will
> return null if pax web is not running in the root subsystem,
Hi,
Since the change for PAXWEB-1161 was merged into the master branch 13
integration tests for the undertow container (all related to
authentication) fail.
As I am not exactly an expert for the undertow container and don't know how
keycloak works (I only know that it has something to do with
Hi,
One problem with the bundleContext.getBundle(0) call is that it will return
null if pax web is not running in the root subsystem, in that case the
region context would be required instead.
Concerning the composite subsystems:
What happens if the composite subsystem exports servlets and filt
Hi,
just one question: Is it possible to set up a build job for the new
pax-web-7.0.x branch?
Best regards
Stephan
Am Montag, 5. Februar 2018 08:38:49 UTC+1 schrieb Achim Nierbeck:
>
> Fine with me.
>
> regards, Achim
>
> 2018-02-05 7:58 GMT+01:00 Jean-Baptiste Onofré >:
>
>> Hi guys,
>>
>>
Hi,
sorry for the late reply, just one word of waning. If you are still on
pax-web 4.x you will probably better stay with the jetty web container.
Undertow is only available with pax-web 6.0 and later. The tomcat support
is rather incomplete in pax-web 4.x (marked as experimental). The tomcat
Hi,
>>>
>>> afaik we're all set to have a 6.1 release.
>>> @Grzegorz, I'd say release now with the current set and with 6.1.1 we
>>> can ship a complete setup :)
>>>
>>> we also are set on the Tomcat front as far as I can
Hi,
currently the jenkins build for the pax-web-6.1.x branch is hanging.
Is someone able to stop that job?
The issue can be reproduced quite easily. The pax-exam conatiner is not
coming up with error messages like this:
12:46:44.137 ERROR {FelixDispatchQueue}
[org.ops4j.pax.logging.log4j2.int
>
>
> Maven stopped taking into account for tomcat, jetty and
> undertow profiles.
>
> The change[1] was related to my general build fixes.
>
> regards
> Grzegorz Grzybek
> ===
> [1]:
> https://github.com/ops4j/org.ops4j.pax.web/commit/247a1f6b90e4a9d4c2e914
Hi,
I have a few (not really related) questions concerning pax-web:
1. There are separate profiles for building tomcat, jetty, and undertow
support. At least when I do the builds locally none of these profiles is
activated by default. The workaround for my local build is to use the
-Prelease p
>>> ready - I started it again from current pax-web-6.0.x, so your Tomcat
>>> changes are already there.
>>>
>>> regards
>>> Grzegorz Grzybek
>>>
>>> 2017-09-12 13:11 GMT+02:00 Grzegorz Grzybek >> >:
>>>
>>>>
Hi,
I fixed this as part of the PAXWEB-1079 fix.
Best regards
Stephan
Am Mittwoch, 13. September 2017 20:26:37 UTC+2 schrieb Achim Nierbeck:
>
> hi Jens,
>
> would you mind documenting your findings on that corresponding Issue?
> As Stephano does a great work on the tomcat front, it would be r
AXWEB-1075 and PAXWEB-1129.
>
> best regards
> Grzegorz Grzybek
>
>
> 2017-09-12 7:36 GMT+02:00 Stephan Siano >:
>
>> Hi,
>>
>> I also think it is a good idea to have a pax-web 6.1.x release with some
>> updated references. I would also like to have the upda
Hi,
I also think it is a good idea to have a pax-web 6.1.x release with some
updated references. I would also like to have the update to Tomcat 8.5.20
in that branch (PAXWEB-1129) and I would also like to pick the additional
integration tests for Tomcat (PAXWEB-1075).
What is the status of the
Hi Achim,
I did the release for tomcat-embed-websocket and here the release:perform
worked fine (in the correct repository). Do you have any idea how the
staging plugin selects the checkout directory?
Best regards
Stephan
Am Donnerstag, 7. September 2017 09:16:12 UTC+2 schrieb Stephan Siano
re
> -DautoVersionSubmodules=true
>
> mvn -Prelease -Darguments="-Prelease" -Dgoals=deploy release:perform
>
>
> regards, Achim
>
>
> 2017-09-04 12:42 GMT+02:00 Stephan Siano >
> :
>
>> Hi Achim,
>>
>> has anyone actually tried that und
s4j1.jira.com/wiki/spaces/ops4j/pages/12060688/Releasing
> can do the releasing :)
>
> about pax tipi, take a look here:
>
> https://ops4j1.jira.com/wiki/spaces/PAXTIPI/pages/28540952/Creating+New+Bundles
>
> regards, Achim
>
>
>
> 2017-08-31 8:40 GMT+02:00
on of this
will get to Nexus. Who can release this (and how is this done)?
Best regards
Stephan
Am Donnerstag, 31. August 2017 07:48:37 UTC+2 schrieb Achim Nierbeck:
>
> Hi
>
> looks good to me.
>
> regards, Achim
>
> 2017-08-30 12:01 GMT+02:00 Stephan Siano >
> :
accident.
> The build should re-build everything needed with the special adapted
> classes for OSGi classloaders.
>
> hope that helps already :)
>
> regards, Achim
>
>
> 2017-08-29 10:02 GMT+02:00 Stephan Siano >
> :
>
>> Hi,
>>
>> During my attem
> Regarding Jira tasks, yes it's common to create a Jira task in the pax
> tipi project (https://ops4j1.jira.com/projects/PAXTIPI/) and also a Jira
> task in Pax Web.
> If you like you can reference the pax tipi one in pax web.
>
> regards, Achim
>
>
> 2017-08-2
Hi,
During my attempt to update the tomcat version in pax-web, I stumbled about
the pax-web-jsp bundle.
pax-web-jsp unpacks the source bundle of tomcat-embed-jasper with the
maven-resources-plugin (exluding some of the java files which are in the
source tree of the pax-web-jsp bundle). As a co
ding a bunch of
> sub-projects.
>
> regarding the juli logger, what ever works best and doesn't break Pax Web
> from working.
> I tried to move around that in the past, but it seemed to be better to
> just include the juli logger inside the tomcat bundles.
>
> regards, A
(or master branch).
>
> regards, Achim
>
> P.S. btw. since Tomcat isn't OSGi ready we did some "enhancements" in the
> Pax Tipi Project.
>
>
> 2017-08-21 15:07 GMT+02:00 Stephan Siano >
> :
>
>> Hi,
>>
>> currently the tomcat support i
Hi,
currently the tomcat support in pax-web references tomcat 8.0.14, which is
almost three years old. The current tomcat versions are 8.0.46 and 8.5.20.
The end of life for tomcat 8.0 is announced for June 30th 2018.
Would it make sense to upgrade the tomcat version in pax-web-6.0x branch to
://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/WabJettyWebIntegrationTest.java
>
> hope this helps :)
>
> regards, Achim
>
>
> 2017-06-02 9:17 GMT+02:00 Stephan Siano
Hi,
I have assigned PAXWEB-629 (configure tomcat via config.xml) to me. I have
a working implementation that can use META-INF/config.xml from a war or
config.xml from the config dir or a config fragment (for default context
configuration).
I could test this manually with a RemoteAddrValve in t
Hi,
to sum up the result:
1. Most of the adapted tests work as in Jetty (this means that they work if
they work with Jetty or don't works if they do not work in Jetty (as the
issue with PAXWEB-1078)).
2. There are actually two open issues that cause tests that run in Jetty to
fail in Tomcat: P
o equivalent ... hmm we need to document that
> and skip it :/
> though I've been under the impression tomcat had a concept for that :)
>
> regards, Achim
>
>
> 2017-03-16 8:14 GMT+01:00 Stephan Siano >:
>
>> Hi Achim,
>>
>> should
regards
>> Marc
>>
>> [1]
>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-base/src/main/java/org/ops4j/pax/web/itest/base/client/JettyTestClient.java
>>
>> Am Mittwoch, 15. März 2017 15:49:07 UTC+1 schrieb Stephan Siano:
>>
me later this week. Feel free to create a Jira issue and assign it to me.
>>
>> regards
>> Marc
>>
>> [1]
>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-base/src/main/java/org/ops4j/pax/web/itest/base/client/JettyTest
> regards
> Marc
>
> [1]
> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-base/src/main/java/org/ops4j/pax/web/itest/base/client/JettyTestClient.java
>
> Am Mittwoch, 15. März 2017 15:49:07 UTC+1 schrieb Stephan Siano:
>>
>
Hi,
I have copied and adapted several (40+) integration tests from jetty to
tomcat. Sorry for the large number of pull requests for that. The tests
were running fine in a local build but were unstable on the Jenkins server.
I have not gone through all tests that are ignored in detail, but for n
Hi,
I have a question about the JIRA workflow for Pax-Web. Do I have to do
something with the JIRA tasks when the pull requests are merged and I think
they are done (e.g. set them to resolved)?
Best regards
Stephan
--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.co
gt;
> Hi Stephan,
>
> we will need a new Issue for that then.
> Though I'm wondering if that one slipped till now or if it is some sort of
> regression.
>
> regards, Achim
>
>
> 2017-03-13 7:46 GMT+01:00 Stephan Siano >:
>
>> HI Achim,
>>
>
Feel free to merge any time.
>
> regards, Achim
>
>
> 2017-03-11 21:47 GMT+01:00 Stephan Siano >
> :
>
>> Hi Achim,
>>
>> I created pull request https://github.com/ops4j/org.ops4j.pax.web/pull/77
>> for the change. Could you have a look? I am n
:26:25 UTC+1 schrieb Achim Nierbeck:
>
> Hi Stephan,
>
> sounds great.
> I think PAXWEB-993 is fine as, those are findings on fixing that.
>
> regards, Achim
>
>
> 2017-03-11 9:59 GMT+01:00 Stephan Siano >:
>
>> Hi Achim,
>>
>> The servlet
so get with Jetty ... never found the reason
> for it :/
> did you check if by any chances the JSF pages actually do work?
>
> regards, Achim
>
>
> 2017-03-10 16:46 GMT+01:00 Stephan Siano >
> :
>
>> Hi,
>>
>> I have tried to enable the JSF based inte
Hi,
I have tried to enable the JSF based integration tests with the tomcat web
container. These tests fail becasue the war-jsf war does not start.
The first issue I see is that the expression factory cannot be found.
javax.el.ELException: Unable to find ExpressionFactory of type:
org.apache.el
/OSGI-INF/metatype/metatype.xml
> [2] -
> https://nierbeck.de/2013/05/bind-certain-web-applications-to-specific-httpconnectors-ii/
> [3] -
> https://github.com/ops4j/org.ops4j.pax.web/blob/master/samples/whiteboard-extended/src/main/java/org/ops4j/pax/web/extender/samples/whiteboar
at do you think?
Best regards
Stephan
Am Freitag, 3. März 2017 20:25:10 UTC+1 schrieb Achim Nierbeck:
>
> Hi Stephan,
>
> see my comments inline :-)
>
> regards, Achim
>
>
> 2017-03-03 14:51 GMT+01:00 Stephan Siano >
> :
>
>> Hi,
>>
>>
Hi,
I am working on [PAXWEB-630] Interpret and use the tomcat-server.xml. While
doing so, I came across an interesting problem.
The tomcat-server.xml can configure host entries (and this does make sense,
since that allows to add additional configurations like valves to the
host).
However, af
Hi Achim,
OK, I will not test this functionality.
Best regards
Stephan
Am Donnerstag, 2. März 2017 09:37:10 UTC+1 schrieb Achim Nierbeck:
>
> Hi,
>
> see my comments inline
>
> regards, Achim
>
>
> 2017-03-02 7:58 GMT+01:00 Stephan Siano >:
>
>> Hi Ac
rds, Achim
>
> [1] -
> https://github.com/ANierbeck/karaf-enterprise-sample/blob/master/datasource-cookbook/src/main/resources/OSGI-INF/blueprint/datasource-cookbook.xml#L14-L18
> [2] -
> https://github.com/ANierbeck/karaf-enterprise-sample/blob/master/sample-persistence/src/main/
Hi,
If the pax-web build is executed behind a firewall (where the internet can
only be accessed through a proxy) the build fails in the pax-web-descriptor
build with some socket timeout issue. The reason behind this is that the
maven-jaxb2-plugin tries to resolve the resource
http://www.w3.org
Hi,
I am currently working on PAXWEB-630 (interpret and use the
tomcat-server.xml). One of the entities that can be configured are
GlobalNamingResources. With my changes, I can see the configured options in
the MBean tree, but when I tried to test them in an integration test it did
not work. O
https://ops4j1.jira.com/browse/PAXWEB-513
>
> 2017-02-27 12:51 GMT+01:00 Stephan Siano >
> :
>
>> Hi Achim,
>>
>> I had a look into the tests. The JSF tests still do not work (the bundle
>> still does not start). Neither does the error and index page sup
%20%3D%20Tomcat%20ORDER%20BY%20created%20DESC%20
> [2] -
> https://github.com/ops4j/org.ops4j.pax.web/tree/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-tomcat
>
>
>
> 2017-02-24 9:13 GMT+01:00 Stephan Siano >:
>
>> Hi,
>>
>> I am new
Hi,
I am new to this list, so please forgive me if I am asking questions that
are already answered elsewhere.
I had some look into the tomcat integration into Pax-Web, which is marked
as being "still experimental but better supported" for quite some time now.
We would like to drive it a little
60 matches
Mail list logo
