Hi Marc, sounds good to me, and since this is a Major version I'm fine with those API Breaking changes.
regards, Achim 2016-09-23 13:49 GMT+02:00 Marc Schlegel <[email protected]>: > After some investigation regarding a implementation for the > whiteboard-dto-spec (PAXWEB-906), it turns out that there is quite some > work to do which will very likely cause breaking changes. > Short summary: the whiteboard-extender doesnt know anything about the > current state in the runtime, all it does is tracking, validation and > delegation to the webcontainer. In order to create the DTOs the > Webcontainer (pax-web-runtime) needs to know about whiteboard-artifacts > which it currently doesnt. > > Probable solution: I tend to couple the whiteboard-extender to a new > service (lets call it WhiteboardManager) which lives in the runtime. The > whiteboard-extender uses this service to register the tracked services > (Servlets, Filters, etc) instead of using the HttpService-API directly. > > This will couple pax-web-extender-whiteboard tighly with pax-web-runtime, > making it impossible to use this bundle together with any other > HttpService-implementation. > I think this should be fine, since all R6 HttpServices provide the same > functionality so there is no need to use pax-web-extender-whiteboard with > other runtimes (though it provides some unspecified bonus features like > Annotation-Scanned Whiteboard-Services). > > *If anyone uses pax-web-extender-whiteboard with a HttpService runtime > other than Pax-Web, please post this here or comment on PAXWEB-906 [1].* > > I am not sure how much time I can contribute to this issue (only > spare-time), but I will give it a try if nobody objects in the near future. > Development will go to a separate branch for better review. > > regards > Marc > > [1] https://ops4j1.jira.com/browse/PAXWEB-906 > > > Am Mittwoch, 14. September 2016 00:54:20 UTC+2 schrieb Achim Nierbeck: >> >> Hi, >> >> I like the idea of Marc. Though right now my day$job is consuming all of >> my time I would love to have OSGi R6 out of the door. After that I'm sure >> we can cut a 6.0.0. We don't need a RC after that. Everything else can go >> in a 6.0.1. >> One more thing: after the version changes in the 4.x line. My plan right >> now is to have sticky versions on packages and version increases on bundles >> and packages which require it. I'll re-enable the version check to be more >> strict after the first release of 6.0 >> >> Regards, Achim >> >> P.s. I'm in Paris right now without good connection on my private phone. >> >> sent from mobile device >> >> Am 13.09.2016 11:56 nachm. schrieb "Marc Schlegel" <[email protected]>: >> >>> Hi Guilaume >>> >>> I would like to see full R6 Whiteboard before an RC goes out. Tomcat >>> stuff can wait since it the other containers work pretty well. >>> I was actually planning on taking a look at PAXWEB-906 [1] but I cannot >>> promise anything. >>> >>> As I mentioned in a post yesterday, I would love to see a more companies >>> getting involved to work on some issues. Currently the main development is >>> done by Achim (though there are some PRs coming in recently). There are >>> currently "only" 8 issues marked for 6.0.0. >>> >>> I guess you are refering to karaf and pax-cdi depending on snapshots of >>> pax-web. How about a short synchronized roadmap, which features are needed >>> by those projects so we can order the backlog. >>> >>> regards >>> Marc >>> >>> [1] https://ops4j1.jira.com/browse/PAXWEB-906?filter=11020 >>> >>> Am Dienstag, 13. September 2016 17:07:51 UTC+2 schrieb Guillaume Nodet: >>>> >>>> I know pax-web 6 isn't finalized yet, it's missing full support for the >>>> OSGi Http Whiteboard and some other tomcat stuff. >>>> However a bunch of projects depend on the snapshot, which makes things >>>> difficult to manage on the long run (especially, they can't release RC >>>> either, I'm thinking about a pax-cdi rc2). >>>> >>>> So what about releasing a RC1 ? The code isn't evolving much at the >>>> moment, so it would make sense to me. >>>> >>>> -- >>>> ----------------------- >>>> Guillaume Nodet >>>> ------------------------ >>>> Red Hat, Open Source Integration >>>> >>>> Email: [email protected] >>>> Web: http://fusesource.com >>>> Blog: http://gnodet.blogspot.com/ >>>> >>>> -- >>> -- >>> ------------------ >>> OPS4J - http://www.ops4j.org - [email protected] >>> >>> --- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > -- > ------------------ > OPS4J - http://www.ops4j.org - [email protected] > > --- > 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 [email protected]. > 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 -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
