You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Tim Kim (JIRA)" <ji...@apache.org> on 2012/08/28 00:38:07 UTC

[jira] [Created] (CB-1284) FileTransfer on PlayBook throws cycle error

Tim Kim created CB-1284:
---------------------------

             Summary: FileTransfer on PlayBook throws cycle error 
                 Key: CB-1284
                 URL: https://issues.apache.org/jira/browse/CB-1284
             Project: Apache Cordova
          Issue Type: Bug
          Components: BlackBerry
    Affects Versions: 2.0.0
         Environment: Playbook




            Reporter: Tim Kim
            Assignee: Tim Kim
            Priority: Minor
             Fix For: 2.1.0


With the recent introduction of not allowing cycles within require (http://markmail.org/thread/ql7v4rq25rpqil4y) have made my FileTransfer implementation on PlayBook non working. 

The error specifically has to do with how I'm requiring the resolveFileSystemUri and FileEntry objects within the FileTransfer class. 

--
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: http://www.atlassian.com/software/jira

[jira] [Commented] (CB-1284) FileTransfer on PlayBook throws cycle error

Posted by "Tim Kim (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CB-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442775#comment-13442775 ] 

Tim Kim commented on CB-1284:
-----------------------------

Fixed in this commit: https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-js.git;a=commit;h=106f57ea9918c15ea8f9146ec2ac7a56eec32bf1

To note: I ended up using the Playbook's implementation of resolveFileSystemUri and FileEntry objects. 
                
> FileTransfer on PlayBook throws cycle error 
> --------------------------------------------
>
>                 Key: CB-1284
>                 URL: https://issues.apache.org/jira/browse/CB-1284
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: BlackBerry
>    Affects Versions: 2.0.0
>         Environment: Playbook
>            Reporter: Tim Kim
>            Assignee: Tim Kim
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> With the recent introduction of not allowing cycles within require (http://markmail.org/thread/ql7v4rq25rpqil4y) have made my FileTransfer implementation on PlayBook non working. 
> The error specifically has to do with how I'm requiring the resolveFileSystemUri and FileEntry objects within the FileTransfer class. 

--
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: http://www.atlassian.com/software/jira

[jira] [Resolved] (CB-1284) FileTransfer on PlayBook throws cycle error

Posted by "Tim Kim (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CB-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Kim resolved CB-1284.
-------------------------

    Resolution: Fixed
    
> FileTransfer on PlayBook throws cycle error 
> --------------------------------------------
>
>                 Key: CB-1284
>                 URL: https://issues.apache.org/jira/browse/CB-1284
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: BlackBerry
>    Affects Versions: 2.0.0
>         Environment: Playbook
>            Reporter: Tim Kim
>            Assignee: Tim Kim
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> With the recent introduction of not allowing cycles within require (http://markmail.org/thread/ql7v4rq25rpqil4y) have made my FileTransfer implementation on PlayBook non working. 
> The error specifically has to do with how I'm requiring the resolveFileSystemUri and FileEntry objects within the FileTransfer class. 

--
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: http://www.atlassian.com/software/jira