[wtp-dev] XML/SSE improvements

["Max Rydahl Andersen" <max.andersen@xxxxxxxxx>]

Hi,

(Not sure if this is best in the newsgroup or here, but just kick me if  
its better for the newsgroup)

I'm in the grey zone at the moment since I have to figure out when I want  
to move
my plugin code from WTP 0.7 to WTP 1.0.

As it stands I can see that the StructuredXMLEditor's api have been made  
more public and that is good.
The question is - is that API considered stable at the moment ? Mainly if  
the extension points name
and semantics are in place ? (api changes are easy to catch by the  
compiler, but the xml in plugin.xml does
not complain if the extension point doesnt exist so damn hard to track  
down ;)

Another thing is the quality of the code completion in XML (see  
https://bugs.eclipse.org/bugs/show_bug.cgi?id=89811)
which basically makes it very hard to create a valid xml file when writing  
the code by hand; and that does not
need to be the case but as far as I can see in the WTP code I can't easily  
customize the code completion rules
for XML yet. e.g. I need to order the inserts by relevance (or even remove  
non-valid xml).

My question is if work have been done in this area with respect to WTP 1.0  
so I can actually get a real benefit
from upgrading to WTP 1.0 ? (I don't need all the functionallity, just the  
possibility to order the proposals
by validity and add required attributes/tag automatically to the inserted  
text - and hopefully without using
internal API)

thanks
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
max@xxxxxxxxxxxxx
http://hibernate.org

JBoss Inc
max.andersen@xxxxxxxxx