cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dick van den Brink (JIRA)" <>
Subject [jira] [Commented] (CB-4851) Android Storage API
Date Thu, 19 Sep 2013 21:13:51 GMT


Dick van den Brink commented on CB-4851:

I'm not here for support, the docs are saying it is part of cordova and not a separate plugin.
That is why I asked if it was a documentation error or if it was accidentally removed. 

I don't think the status of this issue is resolved as the Storage api requires a plugin to
use websql according to your comment and the documentation says otherwise.
> Android Storage API
> -------------------
>                 Key: CB-4851
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 3.0.0
>            Reporter: Dick van den Brink
>            Assignee: Joe Bowser
>              Labels: android, storage
> According to the documentation the Storage API is provided in the core of cordova, but
it is removed from the Android Core.
> Documentation:
> {quote}As of version 3.0, access to Storage APIs is built into Cordova, and does not
require using the CLI to add plugins as described in The Command-line Interface.
> {quote}
> I did add the xml to the config page but I get the following error:
> {quote}
> Error adding plugin org.apache.cordova.Storage.
> exec() call to unknown plugin: Storage
> java.lang.ClassNotFoundException: org.apache.cordova.Storage
> at java.lang.Class.classForName(Native Method)
> at java.lang.Class.forName(
> at java.lang.Class.forName(
> at org.apache.cordova.PluginEntry.getClassByName(
> {quote}
> Is the documentation wrong or is the Storage class incorrectly deleted?
> Note: the storage code is still provided in cordova.js, but not in the jar. Also the
Java code is in the 2.9 branch. It is deleted in the commit with sha1 id: adcbd879c846dd3f7a3db960a3c7af14acbbda41

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message