On 22/10/2013 17:05, Sergey Beryozkin wrote:
Hi Francesco
On 22/10/13 14:58, Francesco Chicchiriccò wrote:
On 21/10/2013 11:31, Sergey Beryozkin wrote:
Hi Francesco,
On 21/10/13 07:58, Francesco Chicchiriccò wrote:
On 18/10/2013 19:06, Sergey Beryozkin wrote:
Hi All,
I wonder if we can try
Hi,
On 23/10/13 12:40, Francesco Chicchiriccò wrote:
On 22/10/2013 17:05, Sergey Beryozkin wrote:
Hi Francesco
On 22/10/13 14:58, Francesco Chicchiriccò wrote:
On 21/10/2013 11:31, Sergey Beryozkin wrote:
Hi Francesco,
On 21/10/13 07:58, Francesco Chicchiriccò wrote:
On 18/10/2013 19:06,
On 21/10/2013 11:31, Sergey Beryozkin wrote:
Hi Francesco,
On 21/10/13 07:58, Francesco Chicchiriccò wrote:
On 18/10/2013 19:06, Sergey Beryozkin wrote:
Hi All,
I wonder if we can try and add a property to WadlGenerator, such as
checkJavaDocs or may be javaDocsClassPath which will point to a
Hi Francesco
On 22/10/13 14:58, Francesco Chicchiriccò wrote:
On 21/10/2013 11:31, Sergey Beryozkin wrote:
Hi Francesco,
On 21/10/13 07:58, Francesco Chicchiriccò wrote:
On 18/10/2013 19:06, Sergey Beryozkin wrote:
Hi All,
I wonder if we can try and add a property to WadlGenerator, such as
On 18/10/2013 19:06, Sergey Beryozkin wrote:
Hi All,
I wonder if we can try and add a property to WadlGenerator, such as
checkJavaDocs or may be javaDocsClassPath which will point to a
generated java docs jar, then suppose it processes a root class like
mypackage.Root, then it will look for
On 18/10/2013 17:08, Winnebeck, Jason wrote:
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, October 18, 2013 10:21 AM
I could not get any XML type information about method parameters; WADL
fragment was something like
param name=executionId
Hi Francesco,
On 21/10/13 07:58, Francesco Chicchiriccò wrote:
On 18/10/2013 19:06, Sergey Beryozkin wrote:
Hi All,
I wonder if we can try and add a property to WadlGenerator, such as
checkJavaDocs or may be javaDocsClassPath which will point to a
generated java docs jar, then suppose it
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Monday, October 21, 2013 3:08 AM
Oh yes, I've tried Swagger (via their JAX-RS / CXF sample [1]) and I
really like its output; however, the final WAR from such very basic
sample is about 40 MB, mainly
On 15/10/2013 17:32, Daniel Kulp wrote:
Interesting…. We haven't really looked at anything javadoc related as that
information isn't available at runtime. It's only available at build time and
thus we'd need special tools and such to parse the javadoc at build time,
output a file or
On 18/10/2013 10:59, Francesco Chicchiriccò wrote:
On 15/10/2013 17:32, Daniel Kulp wrote:
Interesting…. We haven't really looked at anything javadoc related as
that information isn't available at runtime. It's only available at
build time and thus we'd need special tools and such to parse
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, October 18, 2013 5:00 AM
I've been trying Enunciate in these days, for documentation only [3],
via its maven plugin.
While generating doc elements from Javadocs was working fine (I guess
On 18/10/2013 16:04, Winnebeck, Jason wrote:
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, October 18, 2013 5:00 AM
I've been trying Enunciate in these days, for documentation only [3],
via its maven plugin.
While generating doc elements from
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, October 18, 2013 10:21 AM
I could not get any XML type information about method parameters; WADL
fragment was something like
param name=executionId style=template/
while I would have
Hi
On 18/10/13 15:04, Winnebeck, Jason wrote:
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, October 18, 2013 5:00 AM
I've been trying Enunciate in these days, for documentation only [3],
via its maven plugin.
While generating doc elements
Hi All,
I wonder if we can try and add a property to WadlGenerator, such as
checkJavaDocs or may be javaDocsClassPath which will point to a
generated java docs jar, then suppose it processes a root class like
mypackage.Root, then it will look for
/mypackage/Root.html Java Doc resource, load
Hi all,
by reading [1], I am currently annotating JAX-RS methods (for
WADL-generation) like this
/**
* Deletes the user matching the provided userId.
*
* @param userId id of user to be deleted
* @return Deleted user
*/
@DELETE
@Path({userId})
-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Tuesday, October 15, 2013 8:54 AM
To: users@cxf.apache.org
Subject: WADL documentation via Javadoc?
Hi all,
by reading [1], I am currently annotating JAX-RS methods (for
WADL-generation) like this
/**
* Deletes the user
: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Tuesday, October 15, 2013 8:54 AM
To: users@cxf.apache.org
Subject: WADL documentation via Javadoc?
Hi all,
by reading [1], I am currently annotating JAX-RS methods (for
WADL-generation) like this
/**
* Deletes the user
[mailto:ilgro...@apache.org]
Sent: Tuesday, October 15, 2013 8:54 AM
To: users@cxf.apache.org
Subject: WADL documentation via Javadoc?
Hi all,
by reading [1], I am currently annotating JAX-RS methods (for
WADL-generation) like this
/**
* Deletes the user matching the provided userId
Interesting…. We haven't really looked at anything javadoc related as that
information isn't available at runtime. It's only available at build time and
thus we'd need special tools and such to parse the javadoc at build time,
output a file or something that can be picked up later.
Jersey
20 matches
Mail list logo
