January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2155) Table editor should use full canvas area available

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2155?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2155: -------------------------------- Summary: Table editor should use full canvas area available (was: table editor should use full canvas area available) > Table editor should use full canvas area available > -------------------------------------------------- > > Key: DROOLS-2155 > URL: https://issues.jboss.org/browse/DROOLS-2155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX > > DMN table editor should use the full canvas width that is available (minus panels, toolbars, etc.) It should not appear as a smaller fixed size area, with scrollbars, within the canvas. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2155) table editor should use full canvas area available

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2155?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2155: -------------------------------- QE Status: ON_QA (was: NEW) > table editor should use full canvas area available > -------------------------------------------------- > > Key: DROOLS-2155 > URL: https://issues.jboss.org/browse/DROOLS-2155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Minor > Labels: UX > > DMN table editor should use the full canvas width that is available (minus panels, toolbars, etc.) It should not appear as a smaller fixed size area, with scrollbars, within the canvas. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2244) DMN: time(date("2017-08-10")) should return 00:00:00z time

by Lukáš Petrovický (JIRA)

Lukáš Petrovický created DROOLS-2244: ---------------------------------------- Summary: DMN: time(date("2017-08-10")) should return 00:00:00z time Key: DROOLS-2244 URL: https://issues.jboss.org/browse/DROOLS-2244 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.5.0.Final Reporter: Lukáš Petrovický Assignee: Tibor Zimányi According to the specification in section "10.3.2.3.5 date": "Where necessary, including the valuedt function (see 10.3.2.x.6), a date value is considered to be equivalent to a date time value in which the time of day is UTC midnight (00:00:00)." Currently the case time(date("2017-08-10")) returns null, because the evaluation ends with DateTimeException, because internally we represent dates as LocalDate class, which doesn't have time part. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8913) It is not possible to add cache store in infinispan subsystem

by Maxim Karavaev (JIRA)

