Thanks for the test code, it's actually a bug in the implementation. If the listener is registered after the context (which is always true for the default context), it was never called. I just committed a fix for this
Regards Carsten Am 13.05.15 um 11:53 schrieb Thomas Driessen: > Hi Ray, > > I've now the same setup as you posted it but it still doesn't work :( No > Sysouts are printed on my console for contextInitialized. > > I've copied the Testsetup to my Google Drive, so if you want you could have > a look on it: > > https://drive.google.com/folderview?id=0Bw1daHW2hcyZWFhlcldtdGV6alE&usp=sharing > > Best regards, > Thomas > > 2015-05-12 22:33 GMT+02:00 Raymond Auge <[email protected]>: > >> On Tue, May 12, 2015 at 11:28 AM, Achim Nierbeck <[email protected]> >> wrote: >> >>> Hi Ray, >>> >>> even though it might be a bit off-topic, but you started it ;) >>> >>> I encourage everyone to step up and join the OSGi Alliance to get this >> work >>>> progressing faster. To a very large degree this is the limiting factor >>> for >>>> why spec progression is slow). >>> >>> >>> For someone like me who only works on the OSGi related stuff like Pax Web >>> (btw. ServletContextListener work without any issues with it, it's just >> not >>> yet R6 compliant :-) ) and Karaf in his spare time, it's pretty hard to >>> join. There are a couple people out there with great ideas, but can't >> join >>> cause they don't work a company that is interested in funding such >>> involvement. Maybe you as a board member and co-chair for the EEG can >> help >>> those OpenSource folks to participate in this easier. >>> I know of at least one other person who would be willing to join in on >> this >>> but doesn't have a "sponsor" for it. >>> >>> regards, Achim >>> >> >> Thank you for your feedback Achim. There's no simple solution here as I'm >> sure you can guess. However, I certainly will keep this in mind. >> >> - Ray >> >> >>> >>> >>> 2015-05-12 17:18 GMT+02:00 Raymond Auge <[email protected]>: >>> >>>> On Tue, May 12, 2015 at 10:56 AM, Thomas Driessen < >>>> [email protected]> wrote: >>>> >>>>> >>>>> Two small notes: >>>>> 1) the mentioned property "osgi.http.whiteboard.listener" is never >>>>> mentioned in RFC-189 -> should it be mentioned? >>>>> >>>> >>>> There were many refinements made to the spec after progressing from the >>> RFP >>>> stage. >>>> >>>> Unfortunately since there isn't a public document for the draft spec >> yet >>>> (hopefully pretty soon) you'll have to take our word for it, sorry! :( >>>> >>>> Secondly, since the CT for the RI (felix http) isn't complete yet, it's >>>> possible that felix http is not yet working quite as expected. >>>> >>>> [Switching to Appeal mode] >>>> Sadly, this is due to not having the desired number of people available >>> in >>>> the alliance to get all this great work done in a timely fashion (and I >>>> assure you it's very great work, with more exciting work coming down >> the >>>> line)! >>>> >>>> I encourage everyone to step up and join the OSGi Alliance to get this >>> work >>>> progressing faster. To a very large degree this is the limiting factor >>> for >>>> why spec progression is slow). >>>> [End Appeal mode] >>>> >>>> Sincerely, >>>> - Ray (disclosure, I'm a board member and co-chair of the EEG) >>>> >>> >>> >>> >>> -- >>> >>> 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 >>> >> >> >> >> -- >> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> (@rotty3000) >> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> >> (@Liferay) >> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> >> (@OSGiAlliance) >> > > > -- Carsten Ziegeler Adobe Research Switzerland [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
