Community
Participate
Working Groups
Build ID: 20081113203138 Steps To Reproduce: The 'computeCompletionProposals(int documentPosition, String matchString, ITextRegion completionRegion, IDOMNode treeNode, IDOMNode xmlnode)' method in 'org.eclipse.wst.xml.ui.internal.contentassist.AbstractContentAssistProcessor' class does not handle the case where 'xmlnode.getNodeType() == Node.PROCESSING_INSTRUCTION_NODE' . More information: 1.Open the ejb-j2ee-engine.xml file in the XML editor. Switch to the source tab. 2.Put the cursor in the "<?xml version="1.0" encoding="UTF-8"?>" line and try to call the content assist. Thus the 'computeCompletionProposals(int documentPosition, String matchString, ITextRegion completionRegion, IDOMNode treeNode, IDOMNode xmlnode)' method in 'org.eclipse.wst.xml.ui.internal.contentassist.AbstractContentAssistProcessor' class is called with 'xmlnode' parameter -> Node.PROCESSING_INSTRUCTION_NODE.
Georgi, you haven't said what was expected and what is happening instead.
The content assist has changed since Bug 258999. AbstractContentAssistProcessor has been depreciated. But there is still no content assist offered in Node.PROCESSING_INSTRUCTION_NODE. This would be handled now in XMLTagsCompletionProposalComputer. But the question still stands, what options would we offer?
Sounds more like an enhancement to support content assist in the XML declaration. If not, please let us know, and we can adjust. Thanks.