May 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-374) Support for JPA ActivityStore & EventProcessor

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/RTGOV-374?page=com.atlassian.jira.plugin.... ] Brett Meyer updated RTGOV-374: ------------------------------ Git Pull Request: https://github.com/Governance/rtgov/pull/74 (was: https://github.com/Governance/rtgov/pull/74, https://github.com/Governance/rtgov-ui/pull/41) > Support for JPA ActivityStore & EventProcessor > ---------------------------------------------- > > Key: RTGOV-374 > URL: https://issues.jboss.org/browse/RTGOV-374 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 2.0.0.Final > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Need to be able to use JPAActivityStore & EventProcessor within Karaf/OSGi environment, with different databases (e.g. h2, mysql etc) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-418) Shell tab completion for archive commands

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-418?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved SRAMP-418. ---------------------------------------- Resolution: Done > Shell tab completion for archive commands > ----------------------------------------- > > Key: SRAMP-418 > URL: https://issues.jboss.org/browse/SRAMP-418 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.6.0 - Future > > > We have a set of shell commands in the archive: namespace which manipulate s-ramp archives (basically zip files). These commands don't support tab completion very well. We should evaluate each command and see how we can create completers for each parameter. > For example - we could have a completer for any "path within the archive" arguments. There is an archive in scope and we could use the directory ZipEntries in that archive to provide intelligent completions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-422) s-ramp ontologies display editor when created or uploaded an ontology

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved SRAMP-422. ---------------------------------------- Fix Version/s: 0.5.0 - API Management Resolution: Done > s-ramp ontologies display editor when created or uploaded an ontology > --------------------------------------------------------------------- > > Key: SRAMP-422 > URL: https://issues.jboss.org/browse/SRAMP-422 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-419) UI Feature: Export/Download ontology

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-419?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved SRAMP-419. ---------------------------------------- Resolution: Done > UI Feature: Export/Download ontology > ------------------------------------ > > Key: SRAMP-419 > URL: https://issues.jboss.org/browse/SRAMP-419 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > The new Onotology Management UI should have the ability to download/export an ontology to disk. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-421) S-ramp shell UploadArtifactCommand Add name and description

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-421?page=com.atlassian.jira.plugin.... ] Work on SRAMP-421 stopped by David virgil naranjo. > S-ramp shell UploadArtifactCommand Add name and description > ----------------------------------------------------------- > > Key: SRAMP-421 > URL: https://issues.jboss.org/browse/SRAMP-421 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-428) Support Fuse datasources

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-428?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-428: ------------------------------ Description: The installer will need to register the datasource as an OSGi service. {quote} The preferred way of defining the datasource is to expose it as an OSGi service in a blueprint XML. An example that demonstrates this can be found here: https://github.com/FuseByExample/camel-persistence-part2 and the relevant bit of code is here: https://github.com/FuseByExample/camel-persistence-part2/blob/master/data... and is part of a series of Fuse examples that demonstrate various Fuse capabilities that can be found here https://www.jboss.org/products/fuse/fusebyexample.html I would recommend that you clone the example repository and try and run through it. With regards to more formal documentation on defining a JDBC DataSource and XADataSource in Fuse, I found the JBoss Fuse Transaction Guide: https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1... https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1... to be extremely helpful. {quote} > Support Fuse datasources > ------------------------ > > Key: SRAMP-428 > URL: https://issues.jboss.org/browse/SRAMP-428 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > The installer will need to register the datasource as an OSGi service. > {quote} > The preferred way of defining the datasource is to expose it as an OSGi > service in a blueprint XML. An example that demonstrates this can be > found here: > https://github.com/FuseByExample/camel-persistence-part2 and the > relevant bit of code is here: > https://github.com/FuseByExample/camel-persistence-part2/blob/master/data... > and is part of a series of Fuse examples that demonstrate various Fuse > capabilities that can be found here > https://www.jboss.org/products/fuse/fusebyexample.html > I would recommend that you clone the example repository and try and run > through it. > With regards to more formal documentation on defining a JDBC DataSource > and XADataSource in Fuse, I found the JBoss Fuse Transaction Guide: > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1... > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1... > to be extremely helpful. > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-428) Support Fuse datasources

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-428: --------------------------------- Summary: Support Fuse datasources Key: SRAMP-428 URL: https://issues.jboss.org/browse/SRAMP-428 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 0.5.0 - API Management -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-425) Upgrade to integration bom CR8

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.... ] Gary Brown resolved SRAMP-425. ------------------------------ Resolution: Done > Upgrade to integration bom CR8 > ------------------------------ > > Key: SRAMP-425 > URL: https://issues.jboss.org/browse/SRAMP-425 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 0.5.0 - API Management > > > Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-425) Upgrade to integration bom CR8

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-425: ---------------------------------- Two issues occurred when doing the upgrade - the switchyard multiapp WebServiceTest had problems with the updated cxf version, and the new enforcer rules had problems with jansi-1.9. These have been logged as additional jiras. > Upgrade to integration bom CR8 > ------------------------------ > > Key: SRAMP-425 > URL: https://issues.jboss.org/browse/SRAMP-425 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 0.5.0 - API Management > > > Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-425) Upgrade to integration bom CR8

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.... ] Gary Brown updated SRAMP-425: ----------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/415 > Upgrade to integration bom CR8 > ------------------------------ > > Key: SRAMP-425 > URL: https://issues.jboss.org/browse/SRAMP-425 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 0.5.0 - API Management > > > Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2014