Difference between revisions of "Research Notes - NexJ Training Tutorials"

From CDOT Wiki
Jump to: navigation, search
(Created page with '== Current Findings == '''Question:''' Where should one start if one wants to get a '''conceptual understanding''' of the code base of NexJ Model Server Express? <br><br>One can …')
 
(NexJ Concepts)
Line 10: Line 10:
  
 
== NexJ Concepts ==
 
== NexJ Concepts ==
 +
 +
=== NexJ Message ===
 +
* pp. 9-12, 18-21
 +
* '''tree structures'''
 +
** children: Value node, Message node
 +
* a list of NexJ Messages
 +
* format: an '''interna'''l NexJ message is formatted to an '''external''' format ("wire format")
 +
** e.g. a PersonCSV object is formatted to a CSV message
 +
* parse: the external message format is parsed to an internal NexJ message
 +
** e.g. a CSV messag is parsed back to a PersonCSV object

Revision as of 17:01, 5 August 2011

Current Findings

Question: Where should one start if one wants to get a conceptual understanding of the code base of NexJ Model Server Express?

One can download Introduction To NexJ Studio Express from the Open Health Tools Platform. It's useful for getting familiar with NexJ Studio Express. However, one must read NexJ Studio Fundamentals and identify the concepts as a result. Presently this document in not open sourced.

This document has useful clues for one to understand how the Persistence engine and the Integration engine are organized in the NexJ Framework (at the source code level).

  • In particular, one should understand how Class Persistence Mapping is done with the NexJ Studio Express.
  • Also one must learn the NexJ-Scheme language.

As for understanding the concepts implemented by the Integration Engine, one must read NexJ Studio - Integration Fundamentals. Presently this piece of document is not open sourced.

NexJ Concepts

NexJ Message

  • pp. 9-12, 18-21
  • tree structures
    • children: Value node, Message node
  • a list of NexJ Messages
  • format: an internal NexJ message is formatted to an external format ("wire format")
    • e.g. a PersonCSV object is formatted to a CSV message
  • parse: the external message format is parsed to an internal NexJ message
    • e.g. a CSV messag is parsed back to a PersonCSV object