JSON Integration Adapter Code Review 1 Changes
Contents
General
Tasks | Status |
---|---|
Exception
|
|
Documentation
|
|
Code Style
|
Design Document
Task | Status |
---|---|
Update Design Proposal Document
|
JSONMessagePartMapping
Task | Status |
---|---|
Use Hashholder instead of HashSet | |
byte initialization
|
|
StringParser
|
|
RootJSONMessagePartMapping
|
|
Composite Message Part modes
|
|
m_sFormat
|
JSONMessageParser
Issue | Description | Status |
---|---|---|
Remove/Use InvocationContextAware | Do not implement the invocation context aware interface if not used by the class. Or, use the interface for formatting of primitives. | |
Name methods XXXPart, not XXXNode | Rename methods to be XXXPart, for example as writeCompositeMessagePart, instead of writeCompositeMessageNode. | |
Wrap fail | Wrap all instances of fail with IntegrationException. | |
Override JSONParse | Override parse method of JSONParser in the JSONMessageParser class. Do this to avoid changing JSONParser. | |
Use primitive formatter when reading. | When reading information in from a stream in the formatter, use primitive formatter to determine the correct format of a primitive. |
JSONMessageFormatter
Issue | Description | Status |
---|---|---|
Format primitive values before outputting to writers. | Use the StringFormatter to format primitive values before outputting to the writer. For example, timestamps must be formatted before outputting to the writer. | |
Pass enumerations into formatMessageRoot | Do not use member/class variables for storing information unless absolutely necessary. Prefer to pass parameters around so that objects do not grow large as the parser/formatter iterates. |