As replied in another thread, maybe you can simply store the image
download URL (provided by Nuxeo) as a document node property, not the
whole binary data. I think it would be more efficient and easier to
maintain.
Regards,
Woonsan
>>
>> For Convenience the problem can be broken into following parts:
>
>
>> 1.we needed to call the web-service delivering icons and short description
>> on click of browse button(Thanks to you, we implemented this step in no
>> time).
>>
>> 2. need to call 2nd web service giving us the doc bytes of the image(Also
>> done)
>>
>> 3. Need to store the image in the document so that it could be displayed
>> on the website.(? STUCK).
>
> please help.
> Thanks in advance
> Hitesh Sehgal
>
> --
> Hippo Community Group: The place for all discussions and announcements about
> Hippo CMS (and HST, repository etc. etc.)
>
> To post to this group, send email to
hippo-c...@googlegroups.com
> RSS:
>
https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
> ---
> You received this message because you are subscribed to the Google Groups
> "Hippo Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
hippo-communi...@googlegroups.com.
> Visit this group at
https://groups.google.com/group/hippo-community.
> For more options, visit
https://groups.google.com/d/optout.
--
w....@onehippo.com www.onehippo.com
Boston - 745 Atlantic Ave, 8th Floor, Boston MA 02111
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
US
+1 877 414 4776 (toll free)
Europe
+31(0)20 522 4466