[
https://issues.apache.org/jira/browse/CXF-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615035#comment-13615035
]
Christophe S commented on CXF-4924:
-----------------------------------
Hi Sergey,
Thank you for your fast reply.
I am using the approach 'WADL first' and generate Java files with wadl2java.
I have a service with 3 beans starting at the address "/v1" (all beans have to
start at this address). These 3 beans are defined in 3 WADL files: s1.xml,
s2.xml, x3.xml. For now I am concatenating them in one file: allServices.xml so
that the documentation of all the services are shown. I would like the
documentation to be available directly without concatenating theses 3 files.
I would really prefer to have 3 WADL files, as if not I would get a generated
Java file with too many methods inside.
For now I have:
<jaxrs:server id="publicAllServices" address="/v1"
beanNames="s1Bean s2Bean s3Bean"
docLocation="classpath:/wadl/allServices.xml">
<...>
</jaxrs:server>
I would like:
<jaxrs:server id="publicAllServices" address="/v1"
beanNames="s1Bean s2Bean s3Bean"
docLocation="classpath:/wadl/s1.xml classpath:/wadl/s2.xml
classpath:/wadl/s3.xml">
<...>
</jaxrs:server>
Another solution would be to declare many "servers" at the same address but
they override each other then and just the last one stays.
Thanks!
> Many docLocation for a server address
> -------------------------------------
>
> Key: CXF-4924
> URL: https://issues.apache.org/jira/browse/CXF-4924
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-RS
> Reporter: Christophe S
> Priority: Minor
> Fix For: 2.4.1
>
>
> It would be nice to support many files for the docLocation as we can have
> many beans in a service.
> For example, I have 3 WADL services at the same address. WADL2JAVA produces 3
> beans/services. I would like put these 3 beans at the same address and use
> the 3 WADL service files to produce the documentation.
> For now I have to have fake addresses to do this use case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
