Yes, this has presented a number of problems for me in the past. I haven't found a
good work around other than simply not using a transaction of the long-running session
bean. You can push the timeout WAY up, but if you don't know what a reasonable time
to set the transaction timeout to
I'm not sure that I see a difference between using straight SQL in the session bean
versus finding the appropriate entity bean and querying it for the current inventory.
The advantage to using the entity bean is, of course, the portability that you
mention. I would think that two methods on
The final DTD has key-fields and key-field respectively as opposed to the
foreign-key-field versions. Just spent a little time finding that one myself.
David
David P. Russell
Lead Technical Consultant
Idea Integration
[EMAIL PROTECTED]
[EMAIL PROTECTED]
(585) 249-2600
(585) 273-7728
[EMAIL
OK, so I'm a little impatient and posted this question in a longer form two days ago.
Hopefully I won't annoy too many people by adding to the already significant deluge of
mail associated with this list.
Any thoughts on why the generated SQL for an EJB-QL query of the form:
SELECT OBJECT(o)
, and you will need to post a bug report (with only the
simple entity and query).
-dain
David Russell wrote:
OK, so I'm a little impatient and posted this question in a longer form two days
ago. Hopefully I won't annoy too many people by adding to the already significant
deluge of mail associated
After great success with creating a number of CMP beans in 3.0.0, I have finally run
into a snag.
I have a number of CMP EEJBs that I've created that are set to create their own
tables, etc. Those all seem to work fine. I then attempted to implement a new bean to
access information in an
