Bug 164617 - [editor][outline] Support imports of files with extensions other than wsdl or xsd
Summary: [editor][outline] Support imports of files with extensions other than wsdl or...
Status: NEW
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-11-15 05:45 EST by Michael Möhler CLA
Modified: 2010-07-20 11:35 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Möhler CLA 2006-11-15 05:45:41 EST 
Despite registered content types it isn't possible 
to import corresponding files via the Outline of the WSDL editor.

The different content types where registered as follows in the corresponding pluging.xml

   ...
   
   <extension point="org.eclipse.core.runtime.contentTypes">
      <content-type priority="high"
                    name="SOPware Service Description"
                    id="org.sopware.content.type.sdx"
                    base-type="org.eclipse.wst.wsdl.wsdlsource"
                    default-charset="UTF-8"
                    file-extensions="sdx" />
      <content-type priority="high"
                    name="SOPware Service Provider Description"
                    id="org.sopware.content.type.spdx"
                    base-type="org.eclipse.wst.wsdl.wsdlsource"
                    default-charset="UTF-8"
                    file-extensions="spdx" />
   </extension>
   
   ...

Similar faults: 143734; 154850
Comment 1 Valentin Baciu CLA 2007-01-08 13:03:40 EST 
Rich, it seems the import location selection dialog uses an file extension based filter to only display *.wsdl and *.xsd workspace resources. We could probably change it to allow all extensions registered for the WSDL content type and any derived content types. It would be also interesting to know whether the model will properly load these new files. If not, we may need to do some tricks with the EMF resource set used by the editor.
Comment 2 Craig Salter CLA 2007-01-08 13:16:41 EST 
Yep currently EMF doesn't support any notion of content type, so if we wanted to support additional file extensions we'd need to be careful that our model related code doesn't barf (we'd need to make sure imports/includes of other file extensions work too).
Comment 3 Valentin Baciu CLA 2008-11-12 17:00:48 EST 
EMF now supports content types so we may want to look into this sometime in the future.