[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7116: ------------------------------------------- Hi Jeff, I'm looking into this now. In the meantime, try importing the XSD directly into the BPEL process: 1. in the BPEL editor, click on the process canvas, then select the "Imports" tab in the Property Sheet 2. click "Import an XSD..." at the top-left (you may have to scroll the view to get to it) 3. select the policyQuote.xsd You should now be able to see the structure of the receivePolicyQuoteRequest complex type. I agree with you though, the BPEL editor should recursively import all XSDs that are imported by WSDLs -- 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

[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-7116: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 3.2.0.Beta2 -- 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

[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7116: ------------------------------------------- Hi Jeff, After staring at this for several hours I finally realized that the import location is specified as "../schema/*.xsd" - it should be "schema/*.xsd" because the "schema" folder is at the same level as the WSDLs that import the schemas. Now at least the editor recognizes the message types but I'm getting a strange partnerlink "mismatch" in the receive activity. Can you have a look at this? -- 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

[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7116: ------------------------------------------- Good news everyone! At least the phantom error messages problem can be easily reproduced: 1. import the project attached to this JIRA (PolicyQuoteProcessService.zip) 2. open PolicyQuoteProcess.bpel 3. from main menu click "Search->File" and enter "../schema" for the search text 4. in the Search results View, right-click and "Replace all..." and enter "schema" for the replacement text 5. voila! There are 5 errors reported: Description Resource Path Location Type <bpel:receive> activity "ReceivePolicyQuote" specifies a portType "ors:PolicyQuoteProcessService", yet this portType does not match the portType derived from "myRole" of partnerLink "PolicyQuoteProcessService" defined in WSDL "platform:/resource/PolicyQuoteProcessService/bpelContent/PolicyQuoteProcessService1.wsdl" PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 55 BPEL Validation Marker Referenced file contains errors (file:////home/bbrodt/eclipse-3.6-jboss/runtime-jboss-bpel-editor/org.sample.order/bpelContent/order.xsd). For more information, right click on the message in the Problems View and select "Show Details..." orderArtifacts.wsdl /org.sample.order/bpelContent line 1 WSDL Problem The part 'payload' has an invalid value 'orderRequest' defined for its element. Element declarations must refer to valid values defined in a schema. orderArtifacts.wsdl /org.sample.order/bpelContent line 32 WSDL Problem The part 'payload' has an invalid value 'orderResponse' defined for its element. Element declarations must refer to valid values defined in a schema. orderArtifacts.wsdl /org.sample.order/bpelContent line 36 WSDL Problem variable "PolicyQuoteRequest" of type "<wsdl:message "receivePolicyQuoteRequest">" is not compatible with WSDL message "<wsdl:message "receivePolicyQuoteRequest">". PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 55 BPEL Validation Marker -- 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

[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7116: ------------------------------------------- Hi Jeff, I have (finally!) figured out the cause of the erroneous validation errors being reported by the BPEL editor: it has to do with the order in which the imported WSDLs are resolved, and the fact that the validator is comparing the model Object instances when testing for compatible types - it should be comparing the Object contents instead (this is the same issue with string comparison in Java, i.e. string1 == string2 does not mean the same thing as string1.equals(string2)) You can see the effect of this in the project attached to this JIRA; try this: 1. fix the schema location problems as described previously (replace "../schema" with "schema" in all of the WSDLs) 2. in PolicyQuoteProcess.bpel, reverse the order of these two import elements (in other words, PolicyQuoteProcessService1.wsdl should appear AFTER PolicyQuoteProcessArtifacts.wsdl): <bpel:import namespace="http://www.pi4soa.org/PolicyQuote" location="PolicyQuoteProcessService1.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:impo... <bpel:import namespace="http://eclipse.org/bpel/sampleArtifacts" location="PolicyQuoteProcessArtifacts.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"></bpel:impo... 3. save the editor and you should see at least one of the error messages disappear, specifically the one about variable "PolicyQuoteRequest" is incompatible with message type. This is because PolicyQuoteProcessArtifacts.wsdl ALSO imports PolicyQuoteProcessService1.wsdl, before it is imported by the BPEL file. The result is that the java Object which represents the message corresponding to the PolicyQuoteProcessService port type is DIFFERENT from the Object that represents the BPEL variable's message, even though they are one and the same message type. This explains a lot of the "odd behavior" that the editor is exhibiting, but it does not (in this case) explain why the problem goes away when you restart the eclipse workbench. I'm hoping that changing the validation code to look at the contents of the two Objects being compared will fix this problem (although there may be other places in the editor where this is still an issue). This should also fix the compatibility type checking in <assign> (i.e. <from> and <to> type incompatibility being incorrectly reported if the source and target parts are in different message types). -- 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

[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7116: ------------------------------------------- Added <import> location checking because missing XSD imports are not reported by the WSDL validator. -- 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

[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Pavol Srna commented on JBIDE-7116: ----------------------------------- It seems ok, but I am not sure how to correctly verify this. Bob, can you please verify and close it if it is ok? Thanks. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7116?page=com.atlassian.jira.plugin.s... ] Pavol Srna closed JBIDE-7116. ----------------------------- verified (jbdevstudio-eap-linux-gtk-4.0.0.v201012070137R-H33-Beta2 + BPEL) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira