October 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5070) "HQL Editor" & "Hibernate Criteria Editor" enhance exception handling.

by Vitali Yemialyanchyk (JIRA)

"HQL Editor" & "Hibernate Criteria Editor" enhance exception handling. ---------------------------------------------------------------------- Key: JBIDE-5070 URL: https://jira.jboss.org/jira/browse/JBIDE-5070 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Fix For: 3.1.0.CR1 here is JBIDE-5054 similar situation. For Console Configuration with error -> FAILURE: Unhadled Loop exception appears instead of "Bad configuration file" error dialog. Stacktrace: org.hibernate.console.HibernateConsoleRuntimeException: Persistence unit not found: 'null'. at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:150) at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:644) at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:629) at org.hibernate.console.ConsoleConfiguration$2.execute(ConsoleConfiguration.java:291) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64) at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:273) at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:112) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:67) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:53) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:57) -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBIDE-4850) Extending of css views to edit styles in html, jsp files

by Yura Zhishko (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4850?page=com.atlassian.jira.plu... ] Yura Zhishko closed JBIDE-4850. ------------------------------- Verified in 3.1.0.v200910220041N-H228-M4 > Extending of css views to edit styles in html,jsp files > ------------------------------------------------------- > > Key: JBIDE-4850 > URL: https://jira.jboss.org/jira/browse/JBIDE-4850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml source editing > Reporter: Sergey Dzmitrovich > Assignee: Yura Zhishko > Fix For: 3.1.0.M4 > > > to implement the next capabilities: > 1. capability to edit styles inside "style" tag by css views > 2. capability to edit styles inside "...style" attribute css views -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-4416) Modify templates for ui:composition and ui:define

by Yahor Radtsevich (JIRA)

Modify templates for ui:composition and ui:define ------------------------------------------------- Key: JBIDE-4416 URL: https://jira.jboss.org/jira/browse/JBIDE-4416 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.0.1.GA Reporter: Yahor Radtsevich Assignee: Maxim Areshkau Priority: Minor Fix For: 3.1.0.M2 1. ACTUAL BEHAVIOR: If the template file is not found these tags are rendered in green similar as the VPE does not know the tags. DESIRED BEHAVIOR: An icon (a question mark or something like it) should be shown instead. 2. ACTUAL BEHAVIOR: If web-root folder is unknown, the VPE does not try to make assumption what is it. DESIRED BEHAVIOR: It is assumed the the parent directory of the opened file is the web-root. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4775) Open on for css classes

by Sergey Dzmitrovich (JIRA)

Open on for css classes ----------------------- Key: JBIDE-4775 URL: https://jira.jboss.org/jira/browse/JBIDE-4775 Project: JBoss Tools Issue Type: Feature Request Reporter: Sergey Dzmitrovich Assignee: Sergey Dzmitrovich Fix For: 3.1.0.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, 5 months

4
11
0 / 0

[JBoss JIRA] Closed: (JBIDE-4853) AutoRefresh doesn't work after Select All and source edit

by Yura Zhishko (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4853?page=com.atlassian.jira.plu... ] Yura Zhishko closed JBIDE-4853. ------------------------------- Verified in 3.1.0.v200910220041N-H228-M4 > AutoRefresh doesn't work after Select All and source edit > --------------------------------------------------------- > > Key: JBIDE-4853 > URL: https://jira.jboss.org/jira/browse/JBIDE-4853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 3.1.0.M4 > Reporter: Yura Zhishko > Assignee: Yura Zhishko > Priority: Minor > Fix For: 3.1.0.M4 > > Attachments: screenshot-1.jpg, TestCase.swf > > > 1) Create JSF kick start project > 2) Open inputUserName.jsp page > 3) Select All source (Ctrl+A) > 4) Try to insert any symbol or char sequence. > RESULT: VPE isn't refreshed (screenshot-1) all symbols are inserted at the end of the visual DOM. > I've attached a video that describes this issue. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-4816) Dump Source give us different results before and after refresh

by Yura Zhishko (JIRA)

