Open ryangies opened 6 years ago
Well, there's the @com.webcohesion.enunciate.metadata.rs.ServiceContextRoot
annotation, but you'd have to apply it to each resource, so that's a pain.
I'll track this as an enhancement request.
You can also use the @com.webcohesion.enunciate.metadata.rs.ResourceGroup
annotation and apply some custom grouping. But, again, it's applied per-resource.
Thank you. I will pursue the annotations in the meanwhile.
Is there a way that each
include
withinapi-classes
can specify itsrelativeContextPath
?Situation:
I have several services, each in their own Maven project and under the same
groupId
. These services as a whole comprise the application's interface. Because these interfaces call each other (using clients), Enunciate documents "too much" out of the box. I feel having each service exclude its siblings is cumbersome to maintain and violates the idea of isolation. Besides, I then have to wrap all the Enunciate docs in order to provide yet another main navigation to browse all of the interfaces.Attempting this solution:
Create a dedicated project (
pom.xml
) with its ownenunciate.xml
for the sole purpose of documentation. This works great, except I cannot really tell which service is providing the interface. Thus circling back to the question at the top.My ~
pom.xml
:My ~
enunciate.xml
: