[JBoss JIRA] (LOGTOOL-114) Add annotation to help reporting add links to resolution topics
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-114?page=com.atlassian.jira.plugi... ]
James Perkins updated LOGTOOL-114:
----------------------------------
Description:
It may be useful to add links to generated reports.
For example in the below adoc report the {{CODE0001}} could be changed to a link which points to a resolution document.
||Message Id||Message||Log Level||Return Type||
|CODE0001| Failed to start container: %s|—|java.lang.String|
Resolution documents could be documents in the projects or full URL's. The annotation can be placed on the top level interface meaning every method will be generated or placed on a method.
{code:title=Examples}
@BaseURL("http://foo.com/codes#") // for anchors
@BaseURL("http://foo.com/codes/") // for pages
{code}
{code}
@ResolutionDoc(path = "CODE0001.adoc")
@ResolutionDoc(url = "http://foo.com/code", suffix = ".adoc")
@ResolutionDoc(suffix = ".adoc")
{code}
For {{suffix}} the generated id would be used. In the examples above the file name would be {{CODE0001.adoc}}.
was:
It may be useful to add links to generated reports.
For example in the below adoc report the {{CODE0001}} could be changed to a link which points to a resolution document.
||Message Id||Message||Log Level||Return Type||
|CODE0001| Failed to start container: %s|—|java.lang.String|
Resolution documents could be documents in the projects or full URL's. The annotation can be placed on the top level interface meaning every method will be generated or placed on a method.
{code|title=Examples}
@BaseURL("http://foo.com/codes#") // for anchors
@BaseURL("http://foo.com/codes/") // for pages
{code}
{code}
@ResolutionDoc(path = "CODE0001.adoc")
@ResolutionDoc(url = "http://foo.com/code", suffix = ".adoc")
@ResolutionDoc(suffix = ".adoc")
{code}
For {{suffix}} the generated id would be used. In the examples above the file name would be {{CODE0001.adoc}}.
> Add annotation to help reporting add links to resolution topics
> ---------------------------------------------------------------
>
> Key: LOGTOOL-114
> URL: https://issues.jboss.org/browse/LOGTOOL-114
> Project: Log Tool
> Issue Type: Enhancement
> Reporter: James Perkins
>
> It may be useful to add links to generated reports.
> For example in the below adoc report the {{CODE0001}} could be changed to a link which points to a resolution document.
> ||Message Id||Message||Log Level||Return Type||
> |CODE0001| Failed to start container: %s|—|java.lang.String|
> Resolution documents could be documents in the projects or full URL's. The annotation can be placed on the top level interface meaning every method will be generated or placed on a method.
> {code:title=Examples}
> @BaseURL("http://foo.com/codes#") // for anchors
> @BaseURL("http://foo.com/codes/") // for pages
> {code}
> {code}
> @ResolutionDoc(path = "CODE0001.adoc")
> @ResolutionDoc(url = "http://foo.com/code", suffix = ".adoc")
> @ResolutionDoc(suffix = ".adoc")
> {code}
> For {{suffix}} the generated id would be used. In the examples above the file name would be {{CODE0001.adoc}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (LOGTOOL-114) Add annotation to help reporting add links to resolution topics
by James Perkins (JIRA)
James Perkins created LOGTOOL-114:
-------------------------------------
Summary: Add annotation to help reporting add links to resolution topics
Key: LOGTOOL-114
URL: https://issues.jboss.org/browse/LOGTOOL-114
Project: Log Tool
Issue Type: Enhancement
Reporter: James Perkins
It may be useful to add links to generated reports.
For example in the below adoc report the {{CODE0001}} could be changed to a link which points to a resolution document.
||Message Id||Message||Log Level||Return Type||
|CODE0001| Failed to start container: %s|—|java.lang.String|
Resolution documents could be documents in the projects or full URL's. The annotation can be placed on the top level interface meaning every method will be generated or placed on a method.
{code|title=Examples}
@BaseURL("http://foo.com/codes#") // for anchors
@BaseURL("http://foo.com/codes/") // for pages
{code}
{code}
@ResolutionDoc(path = "CODE0001.adoc")
@ResolutionDoc(url = "http://foo.com/code", suffix = ".adoc")
@ResolutionDoc(suffix = ".adoc")
{code}
For {{suffix}} the generated id would be used. In the examples above the file name would be {{CODE0001.adoc}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1715) HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1715?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1715:
------------------------------------------
Note that if we go into the "shutdownServers" logic we need to consider what the correct default timeout in the HostRunningModeControl should be. I believe zero is fine (shutdown immediately).
> HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1715
> URL: https://issues.jboss.org/browse/WFCORE-1715
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.2.0.Final, 3.0.0.Alpha5
> Reporter: Yeray Santana Borges
> Fix For: 3.0.0.Alpha6
>
>
> The ReloadContext created by HostProcessReloadHandler sets the HostRunningModeControl's restartMode but then it never gets restored to the default value. The doReload() method of the ReloadContext should restore it. This ensures the ServerInventoryService.stop() only uses the value set by HostProcessReloadHandler once, for that one reload.
> A concern here is that ServerInventoryService only goes into its "shutdownServers" logic if the restartMode == RestartMode.SERVERS. Which, due to this bug, it will be following any HC reload. But if we restore the default value of restartMode, that is null, and null != RestartMode.SERVERS. So the ""shutdownServers" logic will no longer kick in. But should it? Should the default value of restartMode be "null"? Or should it be RestartMode.SERVERS? If we change the default from null, then the behavior when no reload has happened will change.
> Basically we need to decide whether the "shutdownServers" logic should happen by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1715) HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1715?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1715:
-------------------------------------
Description:
The ReloadContext created by HostProcessReloadHandler sets the HostRunningModeControl's restartMode but then it never gets restored to the default value. The doReload() method of the ReloadContext should restore it. This ensures the ServerInventoryService.stop() only uses the value set by HostProcessReloadHandler once, for that one reload.
A concern here is that ServerInventoryService only goes into its "shutdownServers" logic if the restartMode == RestartMode.SERVERS. Which, due to this bug, it will be following any HC reload. But if we restore the default value of restartMode, that is null, and null != RestartMode.SERVERS. So the ""shutdownServers" logic will no longer kick in. But should it? Should the default value of restartMode be "null"? Or should it be RestartMode.SERVERS? If we change the default from null, then the behavior when no reload has happened will change.
Basically we need to decide whether the "shutdownServers" logic should happen by default.
was:
The ReloadContext created by HostProcessReloadHandler sets the restartMode but then it never gets restored to the default value. The doReload() method of the ReloadContext should restore it. This ensures the ServerInventoryService.stop() only uses the value set by HostProcessReloadHandler once, for that one reload.
A concern here is that ServerInventoryService only goes into its "shutdownServers" logic if the restartMode == RestartMode.SERVERS. Which, due to this bug, it will be following any HC reload. But if we restore the default value of restartMode, that is null, and null != RestartMode.SERVERS. So the ""shutdownServers" logic will no longer kick in. But should it? Should the default value of restartMode be "null"? Or should it be RestartMode.SERVERS? If we change the default from null, then the behavior when no reload has happened will change.
Basically we need to decide whether the "shutdownServers" logic should happen by default.
> HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1715
> URL: https://issues.jboss.org/browse/WFCORE-1715
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.2.0.Final, 3.0.0.Alpha5
> Reporter: Yeray Santana Borges
> Fix For: 3.0.0.Alpha6
>
>
> The ReloadContext created by HostProcessReloadHandler sets the HostRunningModeControl's restartMode but then it never gets restored to the default value. The doReload() method of the ReloadContext should restore it. This ensures the ServerInventoryService.stop() only uses the value set by HostProcessReloadHandler once, for that one reload.
> A concern here is that ServerInventoryService only goes into its "shutdownServers" logic if the restartMode == RestartMode.SERVERS. Which, due to this bug, it will be following any HC reload. But if we restore the default value of restartMode, that is null, and null != RestartMode.SERVERS. So the ""shutdownServers" logic will no longer kick in. But should it? Should the default value of restartMode be "null"? Or should it be RestartMode.SERVERS? If we change the default from null, then the behavior when no reload has happened will change.
> Basically we need to decide whether the "shutdownServers" logic should happen by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1715) HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1715:
----------------------------------------
Summary: HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
Key: WFCORE-1715
URL: https://issues.jboss.org/browse/WFCORE-1715
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha5, 2.2.0.Final
Reporter: Yeray Santana Borges
Fix For: 3.0.0.Alpha6
The ReloadContext created by HostProcessReloadHandler sets the restartMode but then it never gets restored to the default value. The doReload() method of the ReloadContext should restore it. This ensures the ServerInventoryService.stop() only uses the value set by HostProcessReloadHandler once, for that one reload.
A concern here is that ServerInventoryService only goes into its "shutdownServers" logic if the restartMode == RestartMode.SERVERS. Which, due to this bug, it will be following any HC reload. But if we restore the default value of restartMode, that is null, and null != RestartMode.SERVERS. So the ""shutdownServers" logic will no longer kick in. But should it? Should the default value of restartMode be "null"? Or should it be RestartMode.SERVERS? If we change the default from null, then the behavior when no reload has happened will change.
Basically we need to decide whether the "shutdownServers" logic should happen by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-785) no MVEL debugger registered to handle breakpoint
by Tianwei Chen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-785?page=com.atlassian.jira.plugin... ]
Tianwei Chen commented on DROOLS-785:
-------------------------------------
I degraded Eclipse to Mars2, and reinstalled the plugin. It works now. Thanks.
> no MVEL debugger registered to handle breakpoint
> ------------------------------------------------
>
> Key: DROOLS-785
> URL: https://issues.jboss.org/browse/DROOLS-785
> Project: Drools
> Issue Type: Bug
> Components: core engine, eclipse plugin
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Win 7 64, JBoss Developer Studio Version: 8.1.0.GA, JBossAS Tools 3.0.3.Final-v20150325-0035-B129, Java 1.7.0_76
> Reporter: Maurice Betzel
> Assignee: Petr Široký
> Priority: Blocker
>
> Executing Drools-Examples 6.0.2.Final from github containing MVEL dialect resulted in runtime exception:
> 2015-05-16 14:35:28,603 [main] INFO Found kmodule: file:/C:/Users/x3.mbetzel/Development/workspaces/jboss-drools/drools-examples-62/target/classes/META-INF/kmodule.xml
> 2015-05-16 14:35:28,999 [main] INFO KieModule was added: FileKieModule[releaseId=org.drools:drools-examples:6.2.0.Final,file=C:\Users\x3.mbetzel\Development\workspaces\jboss-drools\drools-examples-62\target\classes]
> Exception in thread "main" java.lang.RuntimeException: no debugger registered to handle breakpoint
> at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76)
> 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:930)
> at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:481)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:77)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:379)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:290)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:253)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:370)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:289)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1480)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1422)
> at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:65)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1250) Drools Sample.drl is broken
by Tianwei Chen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1250?page=com.atlassian.jira.plugi... ]
Tianwei Chen commented on DROOLS-1250:
--------------------------------------
I degraded Eclipse to Mars2, and reinstalled the plugin. It works now. Thanks.
> Drools Sample.drl is broken
> ---------------------------
>
> Key: DROOLS-1250
> URL: https://issues.jboss.org/browse/DROOLS-1250
> Project: Drools
> Issue Type: Feature Request
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tianwei Chen
> Assignee: Robert (Bob) Brodt
>
> Hello, I use drools plugin (6.4.0.Final) in Eclipse Neon. I followed the wizard to create a drools project with some example files. After the step were done, Eclipse highlighted errors at the two rules in the Sample.drl file. Here is one of the errors:
> Multiple markers at this line
> - com.sample.DroolsTest.Message cannot be resolved to a type
> - org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> - Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> - org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> - KnowledgeHelper cannot be resolved to a type
> - Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> - Message.GOODBYE cannot be resolved to a type
> - org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> - java.lang.Exception cannot be resolved to a type
> When I ran DroolsTest.java, I got the following error:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575)
> It seems like an library path issue. Please help!
> Thank you very much!
> Tianwei Chen
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1250) Drools Sample.drl is broken
by Tianwei Chen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1250?page=com.atlassian.jira.plugi... ]
Tianwei Chen closed DROOLS-1250.
--------------------------------
Resolution: Done
> Drools Sample.drl is broken
> ---------------------------
>
> Key: DROOLS-1250
> URL: https://issues.jboss.org/browse/DROOLS-1250
> Project: Drools
> Issue Type: Feature Request
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tianwei Chen
> Assignee: Robert (Bob) Brodt
>
> Hello, I use drools plugin (6.4.0.Final) in Eclipse Neon. I followed the wizard to create a drools project with some example files. After the step were done, Eclipse highlighted errors at the two rules in the Sample.drl file. Here is one of the errors:
> Multiple markers at this line
> - com.sample.DroolsTest.Message cannot be resolved to a type
> - org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> - Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> - org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> - KnowledgeHelper cannot be resolved to a type
> - Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> - Message.GOODBYE cannot be resolved to a type
> - org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> - java.lang.Exception cannot be resolved to a type
> When I ran DroolsTest.java, I got the following error:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575)
> It seems like an library path issue. Please help!
> Thank you very much!
> Tianwei Chen
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months