March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-102?page=com.atlassian.jira.plu... ] Ivo Studensky commented on JBLOGGING-102: ----------------------------------------- I can't see any fix at [1] [2] [3] [4] [5] [6] [7] [8]. Am I looking at wrong source code? [1] https://github.com/jboss-logging/jboss-logging/blob/3.1/src/main/java/org... [2] https://github.com/jboss-logging/jboss-logging/blob/3.1/src/main/java/org... [3] https://github.com/jboss-logging/jboss-logging/blob/3.1/src/main/java/org... [4] https://github.com/jboss-logging/jboss-logging/blob/3.1/src/main/java/org... [5] https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/... [6] https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/... [7] https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/... [8] https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/... > Messages#getBundle() needs to be privileged > ------------------------------------------- > > Key: JBLOGGING-102 > URL: https://issues.jboss.org/browse/JBLOGGING-102 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.1.4.GA, 3.2.0.Beta1 > Reporter: Ivo Studensky > Assignee: James Perkins > Fix For: 3.1.3.GA, 3.2.0.Beta1 > > > It ({{org.jboss.logging.Messages#getBundle(Class<T> type, Locale locale)}}) calls {{type.getClassLoader()}} which requires privileges when running with Security Manager. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2655) Show warning for JDBC drivers as modules with no driver

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2655?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2655: ----------------------------------------------- James Livingston <jlivings(a)redhat.com> changed the Status of [bug 1043339|https://bugzilla.redhat.com/show_bug.cgi?id=1043339] from NEW to ASSIGNED > Show warning for JDBC drivers as modules with no driver > ------------------------------------------------------- > > Key: WFLY-2655 > URL: https://issues.jboss.org/browse/WFLY-2655 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: James Livingston > Assignee: Jeff Zhang > Fix For: 8.0.1.Final > > > If a <driver> if configured with no <driver-class>, it will attempt to locate the driver(s) via the service loader which should find all JDBC4-compliant drivers. > When you install a non JDBC4-complicant driver as a module and no <driver-class>, the driver will not be installed. That is expected but emitting a warning that no-drivers could be found in the module would be useful to help users troubleshoot the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3168) Wrong Mojarra version on Linux

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3168?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3168: -------------------------------------- Any chance you installed WF from RPM (or .deb), and there is something screwy in the rpm version? Either way this is not our bug, but should be filed against whoever provides the packages, we don't provided different downloads for Linux and Windows, just the single zip file. > Wrong Mojarra version on Linux > ------------------------------ > > Key: WFLY-3168 > URL: https://issues.jboss.org/browse/WFLY-3168 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.Final > Environment: Linux > Reporter: Thorsten Richter > Assignee: Farah Juma > Labels: jsf, linux, mojarra, viewscoped > > We had a bug on Linux that the @ViewScoped annotation didn't work for AJAX requests. We found out, that the Mojarra version is causing the problem. On our Windows development machines everything worked fine, but on the Linux production server @ViewScoped didn't work. > So we searched for the root cause and found out, that the Mojarra version was different on Linux. > The Linux package of Wildfly contains an older version of Mojarra (2.1.7) within the modules/com/sun/jsf-impl folder that needs to be deleted. > The Windows package of Wildfly doesn't even contain a com folder within modules. > So maybe the whole com folder on Linux is wrong? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3168) Wrong Mojarra version on Linux

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3168?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-3168. ---------------------------------- Resolution: Rejected > Wrong Mojarra version on Linux > ------------------------------ > > Key: WFLY-3168 > URL: https://issues.jboss.org/browse/WFLY-3168 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.Final > Environment: Linux > Reporter: Thorsten Richter > Assignee: Farah Juma > Labels: jsf, linux, mojarra, viewscoped > > We had a bug on Linux that the @ViewScoped annotation didn't work for AJAX requests. We found out, that the Mojarra version is causing the problem. On our Windows development machines everything worked fine, but on the Linux production server @ViewScoped didn't work. > So we searched for the root cause and found out, that the Mojarra version was different on Linux. > The Linux package of Wildfly contains an older version of Mojarra (2.1.7) within the modules/com/sun/jsf-impl folder that needs to be deleted. > The Windows package of Wildfly doesn't even contain a com folder within modules. > So maybe the whole com folder on Linux is wrong? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3176) Certain file types are filtered out and excluded upon deployment

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3176?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-3176. ---------------------------------- Resolution: Done Should be fixed by the inclusion of Undertow 1.0.3 > Certain file types are filtered out and excluded upon deployment > ---------------------------------------------------------------- > > Key: WFLY-3176 > URL: https://issues.jboss.org/browse/WFLY-3176 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Windows 7 x64 > Reporter: Jason Kim > > In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. > The same site along with the references to the *.less files worked on 8.0.0 FInal. I tried with other file types, just making up extensions, and Wildfly would not serve the files, instead it would return aa 404 when trying to access them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3176) Certain file types are filtered out and excluded upon deployment

