January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3723) setting the local to english in CLI commands on non-english systems does not produce english output

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3723?page=com.atlassian.jira.plugin.... ] Romain Pelisse commented on WFLY-3723: -------------------------------------- Zanata is in fact not in charge of building the resources bundles files, so it can't really help us here. As discussed with other developers on chat, I've changed all the call to Locale.getDefault() to Locale.ROOT, which fixes *part* of the issue. Indeed, if I now request an empty locale, I no longer get a French / German answer. However, because the bundle is still not found, if I request en_US (or en_UK for that matter), I still get an answer localized in French. I think I can fix it, and we will work on that. Also, I feel that the partial fix is actually an other issue so I'll probably create a separate issue for it ("Wildfly locale should fallback to ROOT rather than default to ensure the root bundle are used instead of any localized one"), and link it to this one. > setting the local to english in CLI commands on non-english systems does not produce english output > --------------------------------------------------------------------------------------------------- > > Key: WFLY-3723 > URL: https://issues.jboss.org/browse/WFLY-3723 > Project: WildFly > Issue Type: Bug > Components: Localization > Affects Versions: 8.1.0.Final > Environment: Tested on MacOS running in German > Reporter: Tom Fonteyne > Assignee: Romain Pelisse > Priority: Minor > > A German (or french etc...) system must be used to reproduce. > It is likely this is not limited to MacOS, but I do not have a non-english Linux system available > An out of the box install of wildfly/EAP: > Without configuration, the log file is in German as expected. > Using these CLI comands: > :read-operation-description(name=stop-servers,locale=de_DE) -> german > :read-operation-description(name=stop-servers,locale=en_US) -> german > :read-operation-description(name=stop-servers,locale=fr_FR) -> french > So we cannot get the CLI to produce english output > when configuring JAVA_OPTS in domain.conf with: > JAVA_OPTS="$JAVA_OPTS -Duser.language=en -Duser.country=DE -Duser.encoding=utf-8 > The log is now in English -> works as expected; and: > :read-operation-description(name=stop-servers,locale=de_DE) -> german > :read-operation-description(name=stop-servers,locale=en_US) -> english > So it seems we have a bug where the locale set to start the domain takes precedence over the locale set in the CLI command (but only when English is asked) > I presume this is because English is the default locale. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4190) Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4190?page=com.atlassian.jira.plugin.... ] Rafael Benevides reassigned WFLY-4190: -------------------------------------- Assignee: Rafael Benevides (was: Jason Greene) > Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts > -------------------------------------------------------------------------- > > Key: WFLY-4190 > URL: https://issues.jboss.org/browse/WFLY-4190 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3989) TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main"

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3989?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-3989: ----------------------------------- You could probably do it by cherry-picking the PR commits on to a custom branch based off of the 8.1.0.Final tag. With any luck there would be no conflicts. > TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main" > -------------------------------------------------------------------------------- > > Key: WFLY-3989 > URL: https://issues.jboss.org/browse/WFLY-3989 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EE > Affects Versions: 8.1.0.Final > Environment: Windows > Reporter: Prasad Deshpande > Assignee: jaikiran pai > Fix For: 9.0.0.Beta1 > > > The spec mandates that the TCCL be the application's classloader when the component is invoked (even during construction), but I'm getting it as > TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main" from local module loader -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-822) Remove the 'NET' project from JBoss Negotiation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-822?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-822: -------------------------------------- Fix Version/s: Negotiation_2_3_7_Final (was: Negotiation_2_3_6_Final) > Remove the 'NET' project from JBoss Negotiation > ----------------------------------------------- > > Key: SECURITY-822 > URL: https://issues.jboss.org/browse/SECURITY-822 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_11, Negotiation_2_3_7_Final > > > The net project is not used in AS 7, EAP 6 or WildFly so time to delete it. > In WildFly 9 an alternative SASL based approach will be used for EJB invocations. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4222) Upgrade Hibernate ORM to 4.3.8 to uptake HHH-9419

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-4222?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-4222: ------------------------------- Fix Version/s: 9.0.0.Beta1 Thanks for the HHH-9419 patch, will be good to have that (missed case) addressed. > Upgrade Hibernate ORM to 4.3.8 to uptake HHH-9419 > ------------------------------------------------- > > Key: WFLY-4222 > URL: https://issues.jboss.org/browse/WFLY-4222 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Affects Versions: 8.2.0.Final, 9.0.0.CR1 > Reporter: Arcadiy Ivanov > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > > [HHH-9419|https://hibernate.atlassian.net/browse/HHH-9419] fixes incorrect optimistic lock behavior for deleted entities in Hibernate ORM. > The problem is fixed in 4.3 and 5.0 branches. Either 4.3.8 or 5.0.0 Hibernate ORM upgrade is needed once the above versions are released. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-873) Release JBoss Negotiation 2.3.6.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-873?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-873. --------------------------------------- Resolution: Done > Release JBoss Negotiation 2.3.6.Final > ------------------------------------- > > Key: SECURITY-873 > URL: https://issues.jboss.org/browse/SECURITY-873 > Project: PicketBox > Issue Type: Release > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_6_Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-871. --------------------------------------- Resolution: Done > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_6_Final > > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4206) jboss-javaee-7.0-with-resteasy bom exposes JUnit as dependency

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4206?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-4206. ------------------------------- Resolution: Done fixed in boms 8.2.1.Final > jboss-javaee-7.0-with-resteasy bom exposes JUnit as dependency > -------------------------------------------------------------- > > Key: WFLY-4206 > URL: https://issues.jboss.org/browse/WFLY-4206 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 8.2.0.Final > Reporter: James Bodkin > Assignee: Tomaz Cerar > Priority: Minor > > The jboss-javaee-7.0-with-resteasy bom includes the JUnit dependency, I believe this should be included with the jboss-javaee-7.0-with-tools bom instead. (It seems to already be included in tools as well) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1876: ------------------------------ Attachment: views.txt Logs from 4 nodes edg-perf[10-13], containing sequences of installed views. > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3989) TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main"

by Robert Smith (JIRA)

[ https://issues.jboss.org/browse/WFLY-3989?page=com.atlassian.jira.plugin.... ] Robert Smith commented on WFLY-3989: ------------------------------------ Can this be patched in 8.1.0? We are using 8.1.0.Final and are having problems with spring loading in mdbs. > TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main" > -------------------------------------------------------------------------------- > > Key: WFLY-3989 > URL: https://issues.jboss.org/browse/WFLY-3989 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EE > Affects Versions: 8.1.0.Final > Environment: Windows > Reporter: Prasad Deshpande > Assignee: jaikiran pai > Fix For: 9.0.0.Beta1 > > > The spec mandates that the TCCL be the application's classloader when the component is invoked (even during construction), but I'm getting it as > TCCL in constructor of MDB is ModuleClassLoader for Module "org.hornetq.ra:main" from local module loader -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 2015