RE: [Springide-eclip-developer] Brainstorming for bean search functions

[Watkins, D. <dav...@fa...>]

Hiya,
I can see the value of 4 (if I understood=20
the idea correctly) however I'm not sure=20
that 3 is paraticularly useful; I quite=20
often have a bunch of default values and/or=20
properties for hooking mock objects into=20
my beans.  I wouldn't want to see those=20
coming up as unassigned properties as I=20
very rarely assign them.  Perhaps better=20
would be a context option on a bean in the=20
view to display available properties=20
(and perhaps have something like the=20
Source..Override/Implement Methods option=20
in the JDT Editor which can insert some=20
template <property/> markup for you).  =20
However I think this should be on a per bean=20
basis, not across multiple beans.=20

Going back to 4, I take it you mean being=20
able to ask Spring IDE something like:
Show me all the beans which get wired=20
into this argument of this class (or=20
it's subtypes)?

Incidently, looking at your access point=20
list (c), some time ago I looked at how to=20
contribute to an 'unspecified' editor and=20
couldn't see an easy way of doing it.  Given=20
that Spring IDE is 'editor neutral' this may=20
be tricky to implement.  However it may well=20
be the case that I've just missed the relevant=20
extension point!

Cheers,
dw


P.S. are there any plans to look at adding the ability to follow import
tags?  If not, I'll take a=20
look at it when the fresh code arrives. =20


> -----Original Message-----
> From: spr...@li...=20
> [mailto:spr...@li...]
>  On Behalf Of Torsten Juergeleit
> Sent: 31 March 2005 16:00
> To: Spring IDE Developer List
> Subject: [Springide-eclip-developer] Brainstorming for bean=20
> search functions
>=20
> All,
>=20
> I'm thinking about adding a new plugin to Spring IDE's bean=20
> factory plugins which brings support for searching the bean=20
> model. Dave already created a nice extension to Spring IDE=20
> whith this kind of functionality=20
> (http://springui-ext.sourceforge.net/search.html ). This is a=20
> great starting point.
>=20
> Now I'm just wondering which kind of search capabilities you=20
> are interested in?
>=20
> The following is my take:
>=20
> 1. list of beans with a given name (already implemented by Dave)
>=20
> 2. list of beans with a given bean class (already implemented by Dave)
>=20
> 3. list of beans with unassigned properties (no property +=20
> corresponding value defined for a bean class' public setter)
>      http://opensource.atlassian.com/projects/spring/browse/IDE-37
>=20
> 4. list of beans referenced by a given model element (bean,=20
> property or constructor argument)
>=20
>=20
> And what are the access points for these search capabilities?
>=20
> Here is my best guess:
>=20
> a) additional pane in Eclipse list of different search panes (Dave=20
> already implemented a combined pane for 1. and 2.)
>=20
> b) context menu for model elements selected in beans view (could be a=20
> good fit for 3. and 4.)
>=20
> c) context menu for current cursor position in text editor
>=20
>=20
> What do you think?
>=20
> Cheers,
> Torsten
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/info/Sentarus/hamr30
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>=20