Dump Source give us different results before and after refresh -------------------------------------------------------------- Key: JBIDE-4816 URL: https://jira.jboss.org/jira/browse/JBIDE-4816 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Run VPE with Debug options enabled 2) Create JSF 1.2 kick start project 3) Open hello.jsp page 4) Call context menu on the Visual Pane and choose "Dump source": 5) Check Eclipse Console log RESULT: BODY element has the next content: <BODY ID="__content__area__">  <DIV STYLE="-moz-user-modify: read-write;"> <DIV STYLE="display: none; -moz-user-modify: read-only;"> <H1 STYLE="-moz-user-modify: read-write;"> Hello! </H1> </DIV> <DIV> <TABLE STYLE="border: 1px dotted rgb(255, 102, 0); padding: 5px; width: 100%;"> <TR> <TD> <DIV> <H3 STYLE="-moz-user-modify: read-write;"> <SPAN CLASS="vpe-text"> Hello </SPAN> <SPAN CLASS="vpe-text"> , </SPAN> <SPAN CLASS="vpe-text"> Any name </SPAN> <SPAN CLASS="vpe-text"> ! </SPAN> </H3> </DIV> </TD> </TR> </TABLE> </DIV> </DIV> </BODY> 6) Press refresh button and make Dump Source again RESULT: <BODY ID="__content__area__"> <DIV STYLE="-moz-user-modify: read-write;"> <DIV STYLE="display: none; -moz-user-modify: read-only;"> <H1 STYLE="-moz-user-modify: read-write;"> Hello! </H1> </DIV> <DIV> <TABLE STYLE="border: 1px dotted rgb(255, 102, 0); padding: 5px; width: 100%;"> <TR> <TD> <DIV> <H3 STYLE="-moz-user-modify: read-write;" CLASS=""> <SPAN CLASS="vpe-text"> Hello </SPAN> <SPAN CLASS="vpe-text"> , </SPAN> <SPAN CLASS="vpe-text"> Any name </SPAN> <SPAN CLASS="vpe-text"> ! </SPAN> </H3> </DIV> </TD> </TR> </TABLE> </DIV> </DIV> </BODY> The difference between previous and last sources is that  element has gone in last source. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4016) Small mistake in ESB Helloworld Example Client

by Aliaksey Nis (JIRA)

Small mistake in ESB Helloworld Example Client ---------------------------------------------- Key: JBIDE-4016 URL: https://jira.jboss.org/jira/browse/JBIDE-4016 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.0.0.GA Environment: ESB Project examples - Helloworld Client Reporter: Aliaksey Nis Priority: Trivial Look at screenshot. Small mistake in message text in ESB Helloworld Example Client. -- 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, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (JBDS-494) Welcome Screen Still shows at the end of Seam New Project Wizard

by Jim Tyrrell (JIRA)

Welcome Screen Still shows at the end of Seam New Project Wizard ---------------------------------------------------------------- Key: JBDS-494 URL: https://jira.jboss.org/jira/browse/JBDS-494 Project: Developer Studio Issue Type: Feature Request Affects Versions: 2.0.0.beta1 Reporter: Jim Tyrrell Attachments: Why not the default screen instead o fthe landing screen after new Create Seam Project.png After successfully completing the generation of the New Seam Project Wizard I am brought back to the Welcome page as seen in the attached screen shot. This is not to me the correct behavior. It would be nice to have my workspace opened with the projects on the left hand side, servers open on the bottom. It might also be nice to ask if I want to start the JBoss Server bound to this project...and I might even consider starting and deploying the home page so it is viewable in a web browser after the wizard completes. Or should all of this start in the background, or should you prompt the user to do all of this. Thoughts? -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5054) Hibernate mapping diagram bad exception handling.

by Aliaksey Nis (JIRA)

Hibernate mapping diagram bad exception handling. ------------------------------------------------- Key: JBIDE-5054 URL: https://jira.jboss.org/jira/browse/JBIDE-5054 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M4 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.M4 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.M4 JRE 1.5_08 Reporter: Aliaksey Nis EXECUTE: Create Seam 2FP EAR project. Case 1: EXECUTE: Open Hibernate view. Right click on projects configuration, select "Mapping diagram' item. FAILURE: Coz configuration is empty (no entities etc in project) - nothing happens after selecting "Mapping diagram" item. I think it will be better if empty diagram appears in this case. Case 2: EXECUTE: New > Hibernate XML mapping file. EXECUTE: Select Class - Authentificator, press Finish. EXECUTE: Authentificator mapping appears. It is broken (JBIDE-5052) and will cause problems. EXECUTE: Open Hibernate view. Right click on projects configuration, select "Mapping diagram' item. FAILURE: Unhadled Loop exception appears instead of "Bad configuration file" error dialog. Exception stacktrace: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:163) at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:644) at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:629) at org.hibernate.console.ConsoleConfiguration$2.execute(ConsoleConfiguration.java:291) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64) at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:273) at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:112) at org.jboss.tools.hibernate.ui.view.OpenDiagramActionDelegate.run(OpenDiagramActionDelegate.java:78) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251) ... -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5058) Fix JsfUiAllTests.testHtmlFileNewWizardResults

by Alexey Kazakov (JIRA)

Fix JsfUiAllTests.testHtmlFileNewWizardResults ---------------------------------------------- Key: JBIDE-5058 URL: https://jira.jboss.org/jira/browse/JBIDE-5058 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF, QA Affects Versions: 3.1.0.M4 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.1.0.M4, 3.1.0.CR1 Failed to execute runnable (java.lang.NullPointerException) org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:48) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:37) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:27) at org.jboss.tools.jsf.ui.test.HtmlFileNewWizardTest.testHtmlFileNewWizardResults(HtmlFileNewWizardTest.java:39) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) at org.eclipse.core.launcher.Main.main(Main.java:34) Caused by: java.lang.NullPointerException at org.jboss.tools.common.editor.XModelObjectTreeViewComponent$4.run(XModelObjectTreeViewComponent.java:134) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) See http://download.jboss.org/jbosstools/builds/nightly/latestBuild.html for details -- 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, 5 months

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