[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Jeff DeLong commented on JBIDE-5027: ------------------------------------ This situation (not seeing the operations) will go for a while, until some seemingly unrelated change to the file will result in error messages being generated about the PartnerLInk, e.g., Description Resource Path Location Type "portType" is set to "StorePT" on this <bpel:reply> activity but it cannot be resolved (check value of "portType", imports, WSDLs or XSDs). PurchaseGoodsProcess_Store.bpel /StoreProcess/bpel line 69 BPEL Validation Marker Will attach project archive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-5027: ---------------------------------- Hi Jeff, Import your project into my eclipse, there are some errors in the project: 1 the porttype name should be StorePT and CreditAgencyPT, not Store and CreditAgency in the PurchaseGoodsProcess_StoreArtifacts.wsdl 2 in the catch element, the reply should choose a operation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-5027: ---------------------------------- If you want to get the error message in the Problem view, you can clear the project. For now, only when compile the project, we will reload the validate module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Jeff DeLong commented on JBIDE-5027: ------------------------------------ Grid, Thanks for looking at this, and pointing out the problem in the PurchaseGoodsProcess_StoreArtifacts.wsdl. So what happened here (and can happen quite easily to others) is as follows: 1) User has Store.wsdl and CreditAgency.wsdl. User creates PartnerLinks and in doing so creates PartnerLinkTypes. PartnerLinkTypes are defined in PurchaseGoodsProcess_StoreArtifacts.wsdl. User uses these PartnerLinks in receive, invoke, and reply activities. 2) User modifies Store.wsdl and / or CredityAgency.wsdl. e.g. they change the name of the PortType. This does not immediately show up in bpel process as an error. 3) At some point later the user notices that the operations no longer show up in the PartnerLink. User tries to fix by deleting PartnerLink and recreating it. However unless they delete the PartnerLInkType as well, they will still have errors. However the errors will not reference the PurchaseGoodsProcess_StoreArtifacts.wsdl file, even though this is the file with the incorrect PortType names. Would it be possible for changes in a wsdl file to be immediately detected by the bpel validator? Could the generated processnameArtifacts.wsdl be automatically updated without the user having to delete the PartnerLink and PartnerLInkType and recreate them (or hand edit the Artifacts file). Thanks, Jeff -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-5027: ---------------------------------- Would it be possible for changes in a wsdl file to be immediately detected by the bpel validator? Denny will answer this question. Could the generated processnameArtifacts.wsdl be automatically updated without the user having to delete the PartnerLink and PartnerLInkType and recreate them (or hand edit the Artifacts file). I think it is a bit difficult to do. We just need to notify user the error, not need to change something automatically. Description Resource Path Location Type <bpel:invoke> activity "CheckCredit" specifies a portType "cag:CreditAgencyPT", yet this portType does not match the portType derived from "partnerRole" of partnerLink "StoreToCreditAgency" defined in WSDL "platform:/resource/StoreProcess/bpel/CreditAgency.wsdl" PurchaseGoodsProcess_Store.bpel /StoreProcess/bpel line 77 BPEL Validation Marker What did you do? I can not get the error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Jeff DeLong commented on JBIDE-5027: ------------------------------------ In testing out changing the WSDL I find the following: 1) Adding elements to the message. In this case changes to the WSDL file are immediately reflected in: - PartnerLink Details Operations - Variables 2) Changing the names of elements in the message. In this case changes to the WSDL file are immediately reflected in: - PartnerLink Details Operations - Variables However, if the original element whose name is changed is used in either copy statements or variable definitions, the XPATH statements in either case will not be updated, and errors will be generated the next time the BPEL file is updated or the Project cleaned. 3) Changing the name of the PortType. This will not change the name of the PortType in the associated Artifacts.wsdl, and errors will be generated the next time the BPEL file is updated or the Project cleaned. If possible, it would be very useful if ALL changes to an associated WSDL could be propagated throughout the bpel file and the associated Artifacts.wsdl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-5027: ---------------------------------- Hi Jeff, the Partner link type of the bpel file is referenced from wsdl file. So it is wsdl editor issue. If we want to fix it, we need to fix it on eclipe side. And I check this in the bugzilla of eclipse, found two years ago, there was someone that created a bug for this, but no one fix it. https://bugs.eclipse.org/bugs/show_bug.cgi?id=202929 I have added my comment on this bug, don't know if there is someone that will answer the question. Grid -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian reassigned JBIDE-5027: -------------------------------- Assignee: Feng Qian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian updated JBIDE-5027: ----------------------------- Fix Version/s: LATER -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian updated JBIDE-5027: ----------------------------- Issue Type: Feature Request (was: Bug) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Feng Qian commented on JBIDE-5027: ---------------------------------- Brian, the WTP changes for this issue, some are done and added into their coded-base. But some still are not fixed in this realease for now. Up to now, we can add a partnerlink, property, proerty alias, and validate them. But because these not-fixed issues, we can not refactor the portype name change in the bpel and wsdl file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5027?page=com.atlassian.jira.plu... ] Robert (Bob) Brodt commented on JBIDE-5027: ------------------------------------------- This is part of the refactoring effort required for https://jira.jboss.org/jira/browse/JBIDE-6018 Maybe fix this for November release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira