This is a feature request, from link below seems like no other workaround yet but to do the operation in the current connection in the context:
https://groups.google.com/forum/?fromgroups=#!topic/scriptella/BpfD6BJc804
Is it possible to support 'connection-id' in 'onerror' tag? Thanks
Update: The feature has been implemented and it will be included into 1.2 release. Current development snapshot can be download from here: http://javaforge.com/displayDocument/scriptella-1.2-SNAPSHOT.zip?doc_id=222665
I've created a change request and will consider adding this feature in future releases.
Regarding the workaround. Why is it not acceptable?
Related
I set up the live example of the Revit Design Check on my Autodesk Hub.
Link Here: https://revitdesigncheck.herokuapp.com/
After uploading the example model, it never created an issue.
does the live example still work? Or has the older api used in the live example been deprecated? Thanks.
That was indeed a problem, wrong Activity name (probably from old deploy), thanks for bringing this up. It's now fixed, and it created the issue as expected (see image)
We are adding version in the url for making our application backward compatible.
We have an url version: {mysite}.com/v1/author/id
May be in the next version of the app we may use something like this - {mysite}.com/v2/contributors/author/id
In order to support old url format in the new app, we are adding version in the url. By using the version in the path, we will know the url format and handle accordingly.
Is this the best way to do this or is there any other recommend approach for this?
I prefer React Router(Navigate to specific file/folders) on the version differentiation , if your both version is managed in same repository.
I am currently working on an old iOS app. I don't have much idea about cordova.
I am stuck at one place, where code uses window.requestFileSytem . There is some code in success callback of this function.
When I debug, I found that success callback is not triggered. I am not able to find any thing about this function in latest cordova document however there is some thing in older document.
So I am worrying about is window. requestFilesystem method is deprecated. If so then how can I achieve same thing in latest cordova.
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onReqFileSystemSuccess, null);
Any help would be appreciated.
Reviewing #iammilinds answer I have to correct my initial statement:
The window.requestFileSystem method is non-standard and should not be used. See the linked MDN docs.
Yet there are code examples containing the window.requestFileSystem method in the documentation for the cordova file plugin here or here (searching for window.requestFileSystem might help as the dcos are pretty large).
So regarding your initial problem: I'm afraid you'll have to debug it. Maybe checking the browser's console might give you a hint what's wrong. Or try to add an error handler to window.requestFileSystem as the last parameter like so:
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, onReqFileSystemSuccess, onErrorLoadFs);
Yes, it's deprecated.
It's implemented only by Chrome as of today.
This is what Mozilla page for Window.requestFileSystem() for this API says:
Non-standard
This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.
Above notice can be seen for several other "Files & Directories" APIs. However, below notice is significant and is read only for this particular API.
Even compared to the rest of the File and Directory Entries API, requestFileSystem() is especially non-standard; only Chrome implements it, and all other browser makers have decided that they will not implement it. It has even been removed from the proposed specification. Do not use this method!
The correct usage is as discussed in this post: How to use window.requestFileSystem of FileSystem API?
window.requestFileSystem = window.requestFileSystem || // Chrome
window.webkitRequestFileSystem; // Others
i try using SwiftData [1]: http://ryanfowler.github.io/SwiftData ,when import it to my project i have 120 errors that some of them is for println ,how i can resolved another errors?i add string extensions but errors still remains
From the authors' git you can see that the last commit was a year ago; SwiftData is not Swift 2-compliant. E.g. the println error you see is because println was changed to print with the release of Swift 2. Unless you want to port SwiftData to Swift 2 yourself, you can't really resolve this in an easy manner.
However, it seems like an existing user has already had a look at this, see the the posts by user RegisStGelais in the following thread:
SwiftData: Update for Swift 2.1? - Issue #33
For a complete Swift 2-updated version, see this fork by github user Lopdo:
https://github.com/Lopdo/SwiftData
If interested in the changes performed from original SwiftData -> Swift 2-compatible, see Lopdos commit.
Alternatively, have a look at a modified and extended Swift 2-ready version of SwiftData here:
https://github.com/mozilla/firefox-ios/blob/master/Storage/ThirdParty/SwiftData.swift
This is a heavily modified version of SwiftData.swift by Ryan Fowler
This has been enhanced to support custom files, correct binding,
versioning, and a streaming results via Cursors. The API has also been
changed to use NSError, Cursors, and to force callers to request a
connection before executing commands. Database creation helpers,
savepoint helpers, image support, and other features have been
removed.
I'd like to place all the #QueryParams inside a #BeanParam object and further document there. Is this possible?
currently not supported, but you could open a ticket here to see if it can be added
There is a ticket related and provided a patch. However the patch is based on the opener's private swagger branch. The change is very simple so it's easy to make a patch.
https://github.com/wordnik/swagger-core/issues/532
According to change log this feature was added in 1.3.5 version.
https://github.com/wordnik/swagger-core/wiki/Changelog#v135---apr-28-2014
Can confirm that this works with Jersey2 and swagger-jersey2-jaxrs_2.10. Just remember to annotate the properties in the #BeanParam target class.