If we use our own connection pools and handle our own transactions
within the db, is there likely any issue with using other threads to do
background tasks that touch the database? I can see there may be issues
in a regular EJB world with declarative transactions and such (does EJB
have its ow
That's too bad, indeed. I wouldn't have figured that ELs were only
evaluated at run time since they can certainly be converted into
standard Java code as you pointed out. To lose the compile time checks
and incur repeated performance hits to re-evaluate doesn't make much
sense. Perhaps there
