It has been developed for approximately more than 9 months, and I don't know how many times have been revised, there is always something that is not satisfactory. Originally, I can release the first version of the public test in March, but the perfect heart is always driven to the improvement of me, I would rather. Always feel that the current relationship is not very good, trying to find a relationship between the long-term handling of persistent classes. A lot of information on the inspection, also referring to several frameworks, but I still feel very confused. These days are so much more than the company, and the friends are really irritated. I hope that I can change the lasting relationship between the lasting relationship. Good and bad hopes, there is a friend in public testing, and I will have a further improvement, and I have a longer think time. A further simplification of the persistence interface was performed in the current manner, and a transaction manager that across the database is required when using the application server. After all, Dudoj is still The framework does not have transaction management capabilities, which can rely on the container in the EJB environment to control the transaction, and there must be a mechanism to implement cross-data transactions outside the EJB container. I checked a lot of information to discover the JOTM transaction management framework. This framework enables cross-data transactions, multi-connection transactions, compatible with JTA, supports OTS. Detailed information requires further testing, if possible, prepare the integrated transaction management framework to implement cross-data transaction management. It must be released before July 10.
