[EMAIL PROTECTED] wrote:
More on this error. Here is the code in GenericDelegator which writes the error to the log.//throwing an exception is a little harsh for now, just display a really big error message since we want to get all of these fixed... Exception newE = new Exception("Stack Trace"); Debug.logError(newE, "ERROR: Cannot do a find that returns an EntityListIterator with no transaction in place. Wrap this call in a transaction.", module); As the author desired, it is a REALLY big error. I was writing stdout to a file which almost filled up my hard disk with these errors. Could the author comment on why it is important to do this: TransactionUtil.begin(); Map inventory = dispatcher.runSync("getInventoryAvailableByFacility", UtilMisc.toMap("productId", productId, "facilityId", facilityId)); TransactionUtil.commit(); I.E. put the begin/commit around the runSync call other than just to avoid filling up your hard disk?
I'd suggest to avoid redirecting stdout to a file. Jacopo
Skip No virus found in this outgoing message. Checked by AVG. Version: 7.5.519 / Virus Database: 269.21.7/1331 - Release Date: 3/16/2008 10:34 AM
