January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11573) Remove Servlet 3.1 dependency

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-11573?page=com.atlassian.jira.plugin... ] Jan Stourac updated WFLY-11573: ------------------------------- Component/s: Build System Web (Undertow) > Remove Servlet 3.1 dependency > ----------------------------- > > Key: WFLY-11573 > URL: https://issues.jboss.org/browse/WFLY-11573 > Project: WildFly > Issue Type: Task > Components: Build System, Web (Undertow) > Affects Versions: 15.0.1.Final > Reporter: Jan Blizňák > Priority: Major > > There is JBoss Servlet API dependency declared in two different versions 3.1 and 4.0 which is probably a leftover from transition period during EE8 support development. > Since server built from sources contains only dist/target/wildfly-16.0.0.Beta1-SNAPSHOT/modules/system/layers/base/javax/servlet/api/main/jboss-servlet-api_4.0_spec-1.0.0.Final.jar file it should be safe to remove this from WF project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11573) Remove Servlet 3.1 dependency

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11573?page=com.atlassian.jira.plugin... ] Jan Blizňák updated WFLY-11573: ------------------------------- Component/s: (was: EJB) > Remove Servlet 3.1 dependency > ----------------------------- > > Key: WFLY-11573 > URL: https://issues.jboss.org/browse/WFLY-11573 > Project: WildFly > Issue Type: Task > Affects Versions: 15.0.1.Final > Reporter: Jan Blizňák > Priority: Major > > There is JBoss Servlet API dependency declared in two different versions 3.1 and 4.0 which is probably a leftover from transition period during EE8 support development. > Since server built from sources contains only dist/target/wildfly-16.0.0.Beta1-SNAPSHOT/modules/system/layers/base/javax/servlet/api/main/jboss-servlet-api_4.0_spec-1.0.0.Final.jar file it should be safe to remove this from WF project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11573) Remove Servlet 3.1 dependency

by Jan Blizňák (Jira)

Jan Blizňák created WFLY-11573: ---------------------------------- Summary: Remove Servlet 3.1 dependency Key: WFLY-11573 URL: https://issues.jboss.org/browse/WFLY-11573 Project: WildFly Issue Type: Task Components: EJB Affects Versions: 15.0.1.Final Reporter: Jan Blizňák There is JBoss Servlet API dependency declared in two different versions 3.1 and 4.0 which is probably a leftover from transition period during EE8 support development. Since server built from sources contains only dist/target/wildfly-16.0.0.Beta1-SNAPSHOT/modules/system/layers/base/javax/servlet/api/main/jboss-servlet-api_4.0_spec-1.0.0.Final.jar file it should be safe to remove this from WF project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4266) Classes for newer versions are not loaded from Multi-Release-JARs in WARs

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/WFCORE-4266?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-4266: ------------------------------------- That was my mistake, I didn't realize the manifest was nullable. Fixed in the PR. > Classes for newer versions are not loaded from Multi-Release-JARs in WARs > ------------------------------------------------------------------------- > > Key: WFCORE-4266 > URL: https://issues.jboss.org/browse/WFCORE-4266 > Project: WildFly Core > Issue Type: Bug > Components: VFS > Environment: Java 9+ > Reporter: Daniel Schwering > Priority: Major > Attachments: buggywar.src.zip, buggywar.war, multireleaselib-0.0.1-SNAPSHOT.jar, multireleaselib-0.0.1-SNAPSHOT.jar, multireleaselib.src.zip, multireleaselib.src.zip > > > 1 > down vote > favorite > Since Java 9 there are Multi-Release JARs ([MRJARS|https://openjdk.java.net/jeps/238]) that allow different classes for different Java versions to be included in one JAR file. I was surprised when a Wildfly 14 running on Java 11 executed Java-8-code in a JAR included in a WAR although the JAR was a MRJAR with code for Java 11. That JAR included as a dependency for a regular Java SE project is running different code depending on the running JRE, but when included in a WAR, the Java-11-code seems to be ignored. > Is that expected behavior for a webserver, as Java EE 8 does not explicitly require Java 9 (which introduced MRJARs) but only Java 8? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-552) Checker Fails With Maistra Deploy

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-552?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-552. -------------------------------- Resolution: Done > Checker Fails With Maistra Deploy > --------------------------------- > > Key: SWSQE-552 > URL: https://issues.jboss.org/browse/SWSQE-552 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4266) Classes for newer versions are not loaded from Multi-Release-JARs in WARs

by Daniel Schwering (Jira)

