Adligo Inc

Hi Seva, I realized that before I sent it, however I would like to add it as a Use-Case, and the kitchen sink :)_ The JSONx project does provide JSON...

Hi Again Seva, I just noticed your reference to JAX-RS and read the pdf; https://download.oracle.com/otn-pub/jcp/jaxrs-2_0-fr-eval-spec/jsr339-jaxrs-2.0-final-spec.pdf?AuthParam=1564178068_ee8830ae4348633414817d15577d5897 javax.xml.* is *NOT* supported in GWT; http://www.gwtproject.org/doc/latest/RefJreEmulation.html In addition GWT has it's own JSON API...

I see your point of view. My point of view is that GWT is what keeps Java cool, and promotes Java as a standard. I think a lot of folks...

Hi Seva, The following are my thoughts on a standards approach (sorry for verbosity); There are two major types of standards; The "It is Just What Everyone Does" Standard and...

Hi Again Seva, In my opinion there is *no conflict between the client contracts pattern and the obfuscation pattern*. However, the main issue when using both is that both parties...

Hi Seva, To respond to your summary paragraph. I agree that all additional features (marshaling, obfuscation and JavaScript run time support) should be optional in all target environments. The additional...

Hi Seva, Sorry for the delay in my response. I agree with most of what you said, however I do see the following conflicts; 1) In your point number 5...

JAX-RS doesn't fit into my plan, it's just how you are doing schema based marshaling currently in this JSONx project. Schema base Obfuscation is basing the Obfuscation of field names...

Hi Seva, Thanks for your clarification. *GWT compatibility is the primary concern of mine *since I would like to support JavaScript systems like the , Node.js server, and clients like...

Hi Seva, Ok the invoice example sounds like a good place to start. My comments about JAX-RS are just rantings about how things are designed in silos and could work...