You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2010/03/06 10:29:27 UTC

[jira] Created: (ARIES-221) Interceptors can get lost in the interactions between multiple namespace handlers

Interceptors can get lost in the interactions between multiple namespace handlers
---------------------------------------------------------------------------------

                 Key: ARIES-221
                 URL: https://issues.apache.org/jira/browse/ARIES-221
             Project: Aries
          Issue Type: Bug
          Components: Blueprint, JPA, Transaction
    Affects Versions: 0.1
            Reporter: Valentin Mahrwald
            Assignee: Valentin Mahrwald


In a blueprint element like the following one taken from the blog sample

	<bean id="persistenceImpl"
		class="org.apache.aries.samples.blog.persistence.BlogPersistenceServiceImpl">
		<tx:transaction method="*" value="Required" />
		<jpa:context property="entityManager" unitname="blogExample" />
	</bean>

two namespace handlers must interact sensibly to achieve the desired result. 

Currently however there is a prolem. The transaction namespace handler registers interceptors against the bean metadata instance handed to it. The jpa namespace handler on the other hand decorates the bean metadata instance and returns a new one (without any interceptors). Hence, the result bean has no transactions. (Behaviour varies depending on the order of invocation).



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Work started: (ARIES-221) Interceptors can get lost in the interactions between multiple namespace handlers

Posted by "Valentin Mahrwald (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ARIES-221 started by Valentin Mahrwald.

> Interceptors can get lost in the interactions between multiple namespace handlers
> ---------------------------------------------------------------------------------
>
>                 Key: ARIES-221
>                 URL: https://issues.apache.org/jira/browse/ARIES-221
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint, JPA, Transaction
>    Affects Versions: 0.1
>            Reporter: Valentin Mahrwald
>            Assignee: Valentin Mahrwald
>
> In a blueprint element like the following one taken from the blog sample
> 	<bean id="persistenceImpl"
> 		class="org.apache.aries.samples.blog.persistence.BlogPersistenceServiceImpl">
> 		<tx:transaction method="*" value="Required" />
> 		<jpa:context property="entityManager" unitname="blogExample" />
> 	</bean>
> two namespace handlers must interact sensibly to achieve the desired result. 
> Currently however there is a prolem. The transaction namespace handler registers interceptors against the bean metadata instance handed to it. The jpa namespace handler on the other hand decorates the bean metadata instance and returns a new one (without any interceptors). Hence, the result bean has no transactions. (Behaviour varies depending on the order of invocation).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (ARIES-221) Interceptors can get lost in the interactions between multiple namespace handlers

Posted by "Valentin Mahrwald (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Valentin Mahrwald resolved ARIES-221.
-------------------------------------

    Resolution: Fixed

I moved the JPA namespace handler to use MutableBeanMetadata similar to the blueprint extension namespace handler, which resolves the issue in the specific problem case mentioned.

Also, I added a note on the NamespaceHandler interface to specify the responsibilities of the nshandler as regards interceptors.

> Interceptors can get lost in the interactions between multiple namespace handlers
> ---------------------------------------------------------------------------------
>
>                 Key: ARIES-221
>                 URL: https://issues.apache.org/jira/browse/ARIES-221
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint, JPA, Transaction
>    Affects Versions: 0.1
>            Reporter: Valentin Mahrwald
>            Assignee: Valentin Mahrwald
>
> In a blueprint element like the following one taken from the blog sample
> 	<bean id="persistenceImpl"
> 		class="org.apache.aries.samples.blog.persistence.BlogPersistenceServiceImpl">
> 		<tx:transaction method="*" value="Required" />
> 		<jpa:context property="entityManager" unitname="blogExample" />
> 	</bean>
> two namespace handlers must interact sensibly to achieve the desired result. 
> Currently however there is a prolem. The transaction namespace handler registers interceptors against the bean metadata instance handed to it. The jpa namespace handler on the other hand decorates the bean metadata instance and returns a new one (without any interceptors). Hence, the result bean has no transactions. (Behaviour varies depending on the order of invocation).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.