January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9726) Upgrade JSF based on Mojarra 2.2.13.SP5

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9726?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-9726: -------------------------------- Fix Version/s: (was: 11.0.0.Beta1) > Upgrade JSF based on Mojarra 2.2.13.SP5 > --------------------------------------- > > Key: WFLY-9726 > URL: https://issues.jboss.org/browse/WFLY-9726 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Ivo Studensky > Assignee: Bartosz Spyrko-Śmietanko > > Upgrade JSF based on Mojarra 2.2.13.SP4. This incorporates the patch for JBEAP-10758/[JAVASERVERFACES-4240 | https://java.net/jira/browse/JAVASERVERFACES-4240] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9726) Upgrade JSF based on Mojarra 2.2.13.SP5

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9726?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-9726: -------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/10196) > Upgrade JSF based on Mojarra 2.2.13.SP5 > --------------------------------------- > > Key: WFLY-9726 > URL: https://issues.jboss.org/browse/WFLY-9726 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Ivo Studensky > Assignee: Bartosz Spyrko-Śmietanko > > Upgrade JSF based on Mojarra 2.2.13.SP4. This incorporates the patch for JBEAP-10758/[JAVASERVERFACES-4240 | https://java.net/jira/browse/JAVASERVERFACES-4240] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-33) Support non-jar artifacts properly

by Peter Palaga (JIRA)

