enunciate

Can I use a Maven plugin (enunciate) in Gradle?

喜你入骨 提交于 2019-12-30 06:04:50
问题 I have a maven plugin called enunciate that generates nice API documentation. I'd rather use Gradle as my build tool but it looks like it's limited in this aspect or maybe I just don't know how to use it. I'm wondering if it's possible to use a maven plugin (enunciate) in gradle somehow? Do I have to write an ant script and call that? So far I can't find a gradle example for enunciate so I'm guessing it's not supported? 回答1: You can't use a Maven plugin as-is in Gradle; you'll have to port it

Can I use a Maven plugin (enunciate) in Gradle?

删除回忆录丶 提交于 2019-12-30 06:03:46
问题 I have a maven plugin called enunciate that generates nice API documentation. I'd rather use Gradle as my build tool but it looks like it's limited in this aspect or maybe I just don't know how to use it. I'm wondering if it's possible to use a maven plugin (enunciate) in gradle somehow? Do I have to write an ant script and call that? So far I can't find a gradle example for enunciate so I'm guessing it's not supported? 回答1: You can't use a Maven plugin as-is in Gradle; you'll have to port it

How do you document a REST API?

你。 提交于 2019-12-21 04:09:15
问题 How do you document a REST API? Not just the documentation of what the resources are, but really what is the data that gets sent in the request and what the data is that gets sent back in the response. It is not useful enough to know that something expects XML to be sent and returns XML; or JASN; or whatever. How do you document the data that gets sent in the request and the data sent back in the response? Best I could find so far is the Enunciate tool where you can document your REST API and

Enunciate Issue = Assembling the enunciate app. com.sun.tools.apt.mirror.type.ClassTypeImpl cannot be cast to com.sun.mirror.type.AnnotationType

不羁的心 提交于 2019-12-12 02:19:26
问题 I want my Enunciate report to contain Json Example for all the model classes, to test it I modified the enunciate configuraion to include json example and changed my model class from @XmlRootElement(name = "member-response") public class MemberResponse to @JsonRootType @JsonName("MemberResponse") @XmlRootElement public class MemberResponse And then built the maven project and ran mvn -o clean pre-site site:site site:stage -Prest-reports -PskipQuality -DskipTests=true -U Getting the below

Exception while accessing Jersey REST webservice

送分小仙女□ 提交于 2019-12-11 07:59:15
问题 I am trying to get REST webservices working in my app. I am using jersey with Spring 2.5. The endpoints for the webservices are generated with enunciate 1.9. When I deploy the generated war file with Tomcat and access the REST webservice I get the following exception: javax.servlet.ServletException: Servlet.init() for servlet jersey threw exception org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter

Can Enunciate generate docs for an API that handles generic types?

纵然是瞬间 提交于 2019-12-06 03:12:02
问题 Given an abstract, generic Resource class and a concrete implementation: public abstract class AbstractResource<T> { @Autowired private SomeService<T> service; @Path("/{id}") @GET public T get(@PathParam("id") String id) { return service.get(id); } } @Path("/people") public class PersonResource extends AbstractResource<Person> { } It appears that when generating the docs for PersonResource , Enunciate is not picking up the fact that get() returns a Person . Person is not listed in the Data

Can Enunciate generate docs for an API that handles generic types?

北城余情 提交于 2019-12-04 07:28:06
Given an abstract, generic Resource class and a concrete implementation: public abstract class AbstractResource<T> { @Autowired private SomeService<T> service; @Path("/{id}") @GET public T get(@PathParam("id") String id) { return service.get(id); } } @Path("/people") public class PersonResource extends AbstractResource<Person> { } It appears that when generating the docs for PersonResource , Enunciate is not picking up the fact that get() returns a Person . Person is not listed in the Data Model > Data Types section. Under the GET section, Response Body shows the element type as "(custom)".

How do you document a REST API?

試著忘記壹切 提交于 2019-12-04 03:40:43
How do you document a REST API? Not just the documentation of what the resources are, but really what is the data that gets sent in the request and what the data is that gets sent back in the response. It is not useful enough to know that something expects XML to be sent and returns XML; or JASN; or whatever. How do you document the data that gets sent in the request and the data sent back in the response? Best I could find so far is the Enunciate tool where you can document your REST API and the data elements. Is Enunciate the right type of tool for this and am I missing out on any other

How to document a Symfony based REST API (similar to enunciate's documentation capabilities)

纵饮孤独 提交于 2019-12-02 01:46:07
If I have a REST based service written in the Symfony [symfony-project.org] framework (i.e. PHP), is there any decent tools/frameworks out there that will parse my code and generate API documentation? The Java based framework enunciate has documentation capabilities similar to what I need, you can view an example of this here: http://enunciate.codehaus.org/wannabecool/step1/index.html . I understand the premise of REST based services are supposed to be self evident, however I was after something that would generate this documentation for me without the need to manually write up all my

How to document a Symfony based REST API (similar to enunciate's documentation capabilities)

旧巷老猫 提交于 2019-12-01 22:57:41
问题 If I have a REST based service written in the Symfony [symfony-project.org] framework (i.e. PHP), is there any decent tools/frameworks out there that will parse my code and generate API documentation? The Java based framework enunciate has documentation capabilities similar to what I need, you can view an example of this here: http://enunciate.codehaus.org/wannabecool/step1/index.html. I understand the premise of REST based services are supposed to be self evident, however I was after