Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339179 - Add bean.name property to events
Summary: Add bean.name property to events
Status: CLOSED WONTFIX
Alias: None
Product: Gemini.Blueprint
Classification: RT
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 04:07 EST by Glyn Normington CLA
Modified: 2011-06-18 11:22 EDT (History)
2 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 Glyn Normington CLA 2011-03-08 04:07:25 EST 
Currently Gemini Blueprint exposes a "dependencies" property but no corresponding "bean.name" property (which *is* exposed on the corresponding Spring DM events), which is a useful serviceability feature.
Comment 1 Costin Leau CLA 2011-06-09 08:42:43 EDT 
Unfortunately the BlueprintEvent class does not allow for custom properties to be added to it. We'll have to extend it and for the user to cast the event to a custom class. Since Gemini Blueprint already issues OsgiServiceDependencyWaitStartingEvent and BootstrappingDependenciesEvent (which are specific to Gemini) one can use those instead.
Comment 2 Costin Leau CLA 2011-06-09 08:43:36 EDT 
See the previous comment on the resolution
Comment 3 Costin Leau CLA 2011-06-18 11:22:01 EDT 
Closing the bug