February 2012 - switchyard-issues

[JBoss JIRA] (SWITCHYARD-654) m2e: "Plugin execution not covered by lifecycle configuration"

by David Ward (JIRA)

David Ward created SWITCHYARD-654: ------------------------------------- Summary: m2e: "Plugin execution not covered by lifecycle configuration" Key: SWITCHYARD-654 URL: https://issues.jboss.org/browse/SWITCHYARD-654 Project: SwitchYard Issue Type: Bug Components: build Affects Versions: 0.3 Reporter: David Ward Assignee: David Ward Fix For: 0.4 Several of these errors show up in Eclipse, making any quickstart that uses the switchyard-plugin (pretty much all of them) look like it's broken in Eclipse when using m2e. The fix is to add more <pluginExecutionFilter/>s to the parent pom. We already do this for the maven-dependency-plugin, however we need to also add sections for the maven-enforcer-plugin, exec-maven-plugin, and switchyard-plugin. -- 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-653) Add validators to console

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-653: ------------------------------------- Summary: Add validators to console Key: SWITCHYARD-653 URL: https://issues.jboss.org/browse/SWITCHYARD-653 Project: SwitchYard Issue Type: Enhancement Components: console, tooling Affects Versions: 0.3 Reporter: Keith Babo Fix For: 0.5 Validator information for an application is missing from the console and the CLI. -- 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-652) Upgrade to AS 7.1.0 Final

by Nick Cross (JIRA)

Nick Cross created SWITCHYARD-652: ------------------------------------- Summary: Upgrade to AS 7.1.0 Final Key: SWITCHYARD-652 URL: https://issues.jboss.org/browse/SWITCHYARD-652 Project: SwitchYard Issue Type: Task Reporter: Nick Cross Fix For: 0.4 Upgrade SwitchYard from 7.1.0.CR1b to 7.1.0.Final -- 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-651) maven shade plugin missing BPM classes

by David Ward (JIRA)

David Ward created SWITCHYARD-651: ------------------------------------- Summary: maven shade plugin missing BPM classes Key: SWITCHYARD-651 URL: https://issues.jboss.org/browse/SWITCHYARD-651 Project: SwitchYard Issue Type: Bug Components: build, component-bpm, tooling Affects Versions: 0.4 Reporter: David Ward Assignee: David Ward Fix For: 0.4 The work done for SWITCHYARD-635 includes refactoring in the org.switchyard.component.bpm.task package, and the shade plugin was not updated to reflect it. -- 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-650) Add forge command to add open-shift facet/config to switchyard app

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-650: ------------------------------------- Summary: Add forge command to add open-shift facet/config to switchyard app Key: SWITCHYARD-650 URL: https://issues.jboss.org/browse/SWITCHYARD-650 Project: SwitchYard Issue Type: Feature Request Components: tooling Reporter: Keith Babo Fix For: 0.4 This can either be a command or a facet. Making it a facet is kind of interesting, something like: > project install-facet switchyard.openshift The facet installation would be responsible for pulling in the appropriate AS config and any module updates, as well as updating the pom configuration as appropriate. To make things simple, assume this runs on an app created using rhc-create-app for right now. -- 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-649) Fix TODO in BPEL module assembly

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-649: --------------------------------------- Summary: Fix TODO in BPEL module assembly Key: SWITCHYARD-649 URL: https://issues.jboss.org/browse/SWITCHYARD-649 Project: SwitchYard Issue Type: Enhancement Components: build, deployment Affects Versions: 0.3 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 BPEL module assembly has these TODOs:   Remove this and move them to their own module. -- 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-648) Upgrade OpenShift distribution to JBoss AS 7.1

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-648: --------------------------------------- Summary: Upgrade OpenShift distribution to JBoss AS 7.1 Key: SWITCHYARD-648 URL: https://issues.jboss.org/browse/SWITCHYARD-648 Project: SwitchYard Issue Type: Task Components: build, distribution Affects Versions: 0.3 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 -- 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-647) Service metrics

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-647: ------------------------------------- Summary: Service metrics Key: SWITCHYARD-647 URL: https://issues.jboss.org/browse/SWITCHYARD-647 Project: SwitchYard Issue Type: Feature Request Reporter: Gary Brown Will describe some of the features that are required in this area, but after discussion should probably be created as separate sub-tasks. a) Service managed objects Need to have an internal managed object structure for the switchyard service application representing the components of interest. Initially I think from a management/governance perspective, only the public provided/consumed interfaces are relevant, even though there may be multiple internal components that interact to implement the service - but that can be discussed. Suggestion would be to have a hierarchy with the service containing both the provided and consumed interfaces, with each interface further containing its operations. For each operation it should be possible to record invocation stats (e.g. number of invocations and min/avg/max response times) for both normal responses, aswell as fault responses - having the stats broken down per fault type. It may also be useful to record stats against invocations that fail for technical reasons, e.g. communications failure or security. b) RESTful service to provide access to the service managed object information c) Optionally a JMX interface, to enable management products to access the information d) RHQ/JON agent plugin, to periodically collect the service metric information, as well as providing auto-discovery capabilities for services, so that a user does not have to manually configure services into JON e) The final aspect of this task would be to enable developers to define 'event hooks' upon which they can provide additional adhoc governance requirements - however this requirement is probably satisfied by the handler mechanism? Although possible we may wish to provide out of the box handlers geared to this task, possibly with a logging variation (and others??). -- 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-646) riftsaw-bpel-epr is pulling in AS/EAP5 dependencies

by Nick Cross (JIRA)

Nick Cross created SWITCHYARD-646: ------------------------------------- Summary: riftsaw-bpel-epr is pulling in AS/EAP5 dependencies Key: SWITCHYARD-646 URL: https://issues.jboss.org/browse/SWITCHYARD-646 Project: SwitchYard Issue Type: Bug Reporter: Nick Cross Fix For: 0.4 The parent inclusion of <groupId>org.jboss.soa.bpel</groupId> <artifactId>riftsaw-bpel-epr</artifactId> <version>${version.riftsaw.ode}</version> pulls in org.jboss.javaee.jboss-javaee. This clashes in MEAD due to signing issues. The AS5 dependency is not required to build. -- 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-645) message tracing corrupts stream-based messages

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-645: ------------------------------------- Summary: message tracing corrupts stream-based messages Key: SWITCHYARD-645 URL: https://issues.jboss.org/browse/SWITCHYARD-645 Project: SwitchYard Issue Type: Bug Components: core Affects Versions: 0.3 Reporter: Keith Babo Fix For: 0.4 The message trace handler converts message content to a String so that it can be displayed in log output. This is a problem for stream-based messages, since the stream is emptied during the conversion and the resulting message payload is empty for the end recipient. Add logic which detects whether the input is stream-based, and if so, put content back into the message after it's converted to string. -- 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