July 2010 - jbosstools-issues - Jboss List Archives

[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-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: (JBDS-1234) Installer could check OS architecture

by Jiri Peterka (JIRA)

Installer could check OS architecture ------------------------------------- Key: JBDS-1234 URL: https://jira.jboss.org/browse/JBDS-1234 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 3.0.1.GA Reporter: Jiri Peterka Fix For: 3.0.x Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- 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

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6528) test failures running with Tycho

by Nick Boldt (JIRA)

test failures running with Tycho -------------------------------- Key: JBIDE-6528 URL: https://jira.jboss.org/browse/JBIDE-6528 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt 152 test failures reported in latest Tycho build: From: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/... -- 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
16
0 / 0

[JBoss JIRA] Created: (JBDS-1244) Remote server deployment

by Max Rydahl Andersen (JIRA)

Remote server deployment ------------------------ Key: JBDS-1244 URL: https://jira.jboss.org/browse/JBDS-1244 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: servers Reporter: Max Rydahl Andersen Priority: Critical Fix For: 4.0.x -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-6226) Create new GateIn Portal Server

by Feitais (JIRA)

Create new GateIn Portal Server ------------------------------- Key: JBIDE-6226 URL: https://jira.jboss.org/jira/browse/JBIDE-6226 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.0.GA Environment: Windows 7, JBoss Tools 3.1, GateIn-3.0.0-GA Reporter: Feitais Fix For: 3.1.x When I try to create a new server in server view, I don't have the option to create the GateIn Portal. Then I create a JBoss 5.1 application server. But I have to change the VM arguments to prevente startup errors. I put the same arguments from run.bat -- 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

4
6
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 July 2010