Re: large entity field (trackingDigest) is truncated

2010-03-05 Thread Jeroen van der Wal
We're experiencing the same issue after merging with the latest trunk. We still have to do a root cause analysis. Perhaps something with the new conversion framework? -- Jeroen van der Wal Stromboli b.v. +31 655 874050

Re: large entity field (trackingDigest) is truncated

2010-03-03 Thread Scott Gray
Hi Mike, I have no idea if this will help but it will at least allow us to rule one thing out, could you please try changing: sql-type=CLOB to: sql-type=CLOB(2M) Thanks Scott HotWax Media http://www.hotwaxmedia.com On 2/03/2010, at 5:06 PM, Mike Voytovich wrote: The problem was in fact with

Re: large entity field (trackingDigest) is truncated

2010-03-03 Thread Mike Voytovich
Hi Scott, Thanks for the suggestion. I made the diff below and performed a clean-all and rebuilt - and it did NOT fix the problem... regards, -mike --- framework/entity/fieldtype/fieldtypederby.xml(revision 140) +++ framework/entity/fieldtype/fieldtypederby.xml(working copy) @@ -42,7

Re: large entity field (trackingDigest) is truncated

2010-03-02 Thread BJ Freeman
derby should not be used for production system. you might try the Derby docs on apache http://db.apache.org/derby/docs/ = BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Suppilier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=93

Re: large entity field (trackingDigest) is truncated

2010-03-02 Thread Mike Voytovich
Hi BJ, We're still in development, so I was hoping to continue to use Derby for the time being. And yes, I did check the Derby docs - but as I mentioned below, I can't find anyplace where OFBiz changes the default size for CLOB. I'll keep digging... thanks, -mike On 3/2/10 12:06 AM, BJ

Re: large entity field (trackingDigest) is truncated

2010-03-02 Thread BJ Freeman
if I understand you framework\entity\fieldtype\fieldtypederby.xml shows field-type-def type=very-long sql-type=CLOB java-type=String/field-type-def this is as far as ofbiz goes. = BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Suppilier Automation

Re: large entity field (trackingDigest) is truncated

2010-03-02 Thread Mike Voytovich
The problem was in fact with Derby. I switched over to MySQL, and now I see the correct data read out of the ShipmentRouteSegment entity. I think it is indeed an OFBiz bug, since Derby is the default database out of the box - and it will surely bite another new user who is either trying to use

large entity field (trackingDigest) is truncated

2010-03-01 Thread Mike Voytovich
Hi, I’m attempting to use the UPS shipment code in OFBiz to generate shipping labels. Note that we’re still using the default Derby database. OFBiz is able to send the confirm/accept requests and receive the responses, but an error is returned from UPS in handleUpsShipmentAcceptResponse -