August 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Moved: (JBIDE-737) Problems occurr when CSS file is created

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-737?page=all ] Max Andersen moved EXIN-183 to JBIDE-737: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-737 (was: EXIN-183) > Problems occurr when CSS file is created > ---------------------------------------- > > Key: JBIDE-737 > URL: http://jira.jboss.com/jira/browse/JBIDE-737 > Project: JBoss Tools > Issue Type: Bug > Environment: Windows XP > RHDS build-333 > Reporter: Anton Klimkovich > Assigned To: Viacheslav Kabanovich > Attachments: Create_Css.txt, Create_Css2.txt, Create_CSS3.txt, Css edit.txt > > > 1 Right click on WebContent ->New->File->Css... > 2 Inpute file name and press finish > Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". > Log file attached. -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-736) You can only run one Criteria Query before it locks up and you can not run/edit your existing query.

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-736?page=all ] Max Andersen updated JBIDE-736: ------------------------------- Component/s: Hibernate > You can only run one Criteria Query before it locks up and you can not run/edit your existing query. > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-736 > URL: http://jira.jboss.com/jira/browse/JBIDE-736 > Project: JBoss Tools > Issue Type: Bug > Components: Hibernate > Affects Versions: 2.0.0.Beta3 > Environment: Linux Fedora Core 6 > Reporter: Jim Tyrrell > Attachments: Criteria_Screen_Shot.png > > > When you work in the Hibernate Configurations area and click on a Criteria Query you are only able to run the Query once and then close the the window if you want to edit the Criteria query. It seems the area I can type in is "shutdown" from any more typing after the green arrow "play" button is pressed once. -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-736) You can only run one Criteria Query before it locks up and you can not run/edit your existing query.

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-736?page=all ] Max Andersen moved EXIN-322 to JBIDE-736: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-736 (was: EXIN-322) Affects Version/s: 2.0.0.Beta3 (was: 1.0.0.beta1) > You can only run one Criteria Query before it locks up and you can not run/edit your existing query. > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-736 > URL: http://jira.jboss.com/jira/browse/JBIDE-736 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 2.0.0.Beta3 > Environment: Linux Fedora Core 6 > Reporter: Jim Tyrrell > Attachments: Criteria_Screen_Shot.png > > > When you work in the Hibernate Configurations area and click on a Criteria Query you are only able to run the Query once and then close the the window if you want to edit the Criteria query. It seems the area I can type in is "shutdown" from any more typing after the green arrow "play" button is pressed once. -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-735) Open-Ons for Beans and Bean properties don't work in Seam projects.

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-735?page=all ] Max Andersen moved EXIN-451 to JBIDE-735: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-735 (was: EXIN-451) Component/s: JSF (was: Red Hat Developer Studio) (was: The Lost Functionallity) Affects Version/s: 2.0.0.Beta3 (was: 1.0.0.beta1) > Open-Ons for Beans and Bean properties don't work in Seam projects. > ------------------------------------------------------------------- > > Key: JBIDE-735 > URL: http://jira.jboss.com/jira/browse/JBIDE-735 > Project: JBoss Tools > Issue Type: Bug > Components: JSF > Affects Versions: 2.0.0.Beta3 > Environment: Win2k > Eclipse 3.3 > Reporter: Victor Rubezhny > Assigned To: Victor Rubezhny > > Open-On operations on Beans declared in Seam Project don't work. > As result the following test fails: > testELExprPartitioner Failure Wrong recognition for the region: [859-886:org.eclipse.jst.jsp.SCRIPT.JSP_EL2:org.eclipse.jst.jsp.core.jspsource] doesn't matches the region [1041-1058] junit.framework.AssertionFailedError: Wrong recognition for the region: [859-886:org.eclipse.jst.jsp.SCRIPT.JSP_EL2:org.eclipse.jst.jsp.core.jspsource] doesn't matches the region [1041-1058] > at org.jboss.tools.jsf.text.ext.tests.ELExprPartitionerTest.testELExprPartitioner(ELExprPartitionerTest.java:166) > 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:123) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) > at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) > 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:153) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) > at org.eclipse.equinox.launcher.Main.run(Main.java:1169) > at org.eclipse.equinox.launcher.Main.main(Main.java:1144) > at org.eclipse.core.launcher.Main.main(Main.java:30) -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-638) Page flow is under "JBoss Seam" instead of "Seam" in Wizard dialog

by Max Andersen (JIRA)

Page flow is under "JBoss Seam" instead of "Seam" in Wizard dialog ------------------------------------------------------------------ Key: JBIDE-638 URL: http://jira.jboss.com/jira/browse/JBIDE-638 Project: JBoss Tools Issue Type: Feature Request Components: jbpm Affects Versions: 2.0.0.20070731 Reporter: Max Andersen Assigned To: Koen Aers Attachments: pageflowwizard.png jbpm should use the same id as "Seam" from jbosstools. -- 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

18 years, 9 months

2
10
0 / 0

[JBoss JIRA] Created: (JBIDE-639) New Page Flow broken - exception

