Menu
▾
▴
springide-eclip-developer
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(21) |
Oct
(41) |
Nov
(18) |
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
|
Mar
(15) |
Apr
(17) |
May
(2) |
Jun
(6) |
Jul
(13) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2006 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Watkins, D. <dav...@fa...> - 2004-11-04 16:56:30
|
Found a picture of it! http://help.eclipse.org/help30/topic/org.eclipse.jdt.doc.user/images/qs- 11.gif =20 > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Antranig Basman > Sent: 04 November 2004 16:04 > To: spr...@li... > Subject: [Springide-eclip-developer] "Open Java Type"=20 > destroys browse functionality! >=20 > Selecting "Open Java Type" =3D CTRL-ALT-T from the highlighted=20 > class name in either the text or graphical bean definition=20 > view permanently destroys the browse-to functionality in Eclipse! > Instead of showing all of the browsed-to class (usually=20 > accessed via CTRL-SPACE), the editor only shows the code for=20 > the method selected, or if the class, only the code for the=20 > class, omitting the import and package declarations. > This state is permanent! Shutting down Eclipse and restarting=20 > it does not clear it! I'd actually strongly appreciate any=20 > hints on how to edit my preferences file to reverse this,=20 > since I currently have no option but to clear it out completely. >=20 > I'm using Eclipse 3.0.1, GEF 3.0.1, Spring 1.1 and the latest=20 > Spring IDE plugin from the devel update site. >=20 > Thanks, > Antranig. >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE=20 > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >=20 |
|
From: Watkins, D. <dav...@fa...> - 2004-11-04 16:51:03
|
This sounds more like you've accidently pushed the=20 'Show source of seleced element only' toggle button. On=20 mine it's button the next to the instance highlighter and=20 looks like a sheet of A4 with a rectangular index card=20 overlaid and to the right. Can you check that and let us know if that's it. Thanks Cheers, dw > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Antranig Basman > Sent: 04 November 2004 16:04 > To: spr...@li... > Subject: [Springide-eclip-developer] "Open Java Type"=20 > destroys browse functionality! >=20 > Selecting "Open Java Type" =3D CTRL-ALT-T from the highlighted=20 > class name in either the text or graphical bean definition=20 > view permanently destroys the browse-to functionality in Eclipse! > Instead of showing all of the browsed-to class (usually=20 > accessed via CTRL-SPACE), the editor only shows the code for=20 > the method selected, or if the class, only the code for the=20 > class, omitting the import and package declarations. > This state is permanent! Shutting down Eclipse and restarting=20 > it does not clear it! I'd actually strongly appreciate any=20 > hints on how to edit my preferences file to reverse this,=20 > since I currently have no option but to clear it out completely. >=20 > I'm using Eclipse 3.0.1, GEF 3.0.1, Spring 1.1 and the latest=20 > Spring IDE plugin from the devel update site. >=20 > Thanks, > Antranig. >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE=20 > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >=20 |
|
From: Antranig B. <ant...@ca...> - 2004-11-04 16:05:25
|
Selecting "Open Java Type" = CTRL-ALT-T from the highlighted class name in either the text or graphical bean definition view permanently destroys the browse-to functionality in Eclipse! Instead of showing all of the browsed-to class (usually accessed via CTRL-SPACE), the editor only shows the code for the method selected, or if the class, only the code for the class, omitting the import and package declarations. This state is permanent! Shutting down Eclipse and restarting it does not clear it! I'd actually strongly appreciate any hints on how to edit my preferences file to reverse this, since I currently have no option but to clear it out completely. I'm using Eclipse 3.0.1, GEF 3.0.1, Spring 1.1 and the latest Spring IDE plugin from the devel update site. Thanks, Antranig. |
|
From: Watkins, D. <dav...@fa...> - 2004-11-01 12:37:16
|
Torsten, I'd be happy to see a release on Wednesday. However I'm out of the office on Tues and Weds so will be unable to do any meaningful tests=20 with 1.1.2 before the release...=20 Cheers, dw=20 > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Torsten Juergeleit > Sent: 31 October 2004 21:01 > To: Spring IDE Developer List > Subject: [Springide-eclip-developer] New version available on=20 > updatesite >=20 > With the new version the following issues are fixed: >=20 > - validator supports import tags now (checks if imported=20 > BeanDefinition resource exists -> no validation, this is done=20 > if the imported config is changed) >=20 > - validator now ignores non-abstract root bean which has no=20 > class and no parent -> Spring's DTD (comment for bean=20 > attribute "classname") states that it's allowed >=20 > - added missing methods in FileResource to override the dummy=20 > ones from AbstractResource >=20 >=20 > I would like to wait for Spring 1.1.2 (announced for tomorrow=20 > evening)=20 > and release Spring IDE 1.1.0 afterwards, maybe on wednesday. Any=20 > comments? >=20 > Cheers, > Torsten >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >=20 |
|
From: Assaf U. <as...@jo...> - 2004-11-01 11:41:07
|
Thanks, got the latest release and it works now. Assaf > |
|
From: Torsten J. <tor...@on...> - 2004-10-31 21:00:48
|
With the new version the following issues are fixed: - validator supports import tags now (checks if imported BeanDefinition resource exists -> no validation, this is done if the imported config is changed) - validator now ignores non-abstract root bean which has no class and no parent -> Spring's DTD (comment for bean attribute "classname") states that it's allowed - added missing methods in FileResource to override the dummy ones from AbstractResource I would like to wait for Spring 1.1.2 (announced for tomorrow evening) and release Spring IDE 1.1.0 afterwards, maybe on wednesday. Any comments? Cheers, Torsten |
|
From: Torsten J. <tor...@on...> - 2004-10-28 22:23:04
|
David, I modifed the project description of Spring IDE accordingly. Thank you=20= for the hint. > p.s. I've removed the dependancy on the xerces jar from my code (and > managed to figure out how to stop the default attributes writing to = the > file everytime a programatic change is made). Cool, I will check the new version right now. Cheers, Torsten On 27.10.2004, at 21:36, Watkins, David wrote: > Torsten, > I was changing my project description on SourceForge and I noticed = that > if I include the word 'springframework' I get listed when someone > searches on that. The Spring IDE text mentions 'Spring Framework' and > so doesn't get listed if someone is searching for the main framework. =20= > I > appreciate it's very minor (and somewhat off topic) but since it's a > free way to get a tiny bit more exposure it may be worth doing. > > Cheers, > dw > > p.s. I've removed the dependancy on the xerces jar from my code (and > managed to figure out how to stop the default attributes writing to = the > file everytime a programatic change is made). > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_idU88&alloc_id=12065&op=3Dclick > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > |
|
From: Watkins, D. <dav...@fa...> - 2004-10-27 19:36:35
|
Torsten, I was changing my project description on SourceForge and I noticed that if I include the word 'springframework' I get listed when someone searches on that. The Spring IDE text mentions 'Spring Framework' and so doesn't get listed if someone is searching for the main framework. I appreciate it's very minor (and somewhat off topic) but since it's a free way to get a tiny bit more exposure it may be worth doing. Cheers, dw p.s. I've removed the dependancy on the xerces jar from my code (and managed to figure out how to stop the default attributes writing to the file everytime a programatic change is made). |
|
From: Watkins, D. <dav...@fa...> - 2004-10-26 10:03:03
|
>=20 > Hhm, I'm not sure if exposing Xerces might have side effects,=20 > e.g. with other plugin shipping with a different version of=20 > Xerces like XmlBuddy. > Not sure, I thought the way Eclipse handles plugin=20 classpaths should prevent this scenario.... =20 > Is it sufficient for you to use the built-in XML parser of=20 > JDK 1.4 (Apache Crimson)? > The only reason why Spring IDE core ships with it's own copy=20 > of Xerces is because Crimson doesn't support DOM level 3. > ....however this is probably a better idea. I'll look into it. =20 Was thinking of using an alternative approach anyway, so I can=20 avoid the 'unwanted optional attributes' problem I was talking=20 about in an earlier posting. Cheers, dw |
|
From: Watkins, D. <dav...@fa...> - 2004-10-26 09:56:42
|
Thanks Torsten,=20 Just got the latest code from cvs and it works fine now. Cheers, Dave > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Torsten Juergeleit > Sent: 26 October 2004 00:08 > To: Spring IDE Developer List > Subject: Re: [Springide-eclip-developer] Spring IDE=20 > Extensions - Search: Feedback >=20 > David, >=20 > don't worry. I have extended BeansView.show() to support=20 > instances of IBeansModelElement as ShowInContext's input=20 > object or first selection element too. >=20 > The updated version of BeansView and BeansUIUtils is=20 > available in CVS head. >=20 > Cheers, > Torsten >=20 >=20 > On 25.10.2004, at 20:39, Watkins, David wrote: >=20 > > Hi Torsten, > > I've implemented suggestion 1 (a mistake on my behalf. For=20 > item 2 I'm=20 > > actually using IBean's in the search result view. I tried=20 > adding the=20 > > interface and method you suggested but they don't get=20 > called. Instead=20 > > I've hacked another else clause onto the bottom of=20 > > BeansView::show(...) which can construct a=20 > BeansViewLocation from an=20 > > IBean. I haven't checked this in yet as I wanted to run it=20 > past you. > > > > A potentially neater solution to this is to make=20 > BeansViewLocation an=20 > > interface and make Bean into an IAdaptable class (I seem to=20 > remember=20 > > we can do this by registering with an AdapterManager=20 > somewhere so we=20 > > do't have to 'pollute' the bean class too much). Just a thought! > > > > Cheers, > > dw > > > >> -----Original Message----- > >> From: spr...@li... > >> [mailto:spr...@li...] > >> On Behalf Of Torsten Juergeleit > >> Sent: 24 October 2004 22:23 > >> To: Spring IDE Developer List > >> Subject: [Springide-eclip-developer] Spring IDE Extensions - > >> Search: Feedback > >> > >> Dave, > >> > >> the search facility of Spring IDE Extensions is very good. > >> I have a few suggestions: > >> > >> 1. selecting "Search Again" in the search result page with a=20 > >> successful search adds duplicates to the list > >> > >> 2. selecting "Show In / Spring Beans" in the search result=20 > page for a=20 > >> node in the result tree view doesn't navigate to the corresponding=20 > >> node in the Spring Beans view > >> > >> For 2. BeanSearchResultPage has to implement IShowInSource=20 > and return=20 > >> in getShowInContext() an instance of ShowInContext which holds an=20 > >> input object of BeansViewLocation (prepared with project=20 > name, config=20 > >> name, bean name [if available] and property name [if=20 > available]) and=20 > >> a selection object of StructuredSelection (IResource of=20 > the selected=20 > >> node > >> -> project or [config] file). The input object is recognized by=20 > >> -> Spring > >> Beans view and the selection object i recognized by Eclipse's=20 > >> resource navigator or JDT's package explorer. > >> > >> For samples please refer to BeansView.getShowInContext()=20 > or the Beans=20 > >> UI action ShowInView.run(). > >> > >> Ups, to recognize the input object first instead of the=20 > selection (if=20 > >> provided both) I have to modify BeansView.show(). Ok, I=20 > will fix this=20 > >> now. You can find the fix in CVS head. > >> > >> Cheers, > >> Torsten > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: IT Product Guide on=20 > >> ITManagersJournal Use IT products in your business? Tell=20 > us what you=20 > >> think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20 > >> Certificates! Click to find out more=20 > >> http://productguide.itmanagersjournal.com/guidepromo.tmpl > >> _______________________________________________ > >> Springide-eclip-developer mailing list=20 > >> Spr...@li... > >>=20 > https://lists.sourceforge.net/lists/listinfo/springide-eclip-develope > >> r > >> > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: IT Product Guide on=20 > > ITManagersJournal Use IT products in your business? Tell us=20 > what you=20 > > think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20 > > Certificates! Click to find out more=20 > > http://productguide.itmanagersjournal.com/guidepromo.tmpl > > _______________________________________________ > > Springide-eclip-developer mailing list=20 > > Spr...@li... > >=20 > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > > >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on=20 > ITManagersJournal Use IT products in your business? Tell us=20 > what you think of them. Give us Your Opinions, Get Free=20 > ThinkGeek Gift Certificates! Click to find out more=20 > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >=20 |
|
From: Torsten J. <tor...@on...> - 2004-10-25 23:07:46
|
David, don't worry. I have extended BeansView.show() to support instances of IBeansModelElement as ShowInContext's input object or first selection element too. The updated version of BeansView and BeansUIUtils is available in CVS head. Cheers, Torsten On 25.10.2004, at 20:39, Watkins, David wrote: > Hi Torsten, > I've implemented suggestion 1 (a mistake on my behalf. For item 2 I'm > actually using IBean's in the search result view. I tried adding the > interface and method you suggested but they don't get called. Instead > I've hacked another else clause onto the bottom of BeansView::show(...) > which can construct a BeansViewLocation from an IBean. I haven't > checked this in yet as I wanted to run it past you. > > A potentially neater solution to this is to make BeansViewLocation an > interface and make Bean into an IAdaptable class (I seem to remember we > can do this by registering with an AdapterManager somewhere so we do't > have to 'pollute' the bean class too much). Just a thought! > > Cheers, > dw > >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] >> On Behalf Of Torsten Juergeleit >> Sent: 24 October 2004 22:23 >> To: Spring IDE Developer List >> Subject: [Springide-eclip-developer] Spring IDE Extensions - >> Search: Feedback >> >> Dave, >> >> the search facility of Spring IDE Extensions is very good. >> I have a few suggestions: >> >> 1. selecting "Search Again" in the search result page with a >> successful search adds duplicates to the list >> >> 2. selecting "Show In / Spring Beans" in the search result >> page for a node in the result tree view doesn't navigate to >> the corresponding node in the Spring Beans view >> >> For 2. BeanSearchResultPage has to implement IShowInSource >> and return in getShowInContext() an instance of ShowInContext >> which holds an input object of BeansViewLocation (prepared >> with project name, config name, bean name [if available] and >> property name [if available]) and a selection object of >> StructuredSelection (IResource of the selected node >> -> project or [config] file). The input object is recognized by Spring >> Beans view and the selection object i recognized by Eclipse's >> resource navigator or JDT's package explorer. >> >> For samples please refer to BeansView.getShowInContext() or >> the Beans UI action ShowInView.run(). >> >> Ups, to recognize the input object first instead of the >> selection (if provided both) I have to modify >> BeansView.show(). Ok, I will fix this now. You can find the >> fix in CVS head. >> >> Cheers, >> Torsten >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IT Product Guide on >> ITManagersJournal Use IT products in your business? Tell us >> what you think of them. Give us Your Opinions, Get Free >> ThinkGeek Gift Certificates! Click to find out more >> http://productguide.itmanagersjournal.com/guidepromo.tmpl >> _______________________________________________ >> Springide-eclip-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >> > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > |
|
From: Torsten J. <tor...@on...> - 2004-10-25 23:00:36
|
> Oh and whilst I'm thinking about it, is it okay if we mark the Xerces > and xml jars as exported resources otherwise extensions will have to > bundle it's own copy. Hhm, I'm not sure if exposing Xerces might have side effects, e.g. with other plugin shipping with a different version of Xerces like XmlBuddy. Is it sufficient for you to use the built-in XML parser of JDK 1.4 (Apache Crimson)? The only reason why Spring IDE core ships with it's own copy of Xerces is because Crimson doesn't support DOM level 3. Cheers, Torsten On 25.10.2004, at 11:40, Watkins, David wrote: > Thanks! I'll look at how to put those changes in. > > I've also added a quick fix for property mismatches over the weekend... > it only works by selecting the problem from the Problems view, haven't > looked into whether I can modify ruler markers on an unspecified editor > yet (i.e. we don't know what editor the user employs for editing spring > files) - looking at the way the JDT quick fixes work I guess it's > mission impossible as they don't work outside the Java Editor. > > It also has a problem as it uses my XMLSearchReplacer (like the > refactoring support) which has the side effect of writing out the > optional DTD attributes (rather than leaving them blank) I'm currently > looking at how to stop that from happening. Once that's sorted out I > should be able to port the quick fix stuff over to the main > feature/plugins as I don't think it's dependent on Eclipse 3.x > However > it's probably best to leave that until after the (upcoming?) release. > Oh and whilst I'm thinking about it, is it okay if we mark the Xerces > and xml jars as exported resources otherwise extensions will have to > bundle it's own copy. > > Cheers, > dw > > >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] >> On Behalf Of Torsten Juergeleit >> Sent: 24 October 2004 22:23 >> To: Spring IDE Developer List >> Subject: [Springide-eclip-developer] Spring IDE Extensions - >> Search: Feedback >> >> Dave, >> >> the search facility of Spring IDE Extensions is very good. >> I have a few suggestions: >> >> 1. selecting "Search Again" in the search result page with a >> successful search adds duplicates to the list >> >> 2. selecting "Show In / Spring Beans" in the search result >> page for a node in the result tree view doesn't navigate to >> the corresponding node in the Spring Beans view >> >> For 2. BeanSearchResultPage has to implement IShowInSource >> and return in getShowInContext() an instance of ShowInContext >> which holds an input object of BeansViewLocation (prepared >> with project name, config name, bean name [if available] and >> property name [if available]) and a selection object of >> StructuredSelection (IResource of the selected node >> -> project or [config] file). The input object is recognized by Spring >> Beans view and the selection object i recognized by Eclipse's >> resource navigator or JDT's package explorer. >> >> For samples please refer to BeansView.getShowInContext() or >> the Beans UI action ShowInView.run(). >> >> Ups, to recognize the input object first instead of the >> selection (if provided both) I have to modify >> BeansView.show(). Ok, I will fix this now. You can find the >> fix in CVS head. >> >> Cheers, >> Torsten >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IT Product Guide on >> ITManagersJournal Use IT products in your business? Tell us >> what you think of them. Give us Your Opinions, Get Free >> ThinkGeek Gift Certificates! Click to find out more >> http://productguide.itmanagersjournal.com/guidepromo.tmpl >> _______________________________________________ >> Springide-eclip-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >> > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > |
|
From: Watkins, D. <dav...@fa...> - 2004-10-25 18:39:59
|
Hi Torsten, I've implemented suggestion 1 (a mistake on my behalf. For item 2 I'm actually using IBean's in the search result view. I tried adding the interface and method you suggested but they don't get called. Instead I've hacked another else clause onto the bottom of BeansView::show(...) which can construct a BeansViewLocation from an IBean. I haven't checked this in yet as I wanted to run it past you. =20 A potentially neater solution to this is to make BeansViewLocation an interface and make Bean into an IAdaptable class (I seem to remember we can do this by registering with an AdapterManager somewhere so we do't have to 'pollute' the bean class too much). Just a thought! Cheers, dw > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Torsten Juergeleit > Sent: 24 October 2004 22:23 > To: Spring IDE Developer List > Subject: [Springide-eclip-developer] Spring IDE Extensions -=20 > Search: Feedback >=20 > Dave, >=20 > the search facility of Spring IDE Extensions is very good. > I have a few suggestions: >=20 > 1. selecting "Search Again" in the search result page with a=20 > successful search adds duplicates to the list >=20 > 2. selecting "Show In / Spring Beans" in the search result=20 > page for a node in the result tree view doesn't navigate to=20 > the corresponding node in the Spring Beans view >=20 > For 2. BeanSearchResultPage has to implement IShowInSource=20 > and return in getShowInContext() an instance of ShowInContext=20 > which holds an input object of BeansViewLocation (prepared=20 > with project name, config name, bean name [if available] and=20 > property name [if available]) and a selection object of=20 > StructuredSelection (IResource of the selected node=20 > -> project or [config] file). The input object is recognized by Spring > Beans view and the selection object i recognized by Eclipse's=20 > resource navigator or JDT's package explorer. >=20 > For samples please refer to BeansView.getShowInContext() or=20 > the Beans UI action ShowInView.run(). >=20 > Ups, to recognize the input object first instead of the=20 > selection (if provided both) I have to modify=20 > BeansView.show(). Ok, I will fix this now. You can find the=20 > fix in CVS head. >=20 > Cheers, > Torsten >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on=20 > ITManagersJournal Use IT products in your business? Tell us=20 > what you think of them. Give us Your Opinions, Get Free=20 > ThinkGeek Gift Certificates! Click to find out more=20 > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >=20 |
|
From: Watkins, D. <dav...@fa...> - 2004-10-25 09:40:37
|
Thanks! I'll look at how to put those changes in. =20 I've also added a quick fix for property mismatches over the weekend... it only works by selecting the problem from the Problems view, haven't looked into whether I can modify ruler markers on an unspecified editor yet (i.e. we don't know what editor the user employs for editing spring files) - looking at the way the JDT quick fixes work I guess it's mission impossible as they don't work outside the Java Editor. =20 It also has a problem as it uses my XMLSearchReplacer (like the refactoring support) which has the side effect of writing out the optional DTD attributes (rather than leaving them blank) I'm currently looking at how to stop that from happening. Once that's sorted out I should be able to port the quick fix stuff over to the main feature/plugins as I don't think it's dependent on Eclipse 3.x However it's probably best to leave that until after the (upcoming?) release. Oh and whilst I'm thinking about it, is it okay if we mark the Xerces and xml jars as exported resources otherwise extensions will have to bundle it's own copy. Cheers, dw =20 > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Torsten Juergeleit > Sent: 24 October 2004 22:23 > To: Spring IDE Developer List > Subject: [Springide-eclip-developer] Spring IDE Extensions -=20 > Search: Feedback >=20 > Dave, >=20 > the search facility of Spring IDE Extensions is very good. > I have a few suggestions: >=20 > 1. selecting "Search Again" in the search result page with a=20 > successful search adds duplicates to the list >=20 > 2. selecting "Show In / Spring Beans" in the search result=20 > page for a node in the result tree view doesn't navigate to=20 > the corresponding node in the Spring Beans view >=20 > For 2. BeanSearchResultPage has to implement IShowInSource=20 > and return in getShowInContext() an instance of ShowInContext=20 > which holds an input object of BeansViewLocation (prepared=20 > with project name, config name, bean name [if available] and=20 > property name [if available]) and a selection object of=20 > StructuredSelection (IResource of the selected node=20 > -> project or [config] file). The input object is recognized by Spring > Beans view and the selection object i recognized by Eclipse's=20 > resource navigator or JDT's package explorer. >=20 > For samples please refer to BeansView.getShowInContext() or=20 > the Beans UI action ShowInView.run(). >=20 > Ups, to recognize the input object first instead of the=20 > selection (if provided both) I have to modify=20 > BeansView.show(). Ok, I will fix this now. You can find the=20 > fix in CVS head. >=20 > Cheers, > Torsten >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on=20 > ITManagersJournal Use IT products in your business? Tell us=20 > what you think of them. Give us Your Opinions, Get Free=20 > ThinkGeek Gift Certificates! Click to find out more=20 > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >=20 |
|
From: Torsten J. <tor...@on...> - 2004-10-24 21:23:03
|
Dave, the search facility of Spring IDE Extensions is very good. I have a few suggestions: 1. selecting "Search Again" in the search result page with a successful search adds duplicates to the list 2. selecting "Show In / Spring Beans" in the search result page for a node in the result tree view doesn't navigate to the corresponding node in the Spring Beans view For 2. BeanSearchResultPage has to implement IShowInSource and return in getShowInContext() an instance of ShowInContext which holds an input object of BeansViewLocation (prepared with project name, config name, bean name [if available] and property name [if available]) and a selection object of StructuredSelection (IResource of the selected node -> project or [config] file). The input object is recognized by Spring Beans view and the selection object i recognized by Eclipse's resource navigator or JDT's package explorer. For samples please refer to BeansView.getShowInContext() or the Beans UI action ShowInView.run(). Ups, to recognize the input object first instead of the selection (if provided both) I have to modify BeansView.show(). Ok, I will fix this now. You can find the fix in CVS head. Cheers, Torsten |
|
From: Torsten J. <tor...@on...> - 2004-10-22 23:19:14
|
Hi David, right back from holiday and starting with finding nasty bugs ;-) FileResource was terribly broken (no handling of non-existent files). Now it supports initialization with null and an instance of IFile which is non-existent. BeansConfig now handles non-existent config files too (the internal exception field is initialized with a "file not found" BeanDefinitionException). GraphEditorInput didn't handle non-existent config files too (fixed). Thanx for spotting this. The fixed version is available in CVS HEAD or on the update site (needs removal of former Spring IDE installation -> same feature / plugin version number). Cheers, Torsten On 22.10.2004, at 17:15, Watkins, David wrote: > Hi Torsten, > Sorry I've been a bit quiet recently - holiday then found a mountain of > work upon my return! Anyway I've just caught up on the latest code > from > HEAD and I've found a small problem. I can't imagine many people > running into it, however if you rename a registered config file the > internal model doesn't catch it as a problem and the Spring Beans > treeview chucks a NullPointerException. I've got a fix that gets round > the problem but you may have a better idea of how to fix it - the > classes in question are: BeansConfig and FileResource from core. > > I'll check in the fix now and continue looking at the new stuff (some > really nice improvements!). > > Cheers, > Dave W. > > > > >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] >> On Behalf Of Torsten Juergeleit >> Sent: 21 October 2004 22:57 >> To: Spring IDE Developer List >> Subject: Re: [Springide-eclip-developer] GEF crash >> >> Antranig, >> >>> I find a problem when trying to create the GEF graph that >> the entire >>> IDE crashes in a 100% CPU loop. >> >> So let's try to track this down: >> >> Which way did you create the graph (by selecting a config, a >> config set or a single bean)? >> Did this happen with configs of other Spring projects too? >> Is this bug related to complex Spring projects (external >> project references, a lot of beans, config sets with many >> beans, ...) only or are simple projects / config files affected too? >> >> Could you please close all Spring projects in the workspace, >> create a new Spring project with a single config file >> containing a single bean and open the graph of this simple config. >> >>> I also saw this problem in the release plugin when the beans >>> definitions file contained errors. This stopped happening when I >>> corrected them, but with the 19/10/04 release candidate it seems to >>> happen all the time. >> >> What do you mean by "errors"? If the XML is not well-formed >> or doesn't conform to Spring's DTD then the config file is >> not parsed and the corresponding confing node in the bean >> shows only a single node containing the parser's error >> message. Showing a graph on this config file or the dummy >> bean opens an empty graph editor. All the other errors are >> detected by Spring IDE's validator. These kind of errors >> don't have any impact on Spring IDE's beans view or graph >> editor because they are taking effect during runtime of the >> Spring application only (they causing configuration errors >> during initialization of the "real" BeanFactory). >> >>> I'm using: >>> Eclipse 3.0.0 >>> GEF 3.0.1 >>> JDK 1.4.2_04 >> >> Hhm, I'm not sure if it does matter but GEF 3.0.1 requires Eclipse >> 3.0.1 (as stated on GEF's download page). >> Could you please make an additional test by downgrading to GEF 3.0.0. >> Or install the GEF examples and run the Logic example plugin. >> Maybe it's a problem with GEF. >> >> Is anyone else running Eclipse 3.0 with GEF 3.0.1? I'm >> already on Eclipse 3.0.1. >> >> Cheers, >> Torsten >> >> >> On 21.10.2004, at 18:31, Antranig Basman wrote: >> >>> New plugin looks great, I'm very glad for anonymous beans support. >>> I find a problem when trying to create the GEF graph that >> the entire >>> IDE crashes in a 100% CPU loop. >>> I also saw this problem in the release plugin when the beans >>> definitions file contained errors. This stopped happening when I >>> corrected them, but with the 19/10/04 release candidate it seems to >>> happen all the time. >>> I'm using: >>> Eclipse 3.0.0 >>> GEF 3.0.1 >>> JDK 1.4.2_04 >>> >>> Any suggestions for how I can investigate the problem and file a >>> better bug report? >>> >>> Thanks, >>> Antranig. >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: IT Product Guide on >>> ITManagersJournal Use IT products in your business? Tell us >> what you >>> think of them. Give us Your Opinions, Get Free ThinkGeek Gift >>> Certificates! Click to find out more >>> http://productguide.itmanagersjournal.com/guidepromo.tmpl >>> _______________________________________________ >>> Springide-eclip-developer mailing list >>> Spr...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >>> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IT Product Guide on >> ITManagersJournal Use IT products in your business? Tell us >> what you think of them. Give us Your Opinions, Get Free >> ThinkGeek Gift Certificates! Click to find out more >> http://productguide.itmanagersjournal.com/guidepromo.tmpl >> _______________________________________________ >> Springide-eclip-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >> > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > |
|
From: Torsten J. <tor...@on...> - 2004-10-22 23:00:56
|
Assaf, thank you for spotting this. I totally missed the point that child beans are allowed to override the parent bean's class. Ok, fixed that. Now a bean's constructor arguments and properties are always validated against the class provided by the bean (regardless if it's a root or a child bean). For a child bean without a class the corresponding parent's class is used for validation. If no parent bean was found in the same config file then validation is skipped. There's no easy way to guess in which of the other config files the parent bean is defined. If you like then give the updated version which is available on the update site a try. But you have to removed the old version of Spring IDE first because the plugin's version number didn't change. You can delete the feature and all the plugins of Spring IDE from the installation directory manually or use Eclipse's update manager to remove and repair the installed version of Spring IDE. Cheers, Torsten On 22.10.2004, at 10:34, Assaf Urieli wrote: > Testing IDE update 1.1.0. > > I have the following two bean definitions: > <bean id="formulaireAbstrait" > class="com.joliciel.aplikaterm.web.FormulaireAbstrait" > abstract="true"> > <property name="localeResolver"><ref > local="localeResolver"/></property> > </bean> > <bean id="authentifier" > class="com.joliciel.aplikaterm.web.FormulaireAuthentifier" > parent="formulaireAbstrait"> > <property name="formView"><value>login</value></property> > <property name="successView"><value>accueil</value></property> > <property name="serviceUtilisateur"><ref > local="serviceUtilisateur"/></property> > </bean> > > I get the following complaint: > No setter for property "serviceUtilisateur" found in class > "com.joliciel.aplikaterm.web.FormulaireAbstrait" > While it is true that the parent (FormulaireAbstrait) has no such > property, the child (FormulaireAuthentifier) does have the property, > and actual Spring configuration works fine. > > So it looks like the IDE is only searching for properties on the > parent, not the child. > > Best regards, > Assaf > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > |
|
From: Watkins, D. <dav...@fa...> - 2004-10-22 15:15:25
|
Hi Torsten, Sorry I've been a bit quiet recently - holiday then found a mountain of work upon my return! Anyway I've just caught up on the latest code from HEAD and I've found a small problem. I can't imagine many people running into it, however if you rename a registered config file the internal model doesn't catch it as a problem and the Spring Beans treeview chucks a NullPointerException. I've got a fix that gets round the problem but you may have a better idea of how to fix it - the classes in question are: BeansConfig and FileResource from core. I'll check in the fix now and continue looking at the new stuff (some really nice improvements!). Cheers, Dave W. > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Torsten Juergeleit > Sent: 21 October 2004 22:57 > To: Spring IDE Developer List > Subject: Re: [Springide-eclip-developer] GEF crash >=20 > Antranig, >=20 > > I find a problem when trying to create the GEF graph that=20 > the entire=20 > > IDE crashes in a 100% CPU loop. >=20 > So let's try to track this down: >=20 > Which way did you create the graph (by selecting a config, a=20 > config set or a single bean)? > Did this happen with configs of other Spring projects too? > Is this bug related to complex Spring projects (external=20 > project references, a lot of beans, config sets with many=20 > beans, ...) only or are simple projects / config files affected too? >=20 > Could you please close all Spring projects in the workspace,=20 > create a new Spring project with a single config file=20 > containing a single bean and open the graph of this simple config. >=20 > > I also saw this problem in the release plugin when the beans=20 > > definitions file contained errors. This stopped happening when I=20 > > corrected them, but with the 19/10/04 release candidate it seems to=20 > > happen all the time. >=20 > What do you mean by "errors"? If the XML is not well-formed=20 > or doesn't conform to Spring's DTD then the config file is=20 > not parsed and the corresponding confing node in the bean=20 > shows only a single node containing the parser's error=20 > message. Showing a graph on this config file or the dummy=20 > bean opens an empty graph editor. All the other errors are=20 > detected by Spring IDE's validator. These kind of errors=20 > don't have any impact on Spring IDE's beans view or graph=20 > editor because they are taking effect during runtime of the=20 > Spring application only (they causing configuration errors=20 > during initialization of the "real" BeanFactory). >=20 > > I'm using: > > Eclipse 3.0.0 > > GEF 3.0.1 > > JDK 1.4.2_04 >=20 > Hhm, I'm not sure if it does matter but GEF 3.0.1 requires Eclipse > 3.0.1 (as stated on GEF's download page). > Could you please make an additional test by downgrading to GEF 3.0.0.=20 > Or install the GEF examples and run the Logic example plugin.=20 > Maybe it's a problem with GEF. >=20 > Is anyone else running Eclipse 3.0 with GEF 3.0.1? I'm=20 > already on Eclipse 3.0.1. >=20 > Cheers, > Torsten >=20 >=20 > On 21.10.2004, at 18:31, Antranig Basman wrote: >=20 > > New plugin looks great, I'm very glad for anonymous beans support. > > I find a problem when trying to create the GEF graph that=20 > the entire=20 > > IDE crashes in a 100% CPU loop. > > I also saw this problem in the release plugin when the beans=20 > > definitions file contained errors. This stopped happening when I=20 > > corrected them, but with the 19/10/04 release candidate it seems to=20 > > happen all the time. > > I'm using: > > Eclipse 3.0.0 > > GEF 3.0.1 > > JDK 1.4.2_04 > > > > Any suggestions for how I can investigate the problem and file a=20 > > better bug report? > > > > Thanks, > > Antranig. > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: IT Product Guide on=20 > > ITManagersJournal Use IT products in your business? Tell us=20 > what you=20 > > think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20 > > Certificates! Click to find out more=20 > > http://productguide.itmanagersjournal.com/guidepromo.tmpl > > _______________________________________________ > > Springide-eclip-developer mailing list=20 > > Spr...@li... > >=20 > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > > >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on=20 > ITManagersJournal Use IT products in your business? Tell us=20 > what you think of them. Give us Your Opinions, Get Free=20 > ThinkGeek Gift Certificates! Click to find out more=20 > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer >=20 |
|
From: Antranig B. <ant...@ca...> - 2004-10-22 14:47:52
|
> What do you mean by "errors"? If the XML is not well-formed or doesn"t > conform to Spring"s DTD then the config file is not parsed and the > corresponding confing node in the bean shows only a single node > containing the parser"s error message. Showing a graph on this config > file or the dummy bean opens an empty graph editor. All the other > errors are detected by Spring IDE"s validator. These kind of errors > don"t have any impact on Spring IDE"s beans view or graph editor > because they are taking effect during runtime of the Spring application > only (they causing configuration errors during initialization of the > "real" BeanFactory). The errors I had were Spring validation errors. It may simply have been coincidence that removing them corrected the problem (see below) > > I"m using: > > Eclipse 3.0.0 > > GEF 3.0.1 > > JDK 1.4.2_04 > > Hhm, I"m not sure if it does matter but GEF 3.0.1 requires Eclipse > 3.0.1 (as stated on GEF"s download page). > Could you please make an additional test by downgrading to GEF 3.0.0. > Or install the GEF examples and run the Logic example plugin. Maybe > it"s a problem with GEF. Many thanks, this has resolved the problem - graphs work fine now after downgrade to GEF 3.0.0. Great plugin! > Is anyone else running Eclipse 3.0 with GEF 3.0.1? I"m already on > Eclipse 3.0.1. Cheers, Antranig. |
|
From: Assaf U. <as...@jo...> - 2004-10-22 08:33:10
|
Testing IDE update 1.1.0.
I have the following two bean definitions:
<bean id="formulaireAbstrait"
class="com.joliciel.aplikaterm.web.FormulaireAbstrait" abstract="true">
<property name="localeResolver"><ref
local="localeResolver"/></property>
</bean>
<bean id="authentifier"
class="com.joliciel.aplikaterm.web.FormulaireAuthentifier"
parent="formulaireAbstrait">
<property name="formView"><value>login</value></property>
<property name="successView"><value>accueil</value></property>
<property name="serviceUtilisateur"><ref
local="serviceUtilisateur"/></property>
</bean>
I get the following complaint:
No setter for property "serviceUtilisateur" found in class
"com.joliciel.aplikaterm.web.FormulaireAbstrait"
While it is true that the parent (FormulaireAbstrait) has no such
property, the child (FormulaireAuthentifier) does have the property, and
actual Spring configuration works fine.
So it looks like the IDE is only searching for properties on the parent,
not the child.
Best regards,
Assaf
|
|
From: Torsten J. <tor...@on...> - 2004-10-21 21:57:24
|
Antranig, > I find a problem when trying to create the GEF graph that the entire > IDE crashes in a 100% CPU loop. So let's try to track this down: Which way did you create the graph (by selecting a config, a config set or a single bean)? Did this happen with configs of other Spring projects too? Is this bug related to complex Spring projects (external project references, a lot of beans, config sets with many beans, ...) only or are simple projects / config files affected too? Could you please close all Spring projects in the workspace, create a new Spring project with a single config file containing a single bean and open the graph of this simple config. > I also saw this problem in the release plugin when the beans > definitions file contained errors. This stopped happening when I > corrected them, but with the 19/10/04 release candidate it seems > to happen all the time. What do you mean by "errors"? If the XML is not well-formed or doesn't conform to Spring's DTD then the config file is not parsed and the corresponding confing node in the bean shows only a single node containing the parser's error message. Showing a graph on this config file or the dummy bean opens an empty graph editor. All the other errors are detected by Spring IDE's validator. These kind of errors don't have any impact on Spring IDE's beans view or graph editor because they are taking effect during runtime of the Spring application only (they causing configuration errors during initialization of the "real" BeanFactory). > I'm using: > Eclipse 3.0.0 > GEF 3.0.1 > JDK 1.4.2_04 Hhm, I'm not sure if it does matter but GEF 3.0.1 requires Eclipse 3.0.1 (as stated on GEF's download page). Could you please make an additional test by downgrading to GEF 3.0.0. Or install the GEF examples and run the Logic example plugin. Maybe it's a problem with GEF. Is anyone else running Eclipse 3.0 with GEF 3.0.1? I'm already on Eclipse 3.0.1. Cheers, Torsten On 21.10.2004, at 18:31, Antranig Basman wrote: > New plugin looks great, I'm very glad for anonymous beans support. > I find a problem when trying to create the GEF graph that the entire > IDE crashes in a 100% CPU loop. > I also saw this problem in the release plugin when the beans > definitions file contained errors. This stopped happening when I > corrected them, but with the 19/10/04 release candidate it seems > to happen all the time. > I'm using: > Eclipse 3.0.0 > GEF 3.0.1 > JDK 1.4.2_04 > > Any suggestions for how I can investigate the problem and file a > better bug report? > > Thanks, > Antranig. > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Springide-eclip-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer > |
|
From: Antranig B. <ant...@ca...> - 2004-10-21 16:32:32
|
New plugin looks great, I'm very glad for anonymous beans support. I find a problem when trying to create the GEF graph that the entire IDE crashes in a 100% CPU loop. I also saw this problem in the release plugin when the beans definitions file contained errors. This stopped happening when I corrected them, but with the 19/10/04 release candidate it seems to happen all the time. I'm using: Eclipse 3.0.0 GEF 3.0.1 JDK 1.4.2_04 Any suggestions for how I can investigate the problem and file a better bug report? Thanks, Antranig. |
|
From: Torsten J. <tor...@on...> - 2004-10-19 23:07:18
|
I fixed some glitches in the last "final relase" (let's call it "release candidate" now :-): - double-clicking on a property or constructor argument in the BeansView didn't work (start line wasn't set during initialization of BeanNode) - dummy BeanNodes used for displaying error messages in the BeansView wasn't detected (NPE while accessing wrapped core model IBean) - accessing the properties of external BeanNodes / Properties / ConstructorArgument of a ConfigSet in the BeansView opened the properties of the external Spring project instead the one the ConfigSet belongs to CVS head and the update site are up-to-date... Maybe you can give the new version a try. Cheers, Torsten |
|
From: Torsten J. <tor...@on...> - 2004-10-18 20:57:50
|
I did some refactorings, mainly replacing redundant local data from the
internal models of the ui and graph plugin with a reference to the
corresponding element of the core's model. So the UI's property sources
are reusable because they depend on the core plugin's model only.
To reduce coupling of the graph to the ui plugin GraphEditorInput
encapsulates all the code which depends on the ui plugin.
For navigating to a specific node in the BeansView the new type
BeansViewLocation was introduced. By using this type any plugin is able
to select a node within the BeansView, e.g.
BeansViewLocation location = new BeansViewLocation();
location.setProjectName("myproject");
location.setConfigName("myconfig");
location.setBeanName("mybean");
location.setPropertyName("myproperty");
location.show();
Finally a new context menu entry (Open Bean Class) was added to the
bean nodes within the BeansView.
I updated the feature available on the Spring IDE update site.
Maybe you can give it a try.
Hopefully we can release the new version of Spring IDE this week?!?
Any feedback appreciated...
Cheers,
Torsten
|
|
From: Loren R. <lor...@ya...> - 2004-10-15 16:22:24
|
Actually, I *have* taken some time off, and expect to get back to work on spring-ide next week. --- Torsten Juergeleit <tor...@on...> wrote: > Are we ready to release version 1.1.0 of Spring IDE? > > Btw. the list is so silent. Is everybody on > vacation? Or is the list > server not working? > > Cheers, > Torsten? > > |
1 message has been excluded from this view by a project administrator.
