October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11151) Wildfly 14 mix up HTML response in JSF applications

by Tamás Ábele (Jira)

Tamás Ábele created WFLY-11151: ---------------------------------- Summary: Wildfly 14 mix up HTML response in JSF applications Key: WFLY-11151 URL: https://issues.jboss.org/browse/WFLY-11151 Project: WildFly Issue Type: Bug Reporter: Tamás Ábele Assignee: Jason Greene Introduced in wildfly 14 we receive a new JSF implementation (developed years ago), JSF 2.3.5 which is based on mojarra. In certain circumstances this JSF runtime hides the real problem, and makes from an invalid HTML a valid one, and spoils it somewhere else you would never guess, or produces an invalid partial response. Anything can happen. This way the JSF runtime makes it really hard to find the real problem. This behavior led to a more severe error than the original one in two reported cases at github. I opened an issue ([eclipse-ee4j/mojarra#4488|https://github.com/eclipse-ee4j/mojarra/issues/...]) but the mojarra development team closed this issue without solving it, despite the fact how vulnerable JSF become to component rendering problems. Now a lot of teams starting to move towards wildfly 14. They are likely to face similar magical errors like us. In the other case ([jboss/mojarra#21|https://github.com/jboss/mojarra/issues/21]) the developer team switched back to JSF 2.2. I’m also worried to change to wildfly 14, because of the future magical errors it will cause in our systems. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1693) Update AcmeClientSpi to make use of POST-as-GET instead of GET

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1693?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1693: ---------------------------- Description: The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 1, 2019. More details can be found here: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... was: The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 1. More details can be found here: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... > Update AcmeClientSpi to make use of POST-as-GET instead of GET > -------------------------------------------------------------- > > Key: ELY-1693 > URL: https://issues.jboss.org/browse/ELY-1693 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 1, 2019. More details can be found here: > https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1693) Update AcmeClientSpi to make use of POST-as-GET instead of GET

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1693?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1693: ---------------------------- Description: The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 1. More details can be found here: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... was: The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 19. More details can be found here: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... > Update AcmeClientSpi to make use of POST-as-GET instead of GET > -------------------------------------------------------------- > > Key: ELY-1693 > URL: https://issues.jboss.org/browse/ELY-1693 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 1. More details can be found here: > https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1693) Update AcmeClientSpi to make use of POST-as-GET instead of GET

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1693?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1693: ---------------------------- Description: The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 19. More details can be found here: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... was: The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests. Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 19. More details can be found here: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... > Update AcmeClientSpi to make use of POST-as-GET instead of GET > -------------------------------------------------------------- > > Key: ELY-1693 > URL: https://issues.jboss.org/browse/ELY-1693 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests (this change was made during the final stages of IETF review). Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 19. More details can be found here: > https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1693) Update AcmeClientSpi to make use of POST-as-GET instead of GET

by Farah Juma (Jira)

Farah Juma created ELY-1693: ------------------------------- Summary: Update AcmeClientSpi to make use of POST-as-GET instead of GET Key: ELY-1693 URL: https://issues.jboss.org/browse/ELY-1693 Project: WildFly Elytron Issue Type: Task Components: API / SPI Reporter: Farah Juma Assignee: Farah Juma The ACME protocol has been updated to replace unauthenticated GET requests to resources with “POST-as-GET” requests. Once support for "POST-as-GET" requests has been added to Let's Encrypt's staging and production endpoints, we'll need to update our AcmeClientSpi to make use of "POST-as-GET" requests. Let's Encrypt will be removing support for unauthenticated GET requests on Nov. 19. More details can be found here: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unau... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-207) Use Formatter to format log message content

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/LOGMGR-207?page=com.atlassian.jira.plugin... ] David Lloyd updated LOGMGR-207: ------------------------------- Fix Version/s: 2.2.0.Final > Use Formatter to format log message content > ------------------------------------------- > > Key: LOGMGR-207 > URL: https://issues.jboss.org/browse/LOGMGR-207 > Project: JBoss Log Manager > Issue Type: Enhancement > Components: core > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 2.2.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11116: ------------------------------------- Hi [~zidoff]. As I said previously, I tried reproducing the issue locally using the code snippets above and was unable to see the behavior you described. I was hoping that you could come up with a simple test that reliably reproduces the problem without referencing any confidential code. > Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception) > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11116 > URL: https://issues.jboss.org/browse/WFLY-11116 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final > Reporter: Ziad Saade > Assignee: Paul Ferraro > Priority: Critical > > I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow: > > Book.java > TestBean testBean=null; > if(session.getAttribute("testBean")!=null) > testBean = (TestBean)session.getAttribute("testBean"); > else{ > testBean=new TestBean(); > session.setAttribute("testBean",testBean); > } > testBean.setAmount("10"); > > response.sendRedirect("BookPreview"); > > > The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated. > > BookPreview.java > > TestBean testBean = (TestBean)session.getAttribute("testBean"); > String amount = testBean.getAmount; //Null pointer exception when submitting the form > > <form method="Post" action="BookPreview"> > > </form> > > TestBean.java > > public class TestBean implements java.io.Serializable { > > private static final long serialVersionUID = 1L; > private String amount; > > public String getAmount() { > return amount; > } > > public void setAmount(String amount) { > this.amount = amount; > } > } > > Kindly advice how to fix the problem at the level of the server configuration. > PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....) > > Thanks and Best Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3092) User can not see all the definition editing custom data ypes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3092?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3092: ---------------------------------------- [~karreiro] Much like the kebab menu; the Bootstrap {{Select}} needs to have its container set to {{body}}. > User can not see all the definition editing custom data ypes > ------------------------------------------------------------ > > Key: DROOLS-3092 > URL: https://issues.jboss.org/browse/DROOLS-3092 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Daniel José dos Santos > Assignee: Guilherme Carreiro > Priority: Major > Attachments: 46597891-4abb2b00-cae2-11e8-9e05-6649abbdeb23.png > > > When editing "Custom Data Types", not all definitions are visible. This behaviour happens in all browsers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3092) User can not see all the definition editing custom data ypes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3092?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3092: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > User can not see all the definition editing custom data ypes > ------------------------------------------------------------ > > Key: DROOLS-3092 > URL: https://issues.jboss.org/browse/DROOLS-3092 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Daniel José dos Santos > Assignee: Guilherme Carreiro > Priority: Major > Attachments: 46597891-4abb2b00-cae2-11e8-9e05-6649abbdeb23.png > > > When editing "Custom Data Types", not all definitions are visible. This behaviour happens in all browsers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ] Daniel José dos Santos updated DROOLS-3067: ------------------------------------------- Attachment: manual.png > [DMN Designer] Automatic Layout Feature Workbench Integration > ------------------------------------------------------------- > > Key: DROOLS-3067 > URL: https://issues.jboss.org/browse/DROOLS-3067 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, auto.png, manual.png > > > Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature. > h2. Acceptance tests > # -User is prompted if he wants or not to apply autolayout feature- discussed in comments > # Positioning is automatically stored after model opening > # Simple graph, no branches, starting node on left, ending node on right > # Simple graph, no branches, starting node on bottom, ending node on top > # Tree, top node in the middle of the screen, some branches to all sides > # Graph with big crossing of edges, similar to complete graph > # Large (but sparse) graph, not all nodes visible without scrolling -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 October 2018