Peter Palaga created WFBUILD-33: ----------------------------------- Summary: Support non-jar artifacts properly Key: WFBUILD-33 URL: https://issues.jboss.org/browse/WFBUILD-33 Project: WildFly Build Tools Issue Type: Bug Reporter: Peter Palaga Assignee: Peter Palaga The immediate impetus for reporting this is the fact that after upgrading from 1.1.6.Final to 1.2.6.Final our {code} <copy-artifact artifact="io.hawt:hawtio-wildfly" to-location="standalone/deployments/"/> {code} stopped working for the FP plugin. Changing it to {code}<copy-artifact artifact="io.hawt:hawtio-wildfly:war" to-location="standalone/deployments/"/>{code} by adding :war made the FP plugin happy, but it made the provisioning plugin fail with an NPE. It looks like the code parsing and the rendering the groupId:artifactId:type:classifier:version strings is scattered over several methods whose behavior is not 100% consistent. The current objective is: (1) Write a few integration tests to pin the behavior before the change, identifying the broken cases (2) Write the actual fix in such a way that the plugins stay as backwards compatible as possible. I have a fix that works for me, I just need to ensure, my changes keep the plugins backwards compatible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9725) Error during transaction manager commit of non-XA resource does not provokes exception being thrown

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-9725?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated WFLY-9725: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10789 > Error during transaction manager commit of non-XA resource does not provokes exception being thrown > --------------------------------------------------------------------------------------------------- > > Key: WFLY-9725 > URL: https://issues.jboss.org/browse/WFLY-9725 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 11.0.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > In case that an exception is thrown during one-phase commit of non-XA transaction participant the error is swallowed and not returned to the caller > This can happend for example when transaction manager calls commit to the e.g. database resource and connection crash happens. Then jdbc driver returns {{XAException}} with error code like {{XAER_RMFAIL}}. This fact is not reflected by exception being thrown to the caller (e.g. EJB bean). > This causes to the fact that user think the work was committed (e.g. INSERT to database) but in fact connection failure happened and nothing was done. > The fix is part of the Narayana at issue https://issues.jboss.org/browse/JBTM-2983 and it should be released with Narayana 5.7.3.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2247) RPC does not invoke interface's default methods inherited

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2247?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2247. ---------------------------- Resolution: Done Default methods in interfaces are now found as well > RPC does not invoke interface's default methods inherited > --------------------------------------------------------- > > Key: JGRP-2247 > URL: https://issues.jboss.org/browse/JGRP-2247 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.8 > Environment: jgroups 4.0.8.Final > java version "1.8.0_151" > Java(TM) SE Runtime Environment (build 1.8.0_151-b12) > Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode) > on win 10 > Reporter: rokk ebol > Assignee: Bela Ban > Fix For: 4.0.10 > > > org.jgroups.blocks.MethodCall#getAllMethods looks for methods up there in superclasses but not in interfaces, which can contain default methods since java 8 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9725) Error during transaction manager commit of non-XA resource does not provokes exception being thrown

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created WFLY-9725: ------------------------------------- Summary: Error during transaction manager commit of non-XA resource does not provokes exception being thrown Key: WFLY-9725 URL: https://issues.jboss.org/browse/WFLY-9725 Project: WildFly Issue Type: Bug Components: Transactions Affects Versions: 11.0.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka In case that an exception is thrown during one-phase commit of non-XA transaction participant the error is swallowed and not returned to the caller This can happend for example when transaction manager calls commit to the e.g. database resource and connection crash happens. Then jdbc driver returns {{XAException}} with error code like {{XAER_RMFAIL}}. This fact is not reflected by exception being thrown to the caller (e.g. EJB bean). This causes to the fact that user think the work was committed (e.g. INSERT to database) but in fact connection failure happened and nothing was done. The fix is part of the Narayana at issue https://issues.jboss.org/browse/JBTM-2983 and it should be released with Narayana 5.7.3.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9620) ServletContext.getResourceAsStream, for deployments which have (Java EE) servlet overlays, serves files which are outside of the deployment

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-9620?page=com.atlassian.jira.plugin.... ] Yeray Borges updated WFLY-9620: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10748, https://github.com/wildfly/wildfly/pull/10784 > ServletContext.getResourceAsStream, for deployments which have (Java EE) servlet overlays, serves files which are outside of the deployment > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9620 > URL: https://issues.jboss.org/browse/WFLY-9620 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.2.Final, 10.1.0.Final, 11.0.0.Final > Reporter: Laurent ROUSSEL > Assignee: Yeray Borges > Priority: Critical > Fix For: 12.0.0.Alpha1 > > > A user has reported in the forums that there appears to be an issue (since 9.0.x till present 11.0.0 WildFly releases) where files like `/etc/passwd` are served by the web container to the clients, when the client requests a crafted URL against a Java EE deployment which has (Java EE) servlet overlays. Please see the referenced forum thread[1] for more details. > Although, the steps noted in that thread involves Spring framework and gets triggered in a very specific way, the root cause appears to be the call to `ServletContext.getResourceAsInputStream` (which is what the spring framework ends up calling with a path like "/../../../../../../../..//etc/passwd", ends up actually serving the resource even if the path is outside the scope of the deployment to which the servlet context belongs. > I could reproduce this against the latest WildFly in a simple test case that's here [2] > [1] https://developer.jboss.org/thread/276826 > [2] https://github.com/jaikiran/wildfly/commit/ed05258aa824ab91a52ef6554e9707... > P.S: The credit for reporting this issue should go to Laurent Roussel who reported this in the forum thread, but I don't have access to change the "Reporter" field of the JIRA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3540) In non interactive mode, ls -l table format output is bad if any element in return contents is longer than terminal width

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3540?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-3540: ------------------------------ Labels: (was: eap7.1.0-defer) > In non interactive mode, ls -l table format output is bad if any element in return contents is longer than terminal width > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3540 > URL: https://issues.jboss.org/browse/WFCORE-3540 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha6 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > 1. create commands in file command.cli which contains "ls -l /subsystem=elytron/provider-loader=elytron" > 2. start EAP server. > 3 execute command in CLI non interactive mode jboss-cli.sh -c --file=command.cli. > See the table output is malformat -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3540) In non interactive mode, ls -l table format output is bad if any element in return contents is longer than terminal width

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3540?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-14131 to WFCORE-3540: ------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3540 (was: JBEAP-14131) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Affects Version/s: 4.0.0.Alpha6 (was: 7.1.0.DR18) > In non interactive mode, ls -l table format output is bad if any element in return contents is longer than terminal width > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3540 > URL: https://issues.jboss.org/browse/WFCORE-3540 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha6 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > Labels: eap7.1.0-defer > > 1. create commands in file command.cli which contains "ls -l /subsystem=elytron/provider-loader=elytron" > 2. start EAP server. > 3 execute command in CLI non interactive mode jboss-cli.sh -c --file=command.cli. > See the table output is malformat -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2266) [DMN Designer] Override newSizeHandler for DMNSVGShapeDefImpl

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2266: ----------------------------------- Summary: [DMN Designer] Override newSizeHandler for DMNSVGShapeDefImpl Key: DROOLS-2266 URL: https://issues.jboss.org/browse/DROOLS-2266 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Due to changes in JBPM-6512, we should override the _newSizeHandler_ in the class [DMNSVGShapeDefImpl.java|https://github.com/kiegroup/kie-wb-common/blob/ma...] to introduce the same approach in min/max size constraint handling through Stunner, DMN and Forms. -- 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