May 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-248) Update Camel Java DSL handling

by Keith Babo (JIRA)

Update Camel Java DSL handling ------------------------------ Key: SWITCHYARD-248 URL: https://issues.jboss.org/browse/SWITCHYARD-248 Project: SwitchYard Issue Type: Feature Request Components: component-camel, tooling Affects Versions: 0.1 Reporter: Keith Babo Fix For: 0.1 Update the Java DSL handling in Camel component to use RouteBuilder. Also update the forge tooling to include the RouteScanner and generate appropriate config in camel-service command. It was easy enough to take care of SWITCHYARD-240 as part of this work, so that's taken care of as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-247) Add Camel quickstarts

by Keith Babo (JIRA)

Add Camel quickstarts --------------------- Key: SWITCHYARD-247 URL: https://issues.jboss.org/browse/SWITCHYARD-247 Project: SwitchYard Issue Type: Feature Request Components: quickstarts Reporter: Keith Babo Assignee: Keith Babo Fix For: 0.1 Add a camel binding and service quickstart. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-246) FromMapToJava$GraphBuilder.getSetter not working for fluent setter methods

by Tom Fennelly (JIRA)

FromMapToJava$GraphBuilder.getSetter not working for fluent setter methods -------------------------------------------------------------------------- Key: SWITCHYARD-246 URL: https://issues.jboss.org/browse/SWITCHYARD-246 Project: SwitchYard Issue Type: Bug Components: transformation Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 It uses java.beans.Introspector.getBeanInfo() to get the bean property info. This method doesn't seem to work for fluent setter methods (i.e. setter methods that return this instance Vs void). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-245) TransformerFactory not resolving from/to QNames properly for Java types

by Tom Fennelly (JIRA)

TransformerFactory not resolving from/to QNames properly for Java types ----------------------------------------------------------------------- Key: SWITCHYARD-245 URL: https://issues.jboss.org/browse/SWITCHYARD-245 Project: SwitchYard Issue Type: Bug Components: transformation Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.1 It's failing to match compatible java types. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-244) Find a new home for JavaService.toJavaMessageType

by Tom Fennelly (JIRA)

Find a new home for JavaService.toJavaMessageType ------------------------------------------------- Key: SWITCHYARD-244 URL: https://issues.jboss.org/browse/SWITCHYARD-244 Project: SwitchYard Issue Type: Task Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 It uses Class.forName but should be using the commons Classes class. Perhaps we could create some QName utils in commons. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-243) SwitchYardProducer should look up the operationName if no operationName was specified in the Component URI.

by Daniel Bevenius (JIRA)

SwitchYardProducer should look up the operationName if no operationName was specified in the Component URI. ----------------------------------------------------------------------------------------------------------- Key: SWITCHYARD-243 URL: https://issues.jboss.org/browse/SWITCHYARD-243 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 0.1 This has been done for the InboundHandler but I totally missed that this was also required for the SwitchYardProducer. The lookup code can be extracted and the same code used for both classes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-242) Create a mechanism for creating Transformer instances from a TransformModel

by Tom Fennelly (JIRA)

Create a mechanism for creating Transformer instances from a TransformModel --------------------------------------------------------------------------- Key: SWITCHYARD-242 URL: https://issues.jboss.org/browse/SWITCHYARD-242 Project: SwitchYard Issue Type: Enhancement Components: transformation Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 At the moment we're firing different Transformer Factory implementations from inside the TransformerFactory.newTransformer(TransformModel) based on the specific TransformModel type (e.g. Smooks etc). This is hardcoded and sucks... cannot be extended etc. Maybe an annotation on the TransformModel impl that identifies the Transformer factory to be used to construct the Transformer instance e.g. {code} @TransformerFactory(SmooksTransformFactory.class) public interface SmooksTransformModel extends TransformModel { etc.... } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-241) Code JSONTransformFactory into the top level TransformerFactory class

by Tom Fennelly (JIRA)

Code JSONTransformFactory into the top level TransformerFactory class ---------------------------------------------------------------------- Key: SWITCHYARD-241 URL: https://issues.jboss.org/browse/SWITCHYARD-241 Project: SwitchYard Issue Type: Bug Components: transformation Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.1 Needs to be coded into the TransformerFactory.newTransformer(TransformModel) method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-240) Camel-Forge: operation name should be made optional

by Daniel Bevenius (JIRA)

Camel-Forge: operation name should be made optional --------------------------------------------------- Key: SWITCHYARD-240 URL: https://issues.jboss.org/browse/SWITCHYARD-240 Project: SwitchYard Issue Type: Task Components: tooling Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 0.1 The operationName on an camel.binding has been made optional but the same option in the forge plugin is required. Make this optional. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-239) Provide access to invocation/exchange context within component implementations

by Gary Brown (JIRA)

Provide access to invocation/exchange context within component implementations ------------------------------------------------------------------------------ Key: SWITCHYARD-239 URL: https://issues.jboss.org/browse/SWITCHYARD-239 Project: SwitchYard Issue Type: Feature Request Reporter: Gary Brown The SCA spec provides a ComponentContext that has a RequestContext. This enables the component to examine security subject info, but unfortunately no other potential 'header' information carried with a message. It would be useful to provide access to invocation/exchange context (including header properties) information to the component (e.g. bean) implementations, and possibly support the SCA interfaces for future alignment with the standard. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues May 2011