Hi list
We have a number of spring services that use the TransactionProxyFactoryBean transaction wrappers to do the right thing (example at end).
Ideally, I would like to use XFire to expose the transaction-wrapped TaxonomyService (which implements ITaxonomyService).
Even more ideally I'd like to use JSR-181 annotations on ITaxonomyService (and aegis annotations on dependent classes) in order to get it set-up correctly.
I could do this by writing a proxy bean (much as you when using Spring/Axis and generating something like JaxRpcTaxonomyServiceBean that just forwards to the 'real' service), but I was wondering if there is a simpler (minimal configuration) way with xfire ?
Example of a service:
<bean id="TaxonomyService"
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBean">
<property name="transactionManager">
<ref bean="TransactionManager" />
</property>
<property name="target">
<ref bean="TaxonomyServiceTarget" />
</property>
<property name="transactionAttributes">
<props>
<prop key="*">
PROPAGATION_REQUIRED
</prop>
</props>
</property>
</bean>
<bean id="TaxonomyServiceTarget"
class="com.cswgroup.kms.services.beans.TaxonomyServiceBean">
<property name="modelFactory">
<ref bean="ModelFactory" />
</property>
<property name="persistenceManager">
<ref bean="PersistenceManager" />
</property>
<property name="userContextAuthenticator">
<ref bean="UserContextAuthenticator" />
</property>
</bean>
- [xfire-user] Best practice for TransactionProxyFactoryBean b... Nigel Magnay
- [xfire-user] DOMOutHandler problem Adam Chesney
- Re: [xfire-user] DOMOutHandler problem Dan Diephouse
- Re: [xfire-user] Best practice for TransactionProxyFact... Nick Airey
