Skip to content

URI addresses used are inconsistent with previous platforms #123

Closed
jeffheifetz opened this Issue Jun 28, 2012 · 0 comments

2 participants

@jeffheifetz

No description provided.

@jeffheifetz jeffheifetz was assigned Jun 28, 2012
@jeffheifetz jeffheifetz referenced this issue in blackberry-webworks/BB10-WebWorks-Framework Jun 28, 2012
Closed

Next uri address fix #75

@jeffheifetz jeffheifetz pushed a commit to blackberry-webworks/BB10-WebWorks-Framework that referenced this issue Jun 29, 2012
Jeffrey Heifetz This commit fixes blackberry/BB10-WebWorks-Framework#123 that was
introduced when we added  plugins. By doing so we changed the URI
addresses used for our APIs. To address this, the bridge plugin was
changed to a default plugin.

This changes the plugin loading logic, it now will use the default
plugin when the one given is undefined instead of throwing a 404.

This also includes changes so that the default plugin will throw a 404
if something doesn't exist and only after this check for Whitelisting.

Fixes code to not work based on exception
d6f46d8
@jeffheifetz jeffheifetz pushed a commit to blackberry-webworks/BB10-WebWorks-Framework that referenced this issue Jun 29, 2012
Jeffrey Heifetz Changed the URI APIs to not have the bridge plugin.
This commit fixes blackberry/BB10-WebWorks-Framework#123 that was
introduced when we added  plugins. By doing so we changed the URI
addresses used for our APIs. To address this, the bridge plugin was
changed to a default plugin.

This changes the plugin loading logic, it now will use the default
plugin when the one given is undefined instead of throwing a 404.

This also includes changes so that the default plugin will throw a 404
if something doesn't exist and only after this check for Whitelisting.

Fixes code to not work based on exception

Reviewed By: Nukul Bhasin <nbhasin@rim.com>
Tested By: Tracy Li <tli@rim.com>
0514533
@nukulb nukulb closed this Jul 22, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.