by Max Andersen (JIRA)

New Page Flow broken - exception -------------------------------- Key: JBIDE-639 URL: http://jira.jboss.com/jira/browse/JBIDE-639 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.20070731 Reporter: Max Andersen Assigned To: Koen Aers Priority: Blocker Ctrl+N, select Page Flow and Next or Finish gives multiple errors and the dialog is just stuck: java.lang.IllegalArgumentException: Path must include project and resource name: / at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1625) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137) at org.jbpm.ui.pageflow.wizard.NewPageFlowWizardPage.getProcessFolder(Unknown Source) at org.jbpm.ui.pageflow.wizard.NewPageFlowWizard.performFinish(Unknown Source) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742 java.lang.NullPointerException at org.jbpm.ui.pageflow.wizard.NewPageFlowWizardPage.getRootForEmbeddingProject(Unknown Source) at org.jbpm.ui.pageflow.wizard.NewPageFlowWizardPage.initContainerName(Unknown Source) at org.jbpm.ui.pageflow.wizard.NewPageFlowWizardPage.init(Unknown Source) at org.jbpm.ui.pageflow.wizard.NewPageFlowWizard.addPages(Unknown Source) at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:113) java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:3547) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.widgets.Widget.error(Widget.java:438) at org.eclipse.swt.widgets.Text.setText(Text.java:1870) at org.jbpm.ui.pageflow.wizard.NewPageFlowWizardPage.createContainerField(Unknown Source) at org.jbpm.ui.pageflow.wizard.NewPageFlowWizardPage.createControl(Unknown Source) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:669) at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1083) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1142) -- 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

18 years, 9 months

2
8
0 / 0

[JBoss JIRA] Moved: (JBIDE-734) Archives View selection listener odd behavior

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-734?page=all ] Max Andersen moved EXIN-173 to JBIDE-734: ----------------------------------------- Project: JBoss Tools (was: Exadel Integration) Key: JBIDE-734 (was: EXIN-173) > Archives View selection listener odd behavior > --------------------------------------------- > > Key: JBIDE-734 > URL: http://jira.jboss.com/jira/browse/JBIDE-734 > Project: JBoss Tools > Issue Type: Bug > Components: Archives > Affects Versions: 2.0.0.Beta3 > Reporter: Rob Stryker > Assigned To: Rob Stryker > Attachments: selectionBug.swf > > > When the workbench starts, selection listening works. I close the view, re-open it, and MOVE the view, and selection works. I close the view, do NOT move the view, and selection does NOT work. Then i move the view, and selection works magically. > Basically, whenever the view is created, selection *does not* work. Then any of the following actions will allow selection-events to be received: > - Switching to a previously hidden view > - Moving focus to a different application, then back to eclipse > - moving a view (any view) from one location to another -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-734) Archives View selection listener odd behavior

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-734?page=all ] Max Andersen updated JBIDE-734: ------------------------------- Component/s: Archives Affects Version/s: 2.0.0.Beta3 your bug, right ? > Archives View selection listener odd behavior > --------------------------------------------- > > Key: JBIDE-734 > URL: http://jira.jboss.com/jira/browse/JBIDE-734 > Project: JBoss Tools > Issue Type: Bug > Components: Archives > Affects Versions: 2.0.0.Beta3 > Reporter: Rob Stryker > Assigned To: Rob Stryker > Attachments: selectionBug.swf > > > When the workbench starts, selection listening works. I close the view, re-open it, and MOVE the view, and selection works. I close the view, do NOT move the view, and selection does NOT work. Then i move the view, and selection works magically. > Basically, whenever the view is created, selection *does not* work. Then any of the following actions will allow selection-events to be received: > - Switching to a previously hidden view > - Moving focus to a different application, then back to eclipse > - moving a view (any view) from one location to another -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-732) New view in faces-config.xml

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-732?page=all ] Max Andersen moved RHDS-66 to JBIDE-732: ---------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-732 (was: RHDS-66) > New view in faces-config.xml > ---------------------------- > > Key: JBIDE-732 > URL: http://jira.jboss.com/jira/browse/JBIDE-732 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 2.0.0.Beta3 > Reporter: Krasimir Goutcev > > When open faces-config.xml with RedHat XML Editor in Design mode, there is capability to select "View Template" (I think that this is like "New View" )and after that to place in work area . > In Exadel Studio 4 after that view is created. now - nothing happen -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-732) New view in faces-config.xml

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-732?page=all ] Max Andersen updated JBIDE-732: ------------------------------- Affects Version/s: 2.0.0.Beta3 > New view in faces-config.xml > ---------------------------- > > Key: JBIDE-732 > URL: http://jira.jboss.com/jira/browse/JBIDE-732 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 2.0.0.Beta3 > Reporter: Krasimir Goutcev > > When open faces-config.xml with RedHat XML Editor in Design mode, there is capability to select "View Template" (I think that this is like "New View" )and after that to place in work area . > In Exadel Studio 4 after that view is created. now - nothing happen -- 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

18 years, 9 months

1
0
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 August 2007