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

[Brian Fitzpatrick (JIRA)]

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

Brian Fitzpatrick commented on JBIDE-6253:
------------------------------------------

Note that everything at this point has been checked in and is available in trunk. I don't think we have an updated build that includes my fixes from last night, but we will soon I'm sure. 

Latest round of fixes includes:
1. Horizontal alignment (side by side instead of top/bottom) with a slider between.
2. Insert empty SOAP envelope for JAX-WS services if the SOAP text field is empty.
3. Hitting Enter in the Service URL does an Invoke.
4. Other odds and ends...

Remaining issues:
1. Explore using JAX-WS APIs directly instead of the Apache Axis APIs for calling the JAX-WS service.
2. Find a way to get the HTTP headers from whichever API we use for calling JAX-WS services to display both the request headers and the response headers outside the TCP/IP Monitor view. 
3. Investigate the UDDI Browser/WSDL introspection ideas for helping the user a) find the endpoint & action URLs and b) available parameters
4. Find ways to help the user auto-generate sample SOAP for JAX-WS services to make it easier.
5. Hook the actual invoke call into the Eclipse Jobs API so we have a way to see that something is happening. Not sure how to do that since HTTP calls are typically synchronous, not asynchronous. 
6. Figure out how to stash the basic authentication somewhere so you just do it once if you're invoking multiple times. Anybody have suggestions?
7. Open the results data in an editor (based on content type - probably the XML editor) or look into using a Source Viewer on the tab and hooking in the XML highlighting/pretty print functionality. 
8. Provide a method for hiding the SOAP complexity and prompt the user for parameters, generating the SOAP behind the scenes. 
9. 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"


> 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, ws_tester_jaxrs_050710.jpg, ws_tester_jaxws_050710.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