[ https://issues.jboss.org/browse/WFLY-8913?page=com.atlassian.jira.plugin.... ] Maxim Karavaev commented on WFLY-8913: -------------------------------------- I am confused. I'm just download the last version *WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)* and got this error: {noformat} [standalone@localhost:9990 /] /subsystem=infinispan/cache-container=hibernate/local-cache=foobar1:add() {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=infinispan/cache-container=hibernate/local-cache=foobar1/store=STORE:add(class="org.infinispan.configuration.cache.SingleFileStoreConfigurationBuilder") { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache.store.hibernate.foobar1 is already registered", "rolled-back" => true } {noformat} Does it fixed or not? And in which version? > It is not possible to add cache store in infinispan subsystem > ------------------------------------------------------------- > > Key: WFLY-8913 > URL: https://issues.jboss.org/browse/WFLY-8913 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > Adding cache store to already created cache ends by failure even if it should succeed: > {code} > [standalone@localhost:9990 /] /subsystem=infinispan/cache-container=hibernate/invalidation-cache=foobar/store=STORE:add(class="org.infinispan.configuration.cache.SingleFileStoreConfigurationBuilder") > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache.store.hibernate.foobar is already registered", > "rolled-back" => true > } > {code} > This is a regression against 7.1.0.DR18. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9675) cannot disable 'max-post-size' check for undertow listeners

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9675?page=com.atlassian.jira.plugin.... ] Chao Wang updated WFLY-9675: ---------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10756 > cannot disable 'max-post-size' check for undertow listeners > ----------------------------------------------------------- > > Key: WFLY-9675 > URL: https://issues.jboss.org/browse/WFLY-9675 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > With EAP7.1.0.GA, there has been added a validator for 'max-post-size' attribute for listeners in undertow subsystem. This validator requires positive integer values starting with value 1. That means, you cannot disable 'max-post-size' for such listener using 0 value anymore. > In EAP6.4 and EAP7.0, it was possible to disable 'max-post-size' check with 0 value. I understand that we might not want to allow user to set this to 0 value as it might be a potentional security risk. Still, maybe we should relax this restriction as it was possible to configure it that way in previous versions of EAP. > Also there is a [Knowledge Base article|https://access.redhat.com/solutions/714173] regarding to this feature, which we should update in case we won't reconsider our position. > Just for the record - quoting question from mailing list: > {quote} > Dear Experts, > Based on KCS, the "max-post-size" in "http-listener" from "undertow" subsystem can be disabled by setting "0" to it, it worked for EAP 6.x and 7.0 GA. > But in EAP 7.1.0 GA, it didn't work: > ~~~ > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/http-listener=default/:write-attribute(name=max-post-size,value=0) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0117: 0 is an invalid value for parameter max-post-size. A minimum value of 1 is required", > "rolled-back" => true > } > ~~~ > By comparing schemas: > ~~~ > jboss-eap-7.0/docs/schema/wildfly-undertow_x_x.xsd: > <xs:attribute name="max-post-size" type="xs:long" default="0"/> > --- > jboss-eap-7.1/docs/schema/wildfly-undertow_x_x.xsd: > <xs:attribute name="max-post-size" type="xs:long" default="10485760"/> > ~~~ > The behaviour changed. > And I found WFLY-6437 and JBEAP-3974, but failed to open links inside those. > So can I ask if "max-post-size" can be disabled in EAP 7.1.0 GA and the reason if possible? > Best Regards, > Zhang Xu > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Cheng Fang resolved WFLY-9610. ------------------------------ Resolution: Explained > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9676) Build tools 1.2.6.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9676: ------------------------------------ Summary: Build tools 1.2.6.Final Key: WFLY-9676 URL: https://issues.jboss.org/browse/WFLY-9676 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9677) Build tools 1.2.6.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9677: ------------------------------------ Summary: Build tools 1.2.6.Final Key: WFLY-9677 URL: https://issues.jboss.org/browse/WFLY-9677 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3510) Build tools 1.2.6.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3510?page=com.atlassian.jira.plugi... ] Stuart Douglas moved WFLY-9677 to WFCORE-3510: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3510 (was: WFLY-9677) > Build tools 1.2.6.Final > ----------------------- > > Key: WFCORE-3510 > URL: https://issues.jboss.org/browse/WFCORE-3510 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9675) cannot disable 'max-post-size' check for undertow listeners

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9675?page=com.atlassian.jira.plugin.... ] Chao Wang moved JBEAP-14096 to WFLY-9675: ----------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9675 (was: JBEAP-14096) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Affects Version/s: 11.0.0.Final (was: 7.1.0.GA) > cannot disable 'max-post-size' check for undertow listeners > ----------------------------------------------------------- > > Key: WFLY-9675 > URL: https://issues.jboss.org/browse/WFLY-9675 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > With EAP7.1.0.GA, there has been added a validator for 'max-post-size' attribute for listeners in undertow subsystem. This validator requires positive integer values starting with value 1. That means, you cannot disable 'max-post-size' for such listener using 0 value anymore. > In EAP6.4 and EAP7.0, it was possible to disable 'max-post-size' check with 0 value. I understand that we might not want to allow user to set this to 0 value as it might be a potentional security risk. Still, maybe we should relax this restriction as it was possible to configure it that way in previous versions of EAP. > Also there is a [Knowledge Base article|https://access.redhat.com/solutions/714173] regarding to this feature, which we should update in case we won't reconsider our position. > Just for the record - quoting question from mailing list: > {quote} > Dear Experts, > Based on KCS, the "max-post-size" in "http-listener" from "undertow" subsystem can be disabled by setting "0" to it, it worked for EAP 6.x and 7.0 GA. > But in EAP 7.1.0 GA, it didn't work: > ~~~ > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/http-listener=default/:write-attribute(name=max-post-size,value=0) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0117: 0 is an invalid value for parameter max-post-size. A minimum value of 1 is required", > "rolled-back" => true > } > ~~~ > By comparing schemas: > ~~~ > jboss-eap-7.0/docs/schema/wildfly-undertow_x_x.xsd: > <xs:attribute name="max-post-size" type="xs:long" default="0"/> > --- > jboss-eap-7.1/docs/schema/wildfly-undertow_x_x.xsd: > <xs:attribute name="max-post-size" type="xs:long" default="10485760"/> > ~~~ > The behaviour changed. > And I found WFLY-6437 and JBEAP-3974, but failed to open links inside those. > So can I ask if "max-post-size" can be disabled in EAP 7.1.0 GA and the reason if possible? > Best Regards, > Zhang Xu > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018