February 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-573: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Bug) > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

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

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-421?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-421: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Enhancement) > S-ramp shell UploadArtifactCommand Add name and description > ----------------------------------------------------------- > > Key: ARTIF-421 > URL: https://issues.jboss.org/browse/ARTIF-421 > Project: Artificer > Issue Type: Sub-task > 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.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-403) S-RAMP On complete show required parameters with bold style

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-403?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-403. ----------------------------- Resolution: Out of Date > S-RAMP On complete show required parameters with bold style > ----------------------------------------------------------- > > Key: ARTIF-403 > URL: https://issues.jboss.org/browse/ARTIF-403 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Add a custom OptionRenderer for all the required options. That will allow the user to distinguish when clicking tab button, if an option is required or not. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-399) S-RAMP Shell Help Command. Add completers

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-399?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-399. ----------------------------- Resolution: Out of Date > S-RAMP Shell Help Command. Add completers > ----------------------------------------- > > Key: ARTIF-399 > URL: https://issues.jboss.org/browse/ARTIF-399 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Completers should be added to the HelpCommand in case of namespace option or command option, or when both are typed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-397) SRAMP Shell Create custom aesh help format

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-397?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-397. ----------------------------- Resolution: Out of Date > SRAMP Shell Create custom aesh help format > ------------------------------------------ > > Key: ARTIF-397 > URL: https://issues.jboss.org/browse/ARTIF-397 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > The basic Aesh settings display all the options when --help is set as argument. It is not displayed in good style and also is not displayed which of the options are required and which are optional. > Create our own s-ramp options renderer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-643) keycloak configuration should not include host/port

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-643?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-643: ----------------------------- Fix Version/s: 2.1.0.Beta2 > keycloak configuration should not include host/port > --------------------------------------------------- > > Key: RTGOV-643 > URL: https://issues.jboss.org/browse/RTGOV-643 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Jorge Morales > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Keycloak configuration should not include host and port to enable to have the server running in a VM/docker container and the host exposed port be different than the internal guest port. Otherwise, keycloak will try to redirect to that host:port being not accessible. > Change > {code} > <xsl:element name="auth-server-url" namespace="urn:jboss:domain:keycloak:1.0">http://localhost:8080/auth</xsl:element> > {code} > with: > {code} > <xsl:element name="auth-server-url" namespace="urn:jboss:domain:keycloak:1.0">/auth</xsl:element> > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-643) keycloak configuration should not include host/port

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-643?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-643: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/275 > keycloak configuration should not include host/port > --------------------------------------------------- > > Key: RTGOV-643 > URL: https://issues.jboss.org/browse/RTGOV-643 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Jorge Morales > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Keycloak configuration should not include host and port to enable to have the server running in a VM/docker container and the host exposed port be different than the internal guest port. Otherwise, keycloak will try to redirect to that host:port being not accessible. > Change > {code} > <xsl:element name="auth-server-url" namespace="urn:jboss:domain:keycloak:1.0">http://localhost:8080/auth</xsl:element> > {code} > with: > {code} > <xsl:element name="auth-server-url" namespace="urn:jboss:domain:keycloak:1.0">/auth</xsl:element> > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-643) keycloak configuration should not include host/port

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-643?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-643. ------------------------------ Resolution: Done > keycloak configuration should not include host/port > --------------------------------------------------- > > Key: RTGOV-643 > URL: https://issues.jboss.org/browse/RTGOV-643 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Jorge Morales > Assignee: Gary Brown > > Keycloak configuration should not include host and port to enable to have the server running in a VM/docker container and the host exposed port be different than the internal guest port. Otherwise, keycloak will try to redirect to that host:port being not accessible. > Change > {code} > <xsl:element name="auth-server-url" namespace="urn:jboss:domain:keycloak:1.0">http://localhost:8080/auth</xsl:element> > {code} > with: > {code} > <xsl:element name="auth-server-url" namespace="urn:jboss:domain:keycloak:1.0">/auth</xsl:element> > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back

by Gary Brown (JIRA)

Gary Brown created RTGOV-645: -------------------------------- Summary: Resubmitted message should identify source situation to enable further failures (situations) to be linked back Key: RTGOV-645 URL: https://issues.jboss.org/browse/RTGOV-645 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0 When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-644) Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables)

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-644?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-644: ----------------------------- Affects Version/s: (was: 1.0.0.M1) > Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) > -------------------------------------------------------------------------------- > > Key: RTGOV-644 > URL: https://issues.jboss.org/browse/RTGOV-644 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: Information Processor > Reporter: ivan mckinley > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > if a user wishes to execute more complex mvel scripts with variables during information processing then MVEL fails with exception, {1}. > The following test case,2, demonstrates this behaviour in action. > Recommendation is to update line 44 > https://github.com/Governance/rtgov/blob/master/modules/activity-manageme... > Object result=MVEL.executeExpression(_compiledExpression, information, new HashMap()); > {1}Exception > activity event: org.mvel2.ScriptRuntimeException: cannot assign variables; no variable resolver factory available. > at org.mvel2.integration.impl.ImmutableDefaultFactory.throwError(ImmutableDefaultFactory.java:32) > at org.mvel2.integration.impl.ImmutableDefaultFactory.createVariable(ImmutableDefaultFactory.java:36) > at org.mvel2.integration.impl.ClassImportResolverFactory.createVariable(ClassImportResolverFactory.java:61) > at org.mvel2.ast.TypedVarNode.getReducedValueAccelerated(TypedVarNode.java:70) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) > at org.mvel2.MVEL.executeExpression(MVEL.java:954) > at org.overlord.rtgov.activity.processor.mvel.MVELExpressionEvaluator.evaluate(MVELExpressionEvaluator.java:44) > at org.overlord.rtgov.activity.processor.TypeProcessor$PropertyEvaluator.process(TypeProcessor.java:310) > at org.overlord.rtgov.activity.processor.TypeProcessor.process(TypeProcessor.java:166) > at org.overlord.rtgov.activity.processor.InformationProcessor.process(InformationProcessor.java:137) > at org.overlord.rtgov.activity.processor.AbstractInformationProcessorManager.process(AbstractInformationProcessorManager.ja > {2} Test Case > @Test > public void testTransformDOM2() { > org.w3c.dom.Document doc=null; > try { > doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument(); > org.w3c.dom.Element elem=doc.createElement("test"); > doc.appendChild(elem); > elem.appendChild(doc.createTextNode("This is a test")); > } catch (Exception e) { > fail("Failed to build DOM: "+e); > } > String expression = "import javax.xml.transform.TransformerFactory; import javax.xml.transform.Transformer; import javax.xml.transform.dom.DOMSource; import javax.xml.transform.stream.StreamResult; import java.io.ByteArrayOutputStream; ByteArrayOutputStream out = new ByteArrayOutputStream(); DOMSource source = new DOMSource(this); StreamResult result = new StreamResult(out); TransformerFactory transFactory = TransformerFactory.newInstance(); Transformer transformer = transFactory.newTransformer(); transformer.transform(source, result); out.close(); return new String(out.toByteArray());"; > Object _compiledExpression=null; > _compiledExpression = MVEL.compileExpression(expression); > Object result=MVEL.executeExpression(_compiledExpression, doc); > if (result == null) { > fail("Failed to parse"); > } > System.out.println(result); -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 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 2015