[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6253) Need a web service tester (JAX-WS and JAX-RS) in the tooling

[Lukas Jungmann (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12529344#action_12529344 ] 

Lukas Jungmann commented on JBIDE-6253:
---------------------------------------

I was eager to try this out, so I made own build (svn rev. 21932) and generally it looks really great and most of these comments are only nit-picks, some can be treated as bugs ans some as nice-to-have but anyway:

-I'd vote to move this to editor-type window mainly because typically what I/user would like to see is more than first 5-6 lines or words on a line of the request/response
-make tabbed panes (don't know how the tab(s) container is called in SWT) vertically re-sizable (this could maybe solve the previous comment)
-allow user to hit Enter after typing in service url combo to invoke the service
-change cursor to busy one (or provide another visual feedback - progress bar? - to the user) during the service call so he as aware that something is happening (due to the fact that some calls can last longer)
-UI should show all request headers sent to the server, ie. currently I don't know if ie. request's content-length header was set properly for SOAP POST request
-show the length of the request body somewhere in the UI so user can easily set mandatory Content-length header for the POST requests (or set this header for the user auto-magically)


JAX-WS - I was testing Bible web service: http://www.webservicex.net/WCF/ServiceDetails.aspx?SID=43
-HTTP method should be set to POST in UI by default for JAX-WS services, currently it's a bit confusing because UI can show that ie HTTP PUT was done but in fact POST was done
-setting HTTP request headers should be allowed ie. I want to set proper content-type (text/xml vs. application/soap+xml) and content-length headers
-perhaps if SOAP request body is empty then "invoke" button should be disabled (?)
-would be nice if there would be by default some kind of SOAP 1.1 (not sure about SOAP 1.2) request template so the user could type/paste in only the real body of the message

JAX-RS - testing Twitter APIs (http://apiwiki.twitter.com/Twitter-API-Documentation)
-should add '?' to the service URL if it's missing for GET request with parameter(s), in the other words do not require user to type it
-show correct response from the server - test case for this: GET http://api.twitter.com/1/statuses/home_timeline.xml and provide invalid user credentials - UI should show proper response headers (such as ie Status Code: 401 Unauthorized) and correct response body instead of showing "java.io.IOException: Server returned HTTP response code: 401 for URL: http://api.twitter.com/1/statuses/home_timeline.xml"

a note to Basic auth/ssl - mainly for QE/myself (Twitter's support for Basic auth will be removed during June 2010, also note that one can call its API through HTTPS):
it seems this works out of the box, the only problem I see is in caching user credentials during IDE session, this needs to be properly tested. Other scenario to test is the behaviour if server uses invalid (ie. expired SSL certificate)


> Need a web service tester (JAX-WS and JAX-RS) in the tooling
> ------------------------------------------------------------
>
>                 Key: JBIDE-6253
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6253
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Webservices
>    Affects Versions: 3.2.next
>            Reporter: Brian Fitzpatrick
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.2.next
>
>         Attachments: web_service_tester_jaxrs_050410.jpg, web_service_tester_jaxws_050410.jpg
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Though there are testing facilities for web services available in Eclipse, such as the Web Services Explorer (doesn't support JAX-RS) and soapUI (3rd party tool), there has been a call for some rudimentary testing facilities within our tooling as well. 
> This tooling should:
> * Test invoking a JAX-WS service with an incoming SOAP document and show the results
> * Test invoking a JAX-RS service (GET or POST) and show the results

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira