February 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-74) Create documentation process

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-74?page=com.atlassian.jira.plugin.s... ] Kurt Stam commented on SRAMP-74: -------------------------------- If you clone our wiki: https://github.com/Governance/s-ramp/wiki/_access Then in the 'guide' directory you can find the following Readme: https://github.com/Governance/s-ramp/wiki/GuideReadme I'm prefixing all files in the guide directory by Guide to avoid conflicts on the wiki where this directory hierarchy is not reflected; and also it sorts nicely then. I have attached the HTML and PDF versions the docbook builds (note nicely with numbers, TOC, etc). Users can update the asciidoc pages (one for each chapter) right in the wiki, and submit a pull request. > Create documentation process > ---------------------------- > > Key: SRAMP-74 > URL: https://issues.jboss.org/browse/SRAMP-74 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: Milestone 2 (Properties) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > I'm thinking about creating the content using MarkDown (md) format. Github's wiki supports this format and the docs end up as *md files in a github project. > This means that we can work on documentation while being offline, and users can alter the docs in their fork and send us pull requests. > At release time we use a tool like pandoc to convert the md files to docbook format. The docbook files should be checked in with the S-RAMP project itself. We can then put these docbook based files out on jboss.org. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-122) Restructure way jbossas modules are created

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-122?page=com.atlassian.jira.plugin.sy... ] Gary Brown updated BAM-122: --------------------------- Fix Version/s: 1.0.0.M5 (was: 1.0.0.M4) > Restructure way jbossas modules are created > ------------------------------------------- > > Key: BAM-122 > URL: https://issues.jboss.org/browse/BAM-122 > Project: Business Activity Monitoring > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > Use a similar approach to switchyard to build the modules, and allow external modules (e.g. drools, mvel) where they don't already exist. So only overwrite the external modules if not already present. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-122) Restructure way jbossas modules are created

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-122?page=com.atlassian.jira.plugin.sy... ] Gary Brown commented on BAM-122: -------------------------------- Implemented temporary solution to include mvel as an external module, when switchyard has not been installed. This enables BAM to be installed into AS7, although some of the switchyard/drools related examples cannot be used. Once switchyard's external dependency modules are stored as individual maven artifacts, then will pull in all the necessary modules from there, and therefore no be dependent upon switchyard being installed to also gain access to drools. > Restructure way jbossas modules are created > ------------------------------------------- > > Key: BAM-122 > URL: https://issues.jboss.org/browse/BAM-122 > Project: Business Activity Monitoring > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Use a similar approach to switchyard to build the modules, and allow external modules (e.g. drools, mvel) where they don't already exist. So only overwrite the external modules if not already present. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-90) intermittent error when restarting the SwitchYard with BAM distro and sla sample installed.

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-90?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-90: -------------------------- Fix Version/s: 1.0.0.M5 (was: 1.0.0.M4) > intermittent error when restarting the SwitchYard with BAM distro and sla sample installed. > ------------------------------------------------------------------------------------------- > > Key: BAM-90 > URL: https://issues.jboss.org/browse/BAM-90 > Project: Business Activity Monitoring > Issue Type: Bug > Reporter: Jeff Yu > Assignee: Gary Brown > Priority: Minor > Fix For: 1.0.0.M5 > > Attachments: server.log > > > Note, sometimes I got this problem, it is not always.. :-( > reproduce steps: > 1) installed the BAM distro in SwitchYard 0.6 beta2 (by running the mvn install in distro) > 2) started the SwitchYard. (with --server-config=standalone-full.xml) > 3) deploy the sla sample into SwitchYard > 4) Stop the SwitchYard > 5) restart the SwitchYard again. > 6) log in the gadget server with 'admin'(default account) > I saw two sort of problems, one is the server couldn't be restarted successfully,, specifically it got hanged on the sla-monitor.war, and then am told it was deployed failed, and then rollback everything. > 2) sometimes I got 'out of heap' error when I log in the gadget 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-145) Add support for loading the ontologies for the distro

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-145?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-145. ------------------------------- > Add support for loading the ontologies for the distro > ----------------------------------------------------- > > Key: SRAMP-145 > URL: https://issues.jboss.org/browse/SRAMP-145 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Hi Eric, in the build.xml I added a target upload.seeddata.fromsrc. This loads the deployment-status.owl file. We probably need a distro version of this as well. Can you take care of that? > <target name="upload.seeddata.fromsrc" unless="is.dist"> > <echo>Seeding the S-RAMP repo</echo> > <java classname="org.overlord.sramp.shell.commands.ontology.UploadOntologyCommand"> > <classpath refid="client-classpath" /> > </java> > </target> -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-145) Add support for loading the ontologies for the distro

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-145?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-145. --------------------------------- Resolution: Done > Add support for loading the ontologies for the distro > ----------------------------------------------------- > > Key: SRAMP-145 > URL: https://issues.jboss.org/browse/SRAMP-145 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Hi Eric, in the build.xml I added a target upload.seeddata.fromsrc. This loads the deployment-status.owl file. We probably need a distro version of this as well. Can you take care of that? > <target name="upload.seeddata.fromsrc" unless="is.dist"> > <echo>Seeding the S-RAMP repo</echo> > <java classname="org.overlord.sramp.shell.commands.ontology.UploadOntologyCommand"> > <classpath refid="client-classpath" /> > </java> > </target> -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-145) Add support for loading the ontologies for the distro

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-145?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-145: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/181, https://github.com/Governance/s-ramp-distro/pull/17 > Add support for loading the ontologies for the distro > ----------------------------------------------------- > > Key: SRAMP-145 > URL: https://issues.jboss.org/browse/SRAMP-145 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Hi Eric, in the build.xml I added a target upload.seeddata.fromsrc. This loads the deployment-status.owl file. We probably need a distro version of this as well. Can you take care of that? > <target name="upload.seeddata.fromsrc" unless="is.dist"> > <echo>Seeding the S-RAMP repo</echo> > <java classname="org.overlord.sramp.shell.commands.ontology.UploadOntologyCommand"> > <classpath refid="client-classpath" /> > </java> > </target> -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-17) Turn off the log for gadget server shindig integration layer.

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/GADGETS-17?page=com.atlassian.jira.plugin... ] Jeff Yu updated GADGETS-17: --------------------------- Fix Version/s: 1.0.0.M5 (was: 1.0.0.M4) > Turn off the log for gadget server shindig integration layer. > ------------------------------------------------------------- > > Key: GADGETS-17 > URL: https://issues.jboss.org/browse/GADGETS-17 > Project: Gadget Server and Gadgets > Issue Type: Bug > Components: Gadget Server > Affects Versions: 1.0.0.M1 > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0.0.M5 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-34) Situations gadget should present context and properties information to user

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/GADGETS-34?page=com.atlassian.jira.plugin... ] Jeff Yu resolved GADGETS-34. ---------------------------- Resolution: Done > Situations gadget should present context and properties information to user > --------------------------------------------------------------------------- > > Key: GADGETS-34 > URL: https://issues.jboss.org/browse/GADGETS-34 > Project: Gadget Server and Gadgets > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Jeff Yu > Fix For: 1.0.0.M4 > > > The Situation gadget currently displays the descriptive fields associated with a situation, and in the future may provide a more automated means of navigating (or focusing) other gadgets on a business transaction(s) associated with the situation. > However in the short term it would be good if a user could access information about the context (i.e. correlation identifier(s)) and properties associated with the activities that caused the situation. > These details will be added to the Situation object (BAM-115). They shouldn't necessarily be displayed in the table, due to limited space, but possibly could be visible in a tooltip or a popup menu action associated with the situation entry. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-145) Add support for loading the ontologies for the distro

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-145: ------------------------------- Summary: Add support for loading the ontologies for the distro Key: SRAMP-145 URL: https://issues.jboss.org/browse/SRAMP-145 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Governance Reporter: Kurt Stam Assignee: Eric Wittmann Fix For: Milestone 4 Hi Eric, in the build.xml I added a target upload.seeddata.fromsrc. This loads the deployment-status.owl file. We probably need a distro version of this as well. Can you take care of that? <target name="upload.seeddata.fromsrc" unless="is.dist"> <echo>Seeding the S-RAMP repo</echo> <java classname="org.overlord.sramp.shell.commands.ontology.UploadOntologyCommand"> <classpath refid="client-classpath" /> </java> </target> -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2013