[
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.
Operations don't display in PartnerLink Property Details
--------------------------------------------------------
Key: JBIDE-5027
URL:
https://jira.jboss.org/jira/browse/JBIDE-5027
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Affects Versions: 3.1.0.M3
Environment: JBoss BPEL Editor 1.0.0.v200909110340M-H277-M3 with Eclipse 3.5 on
Mac
Reporter: Jeff DeLong
Attachments: PartnerLink.tiff, StoreProcess.zip
I find issues with the PartnerLinks sometimes where the Operation don't display in
the PartnerLink Property Details. This can happen even though the PartnerLilnk / port
information is still viewable in Receive, Invoke, Reply activities.
Also, if a WSDL file is updated, should the PartnerLink information be immediately
updated, or must the PartnerLink be deleted and then re-added?
--
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