Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 95317

Summary:	Files associations are recognized but not used
Product:	[WebTools] WTP Source Editing	Reporter:	Victor Toni <victor.toni>
Component:	wst.xml	Assignee:	wst.xml <wst.xml-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	minor
Priority:	P3	CC:	david_williams, eclipse, eclipse, for.work.things, gsmith, thatnitind
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Victor Toni

2005-05-15 12:30:52 EDT

1) I created a files association for "*.xsl" with "XML Source Page Editor".
2) "Open With" shows "XML Source Page Editor" as default.
3) Opening a "*.xsl" file gives a simple text editor.
4) I had to create an entry in "Content Types" for "*.xsl" to be recognized as XML.
5) Opening a "*.xsl" file gives the XML editor.

IMO step 4) is counterintuitive (especially because of 2).

I am using:
 - Eclipse 3.1M7
 - wtp-wst-sdk-1.0M4.zip
 - JEM-SDK-I20050415.zip
 - GEF-SDK-I20050503.zip
 - emf-sdo-xsd-SDK-I200505050300.zip

Comment 1 Amy Wu

2005-05-16 11:54:30 EDT

Basically what's happenning is if you only associate xsl with the xml source 
page editor, the xml source page editor will open xsl files, but it won't know 
what to do with the content (content assist, highlighting, etc)  Once you 
associate xsl with the xml content type, the xml source page editor, knows 
what to do with xml content, so it can then provide xml function.

If your issue is with the preference pages, you should check out bug 91965  
That bug is about making the file associates and content types preference 
pages make more sense.

Comment 2 Victor Toni

2005-05-16 12:20:03 EDT

I checked my last 3.1M6 installation and it had no "content type" preference.
So maybe this bug can be closed due to changes in the 3.1M7 milestone.

Comment 3 Kim Horne

2005-05-16 12:29:45 EDT

As it is, if a file can be resolved to a content type then the content type editor will always be used even if 
there are other editors associated by traditional filename/file extension bindings.

Comment 4 David Williams

2005-05-17 02:48:17 EDT

*** Bug 95227 has been marked as a duplicate of this bug. ***

Comment 5 David Williams

2005-05-17 02:56:01 EDT

I think this should be treated as a dup of 91965, if I'm misunderstanding, feel
free to reopen. 

*** This bug has been marked as a duplicate of 91965 ***

Comment 6 Victor Toni

2005-05-17 03:18:35 EDT

Fine. I signed it to WST because I didn't know about the new content type dialog.

Comment 7 David Williams

2005-07-25 11:43:39 EDT

Marking as verified as I know this issue is fixed (or correctly categorized).
If, as originator, you disagree or still see, please re-open, or open a new bug. 

Thanks very much for reporting and helping make WTP better.

Comment 8 Nitin Dahyabhai

2005-08-26 05:57:55 EDT

Closing