[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7116) BPEL Editor not seeing message structure when imported into WSDL

[Jeff DeLong (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12554418#action_12554418 ] 

Jeff DeLong commented on JBIDE-7116:
------------------------------------

This explains why I no longer see these issues. Gary fixed Savara wsdl generation to generate a single WSDL file, and I changed the example to use this, and the exceptions went away. Now there is only PolicyQuoteProcessSerivce.wsdl and PolicyQuoteProcessArtifacts.wsdl, although the Artifacts is still last (I will switch the order to see if other deployment exceptions go away).


   <bpel:import namespace="http://soa.jboss.org/EntityServices" location="PolicyQuoteEntityService.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:import>
    <bpel:import namespace="http://soa.jboss.org/TaskServices" location="PolicyQuoteCalculationService.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:import>
    <bpel:import namespace="http://dmv.com/" location="DrivingRecordWSService.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:import>
    <bpel:import namespace="http://creditagency.com/" location="CreditCheckWSService.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:import>
    <bpel:import namespace="http://www.example.org/policyQuoteProcessService" location="PolicyQuoteProcessService.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:import>
    <bpel:import namespace="http://eclipse.org/bpel/sampleArtifacts" location="PolicyQuoteProcessArtifacts.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:import>


> BPEL Editor not seeing message structure when imported into WSDL
> ----------------------------------------------------------------
>
>                 Key: JBIDE-7116
>                 URL: https://jira.jboss.org/browse/JBIDE-7116
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpel
>    Affects Versions: 3.2.0.M2
>         Environment: JBTools3.2Beta1 Eclipse 3.6 on Mac
>            Reporter: Jeff DeLong
>            Assignee: Robert (Bob) Brodt
>             Fix For: 3.2.0.Beta2
>
>         Attachments: PolicyQuoteProcessService.zip, Variables.tiff
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have a WSDL generated from Savara. It looks like this:
>  <wsdl:definitions name="PolicyQuoteProcessService" targetNamespace="http://www.pi4soa.org/PolicyQuote" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://www.pi4soa.org/PolicyQuote" xmlns:pcs="http://www.example.org/policyQuoteCalculationService" xmlns:pol="http://www.example.org/policyQuote" xmlns:pes="http://www.example.org/policyQuoteEntityService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cred="http://creditagency.com/creditCheck" xmlns:pps="http://www.example.org/policyQuoteProcessService" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:dmv="http://dmv.com/drivingRecord">
>     <types xmlns="http://schemas.xmlsoap.org/wsdl/">
>          <schema xmlns="http://www.w3.org/2001/XMLSchema">
>              <import namespace="http://www.example.org/policyQuote" schemaLocation="../schema/policyQuote.xsd"/>
>              <import namespace="http://creditagency.com/creditCheck" schemaLocation="../schema/creditCheck.xsd"/>
>              <import namespace="http://dmv.com/drivingRecord" schemaLocation="../schema/drivingRecord.xsd"/>
>          </schema>
>      </types>
>    <wsdl:message name="receivePolicyQuoteRequest">
>      <wsdl:part name="content" element="pol:policyQuote">
>      </wsdl:part>
>    </wsdl:message>
>  ...
> Where policyQuote schema is imported. When I create a Variable in the BPEL Editor, it does not see the structure of the message. This is a big problem, since with out the message details it is impossible to do Assign / Copy. I will attach the project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira