March 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-105) Deploy S-RAMP to jBPMs JBossAS

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-105?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-105. --------------------------- > Deploy S-RAMP to jBPMs JBossAS > ------------------------------ > > Key: SRAMP-105 > URL: https://issues.jboss.org/browse/SRAMP-105 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.2.0 - Milestone 4 > > > S-RAMP needs a newer version of RestEasy then ships with JBossAS-7.02, which is where the jBPM5 installer deploys to by default. Packaging RestEasy inside the s-ramp war does not work in this case because of an initialization issue with RestEasy. Until that is fixed we recommend deploying s-ramp to separate server. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-105) Deploy S-RAMP to jBPMs JBossAS

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-105?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-105. ----------------------------- Resolution: Done Done, we are using RESTEasy-2.3.5 and JBossAS-7.1.1 now (through the jBPM installer and our own installer) > Deploy S-RAMP to jBPMs JBossAS > ------------------------------ > > Key: SRAMP-105 > URL: https://issues.jboss.org/browse/SRAMP-105 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.2.0 - Milestone 4 > > > S-RAMP needs a newer version of RestEasy then ships with JBossAS-7.02, which is where the jBPM5 installer deploys to by default. Packaging RestEasy inside the s-ramp war does not work in this case because of an initialization issue with RestEasy. Until that is fixed we recommend deploying s-ramp to separate server. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-105) Deploy S-RAMP to jBPMs JBossAS

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-105?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-105: ---------------------------- Fix Version/s: 0.2.0 - Milestone 4 (was: 0.3.0 - Future (Unscheduled)) > Deploy S-RAMP to jBPMs JBossAS > ------------------------------ > > Key: SRAMP-105 > URL: https://issues.jboss.org/browse/SRAMP-105 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.2.0 - Milestone 4 > > > S-RAMP needs a newer version of RestEasy then ships with JBossAS-7.02, which is where the jBPM5 installer deploys to by default. Packaging RestEasy inside the s-ramp war does not work in this case because of an initialization issue with RestEasy. Until that is fixed we recommend deploying s-ramp to separate server. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-40) Implement support for s-ramp properties

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-40?page=com.atlassian.jira.plugin.s... ] Kurt Stam commented on SRAMP-40: -------------------------------- Can this be closed? I think this all works no? > Implement support for s-ramp properties > --------------------------------------- > > Key: SRAMP-40 > URL: https://issues.jboss.org/browse/SRAMP-40 > Project: S-RAMP > Issue Type: Feature Request > Components: Atom Binding, Core, Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.2.0 - Milestone 4 > > > We need to add support for s-ramp properties. See the s-ramp specification (atom binding and foundation document) for details about properties. We need support in the following places: > 1) persistence layer > 2) artifact update > 3) get full artifact details > 4) query filtering > 5) artifact feed via ad-hoc query and specified extra properties (see atom api binding doc, section 3.2) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-40) Implement support for s-ramp properties

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-40?page=com.atlassian.jira.plugin.s... ] Kurt Stam updated SRAMP-40: --------------------------- Fix Version/s: 0.2.0 - Milestone 4 (was: 0.3.0 - Future (Unscheduled)) > Implement support for s-ramp properties > --------------------------------------- > > Key: SRAMP-40 > URL: https://issues.jboss.org/browse/SRAMP-40 > Project: S-RAMP > Issue Type: Feature Request > Components: Atom Binding, Core, Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.2.0 - Milestone 4 > > > We need to add support for s-ramp properties. See the s-ramp specification (atom binding and foundation document) for details about properties. We need support in the following places: > 1) persistence layer > 2) artifact update > 3) get full artifact details > 4) query filtering > 5) artifact feed via ad-hoc query and specified extra properties (see atom api binding doc, section 3.2) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-155) Add capability to deploy to JBossAS-7 domain deployment

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-155: ------------------------------- Summary: Add capability to deploy to JBossAS-7 domain deployment Key: SRAMP-155 URL: https://issues.jboss.org/browse/SRAMP-155 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Components: Governance Reporter: Kurt Stam Assignee: Kurt Stam Fix For: 0.2.0 - Milestone 4 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-155) Add capability to deploy to JBossAS-7 domain deployment

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-155?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-155: ---------------------------- Parent: SRAMP-9 Issue Type: Sub-task (was: Task) > Add capability to deploy to JBossAS-7 domain deployment > ------------------------------------------------------- > > Key: SRAMP-155 > URL: https://issues.jboss.org/browse/SRAMP-155 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.2.0 - Milestone 4 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-12) JON Integration

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-12?page=com.atlassian.jira.plugin.s... ] Kurt Stam updated SRAMP-12: --------------------------- Fix Version/s: 0.2.0 - Milestone 4 (was: 0.3.0 - Future (Unscheduled)) Affects Version/s: (was: 0.3.0 - Future (Unscheduled)) > JON Integration > --------------- > > Key: SRAMP-12 > URL: https://issues.jboss.org/browse/SRAMP-12 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.2.0 - Milestone 4 > > > Instead of direct deployment we should also integrate with JON, so JON can be sent an artifact and JON would perform the deployment. JON is the provisioning tool in this scenario. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-152) Create Event Processor Network derived artifact handler

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-152?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-152: ---------------------------------- EPN may need to be a specific custom artifact type, but rules and mvel scripts could be represented as some form of policy document (possible). Need to consider how rules/scripts may be used in other contexts. However having them readable as text docs would be good. > Create Event Processor Network derived artifact handler > ------------------------------------------------------- > > Key: SRAMP-152 > URL: https://issues.jboss.org/browse/SRAMP-152 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 0.2.0 - Milestone 4 > > > Derive EPN as a Policy Document, from the war deployable artifact. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-86) Add support for Derived Artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-86?page=com.atlassian.jira.plugin.s... ] Eric Wittmann commented on SRAMP-86: ------------------------------------ Yes. For an example, please see: https://github.com/Governance/s-ramp-distro/tree/master/s-ramp-distro-ass... > Add support for Derived Artifacts > --------------------------------- > > Key: SRAMP-86 > URL: https://issues.jboss.org/browse/SRAMP-86 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Implement the Derived Artifact layer. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2013