by Jason Kim (JIRA)

[ https://issues.jboss.org/browse/WFLY-3176?page=com.atlassian.jira.plugin.... ] Jason Kim updated WFLY-3176: ---------------------------- Description: In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. The same site along with the references to the *.less files worked on 8.0.0 FInal. I tried with other file types, just making up extensions, and Wildfly would not serve the files, instead it would return aa 404 when trying to access them. was: In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. The same site worked on 8.0.0 FInal. > Certain file types are filtered out and excluded upon deployment > ---------------------------------------------------------------- > > Key: WFLY-3176 > URL: https://issues.jboss.org/browse/WFLY-3176 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Windows 7 x64 > Reporter: Jason Kim > > In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. > The same site along with the references to the *.less files worked on 8.0.0 FInal. I tried with other file types, just making up extensions, and Wildfly would not serve the files, instead it would return aa 404 when trying to access them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-153) Release EL 3.0 APIs

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-153?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-153: ------------------------------------- JBoss EL 3.0 Spec APIs v 1.0.3.Final has been released: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... This release includes PR #7 to fix the missing resource. > Release EL 3.0 APIs > ------------------- > > Key: JBEE-153 > URL: https://issues.jboss.org/browse/JBEE-153 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: jboss-el-api_3.0_spec-1.0.3.Final > > > Incorporates pull request: > https://github.com/jboss/jboss-el-api_spec/pull/5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-153) Release EL 3.0 APIs

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-153?page=com.atlassian.jira.plugin.s... ] Shelly McGowan resolved JBEE-153. --------------------------------- Resolution: Done > Release EL 3.0 APIs > ------------------- > > Key: JBEE-153 > URL: https://issues.jboss.org/browse/JBEE-153 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: jboss-el-api_3.0_spec-1.0.3.Final > > > Incorporates pull request: > https://github.com/jboss/jboss-el-api_spec/pull/5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3176) Certain file types are filtered out and excluded upon deployment

by Jason Kim (JIRA)

Jason Kim created WFLY-3176: ------------------------------- Summary: Certain file types are filtered out and excluded upon deployment Key: WFLY-3176 URL: https://issues.jboss.org/browse/WFLY-3176 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows 7 x64 Reporter: Jason Kim In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. The same site worked on 8.0.0 FInal. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-153) Release EL 3.0 APIs

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-153?page=com.atlassian.jira.plugin.s... ] Shelly McGowan updated JBEE-153: -------------------------------- Fix Version/s: jboss-el-api_3.0_spec-1.0.3.Final (was: jboss-el-api_3.0_spec-1.0.2.Final) > Release EL 3.0 APIs > ------------------- > > Key: JBEE-153 > URL: https://issues.jboss.org/browse/JBEE-153 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: jboss-el-api_3.0_spec-1.0.3.Final > > > Incorporates pull request: > https://github.com/jboss/jboss-el-api_spec/pull/5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 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 March 2014