Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "OHF SODA Stepstone/ideas"

m (Implementation)
 
(3 intermediate revisions by the same user not shown)
Line 13: Line 13:
 
**WS-MakeConnection for unaddressable edges?
 
**WS-MakeConnection for unaddressable edges?
 
*Check in and update unit tests
 
*Check in and update unit tests
 +
*Investigate new object model and persistence solution
 +
**POJO and JPA (EclipseLink, openJPA)
 +
**EMF and Teneo (Hibernate, EclipseLink, etc.)
 +
**SDO/DAS (EclipseLink)
 +
**BIRT ODA
 +
*Investigate ECF APIs for edge<->backend
 
*Investigate deviceAdmin/Remote Device Manager (perhaps using p2)
 
*Investigate deviceAdmin/Remote Device Manager (perhaps using p2)
 
*Work on data visualization in backend
 
*Work on data visualization in backend

Latest revision as of 15:21, 28 October 2008

Implementation

  • Flush out REST interface between edge and backend
    • Investigate new dk Servlet interface
  • Open bugs and commit
    • JMS support
    • sendWithReply
  • Refactor dk bluetooth connection to use IWorker
  • Improve webservices support
    • flush out and checkin simplesoap impl OR investigate making Apache Muse fit right
    • Dynamic web services (eg. new Distributed OSGi spec)
    • WS-Security
    • WS-Notification
    • WS-MakeConnection for unaddressable edges?
  • Check in and update unit tests
  • Investigate new object model and persistence solution
    • POJO and JPA (EclipseLink, openJPA)
    • EMF and Teneo (Hibernate, EclipseLink, etc.)
    • SDO/DAS (EclipseLink)
    • BIRT ODA
  • Investigate ECF APIs for edge<->backend
  • Investigate deviceAdmin/Remote Device Manager (perhaps using p2)
  • Work on data visualization in backend
    • dojo/birt charting

Infrastructure

  • Get build/updatesite working right with p2 for Ganymede
    • DK works but seems to screw up environment
  • investigate continuous build/functional test harness

Back to the top