April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5026) Add JSF Capabilities are blocked with Eclipse by Updating maven dependences.

by Yura Zhishko (JIRA)

Add JSF Capabilities are blocked with Eclipse by Updating maven dependences. ---------------------------------------------------------------------------- Key: JBIDE-5026 URL: https://jira.jboss.org/jira/browse/JBIDE-5026 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.M4 Environment: Eclipse 3.5.1 with all required plug-ins installed. JBoos Tools installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/ Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Critical 1) Install Eclipse 3.5.1 with all required plug-ins. 2) Help -> Install New Software. 3) Install JBT using link from environment description. 4) Import attached project into workspace. 5) Wait until Updating Maven Dependencies doesn't start. 6) RMB on a project 7) JBoss Tools -> Add JSF Capabilities 8) Press Next > 9) Press Finish RESULT: Dialog and Eclipse are blocked for user actions while Updating is running (screenshot-1). -- 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, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-4685) "Add JSF Capabilities" improvements proposals

by Maxim Areshkau (JIRA)

"Add JSF Capabilities" improvements proposals --------------------------------------------- Key: JBIDE-4685 URL: https://jira.jboss.org/jira/browse/JBIDE-4685 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.0.M3 Add JSF Capabilities menu should be redesigned. -- 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, 6 months

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-1893) Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages

by Anton Klimkovich (JIRA)

Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages ------------------------------------------------------------------------------- Key: JBIDE-1893 URL: http://jira.jboss.com/jira/browse/JBIDE-1893 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 2.0.1 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create JSF with Facelets kickstart project EXECUTE: Create JSF1.2 kickstart project EXECUTE: Window->Preferenses -> JBossTools->Web->JSF->JSF Pages EXECUTE: Press Add button EXECUTE: Press Browse button ASSERT: Two projects available: JSF with Facelets and JSF1.2 kickstarts EXECUTE: Expand pages folder in JSF with Facelets project ASSERT: *.xhtml pages shoul be available . FAILURE: *.xhtml pages are not available . -- 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, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (RHDS-321) Warning in the case of incorrect bean references

by Florian Marwede (JIRA)

Warning in the case of incorrect bean references ------------------------------------------------ Key: RHDS-321 URL: http://jira.jboss.com/jira/browse/RHDS-321 Project: Red Hat Developer Studio Issue Type: Feature Request Reporter: Florian Marwede Priority: Minor See forum thread. The warning should behave like a eclipse warning (yellow underline in the editor and also appear in problem view). It must be configurable, so you can switch it off when you manage your beans in a way RHDS can't analyze. -- 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, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8669) Dot character is not supported in DB schema name in Hibernate Configuration

by Boris Na (JIRA)

Dot character is not supported in DB schema name in Hibernate Configuration --------------------------------------------------------------------------- Key: JBIDE-8669 URL: https://issues.jboss.org/browse/JBIDE-8669 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: LATER Environment: Hibernate tools version is 3.4.0.v20110215-1252-H31-GA (by the way it's not listed in the Jira version menu) Win XP Eclipse Helios Service Release 1 WTP 3.2.3 Dali 2.3.3 MySQL 5.5.9 Reporter: Boris Na Assignee: Max Rydahl Andersen Priority: Minor 1/ Create a schema on MySQL called: myschema.domain 2/ Create a JPA project 3/ Create an entity called myEntity 4/ Create The corresponding Table (via generated script) 5/ Configure Data Source Explorer to the connection => This works well 6/ Configure Hibernate explorer (using above connection) 7/ Try to open the Database part of this view => you get an SQL exception: org.hibernate.exception.SQLGrammarException: Could not get list of suggested identity strategies from database. Probably a JDBC driver problem. (...) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.DOMAIN like 'myentity'' at line 1 (...) Hint: I just checked the SQL query (via MySQL proxy) and it lacks `` around the schema name in one query: show table status from MYSCHEMA.DOMAIN like 'myentity' Just replace dot by underscore and everything works well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8721) OpenOn does not work for JavaScript variables on HTML pages

by Yahor Radtsevich (JIRA)

