You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Joe Bohn <jo...@gmail.com> on 2010/05/10 22:13:08 UTC
Transaction Interceptor service
I noticed that we have a blueprint service defined in the blueprint xml
for the transaction interceptor. However, I don't see this service
itself being used anywhere. The interceptor bean is injected directly
into the TxElementHandler bean rather than using the service. Are there
future plans for this service definition or can it be removed?
The particular service reference I'm looking at is found in
https://svn.apache.org/repos/asf/incubator/aries/trunk/transaction/transaction-blueprint/src/main/resources/OSGI-INF/blueprint/transaction.xml:
<service ref="txinterceptor"
interface="org.apache.aries.blueprint.Interceptor">
<service-properties>
<entry key="namespace"
value="http://aries.apache.org/xmlns/transactions/v1.0.0"/>
</service-properties>
</service>
--
Joe
Re: Transaction Interceptor service
Posted by Valentin Mahrwald <vm...@googlemail.com>.
I think you are right this export serves no purpose in the current Apache Aries code and should be removed :)
On 10 May 2010, at 21:13, Joe Bohn wrote:
>
> I noticed that we have a blueprint service defined in the blueprint xml for the transaction interceptor. However, I don't see this service itself being used anywhere. The interceptor bean is injected directly into the TxElementHandler bean rather than using the service. Are there future plans for this service definition or can it be removed?
>
> The particular service reference I'm looking at is found in https://svn.apache.org/repos/asf/incubator/aries/trunk/transaction/transaction-blueprint/src/main/resources/OSGI-INF/blueprint/transaction.xml:
> <service ref="txinterceptor" interface="org.apache.aries.blueprint.Interceptor">
> <service-properties>
> <entry key="namespace" value="http://aries.apache.org/xmlns/transactions/v1.0.0"/>
> </service-properties>
> </service>
>
>
> --
> Joe