January 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (BAM-89) Error has been thrown when stop the SwitchYard with BAM installed.

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-89?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-89: -------------------------- Fix Version/s: 1.0.0.M4 > Error has been thrown when stop the SwitchYard with BAM installed. > ------------------------------------------------------------------ > > Key: BAM-89 > URL: https://issues.jboss.org/browse/BAM-89 > Project: Business Activity Monitoring > Issue Type: Bug > Reporter: Jeff Yu > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > When you installed the BAM distro, and the samples. Then you just press Ctrl+C to stop the SwitchYard, you'll see the following exception. > ========== > 22:30:33,849 ERROR [org.jboss.ejb3.invocation] JBAS014134: EJB Invocation failed on component EPNManager for method public abstract void org.overlord.bam.epn.EPNManager.removeNetworkListener(org.overlord.bam.epn.NetworkListener): javax.ejb.EJBTransactionRolledbackException: JBAS011049: Component is stopped > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:139) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:204) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:306) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-136) Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-136: ----------------------------------- Summary: Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate Key: SRAMP-136 URL: https://issues.jboss.org/browse/SRAMP-136 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: Milestone 4 The S-RAMP spec is changing the name of the UserDefinedArtifactType. We need to go through our code to mirror that change, once we make the adjustment to the schema/generated java code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-101) Switchyard auditor not handling fault responses correctly

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-101?page=com.atlassian.jira.plugin.sy... ] Gary Brown updated BAM-101: --------------------------- Fix Version/s: 1.0.0.M4 (was: 1.0.0.M3) > Switchyard auditor not handling fault responses correctly > --------------------------------------------------------- > > Key: BAM-101 > URL: https://issues.jboss.org/browse/BAM-101 > Project: Business Activity Monitoring > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > When the switchyard order mgmt example is used - if an unknown item is specified, this causes a fault response from the inventory service. This is not being correctly represented as an activity event. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-59) jBPM activity collector

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-59?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-59: -------------------------- Fix Version/s: 1.0.0.M4 (was: 1.0.0.M3) > jBPM activity collector > ----------------------- > > Key: BAM-59 > URL: https://issues.jboss.org/browse/BAM-59 > Project: Business Activity Monitoring > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Kevin Conner > Fix For: 1.0.0.M4 > > > Create an ActivityCollector to obtain information associated with the execution of a BPMN2 process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-95) Activity store "out of the box" configuration for in-memory H2

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-95?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-95: -------------------------- Fix Version/s: 1.0.0.M4 (was: 1.0.0.M3) > Activity store "out of the box" configuration for in-memory H2 > -------------------------------------------------------------- > > Key: BAM-95 > URL: https://issues.jboss.org/browse/BAM-95 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Jeff Yu > Fix For: 1.0.0.M4 > > > Use the JPA activity store implementation with configuration for an in-memory H2 db. Configurable dbs will be provided as part of next (or later) milestone. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-11) BPEL activity collector

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-11?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-11: -------------------------- Fix Version/s: 1.0.0.M4 (was: 1.0.0.M3) > BPEL activity collector > ----------------------- > > Key: BAM-11 > URL: https://issues.jboss.org/browse/BAM-11 > Project: Business Activity Monitoring > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Kevin Conner > Fix For: 1.0.0.M4 > > > Create an ActivityCollector to obtain information associated with the execution of a BPEL process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-92) Define the BPM activity model components

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-92?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-92: -------------------------- Fix Version/s: 1.0.0.M4 (was: 1.0.0.M3) > Define the BPM activity model components > ---------------------------------------- > > Key: BAM-92 > URL: https://issues.jboss.org/browse/BAM-92 > Project: Business Activity Monitoring > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Kevin Conner > Fix For: 1.0.0.M4 > > > Define a set of appropriate BPM related activity events to represent generic events that occur within a process engine. > These events will be required to describe the activities associated with the switchyard bpel (Riftsaw) and bpm (jBPM) components. > One of the objectives of these events should be to help trace the flow of information through a process. So when information is received (i.e. a received message), it would be useful to know the variable in which it is stored, and how subsequent variable values are derived from this initial information. Also expression evaluation for decision making could be useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-134) Make Derivers pluggable so users can plug in their own

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-134?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-134. ------------------------------- > Make Derivers pluggable so users can plug in their own > ------------------------------------------------------ > > Key: SRAMP-134 > URL: https://issues.jboss.org/browse/SRAMP-134 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > Allow users to plug their own Derivers so they can create derived artifacts automatically for their own artifact types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-134) Make Derivers pluggable so users can plug in their own

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-134?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-134. --------------------------------- Resolution: Done Users can now contribute their own derivers for user-defined artifact types. See the new demo for this feature in the distro for details. > Make Derivers pluggable so users can plug in their own > ------------------------------------------------------ > > Key: SRAMP-134 > URL: https://issues.jboss.org/browse/SRAMP-134 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > Allow users to plug their own Derivers so they can create derived artifacts automatically for their own artifact types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-134) Make Derivers pluggable so users can plug in their own

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-134?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-134: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/137 > Make Derivers pluggable so users can plug in their own > ------------------------------------------------------ > > Key: SRAMP-134 > URL: https://issues.jboss.org/browse/SRAMP-134 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > Allow users to plug their own Derivers so they can create derived artifacts automatically for their own artifact types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues January 2013