|
From: Colin S. <col...@ex...> - 2003-09-03 17:32:24
|
rod...@in... wrote: >>Sounds sort of useful, although unless I am misunderstanding >> >> >how this >would work, it would not be useful for a lot of beans since >you can use >a lot of beans without setting all properties, relying on >defaults, etc. > >Exactly, which is why I intend to leave the default as is. >PicoContainer's approach seems to ignore the value of >defaults (although they have just added support for multiple >constructors, which may permit them). > >A tool would be great. I suffer from occasional typo trouble >too. Apparently IDEA users don't when they refactor because >it's smart enough to offer to update XML in the project as >well. > > For the record Eclipse also will change names in text and other files if you tell it to, so refactoring is not normally the issue for me. I am somewhat of a sloppy typist though, and do sometimes make errors on the initial input, those errors being caught only when I actually try to run the stuff. >I would love to see tool support for Spring. Such as >- Eclipse plugin >- Swing GUI editor >- XSLT that can generate nice documentation from an XML bean >definition file >- any other good suggestions? > > Although a full plugin that validates the whole file would be useful, now that I think of it, what is needed as a first easy step (in Eclipse, and every IDE) and would be very useful for Spring and any other kind of reflexive java programming is a fast one keycombo function to check the string constant you are in for validity as a java class or interface name. I will post an Eclipse feature request for this... This would be of help in using so many projects/libs... |