March 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-203) Merge @SwitchYardDeploymentScanners into @SwitchYardDeploymentConfig

by Tom Fennelly (JIRA)

Merge @SwitchYardDeploymentScanners into @SwitchYardDeploymentConfig -------------------------------------------------------------------- Key: SWITCHYARD-203 URL: https://issues.jboss.org/browse/SWITCHYARD-203 Project: SwitchYard Issue Type: Enhancement Components: test Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 0.1 We currently have 3 different test related annotations. This is not the most user friendly. Should def collapse these 2 annotations together (@SwitchYardDeploymentConfig and @SwitchYardDeploymentScanners) and perhaps consider merging @TestMixIns into that same annotation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-202) Deployment: NullPointerException if component does not contain an implemention element.

by Daniel Bevenius (JIRA)

Deployment: NullPointerException if component does not contain an implemention element. --------------------------------------------------------------------------------------- Key: SWITCHYARD-202 URL: https://issues.jboss.org/browse/SWITCHYARD-202 Project: SwitchYard Issue Type: Bug Components: deployment Reporter: Daniel Bevenius According to SCA Assembly spec a component element can have zero or more implementation elements as its child. But the method getActivator(component) in Deployment.java you can find the following code: {code} private Activator getActivator(ComponentModel component) { String type = component.getImplementation().getType(); Activator activator = _componentActivators.get(type); if (activator == null) { throw new RuntimeException("Unknown configuration component type '" + type + "'. No Activator implementation registered for this type."); } return activator; } {code} I noticed this while working on SWITCHYARD-201 which also contains an example of the config that I'm using (See Keith's last comment) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-201) Camel Component: Implement reference binding support

by Daniel Bevenius (JIRA)

Camel Component: Implement reference binding support ---------------------------------------------------- Key: SWITCHYARD-201 URL: https://issues.jboss.org/browse/SWITCHYARD-201 Project: SwitchYard Issue Type: Task Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 0.1 This task is about adding the ability for Switchyard services to use Camel endpoints by specifying a reference element in the component configuration. Services can use other services and those services are declared using references. The idea is to add the ability for services to specify that they require functionality from a Camel endpoint. The service might consume from a Camel endpoint or they might produce to a Camel endpoint, or both. So for example, say you require to call a service that is implemented in Camel. One way might be to use the @Reference annotation that exists for the Switchyard bean component: {code} public class InventoryServiceBean implements InventoryService { @Reference WarehouseService warehouseService; public ReservationResult reservItem(final long itemId) { if (warehouseService.hasItem(itemId)) { ... } else { return new ReservationResult(false, "Could not fullfill reservation request..."); } } } {code} And the xml configuration for this component: {code:xml} <composite> <component name="Component"> <service name="InventoryService"> <interface.java interface="org.switchyard.examples.InventoryService"/> <implementation.bean class="org.switchyard.examples.InventoryServiceBean"/> </service> <reference name="WarehouseStatusService> <interface.java interface="org.switchyard.examples.WarehouseService"/> <binding.camel uri="invm://warehouseStatusService"/> </reference> </component> <composite> {code} The proxy instance might then be create something like this: {code} CamelContext camelContext = new DefaultCamelContext(); Endpoint endpoint = camelContext.getEndpoint(uri); Class[] interfaces = // create class using WarehousService warehouseService = ProxyHelper.createProxy(endpoint, "org.switchyard.example.WarehouseService"); warehouseService.hasItem(2); {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-200) Add an Application Server test

by Magesh Bojan (JIRA)

Add an Application Server test ------------------------------ Key: SWITCHYARD-200 URL: https://issues.jboss.org/browse/SWITCHYARD-200 Project: SwitchYard Issue Type: Task Components: deployment Affects Versions: M1 Reporter: Magesh Bojan Fix For: 0.1 Need to test the deployment in an AS environment. Probably an Arquillian or a remote AS instance could be used. 1. Deploy the AS distribution [SWITCHAYRD-173] 2. Deploy an application [SWITCHYARD-186] 3. Run tests -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-199) The modules common and extensions are not included in deploy/build/assembly.xml

by Magesh Bojan (JIRA)

The modules common and extensions are not included in deploy/build/assembly.xml ------------------------------------------------------------------------------- Key: SWITCHYARD-199 URL: https://issues.jboss.org/browse/SWITCHYARD-199 Project: SwitchYard Issue Type: Bug Components: core, deployment Affects Versions: M1 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-198) Component services wthout an interface declaration are not picked up by composite marshaller

by Keith Babo (JIRA)

Component services wthout an interface declaration are not picked up by composite marshaller -------------------------------------------------------------------------------------------- Key: SWITCHYARD-198 URL: https://issues.jboss.org/browse/SWITCHYARD-198 Project: SwitchYard Issue Type: Bug Components: configuration Reporter: Keith Babo Fix For: 0.1 2:37 errantepiphany babo_afk: the answer is in V1CompositeMarshaller.java, lines 59-64. Somehow I have to figure out which KIND of service we're talking about, so I look if it has a binding as a child (which means a composite service model), or an interface as a child (which means a component service model). babo_afk: however, I think there's a better way of doing it. Look at lines 71 through 79. In this case we don't look for a child to determine what type of interface to create, we look at the PARENT. We should probably do he same thing in the service class. babo_afk: s/do he same thing in the service class/do the same thing for the service class/ 2:39 babo_afk: does everything above make sense? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-197) Add test support to deployer module

by Keith Babo (JIRA)

Add test support to deployer module ----------------------------------- Key: SWITCHYARD-197 URL: https://issues.jboss.org/browse/SWITCHYARD-197 Project: SwitchYard Issue Type: Task Components: deployment Reporter: Keith Babo Assignee: Keith Babo Fix For: 0.1 There are no implementation or binding tests in deployment, which is a big hole. Fix this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-196) Add support to scan deployments for WSDLs

by Magesh Bojan (JIRA)

Add support to scan deployments for WSDLs ----------------------------------------- Key: SWITCHYARD-196 URL: https://issues.jboss.org/browse/SWITCHYARD-196 Project: SwitchYard Issue Type: Feature Request Affects Versions: M1 Reporter: Magesh Bojan Currently we associate WSDL interfaces with syntax: wsdlURI#wsdl.porttype(<portname>) this should be changed to support the SCA compliant syntax of: namespaceURI#wsdl.porttype(<portname>) where namespaceURI would be the NS of the portname. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-195) Add copyright.txt to release distribution

by Keith Babo (JIRA)

Add copyright.txt to release distribution ----------------------------------------- Key: SWITCHYARD-195 URL: https://issues.jboss.org/browse/SWITCHYARD-195 Project: SwitchYard Issue Type: Task Components: build Reporter: Keith Babo Fix For: 0.1 We need to add a copyright.txt listing contributors to the 0.1 release distribution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-194) Add support for deploying sca:interface.wsdl style services

by Magesh Bojan (JIRA)

Add support for deploying sca:interface.wsdl style services ----------------------------------------------------------- Key: SWITCHYARD-194 URL: https://issues.jboss.org/browse/SWITCHYARD-194 Project: SwitchYard Issue Type: Sub-task Components: configuration, deployment Affects Versions: M1 Reporter: Magesh Bojan Fix For: 0.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues March 2011