February 2015 - overlord-issues - Jboss List Archives

[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: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/273 > 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 > Affects Versions: 1.0.0.M1 > 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

[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 resolved RTGOV-644. ------------------------------ Fix Version/s: 2.1.0.Beta2 Resolution: Done Thanks Ivan for the fix. > 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 > Affects Versions: 1.0.0.M1 > 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

[JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-260: ----------------------------------- Could also initially implement using https://docs.jboss.org/author/display/MODE40/Full+text+search > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-655) Allow users to provide their own query indexes

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-655?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-655: ------------------------------ Description: Through ModeShape's Workspace#getIndexManager(), allow users to provide their own query indexes during startup/runtime. If they know specific queries they may frequently run, this could be a helpful optimization. In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. Note that the MS local index currently supports single-column indexes only. was: If it's possible to configure the ModeShape query indexes during startup or runtime, allow users to provide their own. If they know specific queries they may frequently run, this could be a helpful optimization. In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. Note that the MS local index currently supports single-column indexes only. > Allow users to provide their own query indexes > ---------------------------------------------- > > Key: ARTIF-655 > URL: https://issues.jboss.org/browse/ARTIF-655 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Through ModeShape's Workspace#getIndexManager(), allow users to provide their own query indexes during startup/runtime. If they know specific queries they may frequently run, this could be a helpful optimization. > In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. > Note that the MS local index currently supports single-column indexes only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-655) Allow users to provide their own query indexes

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-655: --------------------------------- Summary: Allow users to provide their own query indexes Key: ARTIF-655 URL: https://issues.jboss.org/browse/ARTIF-655 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer If it's possible to configure the ModeShape query indexes during startup or runtime, allow users to provide their own. If they know specific queries they may frequently run, this could be a helpful optimization. In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. Note that the MS local index currently supports single-column indexes only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-654) ModeShape query indexing

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-654: --------------------------------- Summary: ModeShape query indexing Key: ARTIF-654 URL: https://issues.jboss.org/browse/ARTIF-654 Project: Artificer Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer ModeShape query indexing needs setup: https://docs.jboss.org/author/display/MODE40/Query+and+search#Queryandsea... MS local filesystem index is currently limited to single columns. So, the primary way we could use it may be limited to query-by-sramp:uuid. But realistically, that's the most frequently used one anyway... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-652) New artifact type: Microsoft Office

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-652: --------------------------------- Summary: New artifact type: Microsoft Office Key: ARTIF-652 URL: https://issues.jboss.org/browse/ARTIF-652 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-653) New artifact type: Libre Office

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-653: --------------------------------- Summary: New artifact type: Libre Office Key: ARTIF-653 URL: https://issues.jboss.org/browse/ARTIF-653 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-650) New artifact type: Videos

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-650: --------------------------------- Summary: New artifact type: Videos Key: ARTIF-650 URL: https://issues.jboss.org/browse/ARTIF-650 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-651) New artifact type: Audio

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-651: --------------------------------- Summary: New artifact type: Audio Key: ARTIF-651 URL: https://issues.jboss.org/browse/ARTIF-651 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- 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