asaf.lahav wrote:
FYI, Good news :)
I eventually figured out a way for Felix to load a bundle from a target
Directory by using the following configuration property:
configMap.put("felix.auto.install.2","reference:file:c:/Development/OGSi/OSG
iTestBundle");
Apparently the 'reference:' prefix allows the bundle to be loaded from a
directory rather than a JAR.
Yes, this is the case. The exploded bundle directory should have the
exact same structure of a bundle JAR file (i.e., like you just extracted
the JAR file) and it will work fine.
The "reference:" protocol is not purely for directories, you can also
point to a JAR file, in which case the JAR file will not be copied into
the bundle cache.
-> richard
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Felix
Meschberger
Sent: Tuesday, April 10, 2007 2:36 PM
To: felix-dev@incubator.apache.org
Subject: Re: Must a bundle be in a Jar file?
Hi,
To my knowledge, this is not supported in Felix.
BTW, the spec (page 27) says in section 3.2: "A bundle is deployed as
a Java ARchive (JAR) file."
Doing single-class exchange is not a good thing any way IMHO, as this
might violate the clearly defined lifecycle management of OSGi. In
fact, using the maven-bundle-plugin of Felix makes the development
cycle very easy: Change-Build-Update-Test.
Life class exchange is possible to some degree using a Java debugger,
but this is for simple testing only and does not replace proper
bundling and deployment according to the OSGi spec.
Regards
Felix
On 4/10/07, asaf.lahav <[EMAIL PROTECTED]> wrote:
It would be easier to debug a bundle if it wouldn't be required to be
closed
as a jar file.
Is it possible to create a bundle from class files that are not in a *.jar
file?
