cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Resolved] (CXF-4924) Many docLocation for a server address
Date Thu, 04 Apr 2013 10:07:15 GMT


Sergey Beryozkin resolved CXF-4924.

       Resolution: Fixed
    Fix Version/s:     (was: 2.7.3)
                       (was: 2.4.1)
         Assignee: Sergey Beryozkin

Sure, I've updated the generator to support the retrieval of the referenced resource types,
it is not perfect but I think is consistent with the way WSDL resources with other referenced
WSDL resources are presented - the tool consuming it will just fetch the next resource, the
user has to copy and paste the absolute link URI into a browser :-). I think once we have
an actual HTML-enabled browsing of WADL resources then it will become user friendlier.

Note, one restriction on 2.7.x/2.6.x/2.5.x (but not on the trunk) is that the referenced WADL
resources need to have '.wadl' extension - this is just to do with the way the WADL filtering
is done there, ".xml", ".wadl", etc will work on the trunk 
> Many docLocation for a server address
> -------------------------------------
>                 Key: CXF-4924
>                 URL:
>             Project: CXF
>          Issue Type: Sub-task
>          Components: JAX-RS
>            Reporter: Christophe S
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 2.8.0, 2.5.11, 2.6.8, 2.7.5
> 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:

View raw message