[JBoss JIRA] (DROOLS-2262) [DMN Designer] DRD Grid Column width is not preserved
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2262:
--------------------------------
Steps to Reproduce:
# Create new DMN Diagram
# Add Decision node
# Open DRD of the Decision node
# In the ContextEntry Editor select Decision Table
# Change width of input entry columns and output clause column
# Save and reopen the this DRD
# Column widths will be reset.
was:
# Create new DMN Diagram
# Add Decision node
# Open DRD of the Decision node
# In the ContextEntry Editor select Decision Table
# Change width of input entry columns and output clause column
# Save and reopen the this DND
# Column widths will be reset.
> [DMN Designer] DRD Grid Column width is not preserved
> -----------------------------------------------------
>
> Key: DROOLS-2262
> URL: https://issues.jboss.org/browse/DROOLS-2262
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
>
> DND Grid Column don't preserve the width.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2262) [DMN Designer] DND Grid Column width is not preserved
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2262:
--------------------------------
Steps to Reproduce:
# Create new DMN Diagram
# Add Decision node
# Open DRD of the Decision node
# In the ContextEntry Editor select Decision Table
# Change width of input entry columns and output clause column
# Save and reopen the this DND
# Column widths will be reset.
was:
# Create new DMN Diagram
# Add Decision node
# Open DND of the Decision node
# In the ContextEntry Editor select Decision Table
# Change width of input entry columns and output clause column
# Save and reopen the this DND
# Column widths will be reset.
> [DMN Designer] DND Grid Column width is not preserved
> -----------------------------------------------------
>
> Key: DROOLS-2262
> URL: https://issues.jboss.org/browse/DROOLS-2262
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
>
> DND Grid Column don't preserve the width.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10010) @WebServlet is not working
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-10010?page=com.atlassian.jira.plugin... ]
Kabir Khan closed WFLY-10010.
-----------------------------
> @WebServlet is not working
> --------------------------
>
> Key: WFLY-10010
> URL: https://issues.jboss.org/browse/WFLY-10010
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 12.0.0.Final
> Environment: WildFly 12.0.0.Final
> JDK 9
> Reporter: Rakesh K. Cherukuri
> Assignee: Stuart Douglas
> Priority: Critical
> Labels: @WebServlet
> Attachments: web-servlet-not-working.zip
>
>
> Trying to deploy a simple web module in wildfly 12 that has one servlet with @WebServlet.
> Expectation: The servlet is available at the configured URL
> Actual : Servlet is not put into service and consequently URL gets 404
> Attached is the full module.
> NOTE : The same war file works in WildFly 11 but NOT in WildFly 12
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2424) [DMN Designer] Expression type can not be changed after cleared multiple times
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2424?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2424:
--------------------------------
Description:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1 (/)
-- 2 (/)
-- 3 (/)
was:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1 (/)
-- 2 (/)
-- 3
> [DMN Designer] Expression type can not be changed after cleared multiple times
> ------------------------------------------------------------------------------
>
> Key: DROOLS-2424
> URL: https://issues.jboss.org/browse/DROOLS-2424
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
>
> I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
> If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
> h2. Acceptance test
> - Steps to reproduce fixed, due to code changes, check at different depth level
> -- 1 (/)
> -- 2 (/)
> -- 3 (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2424) [DMN Designer] Expression type can not be changed after cleared multiple times
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2424?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2424:
--------------------------------
Description:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1 (/)
-- 2 (/)
-- 3
was:
I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
h2. Acceptance test
- Steps to reproduce fixed, due to code changes, check at different depth level
-- 1 (/)
-- 2 (x)
-- 3
> [DMN Designer] Expression type can not be changed after cleared multiple times
> ------------------------------------------------------------------------------
>
> Key: DROOLS-2424
> URL: https://issues.jboss.org/browse/DROOLS-2424
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
>
> I spotted this issue during DROOLS-2392 review, however the relation is not probable between them.
> If user changes the expression type of decision multiple times, then save and reopen the decision, the expression type can't be changed more.
> h2. Acceptance test
> - Steps to reproduce fixed, due to code changes, check at different depth level
> -- 1 (/)
> -- 2 (/)
> -- 3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2423) [DMN Designer] Clear command caches context entries
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2423?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2423:
--------------------------------
Description:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] (/)
# check scenario from DROOLS-2424 (/)
# check scenario form DROOLS-2425
# Steps to reproduce fixed - Clear the context entry at depth:
-- 0 (/)
-- 1 (/)
-- 2 (/)
-- 3 (/)
was:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] (/)
# check scenario from DROOLS-2424 (/)
# Steps to reproduce fixed - Clear the context entry at depth:
-- 0 (/)
-- 1 (/)
-- 2 (/)
-- 3 (/)
> [DMN Designer] Clear command caches context entries
> ---------------------------------------------------
>
> Key: DROOLS-2423
> URL: https://issues.jboss.org/browse/DROOLS-2423
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-03-27 11-31-01.png, Screenshot from 2018-03-27 11-31-34.png, Screenshot from 2018-03-27 11-32-52.png
>
>
> This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
> If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
> h2. Acceptance test
> # check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] (/)
> # check scenario from DROOLS-2424 (/)
> # check scenario form DROOLS-2425
> # Steps to reproduce fixed - Clear the context entry at depth:
> -- 0 (/)
> -- 1 (/)
> -- 2 (/)
> -- 3 (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10060) wsconsume script is not working on JDK9+
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10060?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10060:
---------------------------------
Priority: Blocker (was: Major)
> wsconsume script is not working on JDK9+
> ----------------------------------------
>
> Key: WFLY-10060
> URL: https://issues.jboss.org/browse/WFLY-10060
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Web Services
> Affects Versions: 12.0.0.Final
> Reporter: Jan Blizňák
> Assignee: R Searls
> Priority: Blocker
> Attachments: mywsdl2java
>
>
> wsconsume script is not working on JDK9/10/11
> {code:java}
> [jbliznak@rh wildfly-13.0.0.Alpha1-SNAPSHOT]$ java -version
> java version "9.0.4"
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [jbliznak@rh wildfly-13.0.0.Alpha1-SNAPSHOT]$ bin/wsconsume.sh https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> Could not find log4j.properties or log4j.xml configuration, logging to console.
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (jar:file:/tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/com/sun/xml/bind/main/jaxb-runtime-2.3.0.jar!/) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
> WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -compile -exsh false -d /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430 -verbose -classdir /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output -allowElementReferences https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> wsdl2java - Apache CXF 3.2.2
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:6: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebEndpoint;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:7: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebServiceClient;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:8: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebServiceFeature;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:9: error: package javax.xml.ws is not visible
> import javax.xml.ws.Service;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:3: error: package javax.jws is not visible
> import javax.jws.WebMethod;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:4: error: package javax.jws is not visible
> import javax.jws.WebParam;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:5: error: package javax.jws is not visible
> import javax.jws.WebResult;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:6: error: package javax.jws is not visible
> import javax.jws.WebService;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:7: error: package javax.jws.soap is not visible
> import javax.jws.soap.SOAPBinding;
> ^
> (package javax.jws.soap is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:72: error: cannot find symbol
> return super.getPort(EndpointInterfacePort, EndpointInterface.class);
> ^
> symbol: variable super
> location: class org.openuri._2004._04.helloworld.TestService
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:84: error: cannot find symbol
> return super.getPort(EndpointInterfacePort, EndpointInterface.class, features);
> ^
> symbol: variable super
> location: class org.openuri._2004._04.helloworld.TestService
> JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava
> org.apache.cxf.tools.common.ToolException: Failed to compile generated code
> at org.apache.cxf.impl//org.apache.cxf.tools.common.ClassUtils.compile(ClassUtils.java:125)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:303)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412)
> at org.apache.cxf.impl//org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> at org.jboss.ws.jaxws-client//org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:313)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:298)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:108)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:96)
> at org.jboss.modules.Module.runMainMethod(Module.java:348)
> at org.jboss.modules.Module.run(Module.java:328)
> at org.jboss.modules.Main.main(Main.java:557)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order attributes by alphabet
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Jeff Mesnil resolved WFCORE-1985.
---------------------------------
Fix Version/s: 5.0.0.Alpha3
Resolution: Done
> :read-resource-description operation should consistently order attributes by alphabet
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Jiri Ondrusek
> Fix For: 5.0.0.Alpha3
>
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10169) bin/client/jboss-cli-client.jar contains some useless aesh classes
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10169?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10169:
---------------------------------
Description:
bin/client/jboss-cli-client.jar contains some useless aesh classes.
jboss-cli-client.jar should contains only necessary classes. This jar file should not be unnecessarily too large.
{noformat}
./examples
./examples/Example$FooCommand.class
./examples/Example$BlueBoldRenderer.class
./examples/Example$LongOutputCommand.class
./examples/AeshGraphicsExample.class
./examples/Example$ClearCommand.class
./examples/Example$BarActivator.class
./examples/Example$TestConsoleCommand.class
./examples/AeshGraphicsExample$ExitCommand.class
./examples/AeshGraphicsExample$GraphicsCommand.class
./examples/Example$HiddenCommand.class
./examples/Example$DirectoryValidatorInvocation.class
./examples/SimpleExample.class
./examples/Example$ExampleValidatorInvocationProvider.class
./examples/Example$Base.class
./examples/Example$LessCompleter.class
./examples/Example$ExitCommand.class
./examples/Example$HideActivator.class
./examples/SimpleExample$ExitCommand.class
./examples/Example$LsCommand.class
./examples/Example$RunCommand.class
./examples/Example$Rebase.class
./examples/Example$DirectoryValidator.class
./examples/Example$ManProviderExample.class
./examples/Example.class
./examples/Example$GroupCommand.class
./examples/Example$PromptCommand.class
{noformat}
* [github sources|https://github.com/aeshell/aesh/tree/master/src/main/java/examples]
was:
bin/client/jboss-cli-client.jar contains some useless aesh classes.
jboss-cli-client.jar should contains only necessary classes. This jar file should not be unnecessarily too large.
{noformat}
./examples
./examples/Example$FooCommand.class
./examples/Example$BlueBoldRenderer.class
./examples/Example$LongOutputCommand.class
./examples/AeshGraphicsExample.class
./examples/Example$ClearCommand.class
./examples/Example$BarActivator.class
./examples/Example$TestConsoleCommand.class
./examples/AeshGraphicsExample$ExitCommand.class
./examples/AeshGraphicsExample$GraphicsCommand.class
./examples/Example$HiddenCommand.class
./examples/Example$DirectoryValidatorInvocation.class
./examples/SimpleExample.class
./examples/Example$ExampleValidatorInvocationProvider.class
./examples/Example$Base.class
./examples/Example$LessCompleter.class
./examples/Example$ExitCommand.class
./examples/Example$HideActivator.class
./examples/SimpleExample$ExitCommand.class
./examples/Example$LsCommand.class
./examples/Example$RunCommand.class
./examples/Example$Rebase.class
./examples/Example$DirectoryValidator.class
./examples/Example$ManProviderExample.class
./examples/Example.class
./examples/Example$GroupCommand.class
./examples/Example$PromptCommand.class
{noformat}
> bin/client/jboss-cli-client.jar contains some useless aesh classes
> ------------------------------------------------------------------
>
> Key: WFLY-10169
> URL: https://issues.jboss.org/browse/WFLY-10169
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
>
> bin/client/jboss-cli-client.jar contains some useless aesh classes.
> jboss-cli-client.jar should contains only necessary classes. This jar file should not be unnecessarily too large.
> {noformat}
> ./examples
> ./examples/Example$FooCommand.class
> ./examples/Example$BlueBoldRenderer.class
> ./examples/Example$LongOutputCommand.class
> ./examples/AeshGraphicsExample.class
> ./examples/Example$ClearCommand.class
> ./examples/Example$BarActivator.class
> ./examples/Example$TestConsoleCommand.class
> ./examples/AeshGraphicsExample$ExitCommand.class
> ./examples/AeshGraphicsExample$GraphicsCommand.class
> ./examples/Example$HiddenCommand.class
> ./examples/Example$DirectoryValidatorInvocation.class
> ./examples/SimpleExample.class
> ./examples/Example$ExampleValidatorInvocationProvider.class
> ./examples/Example$Base.class
> ./examples/Example$LessCompleter.class
> ./examples/Example$ExitCommand.class
> ./examples/Example$HideActivator.class
> ./examples/SimpleExample$ExitCommand.class
> ./examples/Example$LsCommand.class
> ./examples/Example$RunCommand.class
> ./examples/Example$Rebase.class
> ./examples/Example$DirectoryValidator.class
> ./examples/Example$ManProviderExample.class
> ./examples/Example.class
> ./examples/Example$GroupCommand.class
> ./examples/Example$PromptCommand.class
> {noformat}
> * [github sources|https://github.com/aeshell/aesh/tree/master/src/main/java/examples]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month