Description of problem: Once a message composer is set I'm not able to remove it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Add HTTP binding 2. Add a message composer 3. Press OK and save 4. Go to properties view and try to remove the composer 5. The composer is still there Actual results: Expected results: Additional info:
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1672 Just need BZ approvals to push the fix for this minor issue.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1672 Taking a look at this to make sure it will work for the SOAP binding as well after some feedback from rcernich
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1672 SOAP binding looks AOK with this change. Context Mapper and Message Composer are added/removed just like they should be.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1672 Discovered an issue with the integration between the SOAP binding composite and the message composer, so am working through that.
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1672 Probably the same issue you found, but keep in mind that the "unwrap" option is set on the context mapper with SOAP bindings. So even if the message composer config is empty on the composer tab, if unwrap is enabled the context mapper element still needs to be there.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1672 Yup. Rob pointed that out and I have a solution. Updated the PR already to handle that case, so we should be golden.
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1672 pushed
Verified in jbdsis-7.0.0.CR1 (SwitchYard Tooling - 1.1.2.v20131213-2033-H428-CI)
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1672 to Closed