Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319369 - Rename service scope control property
Summary: Rename service scope control property
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 trivial (vote)
Target Milestone: 2.1.0.M05-incubation   Edit
Assignee: Glyn Normington CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-09 07:35 EDT by Steve Powell CLA
Modified: 2010-10-05 03:58 EDT (History)
1 user (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 Steve Powell CLA 2010-07-09 07:35:51 EDT 
com.springsource.service.scope is a property on services that if set to 'global' allows the service to be made available outside of an application scope.

This is an inappropriate name. Update all references (including in docs and tests) to this property name -- change to something like: org.eclipse.virgo.service.scope.
Comment 1 Glyn Normington CLA 2010-09-20 06:45:55 EDT 
Because a failure to rename this property is likely to be tricky to debug, we tolerate the old property name as a synonym for the new property name, at least for the 2.1.0 release. See http://wiki.eclipse.org/Virgo/Community/Migrating_from_dm_Server#Migrating_from_dm_Server_2.0.x_to_Virgo_2.1.0.x.
Comment 2 Glyn Normington CLA 2010-09-21 09:16:50 EDT 
At Steve's suggestion, when the old property name is encountered, we issue a warning, like this:

<KE0300W> Service property in bundle 'oldService' version '1.0.0' (bean 'oldBean') should be renamed from com.springsource.service.scope to org.eclipse.virgo.service.scope.
Comment 3 Glyn Normington CLA 2010-09-27 08:34:29 EDT 
RC1 is planned instead of milestone 5.