Status: Resolved (View Workflow)
Affects Version/s: None
Fix Version/s: None
Similar Issues:Show 10 results
JBIDE-4460 the org.eclipse.swt.swtexception:Invalid Thread access when choose a wsdl file in the import wsdl wizard JBIDE-7116 BPEL Editor not seeing message structure when imported into WSDL JBIDE-11964 Wrong name of the imported WSDL into BPEL project using 'Import' wizard JBIDE-18316 Errors in project after import WildFly quickstarts (bundled XSD) JBIDE-4173 Parse XSD file to create "structured data model" JBIDE-4953 can't load a wsdl file from a url JBIDE-7478 BPEL validator marks missing WSDL imports only as warnings. JBIDE-11965 Cannot import a wsdl file generated by JBoss ESB into BPEL project JBIDE-3732 It should be possible to use XSD to describe the XML used as source or target JBIDE-8087 Incorrect imports in artifacts WSDL
Open a bpel file, click on the blank of the editor
In the properties view, choose the Imports Tab
Click the Import an XSD button, a wizard open. On the Resource wizard page, you can get all the wsdl and xsd file in the eclipse workspace.
We should fiter the xsd and wsdl file. When click Import an XSD, only show xsd file. And when click Import a wsdl, only show wsdl file.
And When you click Import type=File, regardless you click Import an XSD OR Import a WSDL button, the file browse wizard both show the
xsd files as the default.