Re: To Spring or Not

2017-01-26 Thread Galen M O'Sullivan
Okay, the idea of using the converters when using the data rather than at ingest is quite intriguing and could be a very valuable aspect of the product, especially if it's easy to use. (We do have CacheListeners and the like now, but you have to understand the abstraction and then write some Java c

Re: To Spring or Not

2017-01-26 Thread John Blum
1 clarification... "*So, I do think a Data Conversion (and Formatting) service could be handy in the cases where the data needs to be converted for indexing, querying or other data access operations (e.g. Functions), that has not quite reached the application yet that needs to be handle in an appl

Re: To Spring or Not

2017-01-26 Thread John Blum
Looking at this problem on the flip-side, from an application's perspective (which can also be equated to data going out from the data store)... *Data Conversion* (and *Formatting* for that matter) is quite generic and has little to nothing to do with JSON, XML or any other format. Technically, ha

Re: To Spring or Not

2017-01-26 Thread Jacob Barrett
On Thu, Jan 26, 2017 at 11:36 AM Galen M O'Sullivan wrote: > I think the reason we use JSON is because it's easy. I'm not convinced that > 90% of JSON data is from JavaScript, unless you have data to back that up > -- a lot of scripting languages use it because it's convenient. > Excuse my hyper

Re: To Spring or Not

2017-01-26 Thread Galen M O'Sullivan
I think the reason we use JSON is because it's easy. I'm not convinced that 90% of JSON data is from JavaScript, unless you have data to back that up -- a lot of scripting languages use it because it's convenient. I'm not that familiar with how we handle JSON at present, but it's worth revisiting

Re: To Spring or Not

2017-01-25 Thread Jacob Barrett
So what you are trying to do is to define types for formats that don't have rich types (JSON, CSV, XML without Schema/DTD) and rigid structure for formats without rigid structure structure (JSON is unordered, CSV has no hierarchy, XML may not be strongly ordered) to map into a format that has rich

Re: To Spring or Not

2017-01-25 Thread Udo Kohlmeyer
The thought was to have a framework that could convert any incoming format, provided you have a converter for it. Be it JSON,XML,CSV... maybe even eventually POJO -> PDX... Yes, the starting point is humble... but it can be grown to be a service that will convert data formats... On 1/25/17

Re: To Spring or Not

2017-01-25 Thread Jacob Barrett
Does JAXB/JAX-RS not provide what yo are looking for to define JSON to Object mapping? On Wed, Jan 25, 2017 at 7:59 AM Udo Kohlmeyer wrote: > Hi there, > > I'm currently working on a proposal on a Data Conversion Service. This > service would primarily replace the ailing JSONFormatter, with the

To Spring or Not

2017-01-25 Thread Udo Kohlmeyer
Hi there, I'm currently working on a proposal on a Data Conversion Service. This service would primarily replace the ailing JSONFormatter, with the ability to provide some rules around how fields are converted (String -> Date, String -> Numeric, different Date formats). This of course could b