March 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-466) Capital letters in sample projects names

by Svetlana mukhina (JIRA)

Capital letters in sample projects names ---------------------------------------- Key: JBDS-466 URL: https://jira.jboss.org/jira/browse/JBDS-466 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.0.0.beta1 There should not be text examples, screens or movies containing project names with capital letters, check all guides and inform others about 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

16 years, 10 months

3
26
0 / 0

[JBoss JIRA] Created: (JBIDE-3155) Exceptions thrown when closing Visual Editor

by Asgeir Frimannsson (JIRA)

Exceptions thrown when closing Visual Editor -------------------------------------------- Key: JBIDE-3155 URL: https://jira.jboss.org/jira/browse/JBIDE-3155 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Environment: SUN jdk1.6_u10, Fedora 10 x86_64 using JBoss Tools and drivers from http://download.jboss.org/jbosstools/builds/nightly/3.0.0.CR1/20081108025... Reporter: Asgeir Frimannsson <probably-irrelevant> Step 1: Create a new seam-gen project using ./seam create-project Step 2: Import the project into JBoss tools using File->New->Project Step 3: Set up the Seam build environment etc.. </probably-irrelevant> Step 4: Open a page, e.g. home.xhtml in visual editor Step 5: Close editor ... Exceptions thrown.. !ENTRY org.eclipse.ui 4 0 2008-11-11 09:44:34.790 !MESSAGE The function "removeSelectionListener" returned an error condition (0x80004005) !STACK 0 org.mozilla.xpcom.XPCOMException: The function "removeSelectionListener" returned an error condition (0x80004005) at org.mozilla.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Native Method) at org.mozilla.xpcom.internal.XPCOMJavaProxy.invoke(XPCOMJavaProxy.java:143) at $Proxy16.removeSelectionListener(Unknown Source) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.removeSelectionListener(XulRunnerEditor.java:599) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor$2.widgetDisposed(XulRunnerEditor.java:133) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117) -- 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, 10 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-4068) Add option (Open On) to open the correspondent Seam component when we have a @In annotation in a field and click on the field name .

by Joao Paulo Viragine (JIRA)

Add option (Open On) to open the correspondent Seam component when we have a @In annotation in a field and click on the field name . ------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4068 URL: https://jira.jboss.org/jira/browse/JBIDE-4068 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Joao Paulo Viragine It's very useful when we have an Interface as a component type. (because click on the Interface doesn't open the correspondent Seam component) E.g. @In private MySeamComponent mySeamComponent; When click in mySeamComponent the JBDS/Tools could open the correspondent Seam component (a class annotated with @Name("mySeamComponent") or @Role/@Roles "mySeamComponent") -- 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, 10 months

4
19
0 / 0

[JBoss JIRA] Created: (JBIDE-4052) getFetchMode calles NullPointerException when was not set

by Dmitry Geraskov (JIRA)

getFetchMode calles NullPointerException when was not set --------------------------------------------------------- Key: JBIDE-4052 URL: https://jira.jboss.org/jira/browse/JBIDE-4052 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.0.0.GA Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0 Attachments: patch.txt Stack trace: java.lang.NullPointerException at org.hibernate.tool.hbm2x.Cfg2HbmTool.getFetchMode(Cfg2HbmTool.java:313) at org.hibernate.tool.hbm2x.Cfg2HbmTool.hasFetchMode(Cfg2HbmTool.java:304) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4050) Abstract attribute is never exported in persistent class.

by Dmitry Geraskov (JIRA)

Abstract attribute is never exported in persistent class. --------------------------------------------------------- Key: JBIDE-4050 URL: https://jira.jboss.org/jira/browse/JBIDE-4050 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: FreeMarker, Hibernate Affects Versions: 3.0.0.GA Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0 We use the following code to export the attrubute: <#if clazz.abstract?exists && clazz.abstract> abstract="true" </#if> but "abstract" attribute held into PersistentClass.isAbstract. I guess developers of freemarker check only get+Fieldname and is+Fieldname, like java convension says. So, the working code is: <#if clazz.isAbstract()?exists && clazz.isAbstract()> abstract="true" </#if> Patch and unit test will be attached. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3914) Cfg2HbmTool.needsTable() method returns true for Subclass object

