Difference between revisions of "JSON Integration Adapter Code Review 1 Changes"
m (→Design Document) |
m (→Design Document) |
||
Line 33: | Line 33: | ||
* Make note of any normally standard features which are not implemented by the JSON parser/formatter | * Make note of any normally standard features which are not implemented by the JSON parser/formatter | ||
* Add section about required parts and null values | * Add section about required parts and null values | ||
− | * Add section about | + | * Add section about channels with multiple messages |
| In Progress | | In Progress | ||
|} | |} |
Revision as of 11:06, 24 August 2011
Contents
General
Tasks | Status |
---|---|
Exception
|
Complete for formatter, may be revisited for parser |
Documentation
|
|
Code Style
|
Design Document
Task | Status |
---|---|
Update Design Proposal Document
|
In Progress |
JSONMessagePartMapping
Task | Status |
---|---|
Use Hashholder instead of HashSet | Complete |
byte initialization
|
Complete |
StringParser
|
Complete |
RootJSONMessagePartMapping
|
Complete |
Composite Message Part modes
|
Complete |
m_sFormat
|
Complete |
JSONMessageParser
Task | Status |
---|---|
InvocationContextAware
|
|
Rename methods XXXNode to XXXPart | |
fail
1. Wrap fail so that is throws expection right away 2. Move fail statements from bottom to top, remove else clauses |
1. Complete 2. Incomplete |
parse()
|
|
parsing primitive values
|
JSONMessageFormatter
Task | Status |
---|---|
Format primitive values
|
Complete |
Pass enumerations into formatMessageRoot
|
Complete |