Ok
I did take a look at it, I especially like the Lazy initialization of the HttpContext.
It's one of the reasons JSF is still not working like a charm ...
As far as I'm concerned I think it look good for a merge to trunk.
The polishing can be done later :D

regards, Achim

Am 14.08.2012 21:55, schrieb Achim Nierbeck:
Hi Harald,

I'm gonna take a look asap.
Thanks and regards, Achim

Am 14.08.2012 19:07, schrieb Harald Wellmann:
Update:

- Pax CDI 0.2.0 has been released without web support, but some of this is implemented (and working...) on master in 0.3.0-SNAPSHOT.

- I've pushed my Pax Web cdi branch to GitHub. The overall design is outlined in http://team.ops4j.org/browse/PAXWEB-367.

- The implementation is just a first shot and not very elegant, but all Pax Web tests are green on this branch, as well as some Pax CDI servlet tests.

Achim and other Pax Webbers, it would be great if you could spare some time to review the changes on the cdi branch and let me know what should be improved before merging with master.

Cheers,
Harald




_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general




--
- Apache Karaf <http://karaf.apache.org/> Committer & PMC
- OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>  Committer & 
Project Lead
- OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> 
Committer & Project Lead
- Blog <http://notizblog.nierbeck.de/>


_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to