[
https://issues.apache.org/jira/browse/OFBIZ-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845601#action_12845601
]
Mike Voytovich commented on OFBIZ-3529:
---------------------------------------
Hi Bilgin,
Yes, I updated to tip of trunk, and the problem appears to be resolved.
Regards,
-mike
> Derby database can truncate entity fields > 8K
> -----------------------------------------------
>
> Key: OFBIZ-3529
> URL: https://issues.apache.org/jira/browse/OFBIZ-3529
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Environment: OS X, Derby database
> Reporter: Mike Voytovich
>
> I was attempting to use the UPS shipment code in OFBiz to generate shipping
> labels. Note that this was 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 truncated to
> 8K when being read back from the entity.
> The trackingDigest field-type is "very-long" with a SQL type of "CLOB", so I
> would expect it to save ~20K without issue.
> I switched over to MySQL for the database, and now the data is stored
> correctly.
> Note that there are no error messages in the logs regarding this truncation,
> and there's nothing in the documentation indicating that entity fields are
> limited to 8K when using the Derby database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
