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> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Mike Voytovich sent the following on 3/1/2010 9:43 PM: > 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 - “The > XML document is not well formed”. > > It turns out that we’re properly receiving a 20,000 byte “ShipmentDigest” > from UPS in the handleUpsShipmentConfirmResponse method; but it looks like > this is being truncated to exactly 8K when written out to the > ShipmentRouteSegment entity. i.e., the ShipmentDigest data is correct in / > ofbiz/work/ofbiz/upscert/UpsShipmentConfirmResponse log file; but is 8K (with > the remainder padded with "�") in the UpsShipmentAcceptRequest log file. > > The trackingDigest field-type is “very-long” with a SQL type of “CLOB”, so I > would expect it to save ~20K without issue. > > Has anyone else run into this type of problem? Is there something that needs > to be configured in Derby to allow large entity fields? I did find some > documentation on Derby for setting the CLOB size, but I don’t see anywhere in > OFBiz where this is done. > > thanks, > -mike >
