November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1995) Allow property substitution in EJB Annotations with configurable option

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-1995?page=com.atlassian.jira.plugin.... ] Carlo de Wolf reassigned WFLY-1995: ----------------------------------- Assignee: Chao Wang (was: JBoss SET) > Allow property substitution in EJB Annotations with configurable option > ----------------------------------------------------------------------- > > Key: WFLY-1995 > URL: https://issues.jboss.org/browse/WFLY-1995 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Carlo de Wolf > Assignee: Chao Wang > > Create a configuration option which enables property substitution in EJB annotations. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2481) CDI.current().getBeanManager() returns a beanmanager from a different deployment

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-2481?page=com.atlassian.jira.plugin.... ] Jozef Hartinger moved WELD-1546 to WFLY-2481: --------------------------------------------- Project: WildFly (was: Weld) Key: WFLY-2481 (was: WELD-1546) Affects Version/s: 8.0.0.Beta1 (was: 2.1.0.Final) Component/s: CDI / Weld (was: Bootstrap and Metamodel API) Security: Public > CDI.current().getBeanManager() returns a beanmanager from a different deployment > -------------------------------------------------------------------------------- > > Key: WFLY-2481 > URL: https://issues.jboss.org/browse/WFLY-2481 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.Beta1 > Environment: WildFly master build > Reporter: Emond Papegaaij > Assignee: Jozef Hartinger > > CDI.current().getBeanManager() uses the classname of the calling class to cache BeanManagers returned. This fails if multiple deployments contain classes with the same name. For example, wicket-cdi-1.1 looks up the BeanManager from org.apache.wicket.cdi.CdiConfiguration. If multiple Wicket-CDI applications are deployed in the same container, every BeanManager lookup will return the instance cached on the first call. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2471: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1028474|https://bugzilla.redhat.com/show_bug.cgi?id=1028474] from MODIFIED to ON_QA > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2352) Domain controller fails to restart due to an inconsistent rollback of a redeploy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2352?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2352: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1021763|https://bugzilla.redhat.com/show_bug.cgi?id=1021763] from MODIFIED to ON_QA > Domain controller fails to restart due to an inconsistent rollback of a redeploy > -------------------------------------------------------------------------------- > > Key: WFLY-2352 > URL: https://issues.jboss.org/browse/WFLY-2352 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Osamu Nagano > Assignee: Brian Stansberry > > When you try to redeploy (or deploy with --force option) the same application which has the same contents hash, and a necessary dependency like a datasource beeing injected in the application is lost by some reason, the redeploy operation will delete the contents under $JBOSS_HOME/domain/data/content directory but won't delete entries in domain.xml. Then the domain controller fails to start up because no contents found in the directory. This likely happens when you frequently changes settings during other servers shutting down. > The domain controller fails to restart with the following log messages. > {code} > 12:04:10,623 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "exampleapp.war")]) - failure description: "JBAS010876: No deployment content with hash c1306bc4855f4ed9914c9616f2b999c5c62a79d3 is available in the deployment content repository for deployment 'exampleapp.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > 12:04:10,628 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} > The domain controller should be independent from such a server specific issue and there should be a way to fix this via CLI or Console, not by a manual editing of domain.xml. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2403) Cannot disable Datasource or XADatasource in standalone and domain modes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2403: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 970679|https://bugzilla.redhat.com/show_bug.cgi?id=970679] from MODIFIED to ON_QA > Cannot disable Datasource or XADatasource in standalone and domain modes > ------------------------------------------------------------------------ > > Key: WFLY-2403 > URL: https://issues.jboss.org/browse/WFLY-2403 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > Description of problem: > Cannot disable a Datasource or XADatasource in standalone mode. It's back to enabled state after server reload. > Version-Release number of selected component (if applicable): > 6.1 > How reproducible: > Always > Steps to Reproduce: > Use the http management interface or the CLI > 1.Create a Datasource of XADatasource > 2.Disable it > 3.The response indicates a server reload is required > 4.Execute the reload operation > Actual results: > The datasource is back to enabled state > Expected results: > The datasource should be in disabled state -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2428) MDBs should use the full identifier of the resource adapter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2428?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2428: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1012044|https://bugzilla.redhat.com/show_bug.cgi?id=1012044] from MODIFIED to ON_QA > MDBs should use the full identifier of the resource adapter > ----------------------------------------------------------- > > Key: WFLY-2428 > URL: https://issues.jboss.org/browse/WFLY-2428 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.CR1 > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: 8.0.0.CR1 > > > The .rar suffix shouldn't be stripped anymore, as the resource adapters are registered under their full name. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2435) Upgrade Generic JMS RA to 1.0.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2435?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2435: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1026397|https://bugzilla.redhat.com/show_bug.cgi?id=1026397] from MODIFIED to ON_QA > Upgrade Generic JMS RA to 1.0.1.Final > ------------------------------------- > > Key: WFLY-2435 > URL: https://issues.jboss.org/browse/WFLY-2435 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2410) composite operation containing a host op does not get rolled out to all hosts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2410?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2410: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1015098|https://bugzilla.redhat.com/show_bug.cgi?id=1015098] from MODIFIED to ON_QA > composite operation containing a host op does not get rolled out to all hosts > ----------------------------------------------------------------------------- > > Key: WFLY-2410 > URL: https://issues.jboss.org/browse/WFLY-2410 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > If a composite operation contains an operation targeting the domain as well as a single host, it will only get rolled out to the host specified rather than to the complete domain. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2383) resource-adapter id attribute has to match ra name otherwise MDB is not deployed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2383?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2383: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1012044|https://bugzilla.redhat.com/show_bug.cgi?id=1012044] from MODIFIED to ON_QA > resource-adapter id attribute has to match ra name otherwise MDB is not deployed > -------------------------------------------------------------------------------- > > Key: WFLY-2383 > URL: https://issues.jboss.org/browse/WFLY-2383 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > The resource-adapter id has to have the same name as the ra archive has. Otherwise the the MDB is not deployed. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2425) Use forked version of slf4j to fix concurrency issue with static binding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2425?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2425: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1011821|https://bugzilla.redhat.com/show_bug.cgi?id=1011821] from MODIFIED to ON_QA > Use forked version of slf4j to fix concurrency issue with static binding > ------------------------------------------------------------------------ > > Key: WFLY-2425 > URL: https://issues.jboss.org/browse/WFLY-2425 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.CR1 > > > The slf4j-api static binding is not thread safe. A fork of slf4j-api was needed for EAP so we might as well patch WildFly too. The slf4j bugzilla is http://bugzilla.slf4j.org/show_bug.cgi?id=176. The patch used in the fork is attached to the bz. -- 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

12 years, 8 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 November 2013