[#IDE-573] Support for http//www.springframework.org/schema/tool

Spring IDE

Support for http//www.springframework.org/schema/tool

Created: 04/May/07 03:30 PM Updated: 11/Jan/08 06:25 PM

Component/s:

beans.ui.editor

Affects Version/s:

2.0 M3

Fix Version/s:

2.0.3

Time Tracking:

Not Specified

File Attachments:

mylyn-context.zip (99 kB)

Description

« Hide

There is the http//www.springframework.org/schema/tool namespace with tags for annotating schema elements for custom namespaces with meta information. This information can cover about 80% of typical cases needed for namespace tooling like completion and navigation of custom tags, without authoring non-trivial custom IDE plugin.
Enhance Spring IDE to support http//www.springframework.org/schema/tool xsd annotations

All

Comments

Work Log

Change History

FishEye

Builds

Sort Order:

[ Permlink | « Hide ]

Eugene Lucash <lucash@easysoft.com.ua> added a comment - 04/May/07 03:50 PM

Short TODO
1. Recognize xml elements of types extending beans:identifiedType as Bean definition
and discover bean type and name based on tool:exports element (handle "type" and "identifier" attributes of tool:exports element)
2. Provide completion and navigation to xml annotated with tool:expected-type to spring beans definitions visible to config set.
3. Java Types completion and navigation to xml annotated with tool:expected-type=java.lang.Class and use tool:assignable-to to narrow proposals

[ Permlink | « Hide ]

Eugene Lucash added a comment - 11/Jan/08 04:13 PM

Please provide brief list (or link to) of supported completion and navigation of custom tags based on theirs annotated schema types.

[ Permlink | « Hide ]

Christian Dupuis added a comment - 11/Jan/08 06:24 PM - edited

Yes, sure. I want to put that into a blog post but until that is done I'll put it here:

The beans.core will now detect tool:exports annotations on custom namespaces if no "real" NamespaceHandler for the custom namespace can be found in the running Eclipse plug-in space. That might be case for pretty much every custom namespace. The auto-detected beans will show up in the Spring Explorer (disable the Spring Infrastructure Beans filter in the viewer's properties).
The beans.ui.editor has support for doing content assist and hyperlinking on the elements that have the following annotations:
- <tool:annotation kind="ref" /> - bean reference content assist and hyperlink
- <tool:annotation><tool:expected-type type="java.lang.Class" /></tool:annotation> - class or interface content assist and hyperlink
- <tool:annotation><tool:expected-type type="java.lang.Class" /><tool:assignable-to type="foo.Bar" /></tool:annotation> - class or interface content assist and hyperlink filtered of implementations and subtypes of foo.Bar.

The only outstanding feature that has not being implemented yet is the filtering of bean reference content assist proposals based on the bean property type. That will be covered in ~~IDE-784~~ because that is a general requirement and not specific to the tool namespace.

I'm also planning to add more tool:annotations into the tool namespace of Spring Core to provide a broader range of use cases. E.g. a way to describe possible methods that are allowed for a certain attribute.