[ https://issues.jboss.org/browse/WFCORE-4266?page=com.atlassian.jira.plugi... ] Daniel Schwering commented on WFCORE-4266: ------------------------------------------ I tried to build wildfly with your wildfly-core, but now I get a java.lang.NullPointerException at org.jboss.as.server.deployment.module.VFSResourceLoader.<init>(VFSResourceLoader.java:143) when installing my buggywar.war. I'll try and set up a Wildfly development environment tomorrow so I can maybe debug it. > Classes for newer versions are not loaded from Multi-Release-JARs in WARs > ------------------------------------------------------------------------- > > Key: WFCORE-4266 > URL: https://issues.jboss.org/browse/WFCORE-4266 > Project: WildFly Core > Issue Type: Bug > Components: VFS > Environment: Java 9+ > Reporter: Daniel Schwering > Priority: Major > Attachments: buggywar.src.zip, buggywar.war, multireleaselib-0.0.1-SNAPSHOT.jar, multireleaselib-0.0.1-SNAPSHOT.jar, multireleaselib.src.zip, multireleaselib.src.zip > > > 1 > down vote > favorite > Since Java 9 there are Multi-Release JARs ([MRJARS|https://openjdk.java.net/jeps/238]) that allow different classes for different Java versions to be included in one JAR file. I was surprised when a Wildfly 14 running on Java 11 executed Java-8-code in a JAR included in a WAR although the JAR was a MRJAR with code for Java 11. That JAR included as a dependency for a regular Java SE project is running different code depending on the running JRE, but when included in a WAR, the Java-11-code seems to be ignored. > Is that expected behavior for a webserver, as Java EE 8 does not explicitly require Java 9 (which introduced MRJARs) but only Java 8? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3484) Data type constraints: Date range Include/Exclude actions.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3484?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3484: -------------------------------- Description: Background Persona: Business analyst or Rules practitioner *Use Cases:* As a user I want the ability to define constraints for the Date data type, that enable me to specify if the start and end value is included/excluded in a selected date range. *Note, selection options:* Include/ Include [ .. ] Include/ Exclude [ .. ) Exclude / Include ( .. ] Exclude / Exclude ( .. ) *Verification conditions:* * Scrum team and PO review. was: Background Persona: Business analyst or Rules practitioner Use Cases: As a user I want the ability to define constraints for the Date data type, that enable me to specify if the start and end value is included/excluded in a selected date range. Verification conditions: * Scrum team and PO review. > Data type constraints: Date range Include/Exclude actions. > ---------------------------------------------------------- > > Key: DROOLS-3484 > URL: https://issues.jboss.org/browse/DROOLS-3484 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > *Use Cases:* > As a user I want the ability to define constraints for the Date data type, that enable me to specify if the start and end value is included/excluded in a selected date range. > *Note, selection options:* > Include/ Include [ .. ] > Include/ Exclude [ .. ) > Exclude / Include ( .. ] > Exclude / Exclude ( .. ) > *Verification conditions:* > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2697) [DMN Designer] Improve readability of node labels

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-2697?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2697: ------------------------------------- [~dadossan] [~mstevens1] +1, I looked around at some other applications and many seem to do this as well. > [DMN Designer] Improve readability of node labels > ------------------------------------------------- > > Key: DROOLS-2697 > URL: https://issues.jboss.org/browse/DROOLS-2697 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Attachments: BPMN-label.png, screenshot-1.png, screenshot-2.png > > > Node names are bold text without background rectangle and hence _merge_ into the node SVG. It'd be nicer to change font to regular and provide a (white) background rectangle to improve readability. See https://github.com/kiegroup/kie-wb-common/pull/1929#pullrequestreview-133... > h2. Acceptance criteria > - Download as DMN, import into external tool > - Download as picture -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11565) WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204

by jaikiran pai (Jira)

[ https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin... ] jaikiran pai commented on WFLY-11565: ------------------------------------- Could you try this against a more recent version of WildFly (15.0.1 is the latest released)? > WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204 > ------------------------------------------------------------------------------------------- > > Key: WFLY-11565 > URL: https://issues.jboss.org/browse/WFLY-11565 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Deepak Sahu > Assignee: Jason Greene > Priority: Major > > I am using WildFly Server 9.0.0 Final, Javax ws, Jersey for developing Rest APIs. For all the responses whose httpStatus code is 204, the wildfly server adds Transfer encoding Chunked in the response header, which is not correct as per the Rest Standards. Because of this behavior some of the RestAPI clients hang, as they keep waiting for the response (which is not at all there). > To verify the issue, I tried the same with Springboot instead of deploying the war in WildFly and the Response Header was not added with Transfer Encoding Chuncked. > Let me know if some other information is required to fix this issue, if this is already fixed is there any patch for this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3492: --------------------------------------- [~aglass] FYI > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2019