June 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-319) Validate reference promote value

by Magesh Bojan (JIRA)

Validate reference promote value -------------------------------- Key: SWITCHYARD-319 URL: https://issues.jboss.org/browse/SWITCHYARD-319 Project: SwitchYard Issue Type: Enhancement Components: deployment Affects Versions: 0.1 Reporter: Magesh Bojan Fix For: 0.2 During deployment, check should be made to see if the promote value of a Composite Reference is valid. The value could either point to a <component-name>/<service-name> or a <component-name>. If <component-name> is specified the first reference inside that Component is assumed. -- 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-318) ClientProxyBean.createExchange does not set exchange contract

by Magesh Bojan (JIRA)

ClientProxyBean.createExchange does not set exchange contract ------------------------------------------------------------- Key: SWITCHYARD-318 URL: https://issues.jboss.org/browse/SWITCHYARD-318 Project: SwitchYard Issue Type: Bug Components: component-bean Affects Versions: 0.1 Reporter: Magesh Bojan Fix For: 0.2 ClientProxyBean.createExchange method does not populate InvokerInvocationMetaData. Due to this any transformers that would have usually applied between the reference interface and the actual service implementation are not applied. Debug shows InvokerInvocationMetaData InputType, OutputType and FaultType are null. -- 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-317) CDIBeanManagerJNDIDeployer should only bind the BeanManager for top level deployments

by Daniel Bevenius (JIRA)

CDIBeanManagerJNDIDeployer should only bind the BeanManager for top level deployments ------------------------------------------------------------------------------------- Key: SWITCHYARD-317 URL: https://issues.jboss.org/browse/SWITCHYARD-317 Project: SwitchYard Issue Type: Bug Components: component-bean Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 0.2 I noticed this when deploying the camel-jms-binding quickstart, which contains a hornetq-jms.xml file. What was happening was that the BindingVisitor was getting called for the quickstart jar and also for the hornetq-jms.xml file that exist inside the toplevel deployment. Adding a check and only performing the binding if the deployment unit is a top level deployment should fix the issue. -- 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-316) Fix AS7 dependecies for WSDL api extensions

by Magesh Bojan (JIRA)

Fix AS7 dependecies for WSDL api extensions ------------------------------------------- Key: SWITCHYARD-316 URL: https://issues.jboss.org/browse/SWITCHYARD-316 Project: SwitchYard Issue Type: Bug Components: core, deployment Affects Versions: 0.1 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.2 Using interface.wsdl fails in AS7 due to missing dependecies. -- 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-315) Add camel endpoint validation tests to camel config

by Keith Babo (JIRA)

Add camel endpoint validation tests to camel config --------------------------------------------------- Key: SWITCHYARD-315 URL: https://issues.jboss.org/browse/SWITCHYARD-315 Project: SwitchYard Issue Type: Task Components: component-camel Reporter: Keith Babo Assignee: Mario Antollini Fix For: 0.2 At present, we test the Camel config implementation to make sure it can read and write SCA binding config for each Camel component type. The one thing that's missing is validating that the URI we are producing is interpreted correctly by Camel. As it turns out, there's a pretty easy way of doing this. For example, the following test could be added to V1CamelFileConsumerBindingModelTest: {noformat} @Test public void testCamelEndpoint() { CamelFileBindingModel model = createFileConsumerModel(); String configUri = model.getComponentURI().toString(); CamelContext context = new DefaultCamelContext(); FileEndpoint endpoint = context.getEndpoint(configUri, FileEndpoint.class); Assert.assertEquals(BUFFER_SIZE, endpoint.getBufferSize()); // add asserts for all other config values here ... } {noformat} -- 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-314) Create a JAXB Transformer

by Tom Fennelly (JIRA)

Create a JAXB Transformer ------------------------- Key: SWITCHYARD-314 URL: https://issues.jboss.org/browse/SWITCHYARD-314 Project: SwitchYard Issue Type: Feature Request Components: component-bean, transformation Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.2 This idea came from a forum post created by Jiri Pechanec (link in forum ref field). I think this could be really useful, in particular in conjunction with the bean component. We could auto register XML to Java (and Java to XML) transforms for bean operations whose input/output Java types are annotated with JAXB annotations. Then all you'd need to do to implement a Service and expose it over the SOAP (or REST) would be to implement/generate JAXB Java beans for the service operation types. I think this coud be an easy feature to add and would -- 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-313) Make web service development easier using JAXB annotations

by Jiri Pechanec (JIRA)

Make web service development easier using JAXB annotations ---------------------------------------------------------- Key: SWITCHYARD-313 URL: https://issues.jboss.org/browse/SWITCHYARD-313 Project: SwitchYard Issue Type: Feature Request Reporter: Jiri Pechanec Provide transformers that will automatically convert SOAP payload to/from Java object annotated with JAXB annotations -- 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-312) replace Thread.sleep() and thread locals used for handling IN-OUT

by Keith Babo (JIRA)

replace Thread.sleep() and thread locals used for handling IN-OUT ----------------------------------------------------------------- Key: SWITCHYARD-312 URL: https://issues.jboss.org/browse/SWITCHYARD-312 Project: SwitchYard Issue Type: Enhancement Components: core Reporter: Keith Babo Fix For: 0.2 A number of components are using code like this to handle the response from an InOut exchange: {noformat} while (System.currentTimeMillis() < start + 15000) { if (RESPONSE.get() != null) { return; } try { Thread.sleep(100); } catch (InterruptedException e) { continue; } } {noformat} We need to introduce core support for replacing this code with something that uses wait/notify or similar. -- 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-311) Disable dependency report on maven site run

by Tom Cunningham (JIRA)

Disable dependency report on maven site run ------------------------------------------- Key: SWITCHYARD-311 URL: https://issues.jboss.org/browse/SWITCHYARD-311 Project: SwitchYard Issue Type: Task Components: build Affects Versions: 0.1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 0.2 The maven dependency report takes an obscene amount of time to run. Disabling it by specifying the reportSet to run will speed the site build up a great deal. -- 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-310) Camel input gateways should be configurable using Java implementation too

by Jiri Pechanec (JIRA)

Camel input gateways should be configurable using Java implementation too ------------------------------------------------------------------------- Key: SWITCHYARD-310 URL: https://issues.jboss.org/browse/SWITCHYARD-310 Project: SwitchYard Issue Type: Feature Request Components: component-camel Affects Versions: 0.1 Environment: JBoss AS 7 Reporter: Jiri Pechanec Use case I have a big CSV file that I want to efficiently process. To do this I need 1) Camel file service endpoint 2) Stream the file 3) Split the file by lines 4) Enable parallel processing It can be express in Java using this configuration from("file:...") .log("Message received in ParallelSplitter") .log("${body}") .split(body(String.class).tokenize("\n")) .streaming() .parallelProcessing() .unmarshal() .csv() .to("switchyard://TestService?operationName=longOperation"); Unfortunately Camel inbound gateway supports only setting URI. And if I use Camel service with RouteBuilder then it is mandatory for me to set from to switchyard://... endpoint. So it would be great to enable configuring camel bindings using Java or Spring DSLs -- 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 June 2011