Changes

<big><big> JSON_Adapter</big></big>{{NexJ_Express IndexAdmon/obsolete}} [[Category: NexJ_Past_Projects]][[Category: NexJ Express JSON Adapter]] [[Category: NexJ Express Development]][[Category: NexJ Express]]

Develope Develop an adapter to expose NexJ Express Server objects using JSON<br/>- [https://docs.google.com/document/d/1z8KfOa7sLD6l3g-1djnm6eU4ErfXDcqRX5v7OR0RJho/edit?hl=en&authkey=CJS3xcQP Final Project Proposal] ===Contributors===* [[User:Gbatumbya|Grace Batumbya]] 

<big><big>'''Phase 11: Code Review 5Project Completed''' <br/big></big>Ongoing...

* Proposal proposal for review, make changes as by NexJ until approved<br/>- [https://docs.google.com/document/d/1z8KfOa7sLD6l3g-1djnm6eU4ErfXDcqRX5v7OR0RJho/edit?hl=en&authkey=CJS3xcQP Final Project Proposal]

*The <code>m_tokenValue </code> used in some of the error messages won’t always be populated. For example, in <code>parseArray()</code>, <code>m_tokenValue </code> is used, but it will only be valid if the current token is <code>TOKEN_ATOM</code>. *The <code>boolean.invalidToken</code> error message can be removed and you can use just <code>err.parse.unexpectedToken</code> instead, as one doesn’t know for certain that the input is a <code>Boolean</code>. Same for <code>null.invalidToken</code> and <code>number.invalidToken</code>.

*The boolean.invalidateToken error message can be removed and you <code>parseObject()</code>: the <code>if (sKey == null)</code> check can use just err.parse.unexpectedToken insteadnever succeed, as one doesn’t know for certain that the input because <code>instanceof</code> should return false if its argument is a Booldean. Same for <code>null.invalidateToken and number.invalidToken</code>.

* parseObject(): the if (sKey == null) check can never succeed, because instanceof should return false if its argument is null.===Phase 11: Code Review 11 5 (Done) ===