하늘을향해

ibatis X

  ApplicationContextProvider  
  

@Component public class ApplicationContextProvider implements ApplicationContextAware { private static ApplicationContext ctx; @Override public void setApplicationContext(ApplicationContext ctx) throws BeansException { this.ctx = ctx; } public static ApplicationContext getApplicationContext() { return ctx; } }

  사용법  
  

ApplicationContext ctx = ApplicationContextProvider.getApplicationContext(); Test test = (Test)ctx.getBean(Test.class);

(String) request.getAttribute("javax.servlet.forward.request_uri")

HttpServletRequest req = ((ServletRequestAttributes)RequestContextHolder.getRequestAttributes()).getRequest();

http://dveamer.github.io/backend/SpringRequestContextHolder.html

로깅할 문자의 {}에 차례대로 값이 들어감

logger.info("test:{} test1:{}","testlg","testlg1")

결과 : test : testlg test1:testlg1

https://huskdoll.tistory.com/795

public String test(HttpServletRequest request, Model model, @RequestParam MultiValueMap<String, Object> multiParams){

List<Object> ischks = multiParams.get("ischk");
for(int i=0; i < ischks.size() ; i++){

String testCd = multiParams.get("test_cd").get(i);

}

}

Most Spring applications only need a single transaction manager, but there may be situations where you want multiple independent transaction managers in a single application. The value attribute of the @Transactional annotation can be used to optionally specify the identity of the PlatformTransactionManager to be used. This can either be the bean name or the qualifier value of the transaction manager bean. For example, using the qualifier notation, the following Java code

public class TransactionalService {

    @Transactional("order")
    public void setSomething(String name) { ... }

    @Transactional("account")
    public void doSomething() { ... }
}

could be combined with the following transaction manager bean declarations in the application context.

<tx:annotation-driven/>

    <bean id="transactionManager1" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
        ...
        <qualifier value="order"/>
    </bean>

    <bean id="transactionManager2" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
        ...
        <qualifier value="account"/>
    </bean>

In this case, the two methods on TransactionalService will run under separate transaction managers, differentiated by the "order" and "account" qualifiers. The default <tx:annotation-driven> target bean name transactionManager will still be used if no specifically qualified PlatformTransactionManager bean is found.

참조 URL : https://www.lesstif.com/pages/viewpage.action?pageId=20774954