November 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5159) Choice to choose whether to use the wizard to generate hbm.xml in Hibernate Tools

by Simon Lo (JIRA)

Choice to choose whether to use the wizard to generate hbm.xml in Hibernate Tools --------------------------------------------------------------------------------- Key: JBIDE-5159 URL: https://jira.jboss.org/jira/browse/JBIDE-5159 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M4 Environment: Windows 7 Home Premium, Eclipse 3.5 SR1 Reporter: Simon Lo I hate to generate everything by wizard and being unable to control the output of hbm.xml. It is because our company always have the mismatch problems in column name in database and properties in Java object. It made me so frustrated after using Eclipse Galileo which can only installed JBoss Tools 3.1.x and the behaviour of Hibernate Tools changed so much. I cannot find any option that I can stop the wizard generation and type in everything in hbm.xml by myself. I need to let the wizard to generate everything then delete it to start over. I love the Hibernate Tools before which only generate necessary XML declaration for me and let me do the rest. -- 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

16 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4676) Eclipse Utility Project not included in EAR /lib directory on rebuild

by Margot Media (JIRA)

Eclipse Utility Project not included in EAR /lib directory on rebuild --------------------------------------------------------------------- Key: JBIDE-4676 URL: https://jira.jboss.org/jira/browse/JBIDE-4676 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M2 Environment: Eclipse 3.5 w/ JBoss Tools 3.1.0 M2. Using the "JBoss v5.0" server instead of the "JBoss AS 5.1". Reporter: Margot Media I have an application with a single MDB .jar file and 3 Utility Module .jar files. The utility projects are set up to appear in the EAR under the /lib directory. The first time the EAR file is deployed to the server, the /lib directory is populated correctly. However, if I change my source code and republish to the server, the /lib directory is not present! If I remove the EAR file from the server, then re-add it, the /lib directory is created properly. The first time, it looks like this: Code: MyEar.ear |- /lib | |- Utility1.jar | |- Utility2.jar | |- Utility3.jar |- /META-INF | |- MANIFEST.MF |- MyMDB.jar If I change the code in MyMDB.jar, the EAR file is generated like: Code: MyEar.ear |- /META-INF | |- MANIFEST.MF |- MyMDB.jar with the obvious class path problems by not having the utility jar files present. Steps to reproduce: 1. Create new "Java EE Enterprise Application Project" called MyEar using default configuration. 2. Create new "Java EE Utility Project" called Utlity 1 using the default configuration and add it to MyEar 3. Create new "Java EJB Project" called MyMdb using the default configuration and add it to MyEar 4. Set the Utility1.jar file to appear in the lib directory of MyEar 5. Create a class in the Utility1 project w/ some code (eg a POJO with one member and setter/getter) 6. Create MDB in the MyMDB project using the "Message-Driven Bean (EJB 3.x)" wizard 7. Add code to the MDB to make it dependent upon the Utility1 project 8. Start JBoss and deploy MyEar to the server. Verify that the EAR file correctly included the Utility1.jar file in the /lib directory 9. Make a change to the code in MyMDB and republish MyEar. Verify that the EAR does not include the /lib directory at all -- 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

16 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2023) Population of Action Class / Process Method

by Tom Cunningham (JIRA)

Population of Action Class / Process Method ------------------------------------------- Key: JBIDE-2023 URL: http://jira.jboss.com/jira/browse/JBIDE-2023 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: Mac OS X, nightly 04/04 JBoss Tools build, Europa JEE eclipse build Reporter: Tom Cunningham It would be nice if the ESB editor could somehow populate an action class drop down or do autocompletion of the class name, while at the same time retaining the ability for the user to type in their action class name. Action classes in the drop down should probably be restricted to classes within project which extend AbstractActionLifecycle or AbstractActionPipelineProcessor and the org.jboss.soa.esb.actions package classes. -- 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

16 years, 3 months

7
33
0 / 0

[JBoss JIRA] Created: (JBIDE-3378) Seam EL validation does not use same technique as the EL resolver (Continued)

by Tim Evers (JIRA)

