Right, the Coordinator. I’ve been meaning to see what that is about. Guess now is a good time.
Thanks for the tip! Cheers, =David > On May 31, 2016, at 9:49 PM, Peter Kriens <[email protected]> wrote: > > You could register it with the Coordinator, if present. In OSGi enRoute there > is always a Coordinator setup for each request. (Or should be) > > Kind regards, > > Peter Kriens > >> On 31 mei 2016, at 14:47, David Leangen <[email protected] >> <mailto:[email protected]>> wrote: >> >> >> Yes, thanks! Good enough for me. :-) >> >> BTW - in the error page servlet, is it possible to retrieve the exception >> that caused the error page to be loaded? I can’t seem to find it anywhere… >> I’m guessing not, but one can hope. >> >> >> Cheers, >> =David >> >> >>> On May 31, 2016, at 9:38 PM, Raymond Auge <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> TL;DR; Yes! >>> >>> Complete; Generally speaking the whiteboard pattern implies ordering by >>> what you could call "normal service ordering rules" which is; firstly order >>> by highest ranking, secondly order by lowest service id. It would be very >>> odd for a whiteboard impl to not follow this, in fact I don't know of any >>> examples. >>> >>> HTH, >>> - Ray >>> >>> On Tue, May 31, 2016 at 8:25 AM, David Leangen <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi! >>> >>> If two different HTTP Whiteboard components are both registering an error >>> page with the property “osgi.http.whiteboard.servlet.errorPage”, is the >>> winner determined by the service.ranking? >>> >>> I am assuming so, but I don’t see any clear reference. >>> >>> >>> Cheers, >>> =David >>> _______________________________________________ >>> OSGi Developer Mail List >>> [email protected] <mailto:[email protected]> >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >>> <https://mail.osgi.org/mailman/listinfo/osgi-dev> >>> >>> >>> -- >>> 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) >>> _______________________________________________ >>> OSGi Developer Mail List >>> [email protected] <mailto:[email protected]> >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >>> <https://mail.osgi.org/mailman/listinfo/osgi-dev> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] <mailto:[email protected]> >> https://mail.osgi.org/mailman/listinfo/osgi-dev > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
