Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368899 - correct com.springsource references
Summary: correct com.springsource references
Status: RESOLVED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Miles Parker CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 373856
Blocks: 368761
  Show dependency tree
 
Reported: 2012-01-17 19:14 EST by Miles Parker CLA
Modified: 2012-04-10 16:38 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Parker CLA 2012-01-17 19:14:18 EST 
There are some usages of com.springsource in strings. After externalizing strings we need to fix that.
Comment 1 Miles Parker CLA 2012-03-07 23:20:38 EST 
Leo, can you take a look at the Jmx stuff in org.eclipse.virgo.ide.runtime.internal.core.command? There are still some com.springsource references in there, which makes me wonder how it's working.

There is also one suage in RepositoryUtils, but I think that should be there to support the com.springsource.* style bundles.
Comment 2 Leo Dos Santos CLA 2012-03-08 18:39:28 EST 
Miles, looks to me like the org.eclipse.virgo.ide.management.remote.StandardBundleAdmin is an MBean that registers itself with objectName = "com.springsource.server:type=BundleAdmin". I guess we package up the *management.remote jar and drop it into Virgo. A couple of our JMX commands (JMXBundleAdminExecuteCommand & JMXBundleAdminServerCommand) then look up the MBean with this signature. We can probably change these ids, & recompile the management.remote jar that we package with runtime.core

There's another usage in JMXServerUpdateCommand of "com.springsource.kernel:artifact-type=bundle". We need to run a JMX browser on a running Virgo to see what MBeans it exposes, but I'm guessing that we will have to change it to some sort of "org.eclipse.virgo.kernel.foo" id