Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315312 - Content type for completion proposal automatically set to short instead of full id
Summary: Content type for completion proposal automatically set to short instead of fu...
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.sse (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.3 M1   Edit
Assignee: Nitin Dahyabhai CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-01 17:28 EDT by filip.kis CLA
Modified: 2010-07-31 02:10 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description filip.kis CLA 2010-06-01 17:28:32 EDT
Build Identifier: 20100527-0614

When setting the content type property of proposal computer and using the plugin editor to find the content type it sets the value to the short id instead of full id which then makes the extension not work. Example:

Instead of 

<contentType id="org.eclipse.wst.html.core.htmlsource">

it's just set to

<contentType id="htmlsource">

Reproducible: Always

Steps to Reproduce:
1. Create new plugin project
2. Through plugin editor add org.eclipse.wst.sse.ui.completionProposal
3. Add some content type to the extension (htmlsource is easy to test)
4. Add a class providing the extension and just put a break point in the begining of computeCompletionProposals()
5. Run the plugin in debug mode and triger content assist in a html page, if the breakpoint is not triggered the issue is valid
Comment 1 Nitin Dahyabhai CLA 2010-07-21 23:31:09 EDT
We can, and should, now use a fully qualified ID value when declaring our content types.
Comment 2 Nitin Dahyabhai CLA 2010-07-31 02:10:01 EDT
Fixed in M1 for JS, XML, XSD, HTML, DTD, CSS, and JSP-contributed content types.