David,

In our application we created an Api service [1] which is being called by a
simple routine to migrate existing data. Don't know how the resftul viewer
handles blobs but you could experiment with a Rest client [2] and report
issues here.

[1]
https://github.com/estatio/estatio/blob/master/dom/src/main/java/org/estatio/api/Api.java
[2] https://chrome.google.com/webstore/detail/advanced-rest-client/



On Thu, Feb 20, 2014 at 5:48 AM, David Tildesley <[email protected]>wrote:

> Hi Dan,
>
> Speaking of blobs, we noticed that somehow ISIS is persisting metadata
> with the uploaded blob (e.g. filename and maybe mimetype?). We were just
> wondering how this is done as we have to migrate an existing database table
> with a blob column (jpg photo) to our ISIS based app and we think we may
> have to bulk load through the framework rather than direct to the dom
> entity table. Or any other suggested approach for this once off migration?
>
> Regards,
> David.
>
>
>
>
>
> On Thursday, 20 February 2014 4:27 PM, Dan Haywood (JIRA) <[email protected]>
> wrote:
>
> Dan Haywood created ISIS-705:
> --------------------------------
>
>              Summary: Support actions accepting parameters, and also bulk
> actions, that return Blobs/Clobs
>                  Key: ISIS-705
>                  URL: https://issues.apache.org/jira/browse/ISIS-705
>              Project: Isis
>           Issue Type: Improvement
>           Components: Viewer: Wicket
>     Affects Versions: viewer-wicket-1.3.1
>             Reporter: Dan Haywood
>             Assignee: Dan Haywood
>             Priority: Minor
>              Fix For: viewer-wicket-1.5.0
>
>
> The issue here is that the returned Blob/Clob must be handled with a
> scheduled handler (see ActionResultResponseHandlingStrategy class) but it
> is also necessary to refresh the page by redirecting to a new page.  (In
> the case of an action accepting parameters, want to remove the dialog.  In
> the case of a bulk action, want to clear the toggles and refresh the list).
>
> Haven't yet figured out how to do that ... :-(
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.1.5#6160)
>

Reply via email to