Hi Godwin,
Yes, Jaggery File API is only working within Jaggery app context according
to documentation. so you will have to read it from Java and pass it to
jaggery. That's how we are doing with mobile apps.
On Mon, Oct 17, 2016 at 6:57 PM, Godwin Shrimal wrote:
> Hi Chathura,
>
>
>
> Yes there
Hi Chathura,
Yes there is a better approach than save those files in the jaggery app
> itself. This is mainly because jaggery app is getting bulky, difficult for
> clustering, and less security.
>
> What we have done for mobile app is store them in a secured place such as
> /repository/resource
Hi Godwin,
Yes there is a better approach than save those files in the jaggery app
itself. This is mainly because jaggery app is getting bulky, difficult for
clustering, and less security.
What we have done for mobile app is store them in a secured place such as
/repository/resources/mobileapps
Hi Godwin,
I think all the tasks about create/zip/delete the folder better be done in
modular java code. Then we can call the java code with Jaggery. Then we
would not need to detect the Context. We can use the "system.temp" folder
to store the temporary file/folders.
Cheers,
Ruwan
On Mon, Oct 17
We have done something similar in AppM for mobile apps where publisher
uploads binary (.apk etc) and users comes to store install these apps to
device. Download has handled as a byte stream and storage location is
stored in property of app-manger.xml
(${carbon.home}/repository/resources/mobileapps
Hi All,
We need to dynamically create zip file and allow download it from jaggery
application. For resolve the concurrent access of the system, we are going
to create a directory with the time-stamp and archive that directory and
allow user to download it. Then we need to create a separate cleanup