Community
Participate
Working Groups
The bundle ids look wrong at the very least. Once these are fixed, we should check that the list is consistent and work out why some bundles are missing. Compare: osgi> vsh bundle list Id Name Version State 7 org.eclipse.osgi.services 3.3.0.v20110110 ACTIVE 8 org.eclipse.equinox.cm 1.0.300.v20101204 ACTIVE 20 org.springframework.aop 3.0.5.RELEASE ACTIVE 21 org.springframework.asm 3.0.5.RELEASE ACTIVE 22 org.springframework.expression 3.0.5.RELEASE ACTIVE 23 org.springframework.beans 3.0.5.RELEASE ACTIVE 24 org.springframework.core 3.0.5.RELEASE ACTIVE 25 org.springframework.context 3.0.5.RELEASE ACTIVE 27 org.eclipse.virgo.kernel.agent.dm 3.0.0.M06 ACTIVE 28 org.springframework.osgi.core 1.2.1 ACTIVE 29 S org.springframework.osgi.extender 1.2.1 ACTIVE 30 org.springframework.osgi.io 1.2.1 ACTIVE 31 com.springsource.org.aopalliance 1.0.0 ACTIVE 32 org.eclipse.equinox.ds 1.3.0.v20110124-0830 ACTIVE 33 org.eclipse.equinox.util 1.0.200.v20100503 ACTIVE 40 org.eclipse.virgo.kernel.userregionfactory 3.0.0.M06 ACTIVE 41 com.springsource.org.apache.mina.core 2.0.2 ACTIVE 42 org.apache.felix.gogo.command 0.8.0.v201105062003 ACTIVE 43 org.apache.felix.gogo.runtime 0.8.0.v201105062003 ACTIVE 44 org.apache.felix.gogo.shell 0.8.0.v201105062003 ACTIVE 45 org.eclipse.equinox.console.supportability 1.0.0.N20110626-2000 ACTIVE 46 com.springsource.org.apache.sshd.core 0.5.0 ACTIVE 48 org.eclipse.virgo.kernel.userregion 3.0.0.M06 ACTIVE 49 org.eclipse.virgo.kernel.osgicommand 3.0.0.M06 ACTIVE 61 S org.eclipse.virgo.kernel.deployer.dm 3.0.0.M06 ACTIVE 65 org.eclipse.virgo.kernel.dmfragment 3.0.0.M06 RESOLVED and: osgi> ss "Framework is launched." id State Bundle 0 ACTIVE org.eclipse.osgi_3.7.0.v20110224 40 ACTIVE org.eclipse.virgo.kernel.userregionfactory_3.0.0.M06 47 ACTIVE org.eclipse.equinox.cm_1.0.300.v20101204 48 ACTIVE org.eclipse.virgo.kernel.userregion_3.0.0.M06 49 ACTIVE org.eclipse.virgo.kernel.osgicommand_3.0.0.M06 50 ACTIVE org.eclipse.osgi.services_3.3.0.v20110110 51 ACTIVE com.springsource.org.apache.mina.core_2.0.2 52 ACTIVE org.apache.felix.gogo.command_0.8.0.v201105062003 53 ACTIVE org.apache.felix.gogo.runtime_0.8.0.v201105062003 54 ACTIVE org.apache.felix.gogo.shell_0.8.0.v201105062003 55 ACTIVE org.eclipse.equinox.console.supportability_1.0.0.N20110626-2000 56 ACTIVE com.springsource.org.apache.sshd.core_0.5.0 57 ACTIVE org.springframework.osgi.core_1.2.1 58 ACTIVE org.springframework.osgi.extender_1.2.1 Fragments=65 59 ACTIVE org.springframework.osgi.io_1.2.1 60 ACTIVE org.eclipse.virgo.kernel.agent.dm_3.0.0.M06 61 ACTIVE org.eclipse.virgo.kernel.deployer.dm_3.0.0.M06 62 ACTIVE org.eclipse.equinox.ds_1.3.0.v20110124-0830 63 ACTIVE org.eclipse.equinox.util_1.0.200.v20100503 64 ACTIVE com.springsource.org.aopalliance_1.0.0 65 RESOLVED org.eclipse.virgo.kernel.dmfragment_3.0.0.M06 Master=58 66 ACTIVE org.springframework.aop_3.0.5.RELEASE 67 ACTIVE org.springframework.asm_3.0.5.RELEASE 68 ACTIVE org.springframework.beans_3.0.5.RELEASE 69 ACTIVE org.springframework.context_3.0.5.RELEASE 70 ACTIVE org.springframework.core_3.0.5.RELEASE 71 ACTIVE org.springframework.expression_3.0.5.RELEASE
It appears as if bundles which are present in both the kernel and user region are displaying their kernel bundle ids in the list.
Targeting 3.0.0.RC1 to indicate this bug is a "must fix".
Assigning to Lazar/Borislav.
Created attachment 199954 [details] Patch that fixes the IDs of the listed with vsh bundles This patch fixes the vsh bundle list. The problem was that vsh got the whole bundles list via the quasi framework and searched with bsn and version for bundles in it, so it took the IDs of the first matches. That is why the bundles that are present in both regions were listed with their kernel ID. Fixed by checking if the matched ID is present in the user region's bundleIDs list, if not continue matching.
Assigning to Hristo as he showed interest in integrating this in Virgo.
Created attachment 199959 [details] Fixes the IDs of the listed with vsh bundles
Created attachment 199967 [details] Patch for the problem
Created attachment 199973 [details] Patch for the problem
Lazar can you confirm that you wrote 100% of the code and you have the right to contribute it to Eclipse?
(In reply to comment #9) > Lazar can you confirm that you wrote 100% of the code and you have the right to > contribute it to Eclipse? Yes, I confirm that.
Patch commit id: 73644c6f41c9bb6f4bf292df4c6de2fa98626127
