JRules 设置问题
通过教程来掌握 JRules。在第二个教程的第 5 部分中,它要求您使用 cmd 通过 RetePlus 运行规则
在“运行”菜单上,单击“运行”。 在“运行”对话框中,选择“规则项目”启动配置“ruleediting-start-configuration”。 单击运行。
然而,每次我尝试运行它时,都会弹出一个框,告诉我在“启动”期间发生内部错误,
没有其他实际输出。
我已经导入了完整的教程,它给出了相同的错误,这表明这将是配置问题。我已经更改了运行时 JRE。
有没有人在 JRules 或 Eclipse 中遇到过这个
编辑
我确实设法获得了异常堆栈跟踪:
堆栈跟踪 java.lang.AbstractMethodError 在 com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.setDocumentInfo(DOM2TO.java:373) 在 com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:127) 在 com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:94) 在 com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:661) 在 com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:707) 在 com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.writeDocumentInternal(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.access$000(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase$1.run(来源未知) 在 java.security.AccessController.doPrivileged(本机方法) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.writeDocument(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.write(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase.xmlEntry(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase.fillMetadata(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase.fillResources(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase.fillArchive(来源未知) 在 ilog.rules.engine.IlrRulesetArchiveBuilder.fillArchive(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase.generateArchive(来源未知) 在 ilog.rules.archive.IlrRulesetArchiveBuilderBase.generate(来源未知) 在 ilog.rules.studio.model.archive.IlrRulesetArchiveExporter.export(来源未知) 在 ilog.rules.studio.launching.IlrProjectLaunchConfigurationDelegate.launch(来源未知) 在 org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:639) 在 org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:565) 在 org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:754) 在 org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:944) 在 org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
会话数据 eclipse.buildId=M20070212-1330 java.version=1.6.0_24 java.vendor=太阳微系统公司 BootLoader 常量:OS=win32、ARCH=x86、WS=win32、NL=en_US 框架参数:-perspective ilog.rules.studio.ui.perspectives.RuleEditingPerspective 命令行参数:-os win32 -ws win32 -arch x86 -perspective ilog.rules.studio.ui.perspectives.RuleEditingPerspective
Been getting to grips with JRules doing the tutorials. During part 5 of the 2nd tutorial it ask's you to run the rules via RetePlus using the cmds
On the Run menu, click Run.
In the Run dialog, select the Rule Project launch configuration ruleediting-start-configuration.
Click Run.
However everytime I try to run it I get a pop up box telling me an internal error occurred during: "launching"
No other real output.
I have imported the completed tutorial and it gives the same error so that is suggesting that it would be configuration problem. I have changed the runtime JRE.
Has anyone encoutered this in either in JRules or Eclipse
EDIT
I did manage to get the Exception stack Trace:
Stack Trace
java.lang.AbstractMethodError
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.setDocumentInfo(DOM2TO.java:373)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:127)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:94)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:661)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:707)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.writeDocumentInternal(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.access$000(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.writeDocument(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase$XmlBase.write(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase.xmlEntry(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase.fillMetadata(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase.fillResources(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase.fillArchive(Unknown Source)
at ilog.rules.engine.IlrRulesetArchiveBuilder.fillArchive(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase.generateArchive(Unknown Source)
at ilog.rules.archive.IlrRulesetArchiveBuilderBase.generate(Unknown Source)
at ilog.rules.studio.model.archive.IlrRulesetArchiveExporter.export(Unknown Source)
at ilog.rules.studio.launching.IlrProjectLaunchConfigurationDelegate.launch(Unknown Source)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:639)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:565)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:754)
at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:944)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Session Data
eclipse.buildId=M20070212-1330
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -perspective ilog.rules.studio.ui.perspectives.RuleEditingPerspective
Command-line arguments: -os win32 -ws win32 -arch x86 -perspective ilog.rules.studio.ui.perspectives.RuleEditingPerspective
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
JRE 问题使用捆绑的 JRE 重新安装了软件并且它可以工作。一定是使用 1.6 JDK 作为编译器的问题。
JRE issue reinstalled the software with bundled JRE and it worked. Must be an issue with using the 1.6 JDK as its compiler.