[#IDEA-16346] Support code completion for transaction attributes of TransactionInterceptor, TransactionProxyFactoryBean

IDEA: Feedback

Support code completion for transaction attributes of TransactionInterceptor, TransactionProxyFactoryBean

Created: 14 Nov 07 12:10 Updated: 02 Apr 08 18:44

Component/s:

Editor. Code Completion, J2EE.Spring

Build:

7,549

Description

« Hide

+ Pre-defined standard values, example: PROPAGATION_REQUIRED
+ Exceptions, when user types "-"

Note: It should work for sub-beans also.

Example:

<bean id="transactionInterceptor"
      class="org.springframework.transaction.interceptor.TransactionInterceptor">
    <property name="transactionManager" ref="dataSourceTransactionManager"/>
    <property name="transactionAttributes">
        <props>
            <prop key="endMatch">PROPAGATION_REQUIRED</prop>
        </props>
    </property>
</bean>

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Taras Tielkes - 19 Nov 07 17:25

If I remember correctly, the various settings of a transaction attribute string can occur in any order. Also, the exception parameters support both FQN names as well as "partial FQN" patterns.
So offering useful completion will be hard to implement and/or confusing for the user, and validation of the complete attribute pattern will take some time to implement.

Since the release of Spring 2.0 most people use either <tx:annotation-driven> or <tx:advice>, so in my personal opinion there would be more value in improving support for that.
I'll file some new JIRA tickets concerning that in a few days.