September 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-538) password encryption in overlord commons

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-538?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-538. ------------------------------- Fix Version/s: 0.5.0.Final Resolution: Done > password encryption in overlord commons > --------------------------------------- > > Key: SRAMP-538 > URL: https://issues.jboss.org/browse/SRAMP-538 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0.Final > > > Adapt the installers and distribution packages to the new changes done in overlord commons to encrypt the overlord.properties passwords: > Related overlord-commons jira: > https://issues.jboss.org/browse/OVERLORD-128 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-561) Support Fuse JMS

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-561?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-561: -------------------------------------------- This is the IRC conversation with the fuse fabric guys: <jstrachan> virchete use the JMS API [16:22] --> theute (~theute@redhat/jboss/theute) se ha unido a este canal. [16:22] <jstrachan> Queue queue = new ActiveMQ("any.name.you.like") [16:22] <jstrachan> Queue queue = new ActiveMQQueue("any.name.you.like") [16:23] <virchete> jstrachan but for example in JBoss EAP you need to define in the standalone-full.xml the queues and topics [16:23] <chirino> virchete: or session.createQueue("any.name.you.like") [16:23] <chirino> virchete: jboss likes to make it hard. [16:23] <chirino> :) [16:23] <virchete> jaja [16:23] <virchete> ok chrino [16:23] <chirino> with activemq things are easy. [16:23] <virchete> then you mean if [16:23] <virchete> i include the active mq features [16:24] <virchete> then using the Queue queue = new ActiveMQQueue("any.name.you.like") [16:24] <virchete> would work [16:24] <chirino> yeah. [16:24] <chirino> you have code that's using JMS already right? [16:24] <virchete> yes [16:24] <chirino> yep [16:24] <chirino> that's it > Support Fuse JMS > ---------------- > > Key: SRAMP-561 > URL: https://issues.jboss.org/browse/SRAMP-561 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > SRAMP-433 created JMS events within S-RAMP. For Tomcat, Jetty, and standalone EAP, we use an embedded ActiveMQ broker. For standalone-full EAP, we re-use the existing HornetQ JMS and JNDI resources. > Supposedly, Fuse provides ActiveMQ out-of-the-box. We should re-use that, rather than relying on the embedded broker. Investigate and figure out a way to add the JMS resources during S-RAMP installation, similar to the new configureJMS-jboss-eap-6.xslt. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-117) Pull Fabric profile tasks out of overlord-commons-dist-fuse6 and into a new overlord-commons-dist-fabric-profile

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-117?page=com.atlassian.jira.plug... ] Brett Meyer resolved OVERLORD-117. ---------------------------------- Fix Version/s: Overlord-Commons-2.0.9.Final Resolution: Done > Pull Fabric profile tasks out of overlord-commons-dist-fuse6 and into a new overlord-commons-dist-fabric-profile > ---------------------------------------------------------------------------------------------------------------- > > Key: OVERLORD-117 > URL: https://issues.jboss.org/browse/OVERLORD-117 > Project: Overlord > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > Similar to S-RAMP, DTGov, and RTGov, pull the Fabric profiles into a separate dist within overlord-commons. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plug... ] Eric Wittmann resolved OVERLORD-140. ------------------------------------ Resolution: Done > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > <link rel="icon" type="image/png" href="images/favicon.png"></link> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plug... ] Eric Wittmann closed OVERLORD-140. ---------------------------------- > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > <link rel="icon" type="image/png" href="images/favicon.png"></link> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-141) Ensure all Overlord JARs are marked as 'distributable' in web.xml

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-141?page=com.atlassian.jira.plug... ] Eric Wittmann closed OVERLORD-141. ---------------------------------- > Ensure all Overlord JARs are marked as 'distributable' in web.xml > ----------------------------------------------------------------- > > Key: OVERLORD-141 > URL: https://issues.jboss.org/browse/OVERLORD-141 > Project: Overlord > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > While configuring a clustered server consisting of 2 FSW standalone servers, I needed to manually add <distributable/> tag to all design time governance web applications (there is 5 of them). > http://docs.jboss.org/jbossas/docs/Clustering_Guide/4/html/clustering-htt... > http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html > This is a simple matter of adding the tag to all relevant web.xml files in all overlord web applications for all platforms: > overlord-commons-idp.war > s-ramp-server.war > s-ramp-ui.war > dtgov.war > dtgov-ui.war > rtgov.war > rtgov-ui.war -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plug... ] Eric Wittmann updated OVERLORD-140: ----------------------------------- Fix Version/s: Overlord-Commons-2.0.9.Final > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > <link rel="icon" type="image/png" href="images/favicon.png"></link> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-141) Ensure all Overlord JARs are marked as 'distributable' in web.xml

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-141?page=com.atlassian.jira.plug... ] Eric Wittmann updated OVERLORD-141: ----------------------------------- Fix Version/s: Overlord-Commons-2.0.9.Final > Ensure all Overlord JARs are marked as 'distributable' in web.xml > ----------------------------------------------------------------- > > Key: OVERLORD-141 > URL: https://issues.jboss.org/browse/OVERLORD-141 > Project: Overlord > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > While configuring a clustered server consisting of 2 FSW standalone servers, I needed to manually add <distributable/> tag to all design time governance web applications (there is 5 of them). > http://docs.jboss.org/jbossas/docs/Clustering_Guide/4/html/clustering-htt... > http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html > This is a simple matter of adding the tag to all relevant web.xml files in all overlord web applications for all platforms: > overlord-commons-idp.war > s-ramp-server.war > s-ramp-ui.war > dtgov.war > dtgov-ui.war > rtgov.war > rtgov-ui.war -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-141) Ensure all Overlord JARs are marked as 'distributable' in web.xml

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-141?page=com.atlassian.jira.plug... ] Eric Wittmann resolved OVERLORD-141. ------------------------------------ Resolution: Done > Ensure all Overlord JARs are marked as 'distributable' in web.xml > ----------------------------------------------------------------- > > Key: OVERLORD-141 > URL: https://issues.jboss.org/browse/OVERLORD-141 > Project: Overlord > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > While configuring a clustered server consisting of 2 FSW standalone servers, I needed to manually add <distributable/> tag to all design time governance web applications (there is 5 of them). > http://docs.jboss.org/jbossas/docs/Clustering_Guide/4/html/clustering-htt... > http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html > This is a simple matter of adding the tag to all relevant web.xml files in all overlord web applications for all platforms: > overlord-commons-idp.war > s-ramp-server.war > s-ramp-ui.war > dtgov.war > dtgov-ui.war > rtgov.war > rtgov-ui.war -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-542) If a SNAPSHOT artifact does not include a timestamp, have DeployCommand generate it

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-542?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-542: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/482 > If a SNAPSHOT artifact does not include a timestamp, have DeployCommand generate it > ----------------------------------------------------------------------------------- > > Key: SRAMP-542 > URL: https://issues.jboss.org/browse/SRAMP-542 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Minor > Fix For: 0.6.0 > > > Low priority -- we shouldn't consider this until 0.6. > DeployCommand is currently assuming a SNAPSHOT artifact includes a timestamp. But, if I'm using the CLI to deploy a locally built artifact, it won't. Consider automatically generating a timestamp if it's missing so that I can upload new snapshots. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues September 2014