October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6768) Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2.

by Alexey Kazakov (JIRA)

Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2. ----------------------------------------------------------------------------- Key: JBIDE-6768 URL: https://jira.jboss.org/browse/JBIDE-6768 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x Now we use V1. V2 has some improvements. For instance we can use Validation->Settings page for include/exclude rules. This framework is being developed yet but seems to be stable enough. -- 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

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6619) VPE Resizer is not shown on XULRunner 1.9.2

by Yahor Radtsevich (JIRA)

VPE Resizer is not shown on XULRunner 1.9.2 ------------------------------------------- Key: JBIDE-6619 URL: https://jira.jboss.org/browse/JBIDE-6619 Project: Tools (JBoss Tools) Issue Type: Bug Components: aop Affects Versions: 3.2.0.M2 Environment: XULRunner 1.9.2 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.M2 Compare screenshots on both versions of XULRunner: 1.9.1 and 1.9.2 (screenshots.png). -- 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

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6942) Prompt for Basic Auth when accessing secured WSDL

by Juergen Zimmermann (JIRA)

Prompt for Basic Auth when accessing secured WSDL ------------------------------------------------- Key: JBIDE-6942 URL: https://jira.jboss.org/browse/JBIDE-6942 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Juergen Zimmermann Assignee: Brian Fitzpatrick A SOAP based Web Service can be defined as follows: @WebService(name = "MyService") @WebContext(contextRoot = "/myRoot", authMethod = "BASIC", secureWSDLAccess = true) @EndpointConfig(configName = "Standard WSSecurity Endpoint") Now the WSDL cannot be accessed without BASIC authentication. Therefore, it would be fine, if you could provide a checkbox within the dialog "Select WSDL", so that username and password could be prompted. Just as the checkbox below "Request details" in the main window. -- 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

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5535) New Web Service

by Burr Sutter (JIRA)

New Web Service --------------- Key: JBIDE-5535 URL: https://jira.jboss.org/jira/browse/JBIDE-5535 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Attachments: New_WebService_Wizard.jpg, New_Wizard.jpg There should be a New Web Service Project wizard (the same as New Dynamic Web Project) and a New Web Service component wizard. The New Web Service Project wizard creates the exact same thing as New Dynamic Web Project but with HelloWorldWS.java containing the following: package com.jboss.lab; import javax.jws.WebMethod; import javax.jws.WebService; @WebService public class MyWebService { @WebMethod public String sayHello(String name) { return "Hello2 " + name + "!"; } } And the appropriate entries in the web.xml. <servlet> <servlet-name>MyWebServiceServlet</servlet-name> <servlet-class>com.jboss.lab.MyWebService</servlet-class> </servlet> <servlet-mapping> <servlet-name>MyWebServiceServlet</servlet-name> <url-pattern>/MyWebService</url-pattern> </servlet-mapping> See screenshots for current functionality. This suggestion is based on how Visual Studio handles this scenario. For a New Web Service or New Web Service project, it drops in the annotated mywebservice.asmx automatically. You can deploy the project/component immediately without further editing. -- 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

14 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6396) Filter wizard/Database Collector should correctly identify catalog, schema, and tables even when tables contain dots (".") in the name

by Michael Walker (JIRA)

Filter wizard/Database Collector should correctly identify catalog, schema, and tables even when tables contain dots (".") in the name -------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6396 URL: https://jira.jboss.org/browse/JBIDE-6396 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Michael Walker Attachments: JBIDE-tablename-with-dots-patch-mpw.txt The DefaultDatabaseCollector uses StringHelper.qualifier(String) to determine the catalog and schema name for each table, given the fully-qualified name. StringHelper.qualifier() assumes that everything proceeding the final "." in the fully-qualified name represents the qualifier. This assumption breaks down if a table contains a dot in the name. This is found to be the case when working with MetaMatrix (and possibly Teiid). The result is that the Filter Wizard will generate invalid filters, based on the incorrect naming of catalog and schema for each table. As a fix, I modified DefaultDatabaseCollector to form the qualifier by using the known catalog and schema, rather than by using the StringHelper.qualifier method. I rebuilt tools and verified that this fixed the problem when working with MetaMatrix. This may be better addressed by changing the behavior of StringHelper.qualifier() itself. See forum discussion for details. Patch attached. -- 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

14 years, 10 months

7
28
0 / 0

[JBoss JIRA] Created: (JBDS-411) Need 64-bit windows support

by Samuel Mendenhall (JIRA)

