[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-6253: ------------------------------------- Attachment: web_service_tester_jaxws_050410.jpg I have put together a simple web service tester that handles JAX-WS and JAX-RS. This screen shot shows the results of invoking an external Shakespeare web service. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6253: ------------------------------------------ I have tested my web service tester with a JBossWS web service deployed on a SOA-P 5.0 runtime instance as well as a RESTeasy web service instance and it works fine in both cases. It's a little clunky to figure out what the Action URL is for a service we deploy, but I think we can work on that a bit. (Also note that the "Set Sample Data" button will not be in the final version - it's just to set some example data so you can invoke external JAX-WS and JAX-RS services.) I'm looking for feedback. This obviously doesn't have all the features of something like soapUI - but it does provide a rudimentary test facility for web services. What are the "MUST HAVE" features that this Eclipse view should have? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6253: ------------------------------------------ Lukas, awesome feedback - exactly the kind of thing I was looking for. To answer your first set of points... 1) Right now, a user would have to remove the existing header and add a new one (type name=value in the entry text box and click Add to get it in the list). But we could certainly add a method to edit an existing one rather than going through that trouble. 2) Copy and paste (Ctrl+C/Ctrl+V) are supported in all text fields. 3) Beautifying xml would be a nice thing to have. 4) Remembering the last few Service URLs would be a nice thing to have as well. For your must-have's... 5) What do you mean "Response Headers"? Basically set it up similar to the top half where you see a Response Body and Response Headers tab? Not quite sure how to get the headers back from the URL connection yet, but will certainly look into that. 6) Definitely can add PUT & DELETE support for JAX-RS. 7) And BASIC auth support can be added as well. Nice-to-haves... 8) Great idea to add the ability to save it off as a file (request & response text). 9) And definitely - I've been toying with the idea of a UDDI viewer/browse dialog for a while now, but I assume here you're talking more about loading a local WSDL and being able to interpret operations? 10) Yes, it should go away. Was just a convenience as I was figuring this stuff out. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6253: ------------------------------------------ You bet. I just call 'em as I see 'em. :) 1) I'm not a big fan of the editable table approach either. But I can easily add an "Edit" button. :) 3) Duh. Don't know why I didn't look closer at that dang class! Thanks. I'll get that in there. 9) I'm not sure we can do that either. It would be better IMHO to query a running runtime instance for a list of published services so the user could pick and choose accordingly. But we'll see what I can get working. Let's just keep the ideas in this one JIRA for now - I'll spin out different JIRAs once we have a PRD/ERD for the next JBDS release (sometime in the next few weeks). Plus, this particular bit of code doesn't exist anywhere but on my hard drive yet - so I have to get it into the build. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6253: ------------------------------------------ Basic auth is the next thing to be added, so I will start spinning things off into their own JIRAs tomorrow. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] 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) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-6253: ------------------------------------- Attachment: ws_tester_jaxrs_050710.jpg Updated JAX-RS example. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6253?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6253: ------------------------------------------ Found a way to handle #2 and #5 and split up the testing APIs for easier testing. Note that the dialog is not cancelable at this point, as I haven't found a good way to interrupt a long-running HTTP request, but it's a step in the right direction anyway. Committed changes -- 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

[ https://jira.jboss.org/browse/JBIDE-6253?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-6253: ------------------------------------- Spinning off remaining issues into separate JIRAs... JBIDE-6322: [tester] Look into using JAX-WS APIs directly instead of Axis JBIDE-6323: [tester] Look into UDDI/WSDL introspection to simplify parameter and service invocation JBIDE-6324: [tester] Look into ways to simplify SOAP sample generation JBIDE-6325: [tester] Look into caching basic authentication JBIDE-6326: [tester] Provide method for opening invoke results in an editor JBIDE-6327: [tester] Provide alternate, simpler method for creating SOAP request message JBIDE-6328: [tester] Provide proper response messages and response body Resolving this JIRA and will instead deal with the new JIRAs and any others that come up -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6253?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen resolved JBIDE-6253. ---------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira