Under normal circumstances, I was planning on working on this some today. But we had Christmas play practice, etc... :) Sooo much fun with 20 elementary-age kids running around the church.

I just tested it again and it does work correctly now! Thanks for the uber-fast turnaround. That problem was holding me back, so I can make some real progress now.

Thanks!

Jon Brisibn
http://jbrisbin.com

On Dec 20, 2008, at 9:06 AM, Richard S. Hall wrote:

Ok, this definitely appears to be a bug in Felix. We just added checks to throw exceptions when starting/stopping fragments. I thought I put checks around all cases where we start/stop bundles, but apparently I missed some. I committed a fix for this, so hopefully it should not be an issue now. Just in time, since we are cutting a 1.4.1 release right now. :-)

If you can test it really quickly right now and tell us for sure if it is working, then that would be awesome...but I guess we cannot expect quick turnaround on Saturday. :-)

Thanks for reporting it.

-> richard

Jon Brisbin wrote:
SVN updated and tried again in a fresh install. I used a stock configuration, except for turning fragment validation to warning. My bundles are thus:

felix.auto.start.1 = \
   file:bundle/org.apache.felix.shell-1.1.0-SNAPSHOT.jar \
   file:bundle/org.apache.felix.shell.tui-1.1.0-SNAPSHOT.jar \
   file:bundle/org.apache.felix.bundlerepository-1.3.0-SNAPSHOT.jar \
 file:deploy/log4j.osgi-1.2.15-SNAPSHOT.jar \
 file:deploy/slf4j-api-1.5.6.jar \
 file:deploy/jcl-over-slf4j-1.5.6.jar
felix.auto.install.1 = \
 file:deploy/slf4j-log4j12-1.5.6.jar

Starting up gives me:

WARNING: Fragments with exports, imports, or native code are not currently supported. WARNING: Fragments with exports, imports, or native code are not currently supported. ERROR: Error starting/stopping bundle. (org.osgi.framework.BundleException: Fragment bundles can not be stopped: slf4j.log4j12 [7]) org.osgi.framework.BundleException: Fragment bundles can not be stopped: slf4j.log4j12 [7]
   at org.apache.felix.framework.Felix._stopBundle(Felix.java:2059)
   at org.apache.felix.framework.Felix.stopBundle(Felix.java:2033)
at org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java:1333) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java: 271)
   at java.lang.Thread.run(Thread.java:637)



Thanks!

Jon Brisibn
http://jbrisbin.com

On Dec 19, 2008, at 5:25 PM, Richard S. Hall wrote:

It's possible we have a bug in this checking code, since we added it recently.

I modified the error messsage to include the bundle ID, so make sure it is the bundle you think it is.

Perhaps give your entire configuration.

-> richard

Jon Brisbin wrote:
I'm trying to use a freshly-compiled version of Felix trunk and I can't seem to get SLF4J to work. I get errors like the following, even though the SLF4J fragments are in a felix.auto.install property.

WARNING: Fragments with exports, imports, or native code are not currently supported. ERROR: Error starting/stopping bundle. (org.osgi.framework.BundleException: Fragment bundles can not be stopped.) org.osgi.framework.BundleException: Fragment bundles can not be stopped. at org.apache.felix.framework.Felix._stopBundle(Felix.java: 2059) at org.apache.felix.framework.Felix.stopBundle(Felix.java: 2033) at org.apache.felix.framework.Felix.setBundleStartLevel(Felix.java: 1333) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java: 271)
     at java.lang.Thread.run(Thread.java:613)
Auto-properties start: org.osgi.framework.BundleException: Fragment bundles can not be started.

config:

felix.auto.install.1 = \
file:bundle/slf4j-simple-1.5.6.jar \
file:bundle/jcl-over-slf4j-1.5.6.jar \

Log4J and the SLF4J API is in felix.auto.start.1

Has anyone gotten SLF4J 1.5.6 to work in Felix 1.5?

Thanks!

Jon Brisbin
http://jbrisbin.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to