OSGi already has a design well underway for a "replacement" of HttpService which is whiteboard based and supports bundle based web applications: RFC 66 Web Container Service.
It needs a bit of clean up and then I will work to get a draft made available to the open source communities for comment. But in the meantime, Richard can read and comment upon it... BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] Office: +1 407 849 9117 Mobile: +1 386 848 3788 "Rob Walker (JIRA)" <[EMAIL PROTECTED]> 2006-04-21 06:16 AM Please respond to [email protected] To [email protected] cc Subject [jira] Commented: (FELIX-64) Create a whiteboard adaptor for the HTTP Service [ http://issues.apache.org/jira/browse/FELIX-64?page=comments#action_12375528 ] Rob Walker commented on FELIX-64: --------------------------------- We'd need to ensure that there is a standard property and/or API call that the HTTP Service can use to determine the alias under which to register the servlet automatically. Not used whiteboard approach myself - but it would seem some common/well define OSGi property of the registering bundle/service which the HTTP or whiteboard service could retrieve would be the way to go. > Create a whiteboard adaptor for the HTTP Service > ------------------------------------------------ > > Key: FELIX-64 > URL: http://issues.apache.org/jira/browse/FELIX-64 > Project: Felix > Type: New Feature > Components: HTTP Service > Reporter: Richard S. Hall > Priority: Minor > > The HTTP Service was defined before the whiteboard approach for services became common, so it would be nice to implement a standard adaptor for the HTTP Service that implemented this pattern. To be more precise, the spec'ed behavior of the HTTP Service requires that servlet instances be registered with it explicitly. The whiteboard adaptor would allow servlet instances to be registered as services in the service registry and have the HTTP Service automatically register them by listening for service events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
