January 2008 - jboss-user - Jboss List Archives

[EJB 3.0] - Re: EntityManager not auto-flushing at end of SLSB method

by lpmon

I decided to post the code. I just saw your comment about the "new entity ..." and that does explain part of it (purchase not saved ) as you will see. That does not explain why the changed entity (member) did not get saved. Member was injected in the calling SLSB using SEAM and passed to this method. If it is true that a new entity is not saved on exit that needs to be emphasized in documentation. I started with the trailblazer and use the references. Maybe it is in there but I never noticed it. public @Stateless class PurchaseCreditsBean implements PurchaseCredits { @PersistenceContext EntityManager em; @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) public void purchaseCredits(Member member, int purchaseQty) { Purchase purchase = new Purchase(); purchase.setPurchasedCredits(purchaseQty); member.setCredits(purchaseQty + member.getCredits()); purchase.setMember(member); purchase.setPurchasedCredits(purchaseQty); em.merge(purchase); // TODO should not have to call merge em.merge(member); } } Thanks, my assumption is the SEAM injected entity is behaving as if it is not attached to my em as well. If this is the case I certainly misunderstood this. I bet many others have been down this same path! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116598#4116598 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116598

18 years, 3 months

1
0
0 / 0

[EJB 3.0] - Re: EntityManager not auto-flushing at end of SLSB method

by mazz＠jboss.com

Perhaps its best if you post your code - what's the method look like in its entirety? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116597#4116597 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116597

18 years, 3 months

1
0
0 / 0

[EJB 3.0] - Re: EntityManager not auto-flushing at end of SLSB method

by lpmon

Thanks Mazz. I am aware of the transaction layering effect (for lack of a better term) that applies if one session beans calls another. I am certain all of my session bean methods are exiting. The code is simple and basic. In this particular method I create one entity and modify another. Neither is saved to the DB unless I call em.merge. However, as an experiment, I added this to the method in question: @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) My understanding of this annotation is that the container should begin a new transaction for this method and it will end when the method exits. Correct? Adding this made no difference. I have never seen any of this work as documentation suggests it should work. I have been using JBoss AS for along time but this is my first EJB3 app. What could I have done wrong to cause this behavior? Again, 4.0.5.GA w/EJB3 (used installer and selected EJB3, Windows XP 64-bit) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116596#4116596 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116596

18 years, 3 months

1
0
0 / 0

[EJB 3.0] - Re: EntityManager not auto-flushing at end of SLSB method

by mazz＠jboss.com

Oh, and one other thing. The entity manager will only flush changes that you made to attached POJO entities. You can't just do "new MyEntity()" and expect the entity manager to do anything with it. You must do either em.persist() to attach it as a new entity, an em.find() to load an existing entity into the entity manager session or something similar to load an existing entity into session (like execute a query). em.merge() will, by definition, act as a em.persist() if the object you are merging isn't attached and is a new entity that does not yet exist in the DB. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116594#4116594 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116594

18 years, 3 months

1
0
0 / 0

[EJB 3.0] - Re: EntityManager not auto-flushing at end of SLSB method

by mazz＠jboss.com

Check your transaction demarcation. Just because you exit a method does NOT automatically mean your entity manager flushes the data to the DB. If you exit a method that also exits out of your transaction, THEN it will flush. But if you exit a method that was called with an already started transaction (e.g. tx type== SUPPORTS or an intra-bean call) then it won't necessarily do anything. For example, if you call A.method1 which calls A.method2, exiting A.method2 probably won't do anything special (it could, if you want - see REQUIRES_NEW semantics). Exiting A.method1 won't do anything special either, unless the transaction boundary stops at A.method1 (@TransactionType is REQUIRES for example and it was called outside of any tx) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116593#4116593 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116593

18 years, 3 months

1
0
0 / 0

[EJB 3.0] - EntityManager not auto-flushing at end of SLSB method

by lpmon

JBoss AS 4.0.5.GA, MySQL, nothing unusual about config, Windows XP Examples I have seen suggest that if you modify or create CMP entitybeans inside a session bean method then at the exit of that method these changes will be saved to the DB (flushed without calling em.merge or em.persist). I am not seeing this behavior. I have an app that I did several iterations of the above and the data is never saved. Calling em.flush() doesn't work either. If I call em.merge() it works? The merge call works but as documentation suggests that is inefficient. What's the deal? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116591#4116591 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116591

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Using Seam and Groovy together question

by Fangzx

The above hot deployment problem occurs only in Glassfish v2ur1, in Tomcat 6.0.14, it is ok! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116587#4116587 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116587

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Using Seam and Groovy together question

by Fangzx

The above hot deployment occurs only in Glassfish v2ur1, in Tomcat 6.0.14, it is ok? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116586#4116586 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116586

18 years, 3 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: In Linux environment , jboss-4.2.2.GA don't startup

by javang

Hi all My install env is sun vm, down is the trace: 16:23:33,116 INFO [ServerInfo] Java version: 1.5.0_06,Sun Microsystems Inc. 16:23:33,116 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-b05,Sun Microsystems Inc. 16:23:33,116 INFO [ServerInfo] OS-System: Linux 2.6.9-11.ELsmp,i386 16:23:33,116 DEBUG [ServerInfo] Full System Properties Dump 16:23:33,116 DEBUG [ServerInfo] java.runtime.name: Java(TM) 2 Runtime Environment, Standard Edition 16:23:33,116 DEBUG [ServerInfo] jboss.server.base.dir: /usr/jbossB/server 16:23:33,116 DEBUG [ServerInfo] java.protocol.handler.pkgs: org.jboss.net.protocol 16:23:33,116 DEBUG [ServerInfo] sun.boot.library.path: /usr/jdk15/jre/lib/i386 16:23:33,116 DEBUG [ServerInfo] jboss.server.lib.url: file:/usr/lutop/jbossB/server/all/lib/ 16:23:33,116 DEBUG [ServerInfo] java.vm.version: 1.5.0_06-b05 16:23:33,116 DEBUG [ServerInfo] javax.management.builder.initial: org.jboss.mx.server.MBeanServerBuilderImpl 16:23:33,116 DEBUG [ServerInfo] java.vm.vendor: Sun Microsystems Inc. 16:23:33,117 DEBUG [ServerInfo] java.vendor.url: http://java.sun.com/ 16:23:33,117 DEBUG [ServerInfo] path.separator: : 16:23:33,117 DEBUG [ServerInfo] java.vm.name: Java HotSpot(TM) Server VM View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116582#4116582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116582

18 years, 3 months

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - Re: Cannot get Hibernate SQL logging to work in 4.0.5.GA

by lpmon

A line of text seems to have dropped out of my post. In persistence.xml: I have property name="hibernate.show_sql" value="true" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116581#4116581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116581

18 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user January 2008