[JBoss JIRA] (SWITCHYARD-777) When resizing components, services, and references in the visual editor, the label should also resize
by Brian Fitzpatrick (JIRA)
Brian Fitzpatrick created SWITCHYARD-777:
--------------------------------------------
Summary: When resizing components, services, and references in the visual editor, the label should also resize
Key: SWITCHYARD-777
URL: https://issues.jboss.org/browse/SWITCHYARD-777
Project: SwitchYard
Issue Type: Bug
Components: tooling
Affects Versions: 0.5
Reporter: Brian Fitzpatrick
Assignee: Brian Fitzpatrick
Fix For: 0.5
Resize works great with Rob's latest changes using the new multiple-anchor approach for component references and component services, but now when you resize a component, service, or reference in a composite, the label doesn't resize along with it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (SWITCHYARD-769) Simplify context access in mapping expressions
by David Ward (JIRA)
David Ward created SWITCHYARD-769:
-------------------------------------
Summary: Simplify context access in mapping expressions
Key: SWITCHYARD-769
URL: https://issues.jboss.org/browse/SWITCHYARD-769
Project: SwitchYard
Issue Type: Enhancement
Components: component-rules
Affects Versions: 0.5
Reporter: David Ward
Assignee: David Ward
Priority: Minor
Fix For: 0.5
The work done in SWITCHYARD-714 included the ability to use MVEL expressions to set rules and bpm variables. Inside the expressions, pre-set variables were called exchange, message and context, as well as context_in (same as context), context_out and context_exchange. These last names were there so that map access to the context from an expression would know which Scope to use. This is confusing and messy.
Instead, context_in, context_out and context_exchange should all be removed, and just leave context, message and exchange. Map access to the context in an mvel expression should default to Scope.IN, but add an additional attribute to override that to Scope.OUT or Scope.EXCHANGE. See "contextScope" below:
<mapping expression="context['foobar']" variable="foobar"/>
same as
<mapping expression="context['foobar']" variable="foobar" contextScope="IN"/>
same as
@Mapping(expression="context['foobar']", variable="foobar")
same as
@Mapping(expression="context['foobar']", variable="foobar", contextScope=Scope.IN)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months