Thanks Peter. This solution is good enough for my needs. Nikunj.
Peter Kriens wrote: > The servlet will receive all requests starting with the prefix. That > is /listener/resource will end up with your service, unless another > servlet specifically is registered on that uri. The servlet API > contains methods to get the remainder path. > > Kind regards, > > Peter Kriens > > > > NM> I am new to OSGI and I am trying to use OSGI for a web app. Is it legal > NM> in OSGI to register a wild card alias with HttpService? Let me describe > NM> the scenario so you can understand my question. > > NM> An HTTP servlet is listening at a certain alias say /listener. When it > NM> receives certain requests, the servlet generates a response with a child > NM> URI, which has the same prefix as its own alias, but with an extra path > NM> element, e.g., /listener/resource. > > NM> Upon reading the OSGI R4 spec, I get the impression that unless this new > NM> URI is registered as new alias, any request for the child URI (i.e., > NM> /listener/resource) will not be valid. Is that correct? How do people > NM> deal with dynamically created resources, especially since it does not > NM> make sense to register a new alias for each of these? > > NM> Thanks, > NM> Nikunj Mehta > NM> _______________________________________________ > NM> OSGi Developer Mail List > NM> osgi-dev@bundles.osgi.org > NM> http://bundles.osgi.org/mailman/listinfo/osgi-dev > > _______________________________________________ OSGi Developer Mail List osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
