I think that starting with JBoss 3.2.3 the CMP engine has undergone more or
less drastic changes in order to accommodate more and more performance tuning
switches. I have the _impression_ that as a side-effect JBoss does not honor
some settings in standardjbosscmp-jdbc.xml anymore.
We managed
I am seeing this behaviour too in one of my entities where no matter what the
CMP engine generates fires a seperate SQL SELECT query for each cmp field
accessed.
I am too, using 3.2.6, why is it happening when the default load-group is set
to '*'?
Thanks in advance,
Erez
View the original
You need to properly configure your load groups.
Check out the Jboss administration docs for more details about CMP data loading
settings and implications.
Joachim
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3868688#3868688
Reply to the post :
triathlon98 wrote : You need to properly configure your load groups.
|
| Check out the Jboss administration docs for more details about CMP data
loading settings and implications.
|
| Joachim
Thanks for the answer. That is exactly what I have been doing all day. We
haven't declared
