I'd like to relate this discussion to the svn/git discussion. In such cases, I think it would be much easier if we were using git. Achim could create a branch, commit, ask for review and later merge. It seems to me that it makes things way easier to checkout rather than having to apply a patch for reviewal. Also, the patch can become huge, whereas a branch can contain many small fixes.
I wonder if we should switch pax-web to github asap and do a 1.8.0 release there when the times come. On Wed, Sep 15, 2010 at 10:31, Achim Nierbeck <achim.nierb...@ptv.de> wrote: > Well, currentyl I'm working on parsing the web.xml (done that) transfering > these Information into the Model (almost done) and wan't to configure the > httpContext. > Yesterday I saw that if it is a secured OSGi bundle there is some code for > getting the ApplicationSecurityContext (or something like that, I'm at work > and I don't have the code in front of me:) ) > Now I'm unsure if I should make up an OSGi-Like SecurityContext or if I > should go on with my first Idea to configure the standard httpContext like > the Jetty normaly would do. > > BTW, I think it will be rather large, I alread have touched about 5-8 > existing classes and added about 5-8 new ones :) > > > > -----Ursprüngliche Nachricht----- > Von: general-boun...@lists.ops4j.org [mailto:general-boun...@lists.ops4j.org] > Im Auftrag von Niclas Hedhman (JIRA) > Gesendet: Dienstag, 14. September 2010 21:23 > An: general@lists.ops4j.org > Betreff: [issues] Commented: (PAXWEB-210) Security Constraints for > WebApplications > > > [ > http://issues.ops4j.org/browse/PAXWEB-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13520#action_13520 > ] > > Niclas Hedhman commented on PAXWEB-210: > --------------------------------------- > > If the code change is large, I suggest that the solution is brought up on > mailing list first, for feedback. > > If it is not large, commit and highlight the change in an after-the-fact mail > works good enough I think. > >> Security Constraints for WebApplications >> ---------------------------------------- >> >> Key: PAXWEB-210 >> URL: http://issues.ops4j.org/browse/PAXWEB-210 >> Project: Pax Web >> Issue Type: Improvement >> Components: War Extender, Web Container, Whiteboard Extender >> Affects Versions: 0.7.1, 0.7.2 >> Reporter: Achim Nierbeck >> Assignee: Alin Dreghiciu >> >> Currently it is not possible to configure a security-constraint for any kind >> of web application served by pax-web. >> Therefore no Authentication is possible with pax-web :( >> If I'm running pax-web with the Apache Karaf server there is even an JAAS >> realm I would like to connect to. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.ops4j.org/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
