Thanks for the help Tim.
I am not sure I like this solution. Why do I have to go and change this in
the application-deployments folder? The same question applies to the table
name for the CMP Beans. How do I choose a table name different than the
default one without touvhign the
At 10:29 06.02.2001 , you wrote:
Thanks for the help Tim.
I am not sure I like this solution. Why do I have to go and change this in
the application-deployments folder? The same question applies to the table
name for the CMP Beans. How do I choose a table name different than the
default one
You should not be changing the deployment folder files directly, except to check
to see if something works. You should create your own orion-ejb-jar.xml file in
your own EAR (or build directory if you deploy directly). Orion will then pickup
your version of orion-ejb-jar.xml and add anything else
Thank you again for your very helpful advices!
It saves me a lot of time.
Danut
At 12:55 PM 2/6/2001 -0500, Tim Endres wrote:
You should not be changing the deployment folder files directly, except to
check
to see if something works. You should create your own orion-ejb-jar.xml
file in
your
Danut,
please reread my posting. I wrote that it is not meant as a flame and I was
dead serious about that. you are discussing with people on this list about
why something has to go where in the deployment files, so you obviously
have to know. if you don'zt trake the time to learn those
Check the docs. There is a flag that you need to set to tell Orion
that is does not have "exclusive" access to the database, and that
it needs to recognize when a record is updated by a program other
than Orion.
I believe you need to look at the "exclusive-write-access" attribute
of the
