[
https://issues.apache.org/jira/browse/OLINGO-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939002#comment-13939002
]
Chandan V.A commented on OLINGO-185:
------------------------------------
Hi Carl,
What if callbacks are used for creating instances of type Blob and Clob?
The idea is, the OData JPA processor library on encountering a property with
type Clob.class or Blob.class can call an application specific, registered
callback class that could create an instance of type Clob.class and Blob.class
that are specific to JPA provider implementations. These instances can then be
set into the JPA entity properties by the OData JPA processor library. With
this approach at least we can keep the JPA models clean by restraining from
adding additional setter methods. For this a callback interface can be defined
from OData JPA processor library and applications using Blob and Clob data
types can implement these interfaces and register the call back implementation
via ODataJPAContext.
WDYT?
Thanks,
Kind Regards
Chandan VA
> support for Clob
> ----------------
>
> Key: OLINGO-185
> URL: https://issues.apache.org/jira/browse/OLINGO-185
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
> Affects Versions: V2 1.2.0
> Reporter: Carl J. Mosca
> Assignee: Chandan V.A
> Priority: Blocker
> Labels: blob, clob, jpa
> Fix For: V2 1.3.0
>
> Attachments:
> org.apache.olingo.odata2.jpa.processor.core.access.model.JPATypeConverter.java.diff
>
>
> support for Clob (other BLOB types?) We have successfully processed these as
> String type
--
This message was sent by Atlassian JIRA
(v6.2#6252)
