camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pontus Ullgren (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-9799) JSON/JSON Schema validator
Date Fri, 15 Sep 2017 15:07:00 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167983#comment-16167983
] 

Pontus Ullgren edited comment on CAMEL-9799 at 9/15/17 3:06 PM:
----------------------------------------------------------------

Started to look into this issue again. And started implementing a component based on everit.
However since Everit now does it's distribution mainly using jitpack and does not seem to
publish on maven central anymore this would require a extra repository entry in the pom.xml.
Would this be a problem if/when a PR is created to the Camel project ?

Link as reference
https://github.com/everit-org/json-schema#maven-installation


was (Author: pontus.ullgren):
Started to look into this issue again. And started implementing a component based on everit.
However since Everit now does it's distribution mainly using jitpack and does not seem to
publish on maven central anymore this would require a extra repository entry in the pom.xml.
Would this be a problem if/when a PR is created to the Camel project ?

> JSON/JSON Schema validator
> --------------------------
>
>                 Key: CAMEL-9799
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9799
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Andreas Gebhardt
>             Fix For: Future
>
>
> > Von: Gnanaguru S
> > An: ★ dev@camel.apache.org
> >
> > Subject: \[DISCUSS\] - Thoughts on Apache Camel 2.18 and towards 3.0
> >
> > \[...\]
> > 7.  JSON validator. XML XSD validation is nice and straight forward, but it
> > will be great if we have something similar for JSON as well. like
> > to:json-validator:classpath/response.json
> > \[...\]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message