This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Using nb6.1 i only get code-completion on the first element in the xml editor. My xml file seems to declare the schema correctly: <modes xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="modes.xsd"> <mode id="default-empty-mode" executor="parallel" analysis="false"> </mode> <mode id="default-mode" executor="parallel" analysis="false"> <command ... The schema is loaded correctly as i get code-completion w/ all the xsd documentation in <|mode But i get "no suggestions" for attributes on the <mode> element and if i put the cursor in <|command or any other child element of <mode>. Funny enough i also get "no suggestions" in </modes but i do get code- completion and documentation on attributes for <modes>. The mode.xsd seems correct since manual xml validation works ok. My modes.xml: http://sesat.no/svn/sesat-kernel/trunk/generic.sesam/war/src/main/conf/modes.xml My modes.xsd: http://sesat.no/tmp/modes.xsd
Let me investigate.
*** Issue 132452 has been marked as a duplicate of this issue. ***
Fix integrated: http://hg.netbeans.org/main/rev/2fc7dc80305e. If you cannot wait for the fix, please use the attached jar file; copy it to <NBHOME>/ide9/modules. As per iteam, marking this as a patch1 candidate. This fix will be delivered as a patch on top of NB6.1.
Created attachment 59945 [details] jar file
works a charm.thanks samaresh for a quick fix!
I've backported the changeset http://hg.netbeans.org/main/rev/2fc7dc80305e into release61_fixes repository as http://hg.netbeans.org/release61_fixes/rev/eb186baf479d changeset: 77487:eb186baf479d tag: tip user: samaresh@netbeans.org date: Wed Apr 09 21:42:49 2008 -0500 summary: Issue 132420: XML code-completion only works on first element.
There is a problem to update org.netbeans.modules.xml.schema.completion.nbm from UC. The fix delivery has been moved to patch2.
I don't see this as fixed in Patch 2.
I tested again, looks like I didn't have correct setup of patch2 installation. This *IS* working in patch 2.