by Dmitry Geraskov (JIRA)

Cfg2HbmTool.needsTable() method returns true for Subclass object ---------------------------------------------------------------- Key: JBIDE-3914 URL: https://jira.jboss.org/jira/browse/JBIDE-3914 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.0.0.CR2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Minor <subclass> element in hibernate mapping must not contain "table" attrinbute. Subclass and SingleTableSubclass objects is exported as <subclass>. This means that method Cfg2HbmTool.needsTable(PersistentClass) must return false for Subclass and SingleTableSubclass objects. Now it returns *false* only for SingleTableSubclass . -- 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, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-414) invisible tags in VPE

by Svetlana mukhina (JIRA)

invisible tags in VPE --------------------- Key: JBDS-414 URL: https://jira.jboss.org/jira/browse/JBDS-414 Project: Developer Studio Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.0.0.alpha update info on VPE in visual web tools according to the changes https://jira.jboss.org/jira/browse/JBIDE-1805 -- 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, 11 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-662) centralize requirements folder on in /home/hudson/hudson_workspace/workspace/jbosstools-jbdevstudio-REQUIREMENTS

by Nick Boldt (JIRA)

centralize requirements folder on in /home/hudson/hudson_workspace/workspace/jbosstools-jbdevstudio-REQUIREMENTS ---------------------------------------------------------------------------------------------------------------- Key: JBDS-662 URL: https://jira.jboss.org/jira/browse/JBDS-662 Project: Developer Studio Issue Type: Task Affects Versions: LATER Reporter: Nick Boldt Priority: Minor Fix For: 2.0.1, 2.1.0 To avoid meltdowns like we had in JBQA-2144, to reduce disk usage, and to speed up the rollout of new hudson jobs, I propose we create two folders: /home/hudson/hudson_workspace/workspace/jbosstools-3.0-jbdevstudio-2.0-REQUIREMENTS /home/hudson/hudson_workspace/workspace/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS In there, we will place a copy of all the requirements used by the paired builds, and instead of burning time and bandwidth fetching the 3G of zips every time we start a new job, we'll simply symlink to that folder so new reqs will be added. cd /home/hudson/hudson_workspace/workspace/jbosstools-nightly-3.0.x/jbds-build ln -s /home/hudson/hudson_workspace/workspace/jbosstools-3.0-jbdevstudio-2.0-REQUIREMENTS requirements Thus, for the 4 parallel jobs for JBDS2.0.0/2.0.1 & JBT3.0.0/3.0.1, we'll use about 3G of disk instead of 12. For the 2 parallel jobs for JBDS2.1.0 & JBT3.1.0, we'd save 3G. For the case where this is run on a local box (eg., my own Hudson) we just need a catch that says "if /home/hudson/hudson_workspace/workspace/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS doesn't exist, create it, symlink to it, and begin downloading" .. of course the path there would be ~/.hudson/jobs/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS, but it's the same relative path. -- 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, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2975) jBPM Task Reminder can't update processdefinition.xml

by cmi000 (JIRA)

jBPM Task Reminder can't update processdefinition.xml ----------------------------------------------------- Key: JBIDE-2975 URL: https://jira.jboss.org/jira/browse/JBIDE-2975 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.0.0.alpha, 2.1.2, 2.1.1, 2.1.0.GA Reporter: cmi000 After I input data in Task Reminder, the source was not updated. -- 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, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBDS-451) Eclipse tools for Guvnor guide

by Svetlana mukhina (JIRA)

Eclipse tools for Guvnor guide ------------------------------- Key: JBDS-451 URL: https://jira.jboss.org/jira/browse/JBDS-451 Project: Developer Studio Issue Type: Feature Request Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.beta1 Read eclipse_guvnor_m2_notes.pdf that is attached to the linked task, decide whether it's relevant to Tools users, if yes convert it into xml files with our common structure. -- 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, 11 months

3
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 March 2009