Search:

Type: Posts; User: hanasaki; Keyword(s):

Search: Search took 0.01 seconds.

  1. Unfortunately, I cannot share the configuration...

    Unfortunately, I cannot share the configuration files. The problem was solved by moving all annotated methods into the same class.
    I have found references to it being a "bad idea" to have...
  2. Right. The highest method (first called) does...

    Right. The highest method (first called) does commit as expected. The issue is that the method it calls, in another class, with REQUIRED, actually seems to create a new transaction that commits on...
  3. Spring3 - annotated transaction commits on All method returns

    Spring3
    The below code path is followed in TransactionInterceptor method invoke.
    Debugging line-by-line and checking the DB shows that all annotated @Transactional methods have commit called on the...
  4. @Transactional intercepts annotated method and method it calls and calls etc...

    Spring 3 using an @Transaction(value "manager"...) <= the version that became available in spring3 to deal with multiple transaction managers at the same time.

    A method is annotated as...
  5. Since the ORM is Hibernate - using...

    Since the ORM is Hibernate - using HibernateTransactionManager
    Since this is spring3 - using specific Transactional(value="myTransactionManager") and the methods on C1 and C2 both use the same named...
  6. Thank you for the compliment. I do think I need...

    Thank you for the compliment.
    I do think I need Propagation.REQUIRES_NEW because each call to the first method in C1 should be its own isolated transaction. I imaging that the existing one is...
  7. @Transactional method : transaction not propagated : individual commits

    Using Spring 3 + hibernate3 + c3p0 and hibernate transaction manager.
    In the below I expect the data to be deleted and then inserted in one atomic transaction. The issue is that another process...
  8. Replies
    4
    Views
    3,725

    The suggestion unfortunately still does not...

    The suggestion unfortunately still does not create the tables. One key difference is the loadTimeWeaver in my config. I took that out however it does not result in the tables being created. ...
  9. FYI: spring beans.xml : spring 3.x

    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    ...
  10. FYI: persistence.xml - JPA 2.0

    <?xml version="1.0" encoding="UTF-8"?>
    <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"...
  11. Replies
    4
    Views
    3,725

    This seems quite closely tied to another question...

    This seems quite closely tied to another question / post.
    Instead of post-processing the persistence.xml, the idea is to use spring beans to dynamically provide the information that would normally...
  12. Spring 3.x JPA2 and drop-create tables : howto?

    What can be used in a spring bean xml configuration file to specify that JPA2 should create the needed tables when it runs? (Like the hibernate "drop-create" or "create") This is running in a JUnit...
  13. Common way to deploy WAR & EAR to tomcat, bea, websphere etc... + jndi config?

    Looking for an installer that supports building a WAR / EAR (maybe Maven based)
    It also needs to be able to take the WAR and/or EAR and:

    setup Appserver JNDI resources that can be used by the...
  14. Spring : ServiceConstructionException from new bean under WEB-INF/classes

    Deployment is a WAR file. For some reason the context is throwing a
    ServiceConstructionException when the restful resource bean is setup with an ID. Any ideas why and resolution?

    The only...
Results 1 to 14 of 15