Need 64-bit windows support --------------------------- Key: JBDS-411 URL: https://jira.jboss.org/jira/browse/JBDS-411 Project: Developer Studio Issue Type: Feature Request Affects Versions: 1.1.0.GA Reporter: Samuel Mendenhall Assignee: Max Rydahl Andersen JBDS is not usable on a 64-bit Windows machine. -- 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

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1608) Hibernate Configuration view should display all database

by Vitali Yemialyanchyk (JIRA)

Hibernate Configuration view should display all database --------------------------------------------------------- Key: JBIDE-1608 URL: http://jira.jboss.com/jira/browse/JBIDE-1608 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Vitali Yemialyanchyk Assigned To: Vitali Yemialyanchyk Priority: Minor Fix For: LATER Look at the attached file hibernate.cfg.xml - if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql</property> Hibernate Configuration view -> ... -> Database display correctly mysql database - but if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306</property> look like this Hibernate Configuration view -> ... -> Database display nothing and the user can't understand what is wrong - I provide 2 screenshots the same if <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/mysql1</property> mysql1 - there is no such DB as I think in first case Hibernate Configuration should display all mysql DBs and in the second case the user should get message - something like "Can't find shuch DB" Other thing - then I press right mouse button on Hibernate Configuration view -> ... -> Database - I expect to get possibility to configure DB URL and may be some other properties - the best thing here if I'll get some dialog - or at least possibility to open hibernate.cfg.xml for edit. For this I'll create other new issue... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6731) cannot create bottom-up ws with ws-cxf

by Martin Malina (JIRA)

cannot create bottom-up ws with ws-cxf -------------------------------------- Key: JBIDE-6731 URL: https://jira.jboss.org/browse/JBIDE-6731 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.1.0.GA Environment: jbdevstudio-macosx-cocoa-3.0.1.v201006010437R-H98-GA.jar jboss-eap-5.0.1.CR1.zip with jbossws-cxf-3.1.2.SP6-installer.zip installed Mac OS X Snow Leopard Reporter: Martin Malina Assignee: Brian Fitzpatrick I get an error when trying to created a web service: Failed to Generate Web Service code, please check the log for more details. The details show: Failed to Generate Web Service code, please check the log for more details ... java2ws - Apache CXF 2.2.6 /Users/rasp/jbossqa/workspace-eap/TestWSProject/src/test/ws/jaxws/Echo.java:23: cannot find symbol symbol : class Person location: package test private test.Person arg0; ^ /Users/rasp/jbossqa/workspace-eap/TestWSProject/src/test/ws/jaxws/Echo.java:25: cannot find symbol symbol : class Person location: package test public test.Person getArg0() { ^ ... This only happens when the selected runtime has ws-cxf installed. See the steps to reproduce. -- 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

14 years, 10 months

5
29
0 / 0

[JBoss JIRA] Created: (JBIDE-7050) Cannot change Server runtime when creating web service

by Libor Zoubek (JIRA)

Cannot change Server runtime when creating web service ------------------------------------------------------ Key: JBIDE-7050 URL: https://jira.jboss.org/browse/JBIDE-7050 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Libor Zoubek Assignee: Brian Fitzpatrick When creating bottom-up web service, I am not able to change server runtime. Add more than 1 server runtimes (I used EAP 5 and EAP 5.1) 1. run 'Web Service' wizard 2.Click 'Server Runtime' link 3. Select a runtime other than it was selected before 4. Click OK 5. Back in wizard page no changes are populated Note that this does not seem to be WTP bug, I've tested it on helios-jee (used runtimes JBoss AS 4.2 and 5.0) without any problems. -- 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

14 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBDS-1378) Update struts tutorial to use standard JSP wizard

by Lukas Jungmann (JIRA)

Update struts tutorial to use standard JSP wizard ------------------------------------------------- Key: JBDS-1378 URL: https://jira.jboss.org/browse/JBDS-1378 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Doc - StrutsTools Affects Versions: 4.0.0.Beta2 Reporter: Lukas Jungmann JBT custom wizards for Struts has been replaced by standard Eclipse ones (see JIRA-6256) therefore docs should be updated to reflect this change. I've found out that the only part which should be updated is sec. 2.2.1.1 - there's now no way to select Struts specific Template (StrutsForm/blank) [1]: http://download.jboss.org/jbosstools/nightly-docs/en/struts_tools_tutoria... -- 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

14 years, 10 months

2
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 October 2010