You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Anthony Schexnaildre (JIRA)" <ji...@apache.org> on 2008/07/09 16:39:33 UTC
[jira] Created: (CXF-1695) Service listings for JAX-RS endpoints
Service listings for JAX-RS endpoints
-------------------------------------
Key: CXF-1695
URL: https://issues.apache.org/jira/browse/CXF-1695
Project: CXF
Issue Type: Improvement
Components: REST
Reporter: Anthony Schexnaildre
Priority: Minor
The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin resolved CXF-1695.
-----------------------------------
Resolution: Fixed
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
> Assignee: Sergey Beryozkin
> Fix For: 2.2.3, 2.3
>
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "cybexion (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701971#action_12701971 ]
cybexion commented on CXF-1695:
-------------------------------
yes, I fully agree.
What about using a servlet init param like
<init-param>
<param-name>service-classifier-url-extension</param-name>
<param-value>_services</param-value>
</init-param>
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696991#action_12696991 ]
Sergey Beryozkin commented on CXF-1695:
---------------------------------------
It was really lame. I did reproduce NPE and thought I fixed it when adding a previous comment - but I think in that case it was just a single endpoint that was used, so another lurking NPE in compare() was ignored - fingers crossed, it's fixed now - will merge shortly. Also added a simple check to ensure no NPE occurs.
thanks for you patience :-)
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701897#action_12701897 ]
Sergey Beryozkin commented on CXF-1695:
---------------------------------------
it's unfortunate... Perhaps switching the services listings did work for JAXWS services... Apart from fixing this actual 'switching off' bug, what we also need to do is to introduce some sort of 'classifier', with 'services' being the default value, but for users be able to provide custom values like '/listings' ...
For JAXRS-only services, we will support system queries like _services or _documentation, etc, but for JAXWS/JAXRS services having a custom classifier should help...
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Charlie Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648300#action_12648300 ]
Charlie Collins commented on CXF-1695:
--------------------------------------
Just to clarify, the /services path does not work AT ALL, and causes an NPE (see above comment), if you have JAX-RS services enabled. It's not just that it doesn't list JAX-RS services, it doesn't work period if there are any JAX-RS services configured.
While it would be convenient to list both types, WS and RS, it might also be good just to fix this so that WS services are still listed (even if RS aren't) - when a project has RS services enabled (just ignore the RS ones for now).
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
> Priority: Minor
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Andreas Sahlbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696074#action_12696074 ]
Andreas Sahlbach commented on CXF-1695:
---------------------------------------
Any news for this bug?
CXF 2.2 ist out, but it still crashes hard with an NPE if the services URL ist called. Gives me a pretty hard stand to justify the usage of CXF in a productive environment here.
Is it really this hard just to ignore REST services when creating the content for the services URL?
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Gilberto Ribeiro Olimpio (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631068#action_12631068 ]
Gilberto Ribeiro Olimpio commented on CXF-1695:
-----------------------------------------------
Same here. I'm using CXF 2.1.2
It will be nice if at least CXF didn't show an exception when I try to access "/services".
java.lang.NullPointerException
at org.apache.cxf.service.model.EndpointInfo.getInterface(EndpointInfo.java:54)
at org.apache.cxf.transport.servlet.ServletController$1.compare(ServletController.java:218)
at org.apache.cxf.transport.servlet.ServletController$1.compare(ServletController.java:217)
...
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
> Priority: Minor
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Andreas Sahlbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674245#action_12674245 ]
Andreas Sahlbach commented on CXF-1695:
---------------------------------------
Please take into account that I am relatively new to REST, so I may talk rubbish. :-)
It would be nice if the content you are showing is depending to the accept header of the request. If it's "text/html" go for 3. If it's "application/xml" or something go for 2.
But that's not the point of my initial comment. It's not acceptable that a product crashes hard with an NPE just by using it correctly. This is simply a bug and should be fixed. As already suggested: Just ignore the REST services for the first fix, but don't crash.
Implementing the features you've mentioned would be very nice but that's clearly an improvement and can be done later. This issue should be split up into a bug and an improvement issue. This would be totally ok for me.
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674234#action_12674234 ]
Daniel Kulp commented on CXF-1695:
----------------------------------
Until JAX-RS supports something like WADL, it would be fine by me to just NOT show any of the jaxrs services. Just show the jaxws stuff.
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated CXF-1695:
----------------------------------
Priority: Major (was: Minor)
Sure - I've updated the level.
The questions is what should be the default 'view', once the link pointing to a given JAXRS endpoint is selected
- 1.JavaDocs ?
- 2.WADL ?
- 3.Human readable description in the form of tables showing what methods are suppoted, content-type/accept values, etc
We expect some WADL support coming in but most likely for 2.2.1 or so.
Option 1 is probably the simplest one, while option 3 can be done on top of 2.
All options can be implemented as blocking CXF JAXRS RequestFilter implementations handling query like _javadocs, _wadl, _info
Unfortunately it's unlikely I will be able to allocate the time till 2.2 gets released on this issue.
Thus a patch will be welcomed if it's critical
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin reassigned CXF-1695:
-------------------------------------
Assignee: Sergey Beryozkin
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
> Assignee: Sergey Beryozkin
> Fix For: 2.2.3, 2.3
>
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678285#action_12678285 ]
Sergey Beryozkin commented on CXF-1695:
---------------------------------------
Andreas - NPE will go away in 2.2/2.1.5. We'll look seriously into enabling jaxrs services listings after 2.2 gets released
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "cybexion (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701530#action_12701530 ]
cybexion commented on CXF-1695:
-------------------------------
We have an issues which is related to this bug.
Our REST URL looks like this:
localhost:8280/website/getWebsiteByUrlZone/url/zone/
The method getWebsiteByUrlZone
gets two String parameters: url and zone
Now we have the situation in productions, that some users use a zone named 'services'
Now our Interface does not work any more.
Also switching the list functionality off in web.xml using "hide-service-list-page" does not work at inside the Code this is totally hardcoded:
ServletController.java:
if (request.getRequestURI().endsWith("/services")
|| request.getRequestURI().endsWith("/services/")
This statement:
if (!isHideServiceList) {
should be put directly inside the invoke method, before the url is checked
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731997#action_12731997 ]
Sergey Beryozkin commented on CXF-1695:
---------------------------------------
This is now done, HTML view for WADL instances will be done later.
'service-list-path' servlet parameter can be used to overwrite the default 'services' .
"hide-service-list-page" has the expected effect too
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
> Assignee: Sergey Beryozkin
> Fix For: 2.2.3, 2.3
>
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Andreas Sahlbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674217#action_12674217 ]
Andreas Sahlbach commented on CXF-1695:
---------------------------------------
Why is this an "Improvement"??? This is clearly a bug, because that's a feature that does not work at all if you have just one REST service implemented. It does not work but fails with an NPE visible to the End-User.
IMHO this should be a "major bug" the way it currently fails.
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
> Priority: Minor
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1695) Service listings for JAX-RS endpoints
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated CXF-1695:
----------------------------------
Fix Version/s: 2.3
2.2.3
> Service listings for JAX-RS endpoints
> -------------------------------------
>
> Key: CXF-1695
> URL: https://issues.apache.org/jira/browse/CXF-1695
> Project: CXF
> Issue Type: Improvement
> Components: REST
> Reporter: Anthony Schexnaildre
> Assignee: Sergey Beryozkin
> Fix For: 2.2.3, 2.3
>
>
> The /services path does not work for listing JAX-RS services. Ultimately listing these endpoints along with the SOAP endpoints, et el, would be ideal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.