[#OSGI-315] <context:component-scan /> doesn't work in an OSGi environment

Spring OSGi

<context:component-scan /> doesn't work in an OSGi environment

Created: 06/Jan/08 08:53 AM Updated: 21/Mar/08 04:22 AM

Component/s:

CORE

Affects Version/s:

1.0 RC1

Fix Version/s:

1.1 M1

Time Tracking:

Issue & Sub-Tasks

Issue Only

Not Specified

Issue Links:

Depends

This issue depends on:

~~OSGI-344~~ support classpath and classpath* wildcards inside the OSGi space

Related

This issue is related to:

~~OSGI-210~~ getResource()/getResources() called on "/"

Sub-Tasks:

All

Open

1.	~~offer resolver for translating osgi specific URLs to Java native ones~~	Resolved	Costin Leau
2.	~~consider downgrading to bundlespace wildcard matching on platforms where the classpath cannot be constructed~~	Resolved	Costin Leau
3.	~~Felix native URL resolver~~	Resolved	Costin Leau
4.	~~KF native URL resolver~~	Resolved	Costin Leau
5.	~~Equinox native URL resolver~~	Resolved	Costin Leau

Description

« Hide

It's likely that wildcard on root path are not supported yet.

All

Comments

Work Log

Change History

FishEye

Builds

Sort Order:

[ Permlink | « Hide ]

Costin Leau added a comment - 07/Jan/08 01:54 PM

The problem with classpath discovery is that there is no way to detect existing resources. One has to use the filesystem or jar structure to determine available context. However, inside the OSGi environment this is quite hard to achieve since the classpath is computer by the platform and the bundles can be packed or unpacked and placed in a dedicated location by the actual OSGi implementation.

[ Permlink | « Hide ]

Costin Leau added a comment - 21/Mar/08 04:22 AM

Fixed and tested in M1 through the classpath* support in the IO module.