On 8 Oct 2009, at 21:06, Felix Meschberger wrote:
which ? the ones with servlet path collisions ?
yes, servlet path collision, I need to check that de-registration
really
works.
*but*
with 2 servlets registered to the same path I haven't worked out the
order in which they should be used, probably part of the sort order
thats required.
speaking of two servlets at the same path: these are OSGi services and
OSGi services as per the spec have a defined ranking:
"When registering a service object, a bundle may optionally
specify a service.ranking number as one of the service object’s
properties. If multiple qualifying service interfaces exist,
a service with the highest SERVICE_RANKING number, or when
equal to the lowest SERVICE_ID, determines which service object
is returned by the Framework." OSGi Core, 5.2.5, Service Properties
So, I would assume that we should order according to the
serivce.ranking
and service.id properties of the registered servlet -- we might pass
on
these two propreties from the servlet service registration to the
ServletResourceProvider registration (though property renaming esp.
for
the service.id would be required) to order the same named servlets.
That makes sense, I will see if I can work it into the rework.
Thanks
Ian
Regards
Felix
