[#OSGI-431] OSGiHttpInvokerServiceExporter which is aware of bundlename and bundleversion

Spring OSGi

OSGiHttpInvokerServiceExporter which is aware of bundlename and bundleversion

Created: 11/Apr/08 03:23 AM Updated: 21/May/08 03:07 AM

Component/s:

WEB

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

VersionAwareContextPath.patch (15 kB)

Issue Links:

Related

This issue is related to:

~~OSGI-497~~ allow better subclassingof DefaultContextStrategy

Description

« Hide

It would be great to have a "OSGiHttpInvokerServiceExporter", that exports services under the
following url schema /<bundlename>/<bundle-version>/<beanname> with a
special behaviour for the bundle-version part. By convention it is expected that bundles follow
the apache version pattern major.minor.bugfix and only major.minor is
exported so bugfixes take effect immediate, but also different
versions can be used

All

Comments

Work Log

Change History

FishEye

Builds

Sort Order:

[ Permlink | « Hide ]

Björn Voß added a comment - 15/May/08 06:40 PM

I implemented a ContextPathStrategy for this concern.
And may be this issue can be linked to ~~OSGI-483~~.

[ Permlink | « Hide ]

Björn Voß added a comment - 15/May/08 06:58 PM

It would be great to have at least the abstract class present so there is no need to reimplement the encoding and header support.
I don't like code duplication ;-)

[ Permlink | « Hide ]

Costin Leau added a comment - 21/May/08 02:35 AM

Bjorn, I've created a separate issue for your proposal since it doesn't matches the actual request for this issue. I've left the patch in place but in the future, please create another task/sub-task rather then reusing an existing one.
Thanks.

[ Permlink | « Hide ]

Björn Voß added a comment - 21/May/08 03:07 AM

Sorry Costin, I didn't saw the two points here.
And I'll do so in the future.