"no-select-before-insert" works for me and improved the performance of my app.
In server.log I also only see "Starting" and "Deployed".
at the top of my jbosscmp-jdbc, i have a defaults section. try that.
I put the <entity-command name= "no-select-before-insert/> in the defaults section of the "standardjbosscmp-jdbc.xml" file.
I don't have a jbosscmp-jdbc.xml file.
Could this be the problem?
Where should a jbosscmp-jdbc.xml be located, and what should its format be? IS it just overrides from the 'standard', like jboss.xml is to standardjboss.xml?
i dont know if not having jbosscmp-jdbc.xml is the problem. i woudl assume that if you edited standardjbosscmp-jdbc.xml, it shoudl work.
if you dont have a jbosscmp-jdbc.xml (for each ejb.jar), then jboss uses all the defaults. in this file, you specify the field column mappings (so you have control), tabel creation, table names, relationship mappings, as well as override standardjbosscmp-jdbc.xml settings, etc.
this might sound stupid, but are you sure you are editing the right standardjbosscmp-jdbc.xml (in the active instance directory?) e.g...the file for 'defaults', and not the one for 'all'?
the dtd for jbosscmp-jdbc.xml is in the docs/dtd dir. also, dishing out $10 for the docs, may be useful. i dont see how i coudl use cmp pain free without the docs.
I'm definately using the right standardjbosscmp-jdbc.xml file. So maybe its not a config problem?
Could it be somthing about the INSERT or the Table I'm inserting into? Does the primary key field value need to be first in the INSERT statement arg list?
No, the parameter order doesnt matter. typically, the container will create the row (insert) with the pk, then do an update (update) for all other bean values. (inefficient yes..but i dont know whats best, i've never tried to wire a cmp engine)
try making a minimal jbosscmp-jdbc.xml file like below. just place it next to your ejb-jar.xml in your jar/ear. if this doesnt work...sorry dude...i dunno. i just did this yesterday (disabled select before insert), and it worked for me. jb3.2.1. good luck..gotta get back to my behind schedule project! :)
<?xml version="1.0" encoding="UTF-8"?>
Thanks for the suggestion. I tried the minimal jbosscmp-jdbc.xml file idea, but it still gives me the SELECT before the INSERT. I'm wondering if this is a feature that only works for EJB2.0 beans? I'm still using EJB1.1.
You are correct, not handled in jaws.
See class org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand
This option seems to be added in jboss 3.2.x (as I can see in the DTD)