August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1514) Add license file to jandex distribution

by Marek Goldmann (JIRA)

Add license file to jandex distribution --------------------------------------- Key: AS7-1514 URL: https://issues.jboss.org/browse/AS7-1514 Project: Application Server 7 Issue Type: Task Reporter: Marek Goldmann Priority: Minor Please add license file to the root of the project https://github.com/jbossas/jandex -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9383) Extended persistence context no longer extended

by Nicklas Karlsson (JIRA)

Extended persistence context no longer extended ----------------------------------------------- Key: JBAS-9383 URL: https://issues.jboss.org/browse/JBAS-9383 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Nicklas Karlsson I have a @ConversationScoped @Stateful bean with a @PersistenceContext(type = PersistenceContextType.EXTENDED) EntityManager em. I load an object by merging it into the em and storing it in the bean in the normal fashion but when I later do em.persist(foo) the persistence manager tries to insert it as a fresh object. em.contains(foo) also returns false. This is in trunk, it works on 6.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8815) Regression in Hibernate session/sessionfactory injection

by Scott Marlow (JIRA)

Regression in Hibernate session/sessionfactory injection -------------------------------------------------------- Key: JBAS-8815 URL: https://issues.jboss.org/browse/JBAS-8815 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 6.0.1 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 6.0.1 Regression caused by fix for JBAS-8563. This impacts the Hibernate specific support mentioned here http://bill.burkecentral.com/2007/07/06/co-existence-with-hibernate-jpa-a.... The regression is that the following will no longer work: @PersistenceContext(unitName="custDb") org.hibernate.Session session; @PersistenceUnit(unitName="custDb") SessionFactory factory; The workaround is to instead use the JPA 2.0 EntityManager.unwrap(Session.class). org.jboss.ejb3.test.longlived.unit.EntityUnitTestCase.testHibernateLongLivedSession fails with error: 2011-01-18 08:39:08,248 ERROR [org.jboss.ejb3.proxy.impl.factory.session.stateful.StatefulSessionProxyFactoryBase] (WorkerThread#1[127.0.0.1:54163]) Could not obtain new Session ID from SFSB Container: javax.ejb.EJBException: java.lang.IllegalArgumentException: failed to set value ExtendedEntityManager: persistence.unit:unitName=longlived-test.jar#tempdb on field org.hibernate.Session org.jboss.ejb3.test.longlived.HibernateShoppingCartBean.em at org.jboss.ejb3.cache.simple.SimpleStatefulCache.create(SimpleStatefulCache.java:438) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.stateful.StatefulContainer.createSession(StatefulContainer.java:440) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.session.SessionContainer.createSession(SessionContainer.java:677) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.proxy.impl.factory.session.stateful.StatefulSessionProxyFactoryBase.getNewSessionId(StatefulSessionProxyFactoryBase.java:227) [:1.0.11] at org.jboss.ejb3.proxy.impl.factory.session.stateful.StatefulSessionProxyFactoryBase.createProxyBusiness(StatefulSessionProxyFactoryBase.java:140) [:1.0.11] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_23] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_23] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) [jboss-aop.jar:2.2.1.GA] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) [:1.0.1.GA] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:898) [:] at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791) [:] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) [:] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) [:] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) [:] Caused by: java.lang.IllegalArgumentException: failed to set value ExtendedEntityManager: persistence.unit:unitName=longlived-test.jar#tempdb on field org.hibernate.Session org.jboss.ejb3.test.longlived.HibernateShoppingCartBean.em at org.jboss.injection.injector.util.FieldInjectionPoint.set(FieldInjectionPoint.java:73) [:1.0.0-alpha-6] at org.jboss.injection.injector.EEInjector.inject(EEInjector.java:159) [:1.0.0-alpha-6] at org.jboss.injection.injector.EEInjector.inject(EEInjector.java:134) [:1.0.0-alpha-6] at org.jboss.injection.injector.EEInjector.inject(EEInjector.java:82) [:1.0.0-alpha-6] at org.jboss.injection.manager.core.DefaultInjectionContext.proceed(DefaultInjectionContext.java:58) [:1.0.0-alpha-6] at org.jboss.injection.manager.core.DefaultInjectionManager.inject(DefaultInjectionManager.java:58) [:1.0.0-alpha-6] at org.jboss.injection.manager.core.DefaultInjectionManager.inject(DefaultInjectionManager.java:64) [:1.0.0-alpha-6] at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionInvocation.java:140) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:125) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:116) [:1.7.19-SNAPSHOT] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:116) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1363) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.stateful.StatefulContainer.createBeanContext(StatefulContainer.java:184) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.stateful.StatefulContainer.create(StatefulContainer.java:136) [:1.7.19-SNAPSHOT] at org.jboss.ejb3.cache.simple.SimpleStatefulCache.create(SimpleStatefulCache.java:417) [:1.7.19-SNAPSHOT] ... 15 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-8563) Implement persistence-context-ref resource provider

