April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6956) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Brand Neu (JIRA)

[ https://issues.jboss.org/browse/AS7-6956?page=com.atlassian.jira.plugin.s... ] Brand Neu edited comment on AS7-6956 at 4/19/13 8:11 AM: --------------------------------------------------------- Hi, relevant source-snippet from class: @ManagedBean(name="KorrekturgrundFacade") @SessionScoped @Stateful public class StdGrundKorrekturFacade extends AbstractFacade<StdGrundKorrektur> { @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) ... } was (Author: brand-neu): Hi, relevant source-snippet from class: <pre> @ManagedBean(name="KorrekturgrundFacade") @SessionScoped @Stateful public class StdGrundKorrekturFacade extends AbstractFacade<StdGrundKorrektur> { @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) ... } </pre> > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: AS7-6956 > URL: https://issues.jboss.org/browse/AS7-6956 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brand Neu > Assignee: Scott Marlow > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6958) Remove EL JARs from Hibernate Validator module

by Gunnar Morling (JIRA)

Gunnar Morling created AS7-6958: ----------------------------------- Summary: Remove EL JARs from Hibernate Validator module Key: AS7-6958 URL: https://issues.jboss.org/browse/AS7-6958 Project: Application Server 7 Issue Type: Feature Request Components: EE Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Gunnar Morling Assignee: David Lloyd With AS7-6665 (Update of the Hibernate Validator module to HV 5), the Unified EL RI JARs were added to the HV module in order to satisfy the dependency to the EL API added as of HV5/BV 1.1. These module internal JARs should be removed once there is an AS module providing an EL implementation usable for all kinds of deployments. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6956) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6956?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6956: ----------------------------------- >From the attached stack trace, in org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance.findExtendedPersistenceContext() variable currentInjectedXPCs appears to be null. {code} // will look directly at the top level bean being created (registerExtendedPersistenceContext() registers xpc there). result = currentInjectedXPCs.findExtendedPersistenceContextDeepInheritance(puScopedName); {code} > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: AS7-6956 > URL: https://issues.jboss.org/browse/AS7-6956 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brand Neu > Assignee: Scott Marlow > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6956) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6956?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6956: ----------------------------------- Workaround: If you want an extended persistence context in a web application, change to @PersistenceUnit(unitName = "MyPU") EntityManagerFactory. The EntityManager that you get from the EntityManagerFactory will be application managed (instead of container managed) and is probably what you want. The scope of the an application managed persistence context is that the EntityManager will stay open until you call close on it. > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: AS7-6956 > URL: https://issues.jboss.org/browse/AS7-6956 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brand Neu > Assignee: Scott Marlow > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6956) NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6956?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6956: ----------------------------------- Interesting, I didn't try this from a web application because you should only use PersistenceContextType.EXTENDED in a stateful session bean. Thanks for the bug report, I will definitely fix this! > NullPointer @ org.jboss.as.jpa.container.ExtendedPersistenceDeepInheritance > --------------------------------------------------------------------------- > > Key: AS7-6956 > URL: https://issues.jboss.org/browse/AS7-6956 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brand Neu > Assignee: Scott Marlow > Attachments: JBoss Web_7.2.0.Final - JBWEB000064 Error report.htm > > > Webproject with ManagedBean contains following PersistenceContext: > @PersistenceContext(unitName = "MyPU", type = PersistenceContextType.EXTENDED) > WebApp run fine under Jboss-7.1, in JBoss-7.2 (EAP-6.1.0) we've got NulPointer-Exception and therefore further exceptions. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6957) Cannot replace jar that bundle depends on

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6957?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6957: -------------------------------- Summary: Cannot replace jar that bundle depends on (was: Cannot replace dependent jar) > Cannot replace jar that bundle depends on > ----------------------------------------- > > Key: AS7-6957 > URL: https://issues.jboss.org/browse/AS7-6957 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 8.0.0.Beta1 > > > With an OSGi webapp that depends on a jar the jar cannot be replaced. > See BundleReplaceTestCase.testDependentJarReplace() -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6957) Cannot replace dependent jar

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6957: ----------------------------------- Summary: Cannot replace dependent jar Key: AS7-6957 URL: https://issues.jboss.org/browse/AS7-6957 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 8.0.0.Beta1 With an OSGi webapp that depends on a jar the jar cannot be replaced. See BundleReplaceTestCase.testDependentJarReplace() -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6938) Add and deploy does not fail if runtimeName already exists

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6938?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reassigned AS7-6938: ----------------------------------- Assignee: Thomas Diesler (was: Brian Stansberry) > Add and deploy does not fail if runtimeName already exists > ---------------------------------------------------------- > > Key: AS7-6938 > URL: https://issues.jboss.org/browse/AS7-6938 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, Server > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 8.0.0.Alpha1 > > > The ServerDeploymentHelper has this code > {code} > public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException { > ServerDeploymentActionResult actionResult; > try { > DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan(); > builder = builder.add(runtimeName, input).andDeploy(); > DeploymentPlan plan = builder.build(); > DeploymentAction action = builder.getLastAction(); > Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); > ServerDeploymentPlanResult planResult = future.get(); > actionResult = planResult.getDeploymentActionResult(action.getId()); > } catch (Exception ex) { > throw new ServerDeploymentException(ex); > } > if (actionResult.getDeploymentException() != null) > throw new ServerDeploymentException(actionResult); > return runtimeName; > } > {code} > which does not fail if the runtimeName already exists > There is a debug log like this > {code} > 11:11:25,103 DEBUG [org.jboss.as.controller.management-operation] (pool-4-thread-1) JBAS014616: Operation ("add") failed - address: ([("deployment" => "v200.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"v200.jar\")]" > {code} -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating runtime-exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5432?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5432: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 952629|https://bugzilla.redhat.com/show_bug.cgi?id=952629] fix is present in EAP 6.1.0.ER5 and has been in EAP branch for a longer time. commits: 96bcd07e and 90ac80ca. setting to verified.. > TransactionRolledbackLocalException doesn't reference the originating runtime-exception > --------------------------------------------------------------------------------------- > > Key: AS7-5432 > URL: https://issues.jboss.org/browse/AS7-5432 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: Barnabas Bodnar > Assignee: jaikiran pai > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > If a runtime-exception thrown by an EJB v2.x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()). > The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here. > This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException(). -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating runtime-exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5432?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5432: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 952629|https://bugzilla.redhat.com/show_bug.cgi?id=952629] from ON_QA to VERIFIED > TransactionRolledbackLocalException doesn't reference the originating runtime-exception > --------------------------------------------------------------------------------------- > > Key: AS7-5432 > URL: https://issues.jboss.org/browse/AS7-5432 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: Barnabas Bodnar > Assignee: jaikiran pai > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > If a runtime-exception thrown by an EJB v2.x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()). > The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here. > This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException(). -- 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

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013