June 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6328) [tester] Provide proper response messages and response body

by Brian Fitzpatrick (JIRA)

[tester] Provide proper response messages and response body ----------------------------------------------------------- Key: JBIDE-6328 URL: https://jira.jboss.org/browse/JBIDE-6328 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.next Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.next 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" -- 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

15 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6323) [tester] Look into UDDI/WSDL introspection to simplify parameter and service invocation

by Brian Fitzpatrick (JIRA)

[tester] Look into UDDI/WSDL introspection to simplify parameter and service invocation --------------------------------------------------------------------------------------- Key: JBIDE-6323 URL: https://jira.jboss.org/browse/JBIDE-6323 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 Investigate the UDDI Browser/WSDL introspection ideas for helping the user a) find the endpoint & action URLs and b) available parameters -- 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

15 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6409) Externalize strings for org.jboss.tools.jsf.ui.editor.check package

by Denis Golovin (JIRA)

Externalize strings for org.jboss.tools.jsf.ui.editor.check package ------------------------------------------------------------------- Key: JBIDE-6409 URL: https://jira.jboss.org/browse/JBIDE-6409 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Affects Versions: 3.2.0.M1 Reporter: Denis Golovin Assignee: Yura Zhishko Fix For: 3.2.0.M1 Externalize all strings to be in org.jboss.tools.ui messages.properties file. -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-6275) [tester] REST POST/PUT requests are not sending request body

by Lukas Jungmann (JIRA)

[tester] REST POST/PUT requests are not sending request body ------------------------------------------------------------ Key: JBIDE-6275 URL: https://jira.jboss.org/jira/browse/JBIDE-6275 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.next Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Priority: Critical -open Web Service Tester View -test following service: Type: JAX-RS Method POST Service URL: http://www.webservicex.net/BibleWebservice.asmx/GetBibleWordsByChapterAnd... request body: BookTitle=John&chapter=3&Verse=2 request headers: Content-Type=application/x-www-form-urlencoded, Content-Length=32 -configure monitor -and invoke the service => no response comes back from the server and TCP/IP monitor shows only: POST /BibleWebservice.asmx/GetBibleWordsByChapterAndVerse HTTP/1.1 Content-Length: 32 Content-Type: application/x-www-form-urlencoded User-Agent: Java/1.6.0_18 Host: localhost:8077 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive which means that there's no content sent to the server suspicious code seems to be in JAXRSWSTestView.java: 616: if (!method.equalsIgnoreCase(GET)) 617: body = EMPTY_STRING; 618: 619: // if no actual text in the request body, set to null 620: if (body.trim().length() == 0) body = null; which sets request body to "null" for POST/PUT requests -- 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

15 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6280) [tester] full response (body and headers) should be shown for REST requests

by Lukas Jungmann (JIRA)

[tester] full response (body and headers) should be shown for REST requests ---------------------------------------------------------------------------- Key: JBIDE-6280 URL: https://jira.jboss.org/jira/browse/JBIDE-6280 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.next Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Response from the server for wrong/invalid REST request has usually set other than HTTP 2xx status code and contains some explanatory message. Currently status code is hidden/wrapped in IOException message printed to the response body tab in the tester and explanatory message is completely hidden from the user and this should be fixed. steps: do GET http://www.zvents.com/rest/event_update in a tester Actual: bug 1: exception dialog with message Exception: Server returned HTTP response code: 401 for URL: http://www.zvents.com/rest/event_update? appears bug 2: response body shows: "java.io.IOException: Server returned HTTP response code: 401 for URL: http://www.zvents.com/rest/event_update?" which is kind of wrong from tester behavior point of view bug 3: response headers tab is empty Expected: -no exception window appears -response body shows proper message returned from the server, in this particular case it is: <?xml version="1.0" encoding="UTF-8"?> <rsp status="failed"> <msg>Invalid API Key.</msg> </rsp> -response headers tab shows at least correct HTTP status code, in this case: "Status Code: 401 Unauthorized" -- 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

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6283) [tester] User input for request parameters/headers should be validated

by Lukas Jungmann (JIRA)

[tester] User input for request parameters/headers should be validated ---------------------------------------------------------------------- Key: JBIDE-6283 URL: https://jira.jboss.org/jira/browse/JBIDE-6283 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.next Reporter: Lukas Jungmann currently user can enter arbitrary string as a request parameter/header, including invalid ones, such as ie 'a' - we should not allow that and tell user that he should enter param/header in '[name]=[value]' format instead -- 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

15 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6282) [tester] Cannot see more than 7 request parameters/headers

by Lukas Jungmann (JIRA)

[tester] Cannot see more than 7 request parameters/headers ---------------------------------------------------------- Key: JBIDE-6282 URL: https://jira.jboss.org/jira/browse/JBIDE-6282 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Lukas Jungmann Attachments: screenshot.png -add more than 7 arbitrary request parameters/headers in a tester => see attached screenshot, there's no way to get 8th param visible, some vertical scrollbar would fix this -- 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

15 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4827) Create automated UI functional tests for Hibernate Tools

by Jiri Peterka (JIRA)

Create automated UI functional tests for Hibernate Tools -------------------------------------------------------- Key: JBIDE-4827 URL: https://jira.jboss.org/jira/browse/JBIDE-4827 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Affects Versions: 3.1.0.CR1 Reporter: Jiri Peterka Fix For: 3.0.0.cr1 Create automated UI functional tests for Hibernate Tools. Test cases will be follow manual test cases. -- 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

15 years, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6141) Hibernate tools creates redundant console

by Jiri Peterka (JIRA)

Hibernate tools creates redundant console ------------------------------------------ Key: JBIDE-6141 URL: https://jira.jboss.org/jira/browse/JBIDE-6141 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.GA Environment: JBDS 3.0.0 GA #50, Linux 32, JDK 1.5 Reporter: Jiri Peterka Fix For: 3.1.1 Simple steps: 1. Create Java Project 2. Create Hibernate Console configuration (hibtest for example) 3. Create configuration file 4. Click finished After that also some redundant console hibernate (1) / hibernate (2) is created -- 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

15 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6467) pages.xml editor marks existing pages as non-existing.

by Alexey Kazakov (JIRA)

pages.xml editor marks existing pages as non-existing. ------------------------------------------------------ Key: JBIDE-6467 URL: https://jira.jboss.org/browse/JBIDE-6467 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.M2 1. Create new seam web project. 2. Open pages.xml. 3. Open Graphical tab. 4. /error.xhtml and /home.xhtml are shown as non-existing (they are gray). But it's not correct. -- 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

15 years, 10 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2010