OpenOn does not work for JavaScript variables on HTML pages ----------------------------------------------------------- Key: JBIDE-8721 URL: https://issues.jboss.org/browse/JBIDE-8721 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.CR1 Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Attachments: javascript-prj.zip OpenOn does not work for JavaScript variables on HTML pages. *Steps to reproduce:* # Import attached project [^javascript-prj.zip] into workspace. # Open index.html with "JBoss Tools HTML Editor" # Point cursor before "a + 1" as it is shown below: {code:xml|title=index.html|borderStyle=solid} <html> <head> <script type="text/javascript"> var a = 1; var b = |a + 1; </script> </head> </html> {code} # Press Open Declaration hotkey (F3 or Ctrl-click by default) *Actual result:* Nothing happens. *Expected result:* The cursor must move to the declaration of the variable 'a'. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7100) Wrond proposals appear in CA Window for CSS styles inside <style></style> tag

by Victor Rubezhny (JIRA)

Wrond proposals appear in CA Window for CSS styles inside <style></style> tag ----------------------------------------------------------------------------- Key: JBIDE-7100 URL: https://jira.jboss.org/browse/JBIDE-7100 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Environment: Eclipse 3.6; WTP 3.2 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Wrong proposals appear in CA Window for CSS styles inside <style></style> tag when: 1. There is at least one whitespace character is placed between opening and closing "style" tags -and- 2. The CA is invoked when the cursor is pointed right before the closing tag (i.e. "<style type="text/css"> |</style>", where "|"-char indicates the cursor position. In such cases WTP suggests proposals for a new tags insertion, but not the CSS proposals. Probably it's WTP's issue, because: 1. WTP decides which kind of proposals are to be calculated at some cursor position. 2. We don't add any computers for CSS proposals since WTP 3.2 -- 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, 7 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-2438) Support for backing bean configuration in Spring application context

by Claus Nyhus (JIRA)

Support for backing bean configuration in Spring application context -------------------------------------------------------------------- Key: JBIDE-2438 URL: http://jira.jboss.com/jira/browse/JBIDE-2438 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Claus Nyhus Hi, When using Spring with JSF it is very compelling to define backing beans in Springs application context (either via XML configuration or annotations) rather than in faces-config.xml. The downside of this is that you cannot use completion on properties from the backing beans in JBoss tools when editing JSF pages (e.g. facelets files). It would be very nice if JBoss Tools could pick up backing beans from a Spring application context and treat them the same way backing beans from faces-config.xml is handled. Cheers /Claus References for defining backing beans in an Spring application context: http://prime.com.tr/cagataycivici/?p=92 http://prime.com.tr/cagataycivici/?p=94 -- 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, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?

by Nick Boldt (JIRA)

Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ? --------------------------------------------------------------------------------- Key: JBDS-1635 URL: https://issues.jboss.org/browse/JBDS-1635 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: Build, Requirements Affects Versions: 5.0.0.M1 Reporter: Nick Boldt Assignee: Fred Bricon >From Max: > We're not planning on supporting JBoss Maven Integration (org.jboss.tools.maven.*) before there is stable api from m2e. > But I guess it could be put on the Extras site as a 3rd party "selected" plugin. > The maven stuff can't just be put into JBDS 4.x sites without some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it. >From Sneja: +1 Awaiting feedback from Fred. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-6883) Smooks wizard throws exception and doesn't open file when wizard finishes

by Brian Fitzpatrick (JIRA)

Smooks wizard throws exception and doesn't open file when wizard finishes ------------------------------------------------------------------------- Key: JBIDE-6883 URL: https://jira.jboss.org/browse/JBIDE-6883 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: smooks Affects Versions: 3.2.x Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta When you use the new Smooks Configuration File wizard to create a Smooks file, it creates the file and then should open it in the editor. Instead, I'm seeing this error: !ENTRY org.jboss.tools.smooks.ui 4 4 2010-08-20 15:46:20.968 !MESSAGE Error !STACK 1 org.eclipse.ui.PartInitException: Unable to open editor, unknown editor ID: org.jboss.tools.smooks.configuration.editors.MultiPageEditor at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:633) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2860) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2682) at org.jboss.tools.smooks.configuration.wizards.SmooksConfigurationFileNewWizard$2.run(SmooksConfigurationFileNewWizard.java:142) 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:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1008) at org.jboss.tools.smooks.configuration.wizards.SmooksConfigurationFileNewWizard.performFinish(SmooksConfigurationFileNewWizard.java:87) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) !SUBENTRY 1 org.eclipse.ui 4 0 2010-08-20 15:46:20.983 !MESSAGE Unable to open editor, unknown editor ID: org.jboss.tools.smooks.configuration.editors.MultiPageEditor -- 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, 7 months

2
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 April 2011