I'm working on improving our internal geolocation node map (based on the work Alex Bennee started) and trying to migrate it to use Hibernate instead of direct SQL, starting with the REST api.
Presently it doesn't seem at all easy to get "all nodes, and for each node a list of alarms and recent outages" out of the rest pages without doing separate queries and joining the data up on the client side. I'd rather avoid this. Is what I'm trying to do outside the scope of rest, or would it be profitable to extend the rest package to permit fetching of "NodeState" elements which contain information from various sources bundled together? Obviously as this is internal we can make it work just by keeping the direct SQL queries, or move the servlets to use Hibernate, but we'd much rather share any useful rest changes upstream and keep the forking minimal. So: what is the intended scope of the rest api? Thanks, Duncan Mackintosh NMS Software Engineer Cambridge Broadband Networks Limited Registered in England and Wales under company number: 03879840 Registered office: Selwyn House, Cambridge Business Park, Cowley Road, Cambridge CB4 0WZ, UK. VAT number: GB 741 0186 64
------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________ 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