by Shelly McGowan (JIRA)

Implement persistence-context-ref resource provider --------------------------------------------------- Key: JBAS-8563 URL: https://jira.jboss.org/browse/JBAS-8563 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Scott Marlow Fix For: 6.0.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
19
0 / 0

[JBoss JIRA] Created: (AS7-1510) Configuration persister strips out comments

by Nicklas Karlsson (JIRA)

Configuration persister strips out comments ------------------------------------------- Key: AS7-1510 URL: https://issues.jboss.org/browse/AS7-1510 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Nicklas Karlsson Assignee: Brian Stansberry If you comment out stuff in standalone.xml and make a configuration change that will result in persisting the xml file, the commented content is stripped out. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1477) Fails to start with non-descriptive message if <formatter /> tag is missing from a logger.

by James Perkins (JIRA)

Fails to start with non-descriptive message if <formatter /> tag is missing from a logger. ------------------------------------------------------------------------------------------ Key: AS7-1477 URL: https://issues.jboss.org/browse/AS7-1477 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.0.1.Final The error message for a missing <formatter /> tag needs to be more descriptive. If a formatter is required, run a validation test. Otherwise perform null checks. Example: 09:53:28,326 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.logging.handler.CONSOLE: org.jboss.msc.service.StartException in service jboss.logging.handler.CONSOLE: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1786) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] Caused by: java.lang.NullPointerException at org.jboss.as.logging.ConsoleHandlerService.start(ConsoleHandlerService.java:55) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) ... 4 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1438) Add support for custom logging handlers

by James Perkins (JIRA)

Add support for custom logging handlers --------------------------------------- Key: AS7-1438 URL: https://issues.jboss.org/browse/AS7-1438 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.1.0.Alpha1 Need the ability to allow for custom logging handlers. For example using the log4j SMTPAppender. See http://community.jboss.org/message/618595 for more details on this specific use case. Example XML usage: <custom-handler module="org.logging.fu" class="org.logging.fu.UngaBunga"> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-613) Release JBoss Security 2.0.4.SP8

by Derek Horton (JIRA)

Release JBoss Security 2.0.4.SP8 -------------------------------- Key: SECURITY-613 URL: https://issues.jboss.org/browse/SECURITY-613 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Release Security Level: Public (Everyone can see) Components: JBossSX Reporter: Derek Horton Assignee: Marcus Moyses Fix For: JBossSecurity_2.0.4.SP7 New release of JBossSX. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1506) NullPointerException in TransactionManagementAnnotationProcessor

by jaikiran pai (JIRA)

NullPointerException in TransactionManagementAnnotationProcessor ---------------------------------------------------------------- Key: AS7-1506 URL: https://issues.jboss.org/browse/AS7-1506 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.0.1.Final A bean configured like: {code} @TransactionManagement @Stateless public class Bean { ... {code} results in a NPE in TransactionManagementAnnotationProcessor: {code} Caused by: java.lang.NullPointerException at org.jboss.as.ejb3.deployment.processors.TransactionManagementAnnotationProcessor.processTransactionManagement(TransactionManagementAnnotationProcessor.java:67) at org.jboss.as.ejb3.deployment.processors.TransactionManagementAnnotationProcessor.processComponentConfig(TransactionManagementAnnotationProcessor.java:57) at org.jboss.as.ee.component.AbstractComponentConfigProcessor.deploy(AbstractComponentConfigProcessor.java:53) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more {code} See referenced forum thread for details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1501) Adding logging levels for specific logging categories deosn't seem to work on anything below INFO.

by James Perkins (JIRA)

Adding logging levels for specific logging categories deosn't seem to work on anything below INFO. -------------------------------------------------------------------------------------------------- Key: AS7-1501 URL: https://issues.jboss.org/browse/AS7-1501 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.1.0.Alpha1 Adding a <logger /> to the configuration with a custom logging level of anything below INFO, e.g. TRACE or DEBUG, seems to have no affect. The following should log all hibernate messages, but only logs INFO and higher. <logger category="org.hibernate"> <level name="ALL"/> </logger> The following should only log warning messages, which it does. <logger category="org.hibernate"> <level name="WARN"/> </logger> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
2
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 August 2011