Difference between revisions of "JSON Integration Adapter"
m (→Project Phases) |
m (→Project Phases) |
||
| Line 27: | Line 27: | ||
Phase I. Research | Phase I. Research | ||
| − | # | + | # Complete Fundamentals of NexJ Studio tutorial |
| − | # | + | # Complete NexJ Integration tutorial |
| − | # | + | # Install NexJ Studio Express from source |
Phase II. Planning and Approval | Phase II. Planning and Approval | ||
| − | # | + | # Receive general approval for project |
| − | # | + | # Receive approval for JSON encoding options |
| − | # | + | # Receive approval for JSON formatting options |
Phase III. Message Formatter | Phase III. Message Formatter | ||
| − | # | + | # Add JSON to .XSD base types |
| − | # | + | # Create sample JSON .message |
| − | # | + | # Parse sample JSON .message with JUnit Test |
| − | # | + | # Create first set of unit tests for Message Formatter |
| − | # | + | # Code Message Formatter first draft |
| − | # | + | # Resolve issues with first set of unit tests |
| − | # | + | # Create second set of unit tests |
| − | # | + | # Resolve issues with second set of unit tests |
| − | # | + | # Refactor and code message formatter |
Phase IV. Message Parser First Draft | Phase IV. Message Parser First Draft | ||
| − | # | + | # Discover how to connect JSON RPC parser with Message Parser |
| − | # | + | # Create first set of trivial unit tests for Message Parser |
| − | # | + | # Code Message Parser skeleton |
| − | # | + | # Pass first set of trivial unit tests |
| − | # | + | # Create second set of unit tests (non-trivial) for Message Parser |
| − | # | + | # Code Message Formatter first draft |
| − | # | + | # Resolve issues with second set of unit tests |
| − | # | + | # Refactor |
Phase V. Integration and Stress Tests | Phase V. Integration and Stress Tests | ||
| − | # | + | # Test Message Formatter and Message Parser with integration and stress tests |
| − | # | + | # Test through NexJ Studio Express GUI (manual testing) |
Phase VI. Internal Code Review | Phase VI. Internal Code Review | ||
| − | # | + | # Internally review code at CDOT |
Phase VII. Optimization | Phase VII. Optimization | ||
| − | # | + | # Find more code optimizations relevant to Enterprise environments |
Phase VIII. First Code Review at NexJ | Phase VIII. First Code Review at NexJ | ||
| − | # | + | # Date TBA |
Phase IX. Code Rewrite | Phase IX. Code Rewrite | ||
| − | # | + | # Rewrite code to conform with NexJ suggestions and |
Phase X. Second Code Review at NexJ | Phase X. Second Code Review at NexJ | ||
| − | # | + | # Date TBA |
Phase XI. Project Completion | Phase XI. Project Completion | ||
Revision as of 14:00, 16 June 2011
Contents
Project Repository
https://bitbucket.org/b_lim/nexj-express-json-integration-adapter/overview
Project Goal
To create an adapter for the NexJ Core similar in methodology and design of existing message adapters (XML, Fixed, CSV etc.) but using the JSON format
Contributors
Current Status
See https://bitbucket.org/b_lim/nexj-express-json-integration-adapter/changesets for changesets.
Forked NexJ code and created public repository for others to monitor progress and contribute.
Completed overview of NexJ Integration classes and coding method and class stubs. In process of creating unit tests.
Project Phases
JSON Integration Adapter Phases
Phase I. Research
- Complete Fundamentals of NexJ Studio tutorial
- Complete NexJ Integration tutorial
- Install NexJ Studio Express from source
Phase II. Planning and Approval
- Receive general approval for project
- Receive approval for JSON encoding options
- Receive approval for JSON formatting options
Phase III. Message Formatter
- Add JSON to .XSD base types
- Create sample JSON .message
- Parse sample JSON .message with JUnit Test
- Create first set of unit tests for Message Formatter
- Code Message Formatter first draft
- Resolve issues with first set of unit tests
- Create second set of unit tests
- Resolve issues with second set of unit tests
- Refactor and code message formatter
Phase IV. Message Parser First Draft
- Discover how to connect JSON RPC parser with Message Parser
- Create first set of trivial unit tests for Message Parser
- Code Message Parser skeleton
- Pass first set of trivial unit tests
- Create second set of unit tests (non-trivial) for Message Parser
- Code Message Formatter first draft
- Resolve issues with second set of unit tests
- Refactor
Phase V. Integration and Stress Tests
- Test Message Formatter and Message Parser with integration and stress tests
- Test through NexJ Studio Express GUI (manual testing)
Phase VI. Internal Code Review
- Internally review code at CDOT
Phase VII. Optimization
- Find more code optimizations relevant to Enterprise environments
Phase VIII. First Code Review at NexJ
- Date TBA
Phase IX. Code Rewrite
- Rewrite code to conform with NexJ suggestions and
Phase X. Second Code Review at NexJ
- Date TBA
Phase XI. Project Completion
Project Repository
To be determined
Resources
NexJ Developer's Guide
NexJ Integration Fundamentals
