Hi Sergey,
Thanks for the feedback.
I need JSON schema for client GUI which can render service interface based on
this json schema, the json schema is very convenient for interface view.
That's why I introduce the jackson dependency which can get json schema for a
given class neatly.
Cheers
－－－
I made a few changes to the javadoc stuff. If LDAP ever comes back, I’ll get
it committed.
Basically, for the distribution, I’ll leave the javadoc at just the “core”
javadoc. However, it also generates a jar of the full javadoc for everything.
This is what will be deployed to the website.
On Apr 3, 2014, at 4:30 PM, Andrew Janke wrote:
> Hi, CXF folks,
>
> I saw in the dev mailing list that you recently switched from svn to git, but
> it looks like this isn't fully reflected on the project web page. The "Source
> Repository" page (http://cxf.apache.org/source-repository.html)
Hi, CXF folks,
I saw in the dev mailing list that you recently switched from svn to
git, but it looks like this isn't fully reflected on the project web
page. The "Source Repository" page
(http://cxf.apache.org/source-repository.html) refers to git, but the
"Getting Involved" page (http://cxf
Hi Freeman
Why do you need JSON schema for it ?
I don't think it is realistic to expect XMLSchema document can be mapped
1 to 1 to a corresponding JSON schema.
Cheers, Sergey
On 03/04/14 02:57, Freeman Fang wrote:
Hi Dan,
Is there any neat way we can get Json schema from XmlSchema?
Thanks
Hi,
For me javadocs will be reasonable for APIs staying stable between major
releases.
Users can rely to use this in custom code.
Such classes are mostly located in cxf-api, my +1 to restrict distribution to
cxf-api javadoc (despite of fact that there are also some useful javadocs in
cxf-core)
