[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-2243) Transaction problems, possible bug in ApplicationExceptionComponentMetaDataLoaderFactory

[Benoit Heinrich (JIRA)]

    [ https://issues.jboss.org/browse/EJBTHREE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594804#comment-12594804 ] 

Benoit Heinrich commented on EJBTHREE-2243:
-------------------------------------------

I did a local change by fixing the name of the wrong variable and that worked for me.

Here is a little patch for the fix:
{code}
Index: src/main/java/org/jboss/ejb3/tx/metadata/ApplicationExceptionComponentMetaDataLoaderFactory.java
===================================================================
--- src/main/java/org/jboss/ejb3/tx/metadata/ApplicationExceptionComponentMetaDataLoaderFactory.java    (revision 111157)
+++ src/main/java/org/jboss/ejb3/tx/metadata/ApplicationExceptionComponentMetaDataLoaderFactory.java    (working copy)
@@ -56,7 +56,7 @@
       if(signature instanceof ClassSignature)
       {
          ApplicationExceptionMetaData appExMetaData = findApplicationException(metaData, signature.getName());
-         if(metaData != null)
+         if(appExMetaData != null)
             return new BridgedMetaDataLoader<ApplicationExceptionMetaData>(key, appExMetaData, classLoader, defaultBridges);
       }
       return null;
{code}

I hope you can integrate for the next 6.1.0 version of jboss ;)


Cheers,
/Benoit

> Transaction problems, possible bug in ApplicationExceptionComponentMetaDataLoaderFactory
> ----------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2243
>                 URL: https://issues.jboss.org/browse/EJBTHREE-2243
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: transactions
>    Affects Versions: EJB3_1 1.0.3
>         Environment: JBoss AS 6.0.0.Final
>            Reporter: Benoit Heinrich
>            Assignee: jaikiran pai
>
> I think I've found a possible bug with transaction attributes management in jboss 6.0.0 Final.
>  
> The problem appears when using the @TransactionAttribute annotation on an EJB bean with the @Interceptors.
>  
> When using that it seems that the @TransactionAttribute annotation is ignored.
>  
> By removing the @Interceptors annotation it works and the right transaction attribute is used.
>  
> More details available in the jboss forum link.
> Cheers,
> /Benoit

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira