[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1825:
-----------------------------------
Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> [Guided Decision Table] Ability to change HIT policy in a decision table anytime
> --------------------------------------------------------------------------------
>
> Key: DROOLS-1825
> URL: https://issues.jboss.org/browse/DROOLS-1825
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor
> Affects Versions: 7.1.0.Beta2
> Reporter: Ivo Bek
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: UX
> Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy.
> Thus, it should be possible to change HIT policy in a decision table anytime.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1609:
-----------------------------------
Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> Augment FEEL AST node at compilation with return type
> -----------------------------------------------------
>
> Key: DROOLS-1609
> URL: https://issues.jboss.org/browse/DROOLS-1609
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Minor
>
> This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (DROOLS-1959) [DMN Editor] Extend marshaller support for Expressions
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1959?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1959:
-----------------------------------
Sprint: 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> [DMN Editor] Extend marshaller support for Expressions
> ------------------------------------------------------
>
> Key: DROOLS-1959
> URL: https://issues.jboss.org/browse/DROOLS-1959
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
> When UI support for DMN Expression is available, the marshaller shall be extended to support marshalling between DMN xml and the stunner representation of the expression.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (DROOLS-1946) DMN Editor
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1946:
-----------------------------------
Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> DMN Editor
> ----------
>
> Key: DROOLS-1946
> URL: https://issues.jboss.org/browse/DROOLS-1946
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Labels: UX
> Fix For: 7.6.0.Final
>
>
> Place holder for all DMN Editor related activities
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (WFCORE-3484) Nonintuitive error message when for loop is used inside of if/try/batch constructs
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3484?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-3484:
----------------------------------------------
You have revealed multiple issues there:
1) Variables can't be set and used inside if/try/for.
For example:
if (outcome != success) of /system-property=test:read-resource
set foo=bar
echo $foo
==> You will get an exception. This is the same exception that you are getting when echoing propName
2) There is no check when a redirection is already active and a new redirection is used:e.g.: try followed by if, if followed by if, ... The CLI accepts the new redirection silently.
3) Command name completion is not helpful, although a redirection is active (eg: if), other redirections are proposed (try, for).
> Nonintuitive error message when for loop is used inside of if/try/batch constructs
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-3484
> URL: https://issues.jboss.org/browse/WFCORE-3484
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha5
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> CLI enables to use for loop construct for looping over commands or operations. See WFCORE-3236 for details. Because of design limitations of CLI, using of for loop is not supported inside of if, try, for and batch constructs. However if you try to do that, error message is not intuitive in all cases and it is difficult to find out why the code does not work.
> Let's see on real examples.
> {code:title=Using for inside if}
> [standalone@embedded /] if (outcome != success) of /system-property=test:read-resource
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> [standalone@embedded /] echo $propName
> Unrecognized variable propName
> {code}
> As you can see in the example, when you write aforementioned commands into the CLI, no error is thrown until you use the variable declared in the for construct. Additionally the error message is not saying anything about that using of "for" is not allowed inside of "if".
> {code:title=Using for inside try}
> [standalone@embedded /] try
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> [standalone@embedded /] echo $propName
> Unrecognized variable propName
> {code}
> The same applies here as for "if" case.
> {code:title=Using for inside batch}
> [standalone@embedded /] batch
> [standalone@embedded / #] for propName in :read-children-names(child-type=system-property)
> The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).
> {code}
> In the batch case, the error message is better (it says that command is not available), but still it is not clear why the command is not available.
> {code:title=Using for inside for}
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> for is not allowed while in for block
> {code}
> Using of nested for loops generates nice error message which clearly explains what is wrong. All other cases should throw similar error.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (WFLY-9643) Getting Internal server error on exception if the rest service content type is "application/xml"
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-9643?page=com.atlassian.jira.plugin.... ]
Marek Kopecký updated WFLY-9643:
--------------------------------
Steps to Reproduce:
1) create a rest service
{code:java}
@RestController
@RequestMapping({"security/testController"})
public class TestController
{
@RequestMapping(value={"/applicationList"}, method={org.springframework.web.bind.annotation.RequestMethod.GET}, headers={"Accept=application/xml"} , produces=MediaType.APPLICATION_JSON_VALUE)
public TreeDataProvider getListOfApplication()
{
return new TreeDataProvider();
}
}
{code}
2) Create a Spring interceptor and throw an exception
3) create a spring exception handler to return exception as json
was:
1) create a rest service
@RestController
@RequestMapping({"security/testController"})
public class TestController
{
@RequestMapping(value={"/applicationList"}, method={org.springframework.web.bind.annotation.RequestMethod.GET}, headers={"Accept=application/xml"} , produces=MediaType.APPLICATION_JSON_VALUE)
public TreeDataProvider getListOfApplication()
{
return new TreeDataProvider();
}
}
2) Create a Spring interceptor and throw an exception
3) create a spring exception handler to return exception as json
> Getting Internal server error on exception if the rest service content type is "application/xml"
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-9643
> URL: https://issues.jboss.org/browse/WFLY-9643
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Gopal krishna
> Assignee: Alessio Soldano
>
> We are getting Internal server error if any exception is thrown from spring interceptor when rest API header is set as "application/xml". This works if the rest API header is set as "application/json".
> we didnt see this issue in jboss 7 and WAS
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (WFCORE-3484) Nonintuitive error message when for loop is used inside of if/try/batch constructs
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3484?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise moved WFLY-9621 to WFCORE-3484:
----------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-3484 (was: WFLY-9621)
Component/s: CLI
(was: CLI)
Affects Version/s: 4.0.0.Alpha5
(was: 11.0.0.Final)
> Nonintuitive error message when for loop is used inside of if/try/batch constructs
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-3484
> URL: https://issues.jboss.org/browse/WFCORE-3484
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha5
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> CLI enables to use for loop construct for looping over commands or operations. See WFCORE-3236 for details. Because of design limitations of CLI, using of for loop is not supported inside of if, try, for and batch constructs. However if you try to do that, error message is not intuitive in all cases and it is difficult to find out why the code does not work.
> Let's see on real examples.
> {code:title=Using for inside if}
> [standalone@embedded /] if (outcome != success) of /system-property=test:read-resource
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> [standalone@embedded /] echo $propName
> Unrecognized variable propName
> {code}
> As you can see in the example, when you write aforementioned commands into the CLI, no error is thrown until you use the variable declared in the for construct. Additionally the error message is not saying anything about that using of "for" is not allowed inside of "if".
> {code:title=Using for inside try}
> [standalone@embedded /] try
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> [standalone@embedded /] echo $propName
> Unrecognized variable propName
> {code}
> The same applies here as for "if" case.
> {code:title=Using for inside batch}
> [standalone@embedded /] batch
> [standalone@embedded / #] for propName in :read-children-names(child-type=system-property)
> The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).
> {code}
> In the batch case, the error message is better (it says that command is not available), but still it is not clear why the command is not available.
> {code:title=Using for inside for}
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> [standalone@embedded /] for propName in :read-children-names(child-type=system-property)
> for is not allowed while in for block
> {code}
> Using of nested for loops generates nice error message which clearly explains what is wrong. All other cases should throw similar error.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (WFLY-9646) Wsconsume is not able to generate jar file from wsdl
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-9646?page=com.atlassian.jira.plugin.... ]
Marek Kopecký updated WFLY-9646:
--------------------------------
Component/s: Scripts
> Wsconsume is not able to generate jar file from wsdl
> ----------------------------------------------------
>
> Key: WFLY-9646
> URL: https://issues.jboss.org/browse/WFLY-9646
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Web Services
> Reporter: Marek Kopecký
> Assignee: Alessio Soldano
> Priority: Blocker
>
> *Description:*
> Wsconsume is able to generate jar file from wsdl on WildFly 11. On WildFly master, wsconsume doesn't create any files in "out" folder. It leads to Exception from wsdl2java tool.
> *Steps to reproduce:*
> # cd $\{JBOSS_HOME\}/bin
> # # download Echo1.wsdl, Echo1Service.wsdl and Echo1Service_schema1.xsd files, these files are attached to this jira
> # mkdir out
> # ./wsconsume.sh -j wsClientShort.jar -p org.jboss.test.script -o out Echo1Service.wsdl
> *Actual results:*
> {noformat}
> [mkopecky@dhcp-10-40-4-226 bin]$ ./wsconsume.sh -j wsClientShort.jar -p org.jboss.test.script -o out Echo1Service.wsdl
> Could not find log4j.properties or log4j.xml configuration, logging to console.
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -clientjar wsClientShort.jar -compile -exsh false -p org.jboss.test.script -d /home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583 -verbose -classdir /home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out -allowElementReferences file:/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/Echo1Service.wsdl
> wsdl2java - Apache CXF 3.1.12
> JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava
> org.apache.cxf.tools.common.ToolException: java.security.AccessControlException: access denied ("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583/org/jboss/test/script/package-info.java" "read")
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:423)
> at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:313)
> at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:298)
> at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:108)
> at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:96)
> at org.jboss.modules.Module.run(Module.java:344)
> at org.jboss.modules.Main.main(Main.java:525)
> Caused by: java.security.AccessControlException: access denied ("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583/org/jboss/test/script/package-info.java" "read")
> at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
> at java.security.AccessController.checkPermission(AccessController.java:884)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
> at java.io.File.isDirectory(File.java:844)
> at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:69)
> at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:64)
> at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromFiles(JavacFileManager.java:785)
> at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromStrings(JavacFileManager.java:185)
> at org.apache.cxf.common.util.Compiler.useJava6Compiler(Compiler.java:192)
> at org.apache.cxf.common.util.Compiler.compileFiles(Compiler.java:141)
> at org.apache.cxf.tools.common.ClassUtils.compile(ClassUtils.java:123)
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:306)
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
> at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:415)
> ... 8 more
> [mkopecky@dhcp-10-40-4-226 bin]$ ll out/
> total 0
> [mkopecky@dhcp-10-40-4-226 bin]$
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (WFLY-9646) Wsconsume is not able to generate jar file from wsdl
by Marek Kopecký (JIRA)
Marek Kopecký created WFLY-9646:
-----------------------------------
Summary: Wsconsume is not able to generate jar file from wsdl
Key: WFLY-9646
URL: https://issues.jboss.org/browse/WFLY-9646
Project: WildFly
Issue Type: Bug
Components: Web Services
Reporter: Marek Kopecký
Assignee: Alessio Soldano
Priority: Blocker
*Description:*
Wsconsume is able to generate jar file from wsdl on WildFly 11. On WildFly master, wsconsume doesn't create any files in "out" folder. It leads to Exception from wsdl2java tool.
*Steps to reproduce:*
# cd $\{JBOSS_HOME\}/bin
# # download Echo1.wsdl, Echo1Service.wsdl and Echo1Service_schema1.xsd files, these files are attached to this jira
# mkdir out
# ./wsconsume.sh -j wsClientShort.jar -p org.jboss.test.script -o out Echo1Service.wsdl
*Actual results:*
{noformat}
[mkopecky@dhcp-10-40-4-226 bin]$ ./wsconsume.sh -j wsClientShort.jar -p org.jboss.test.script -o out Echo1Service.wsdl
Could not find log4j.properties or log4j.xml configuration, logging to console.
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -clientjar wsClientShort.jar -compile -exsh false -p org.jboss.test.script -d /home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583 -verbose -classdir /home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out -allowElementReferences file:/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/Echo1Service.wsdl
wsdl2java - Apache CXF 3.1.12
JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava
org.apache.cxf.tools.common.ToolException: java.security.AccessControlException: access denied ("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583/org/jboss/test/script/package-info.java" "read")
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:423)
at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:313)
at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:298)
at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:108)
at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:96)
at org.jboss.modules.Module.run(Module.java:344)
at org.jboss.modules.Main.main(Main.java:525)
Caused by: java.security.AccessControlException: access denied ("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583/org/jboss/test/script/package-info.java" "read")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
at java.security.AccessController.checkPermission(AccessController.java:884)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
at java.io.File.isDirectory(File.java:844)
at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:69)
at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:64)
at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromFiles(JavacFileManager.java:785)
at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromStrings(JavacFileManager.java:185)
at org.apache.cxf.common.util.Compiler.useJava6Compiler(Compiler.java:192)
at org.apache.cxf.common.util.Compiler.compileFiles(Compiler.java:141)
at org.apache.cxf.tools.common.ClassUtils.compile(ClassUtils.java:123)
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:306)
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:415)
... 8 more
[mkopecky@dhcp-10-40-4-226 bin]$ ll out/
total 0
[mkopecky@dhcp-10-40-4-226 bin]$
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months