cornercorner
FeaturesPluginsDocs & SupportCommunityPartners

SpringSupportIssues65

Issues in the Spring Framework support in NetBeans 6.5

Functional issues

  • should rather use the commons-logging.jar library already in NetBeans (issue 131117).
  • Upgrade bundled Spring libraries to 2.5.1?
  • We could. The only problem is that we have an OSR running for 2.5 and I'm not sure it covers 2.5.1 too. I'll check.
  • OSRs cover minor release versions as well. IMO should not be an issue.
  • Bundle api docs for Spring MVC jar (and perhaps spring.jar as well)?
  • Too large to be practical for the Basic IDE. Instead, perhaps we should devise a scheme to download the Spring library instead of bundling it.

Implementation issues

  • (P1) Code completion should have unit tests.
  • (P1) The COmpletionManager class has become too big. Each its nested class should be put in a separate top-level class - Done .
  • (P1) Performance of Java code completion could be improved (issue 130989) - Done .
  • (P2) Provide code completion for bean names (based on it's implementation class' simple name)
  • (P2) Should remove NodeBasedSpringBean and MutableSpringBean and remove then with calls into the model.
  • (P2) SpringXMLConfigHyperlinkProvider should not make assumption about the calling order of HP methods - Done .
  • (P1) SpringXMLConfigEditorUtils is doing too much, it should be split into separate classes - Done .
  • (P1) Current code mostly works with simple names instead of qualified names. Since Spring config files make heavy use of namespaces, proper namespace support needs to be implemented.
  • (P2) Model needs to allow to find beans by offset.
  • (P2) Model needs to take <alias> tags into account - Done .
  • (P2) Model needs to provide information about <constructor-arg> children of a bean along with their attributes. This is necessary to disambiguate between overloaded factory methods.
  • (P1) Currently, if a file is in multiple config file groups, models for these groups will create separate models for the file instead of sharing a single model.
  • (P2) Spring MVC support should only use FreeMarker for all text replacement operations in templates (issue 128437).
  • (P3) Spring Beans Context File visible in Template Manager, but Open in Editor is disabled for it.
  • (P3) Currently, the code is littered with string constants of tag and attribute names. Collect all of these and put them in one place, eg. SpringXMLTags.BEANS and SpringXMLAttributes.CLASS - Done
  • (P3) Add code completion for bean tag's primary attribute - Done