February 2012 - switchyard-issues

[JBoss JIRA] (SWITCHYARD-664) CamelActivator should create context on activateBinding() rather than on start()

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-664: --------------------------------------- Summary: CamelActivator should create context on activateBinding() rather than on start() Key: SWITCHYARD-664 URL: https://issues.jboss.org/browse/SWITCHYARD-664 Project: SwitchYard Issue Type: Bug Components: component-camel Affects Versions: 0.3 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 Camel component activator creates context during the start() method. However, this poses a problem due to not all the TypeConverters being registered. So idea is to move this context creation to activateBinding() method. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-663) Add BPEL quickstart with JMS binding

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-663: ------------------------------------- Summary: Add BPEL quickstart with JMS binding Key: SWITCHYARD-663 URL: https://issues.jboss.org/browse/SWITCHYARD-663 Project: SwitchYard Issue Type: Enhancement Components: quickstarts Affects Versions: 0.4 Reporter: Keith Babo Fix For: 0.4 Create a quickstart that uses a JMS binding for BPEL instead of SOAP. See the modified say_hello quickstart in my bpel_jms branch here: https://github.com/kcbabo/quickstarts/tree/bpel_jms/bpel-service Instead of modifying the existing say_hello quickstart, we should create a new quickstart in bpel-service/ called jms_binding (or similar). AFAIC, we can use the same BPEL process in say_hello, I just want a distinct quickstart so that we can highlight the JMS binding. I have some crappy test code in my branch that I would prefer to remove in favor of a solution that uses the HornetQMixIn. We could even add an option for remote testing like I have done here: https://github.com/jboss-switchyard/quickstarts/tree/master/demos/multiAp... And maybe use the new remote HornetQ support that Tomo has added. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-662) Add runtime admin and monitoring

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-662: ------------------------------------- Summary: Add runtime admin and monitoring Key: SWITCHYARD-662 URL: https://issues.jboss.org/browse/SWITCHYARD-662 Project: SwitchYard Issue Type: Enhancement Components: console, core, distribution Affects Versions: 0.4 Reporter: Keith Babo Fix For: 0.4 Add core support for runtime admin and monitoring. This should be event-based so that modules outside of runtime can both listen for and generate events. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-661) quickstart demos not included in maven deploy

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-661: ------------------------------------- Summary: quickstart demos not included in maven deploy Key: SWITCHYARD-661 URL: https://issues.jboss.org/browse/SWITCHYARD-661 Project: SwitchYard Issue Type: Bug Components: distribution, quickstarts Affects Versions: 0.4 Reporter: Keith Babo Fix For: 0.4 The multiApp and policyTransaction quickstarts are not included in the quickstart parent pom.xml, which means they are skipped during mvn deploy. This probably means they are also excluded from the distribution as well. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-660) Fix Camel InOut exception handling

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-660: --------------------------------------- Summary: Fix Camel InOut exception handling Key: SWITCHYARD-660 URL: https://issues.jboss.org/browse/SWITCHYARD-660 Project: SwitchYard Issue Type: Bug Components: component-camel Affects Versions: 0.3 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 Camel component's OutboundHandler does not handle exceptions from InOut messages properly. http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel..., org.apache.camel.Processor) API says "Notice: that if the processing of the exchange failed with an Exception it is not thrown from this method, but you can access it from the returned exchange using Exchange.getException()." -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-659) Add configuration support for Camel CXFRS component

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-659: --------------------------------------- Summary: Add configuration support for Camel CXFRS component Key: SWITCHYARD-659 URL: https://issues.jboss.org/browse/SWITCHYARD-659 Project: SwitchYard Issue Type: Feature Request Components: component-camel Affects Versions: 0.3 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 Add configuration support for Camel CXFRS component http://camel.apache.org/cxfrs.html -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-658) Add a camel-rest-binding quickstart

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-658: --------------------------------------- Summary: Add a camel-rest-binding quickstart Key: SWITCHYARD-658 URL: https://issues.jboss.org/browse/SWITCHYARD-658 Project: SwitchYard Issue Type: Feature Request Components: quickstarts Affects Versions: 0.3 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 Add a quickstart that creates a deployment that use Camels CXFRS Component. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-657) Use HornetQMixIn in AS7 release tests that connects to HornetQ

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-657: -------------------------------------------- Summary: Use HornetQMixIn in AS7 release tests that connects to HornetQ Key: SWITCHYARD-657 URL: https://issues.jboss.org/browse/SWITCHYARD-657 Project: SwitchYard Issue Type: Sub-task Components: test Reporter: Tomohisa igarashi -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-656) CreateSwitchYardProjectOperation allow for null package

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-656: ------------------------------------- Summary: CreateSwitchYardProjectOperation allow for null package Key: SWITCHYARD-656 URL: https://issues.jboss.org/browse/SWITCHYARD-656 Project: SwitchYard Issue Type: Enhancement Components: tooling Reporter: Gary Brown Would be good if the package defined in the metadata could be optional, and therefore not created as part of the project. In my particular case, it is easier to have the project setup before creating the artifacts (and therefore identifying the package names) afterwards. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-655) Error log shows "Project facet jboss.m2 has not been defined" entry on startup with SwitchYard Eclipse tools

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-655: ------------------------------------- Summary: Error log shows "Project facet jboss.m2 has not been defined" entry on startup with SwitchYard Eclipse tools Key: SWITCHYARD-655 URL: https://issues.jboss.org/browse/SWITCHYARD-655 Project: SwitchYard Issue Type: Bug Components: tooling Affects Versions: 0.4 Reporter: Gary Brown The following entry appears in the error log when the latest trunk version of SwitchYard tools are installed: Error Wed Feb 22 11:34:46 GMT 2012 Project facet jboss.m2 has not been defined. It is used in plugin org.switchyard.tools.ui. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues February 2012