Seam EL validation does not use same technique as the EL resolver (Continued) ----------------------------------------------------------------------------- Key: JBIDE-3378 URL: https://jira.jboss.org/jira/browse/JBIDE-3378 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.beta1, 3.0.0.alpha, 2.1.2 Environment: Latest nightly build of JBoss Tools. On eclipse 3.4 SR1. JSF/Facelets/Richfaces/Seam 2.1.x environment Reporter: Tim Evers JBoss Tools does not validate method EL expressions properly if the method name starts with 'is' If I have a method in my SEAM bean like this. public boolean isEditButtonDisplayed() { return true; //removed what this method actually does for example } and then I have in my xhtml this: <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.isEditButtonDisplayed()}" /> When I validate this it says: "isEditButtonDisplayed" cannot be resolved. It looks like when the validation method sees the word 'is' it automatically thinks that the expression is a value expression. This should not be the case. Infact if I end my expression witih '()' it should always look for a method. The behaviour of the EL validation should be exactly the same as what happens when I run the system. But this is not what is happening. If I change my code to what the JBoss Tools autocomplete says to it actually breaks the application. According to JBoss Tools it says I should have this. <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.editButtonDisplayed}" /> Which of course will not work when the app is deployed. This is somewhat related to: https://jira.jboss.org/jira/browse/JBIDE-2673 just a different scenario. The fundamental problem is that the rules of validation are not the same as a running app. -- 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

16 years, 3 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4758) EL OpenOns should use new unified EL Resolvers mechanism from org.jboss.tools.common.el

by Alexey Kazakov (JIRA)

EL OpenOns should use new unified EL Resolvers mechanism from org.jboss.tools.common.el --------------------------------------------------------------------------------------- Key: JBIDE-4758 URL: https://jira.jboss.org/jira/browse/JBIDE-4758 Project: JBoss Tools Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.M3 -- 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

16 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4402) Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details.

by Nick Boldt (JIRA)

Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details. ------------------------------------------------------------------------------------------------- Key: JBIDE-4402 URL: https://jira.jboss.org/jira/browse/JBIDE-4402 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.1.0.M1 Reporter: Nick Boldt http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-2.... [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. Suggest reviewing your sources w/ PDE API Tools and compiling locally to see what these unsafe/unchecked operations are. -- 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

16 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5274) Copy/Move JBT project configuration dialogs to Project->Configure menu.

by Alexey Kazakov (JIRA)

Copy/Move JBT project configuration dialogs to Project->Configure menu. ----------------------------------------------------------------------- Key: JBIDE-5274 URL: https://jira.jboss.org/jira/browse/JBIDE-5274 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0.CR1 -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-729) generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions

by Nick Boldt (JIRA)

generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions -------------------------------------------------------------------------------------- Key: JBDS-729 URL: https://jira.jboss.org/jira/browse/JBDS-729 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.1 Reporter: Nick Boldt Assignee: Denis Golovin >From Denis: > Bumped in JBDS launch problem, the reason is - migration to Eclipse 3.5 wasn't done for installer. Fixed for linux version, but need find a way to update original config.ini/eclipse.ini files during build adding xsl.transformation plug-ins in it without keeping a copies of ini files -- 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

16 years, 3 months

3
22
0 / 0

[JBoss JIRA] Created: (JBIDE-4985) New seam projects should configure hibernate tools with the DTP connection

by Max Rydahl Andersen (JIRA)

New seam projects should configure hibernate tools with the DTP connection -------------------------------------------------------------------------- Key: JBIDE-4985 URL: https://jira.jboss.org/jira/browse/JBIDE-4985 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate, Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Fix For: 3.1.0.M4, 3.1.0.CR1 Now that hibernate console supports DTP connection profiles shouldn't we start using that for our Seam projects ? Removing the need to have connection info in the hibernate-console.properties ? (the other fields related to tx and others still need to there though) -- 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

16 years, 3 months

4
17
0 / 0

[JBoss JIRA] Created: (JBDS-962) Unable to find feature.xml in directory when JBDS start .

by Svetlana Yasenovich (JIRA)

Unable to find feature.xml in directory when JBDS start . --------------------------------------------------------- Key: JBDS-962 URL: https://jira.jboss.org/jira/browse/JBDS-962 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: WindowsXP SP2 JBoss Developer Studio Version: 3.0.0.M4 Build id:jbdevstudio-eap-win32-3.0.0.v200911180352M-H96-M4 JRE 1.6 Reporter: Svetlana Yasenovich EXECUTE: Start JBDS. FAILURE: Exception related to missed feature thrown in error log: Unable to find feature.xml in directory: C:\jbdevstudio\studio\eclipse\features\com.jboss.jbds.product.feature_3.1.0.v200911180352M-H96-M4 -- 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

16 years, 3 months

3
9
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 November 2009