I'm on a project that has a base class entity, HistoricalEntity, that is
extended when we want an entity that keeps track of its changes. This entity
is extended by several other, sometimes unrelated, entities.
Although everything works, Hibernate generates some extremely long sql queries
I am having a problem, which I believe may be due to a bug, where having
multiple @ManyToMany relationships to the same entity is causing
BatchUpdateExceptions.
Example Entities:
Television: a television set
Channel: a television channel
television-sportsChannels: ManyToMany between Television
Hello,
I'm a big fan of the @Service EJB 3.0 extension because makes it easy to write
singleton EJB's. Unfortunately, I haven't had much luck with these in a
clustered environment. It appears that, even with the @Clustered annotation,
each node of the cluster gets it's on singleton instance
For anyone that is interested, this bug is fixed in Seam 2.0 GA on JBoss 4.2.1
GA 4.2.2 GA. It may also work with earlier versions of JBoss but I haven't
had a need to test it.
Thanks again for the help,
Austin
View the original post :
If I could attach the code I would but since I see no way, here's some more
inline code.
I modified the booking application and deployed it on both 4.2.1GA and 4.2.2GA,
both of which appear to have the same FlushMode issue.
In addition to my changes to get it working with JSF 1.2 RI I did
You were absolutely correct. I didn't catch that the SMPC was actually a Seam
Component and need to be retrieved with @In rather than @PersistenceContext.
After making this change I have learned several things and found one that I
believe to be a bug.
SMPC's only manage entity beans for the
I obtain a persistence context like this:
@PersistenceContext(type=PersistenceContextType.EXTENDED)
| private EntityManager em;
|
I changed my managed persistence context to match my code (since I use it as em
in several places):
core:managed-persistence-context name=em
|
Environment:
I have tried this in serveral environments...
Seam 1.2.1
JBoss 4.0.5 and 4.2.1
Myfaces (JSF 1.1) and JSF 1.2 RI
Windows XP and Solaris 10
HSQLDB and Oracle
Scenario:
I have a basic situation where I want to edit an entity (and it's related
entities on an edit page), go to a
I believe that I am using a seam managed persistence context...
From my components.xml
|core:managed-persistence-context name=entityManager
| auto-create=true
|persistence-unit-jndi-name=java:/myEntityManagerFactory/
|
From my
