It was rightly suggested that I forward this to the devel list. (=
----
So I've been trying to write some web stuff for OpenNMS using JS frameworks
and I've run into a handful of roadblocks.
There are a bunch of CRUD operations missing from the REST API but if I can
figure this Jersey business out it shouldn't be too hard to implement. But
it means some parts of the API could change. I'm doing this work in
feature-angular-browser, only locally right now.
The other problem is that the REST API is arguably emitting broken JSON.
This can be worked around using hash array notation, as Alejandro corrected
me, but it still isn't technically very correct as you cannot access an
object like:
var foo = jsonData;
console.log(foo.@count); // doesn't work
console.log(foo["@count"]); // does work
Fixing this means injecting a new JAXB Context Resolver that builds JSON
using 'natural' notation instead of mapped. The problem is that JAXB puts
the @ symbol in front of attributes..
The problem is if I do this anyone who has worked around the '@' notation
will break... How many people do you think are using the REST API in JSON
notation? Is this a concern for TOG?
--
Matt Raykowski
/s
--
Matt Raykowski
/s
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
