July 2011 - switchyard-issues - Jboss List Archives

[JBoss JIRA] Created: (SWITCHYARD-340) Add OSGi framework support for SwitchYard

by Keith Babo (JIRA)

Add OSGi framework support for SwitchYard ----------------------------------------- Key: SWITCHYARD-340 URL: https://issues.jboss.org/browse/SWITCHYARD-340 Project: SwitchYard Issue Type: Feature Request Components: distribution Reporter: Keith Babo Few things involved here, which should be straightforward: - Add OSGi bundle manifests for all SwitchYard modules - Abstract out ServiceLoader lookups in the current code so that OSGi ServiceRegistry can be used instead - Implement bundle extender pattern in OSGi deployer bundle to activate SwitchYard applications - Test! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-339) Clojure module version numbers are reversed

by Rob Cernich (JIRA)

Clojure module version numbers are reversed ------------------------------------------- Key: SWITCHYARD-339 URL: https://issues.jboss.org/browse/SWITCHYARD-339 Project: SwitchYard Issue Type: Bug Components: component-clojure Reporter: Rob Cernich Assignee: Rob Cernich Priority: Minor Fix For: 0.2 The version numbers for the modules in the assembly are reversed. The SY component is using the Clojure jar version while the Clojure jar is using the SY component version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-338) Add admin module and initial admin interfaces

by Keith Babo (JIRA)

Add admin module and initial admin interfaces --------------------------------------------- Key: SWITCHYARD-338 URL: https://issues.jboss.org/browse/SWITCHYARD-338 Project: SwitchYard Issue Type: Sub-task Components: admin Reporter: Keith Babo Assignee: Keith Babo Fix For: 0.2 Create an admin module within core and add the initial interfaces and implementation for admin tasks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-337) Add administration interfaces for SwitchYard

by Keith Babo (JIRA)

Add administration interfaces for SwitchYard --------------------------------------------- Key: SWITCHYARD-337 URL: https://issues.jboss.org/browse/SWITCHYARD-337 Project: SwitchYard Issue Type: Feature Request Components: admin Reporter: Keith Babo Fix For: 0.2 Top-level issue for tasks related to adding administration interfaces to SwitchYard core. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-336) Add BPM component + dependencies to AS 6 and 7 distributions

by Keith Babo (JIRA)

Add BPM component + dependencies to AS 6 and 7 distributions ------------------------------------------------------------ Key: SWITCHYARD-336 URL: https://issues.jboss.org/browse/SWITCHYARD-336 Project: SwitchYard Issue Type: Task Components: distribution Reporter: Keith Babo Fix For: 0.2 Need to add the component and dependencies to the AS distributions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-335) Create mechanism for identifying SwitchYard application deployments

by Rob Cernich (JIRA)

Create mechanism for identifying SwitchYard application deployments ------------------------------------------------------------------- Key: SWITCHYARD-335 URL: https://issues.jboss.org/browse/SWITCHYARD-335 Project: SwitchYard Issue Type: Feature Request Components: admin Reporter: Rob Cernich Assignee: Rob Cernich Fix For: 0.2 Create a mechanism for identifying SY specific applications deployed to AS7. This is required to allow tooling to filter out non-SY deployments from its deployments list. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-334) Unnecessary service registration if promoted service name same as component service name

by David Ward (JIRA)

Unnecessary service registration if promoted service name same as component service name ---------------------------------------------------------------------------------------- Key: SWITCHYARD-334 URL: https://issues.jboss.org/browse/SWITCHYARD-334 Project: SwitchYard Issue Type: Bug Components: deployment Reporter: David Ward Assignee: David Ward Priority: Minor Fix For: 0.2 If the promoted service has the same name as the component service, this results in two services with the same name being registered. They both point to the same handler, so it's not a critical issue, but it's something that we should clean up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-333) Create a transform-jaxb quickstart

by Keith Babo (JIRA)

Create a transform-jaxb quickstart ---------------------------------- Key: SWITCHYARD-333 URL: https://issues.jboss.org/browse/SWITCHYARD-333 Project: SwitchYard Issue Type: Task Components: quickstarts Reporter: Keith Babo Assignee: Mario Antollini Fix For: 0.2 Create a quickstart to demonstrate use of automatic JAXB transformation based on JAXB annotations in a service interface. Here's the discussion I had with Mario on IRC: > basically it means that you can write a Java service and use JAXB annotated classes as the message types > so declare a service interface which has a method where the parameter and return type are both JAXB annotated objects > hook that up to a web service binding > and that should be it > the runtime should automatically detect the JAXB annotated classes and execute them > so you don't have to define a transformer > so basically the work for the quickstart is this: > 1) create a new application with a Java service > 2) annotate the objects used in the service interface with JAXB annotations > 3) bind it to soap > 4) write a unit test using Http MixIn and XMLUnit to assert that the expected result is returned -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-332) Add drools component and implementation

by Keith Babo (JIRA)

Add drools component and implementation --------------------------------------- Key: SWITCHYARD-332 URL: https://issues.jboss.org/browse/SWITCHYARD-332 Project: SwitchYard Issue Type: Feature Request Reporter: Keith Babo Assignee: David Ward Fix For: 0.2 Add the ability to implement services using Drools. I'm on the fence about what the implementation should be named. We could go with "implementation.drools", but that doesn't sit right with me. I don't think "implementation.rules" is perfect, but it is better. In terms of feature set, I would be happy with an initial implementation that was feature equivalent to the BRP in JBoss ESB 4.x - i.e. stick messages into a knowledge session and crank on them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (SWITCHYARD-331) Use TraX Source for message content in SOAP component

by Keith Babo (JIRA)

Use TraX Source for message content in SOAP component ----------------------------------------------------- Key: SWITCHYARD-331 URL: https://issues.jboss.org/browse/SWITCHYARD-331 Project: SwitchYard Issue Type: Task Components: component-soap Reporter: Keith Babo Fix For: 0.2 See the comments in SWITCHYARD-318 for a complete background on why we want to make this change. From a content conversion standpoint, Source/DOMSource provides a greater number of options and does not require a module dependency on com.sun.xml.messaging.saaj. The change to SOAP component is minimal as we can simply wrap the existing Element reference in a DOMSource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues July 2011