Re: [pax-cdi] status (CDI, JSF, pax-web)

Awesome work Grzegorz Am Dienstag, 30. Januar 2018 13:13:34 UTC+1 schrieb Grzegorz Grzybek: > > Actually... I got it working! (MyFaces, Weld, pax-cdi and pax-web-jetty) - > it was my fault with proxies for annotations. > > But "What I had to change" is still valid - I can try proposing a PR

Re: pax-web - myfaces - primefaces

Hi Serhan This is more a JSF related issue than Pax-Web. Resources follow certain rules how they are resolved https://docs.oracle.com/javaee/6/tutorial/doc/girgm.html The "composite" part in the namespace is more or less a marker that tells JSF to resolve a resource in the JSF way (which is

Re: [pax-web][proposal] Reorganization of branches

I will have a look at the WhiteboardR7JaxRsIntegrationTest. Am Freitag, 13. Oktober 2017 13:30:56 UTC+2 schrieb Grzegorz Grzybek: > > Hello > > I just pushed changes to master branch - it's now at version > 7.0.0-SNAPSHOT. All tests pass except usual >

Re: Pax products and JPMS of Java 9

There has been a similar question on the OSGi Dev mailing-list [1]. Basically they say the same: OSGi will work in JPMS (as a classpath-application) but there is currently no way of mixing modules and bundles. [1] https://mail.osgi.org/pipermail/osgi-dev/2017-September/006550.html regards

Re: Preparing pax-web-6.0.7 release

+1 Am Donnerstag, 24. August 2017 12:07:47 UTC+2 schrieb Grzegorz Grzybek: > > Hello > > I'd like to release 6.0.7 of pax-web - with fixes to: > – PAXWEB-1117 – Race condition when registering servlets and so forth > – PAXWEB-1118 – Missing dependency (jetty-deploy bundle) in >

Re: PaxWeb: Whiteboard and compliance to the R6 specification

Hi Jérémie We definately want to be spec-compliant and I didnt realize that there are so many points missing. I know we have some parts missing regarding the whiteboard-dtos (mostly error cases). Do you already have access to our Jira? If not, we can add you there so you can submit a

Re: [pax-exam] move to pax-exam 5?

+1 regards Marc Am Mittwoch, 12. Juli 2017 13:41:47 UTC+2 schrieb Jean-Baptiste Onofré: > > +1 > > Regards > JB > > > On 07/12/2017 10:24 AM, 'Christoph Läubrich' via OPS4J wrote: > > Hi, > > > > I'd like to clean up the the Container API (see PAXEXAM-822 and linked > ones), > > simplyfy

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

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 wa

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

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. >> >> regard

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

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

Re: [pax-cdi] Application scoped bean and its lifecycle

Hi Pavel. Thanks for your findings regarding the Weld issues and providing a workaround. BTW: I doubt that you will get more answers by posting jokes about the community. Please keep in mind that PAX-CDI 1.0.0 is not released yet, so there are probably not many people using it yet. regards

Re: Issue with Whiteboard Resource Servlet Name

bruary 24, 2017 at 3:36:39 AM UTC-5, Marc Schlegel wrote: >> >> Hi Nick >> >> Thanks for spotting this. Your solution sounds reasonable, but we need to >> check the implications. >> Could you please file a Jira-issue [1] and provide an example how you

Re: [pax-web-tomcat] tests and issues found

Thanks for your work. Regarding your second question: this might be related to the new Jetty-TestClient which was added last year as a replacement for Apache HttpComponents. The error could come from two sources 1. The abstraction layer in the JettyTestClient [1] has a bug when building

Re: [PAXWEB-993] JSF Integration Tests with Tomcat

Welcome to the club :-) The second exception seems to occur with MyFaces in all OSGi environments. I can reproduce this also on a IBM Liberty Profile when stopping a WAB with JSF-support. Regarding the ExpressionFactory: I've also spent some time on this issue and couldnt get it to work yet.

Re: [ANN] - Release of Pax Web 6.0

Just some additional information: Pax-CDI RC2 was backported to work with Pax-Web 4.4 as well regards Marc Am Mittwoch, 21. Dezember 2016 19:05:30 UTC+1 schrieb Achim Nierbeck: > > Hi Pavel, > > afaik the samples and tests used 1.0.0.RC2 [1] > > regards, Achim > > [1] -

Re: [ANN] Pax-Web 4.4.0 and Pax-Cdi 1.0.0.RC2 released

I was going to give it a test-drive, unfortunately the build broke [1]. Currently only RC1 is available on Central [2]. [1] http://ci.ops4j.org/jenkins/job/org.ops4j.pax.cdi/ [2] https://mvnrepository.com/artifact/org.ops4j.pax.cdi/pax-cdi-api regards Marc Am Mittwoch, 19. Oktober 2016

Re: [Pax-Cdi/Web] JSF cannot access CdiBean

Just saw your comment on the Jira issue. I will go ahead and create an integration-test for Pax-Web 4.4.0-SNAPSHOT with the latest Pax-Cdi snapshot. Am Mittwoch, 12. Oktober 2016 15:46:37 UTC+2 schrieb Marc Schlegel: > > Awesome, thank you very much. > > I think it would be e

Re: Pax-CDI (1.0.0-SNAPSHOT): How to inject OSGi-Service in Bean

:56 UTC+2 schrieb Guillaume Nodet: > > > > Le mercredi 5 octobre 2016 18:33:51 UTC+2, Marc Schlegel a écrit : >> >> I am still trying to figure out how to use Pax-CDI with JSF in Pax-Web. >> >> *When I inject a OSGi-Service in a CD

Re: Pax-CDI (1.0.0-SNAPSHOT): How to inject OSGi-Service in Bean

the > 1.0.0-SNAPSHOT ? > Could be another annotation now. > > regards, Achim > > > 2016-10-05 18:33 GMT+02:00 Marc Schlegel <masch...@gmail.com > >: > >> I am still trying to figure out how to use Pax-CDI with JSF in Pax-Web. >> >> *When I in

Pax-CDI (1.0.0-SNAPSHOT): How to inject OSGi-Service in Bean

I am still trying to figure out how to use Pax-CDI with JSF in Pax-Web. *When I inject a OSGi-Service in a CDI-Bean I get a IllegalStateException* java.lang.IllegalArgumentException: Beans with @Service, @Component or @Config injection points should be annotated with @Component @RequestScoped

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

Here are my two cents Regarding the whiteboard-extender, I was actually thinking of moving this into the webcontainer, because due to the whiteboard-dto spec those two are closely related anyways. My idea was to deprecate the (upcoming) WhiteboardManager-service right away in order to merge

Re: [DISCUSS] Pax-Web 6.0.RC1 release

Honestly, I choose the Whiteboard-Issue because it helps me understand the project, so I can fix more serious bugs later on. Furthermore the issue was, in my opinion, blocking a release 6.0.0 and I was confident that I wont break anything since it is a simple addition (turned out not be so

Re: PAX-WEB IllegalStateException with scavenging sessions

Hi Pavel First, we need to figure out whats going wrong here. Since Pax-CDI is involved as well, it might be a bug there. Please keep in mind, we cannot give any dates about fixes. It will be fixed if somebody finds the time to work on the issue. I would love to see more companies involved in

Re: PAX -WEB/CDI: how to stop war bundle with CDI?

Just to give some advice here. If you could create a Gihub-repository and upload your example we might be able to help. CDI is currently work-in-progess. On the Aries Mailinglists are some discussions about CDI+DS integration and how to handle those proxies CDI is based on. Now, this might