[JBoss JIRA] Created: (JBIDE-1557) Exceptions appeared in error log when I tried to move cursor over area selected in attached picture. See attachment.
by Andrei Scherbovich (JIRA)
Exceptions appeared in error log when I tried to move cursor over area selected in attached picture. See attachment.
--------------------------------------------------------------------------------------------------------------------
Key: JBIDE-1557
URL: http://jira.jboss.com/jira/browse/JBIDE-1557
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 2.0.0.GA
Reporter: Andrei Scherbovich
Assigned To: Maxim Areshkau
Attachments: 1.jpg
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ClassCastException: $Proxy14)
at org.eclipse.swt.SWT.error(SWT.java:3563)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
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.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
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 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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
Caused by: java.lang.ClassCastException: $Proxy14
at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.findVisbleParentElement(XulRunnerEditor.java:424)
at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.showSelectionRectangle(XulRunnerEditor.java:486)
at org.jboss.tools.vpe.editor.VpeController$18.run(VpeController.java:2296)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
... 23 more
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1500) Code Assist not work in HQL Editor when configuration was not loaded
by Dima Geraskov (JIRA)
Code Assist not work in HQL Editor when configuration was not loaded
--------------------------------------------------------------------
Key: JBIDE-1500
URL: http://jira.jboss.com/jira/browse/JBIDE-1500
Project: JBoss Tools
Issue Type: Bug
Components: Hibernate
Affects Versions: 2.0.1
Reporter: Dima Geraskov
Assigned To: Dima Geraskov
Priority: Minor
Fix For: 2.0.1
Steps to reproduce:
1. Start IDE with any project and hibernate console configuration
2. Open Hibernate Configurations View
3. Right Click on the first console configuration in view's tree
4. In context menu select HQL Editor
=> this console configuration will be selected in the top of HQL Editor
(it is still not loaded as we haven't expanded it in view)
5. If you have entity named "Customer" for example write "from Cus" in the editor and press Ctrl+Space
6. Observe that no message shown and Code Assist not works.
=>It happends because selected console configuration still not loaded.
7. Expand in Hibernate Console Configguration selected configuration
=> Now it is loaded
8. Repeat step 7
9. Observe that Code Assist works all right.
As I think should be shown message box with question like this: "Console configuration not loaded. Do you want load it now?"
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1657) Imported Project's classpath container assuming server exists
by Rob Stryker (JIRA)
Imported Project's classpath container assuming server exists
-------------------------------------------------------------
Key: JBIDE-1657
URL: http://jira.jboss.com/jira/browse/JBIDE-1657
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Rob Stryker
Fix For: 2.0.1
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider$RuntimeClasspathContainer.getDescription(ProjectRuntimeClasspathProvider.java:120)
at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getCPListElementText(CPListLabelProvider.java:261)
at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getText(CPListLabelProvider.java:78)
at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getText(WrappedViewerLabelProvider.java:108)
at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:164)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:135)
at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:386)
My guess is that your classpath container thinks the server exists...which it wont do in this case when he is creating a new project.
That should be fixed in .0.1
Workaround for user: delete the classpath entry about JBoss 4 server in classpath.
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
by Chris Simons (JIRA)
Unable to select "Add JSF Capability" nor register new TLDs
-----------------------------------------------------------
Key: JBIDE-1658
URL: http://jira.jboss.com/jira/browse/JBIDE-1658
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 2.0.0.GA
Environment: Windows XP SP2
Eclipse Europa 3.3 with JBoss Tools 2.0GA
Seam 2.0GA runtimes
Using icefaces.tld v. 1.6.1
Reporter: Chris Simons
Having trouble selecting "Add JSF Capability" on a project checked out through SVN that previously had the capability added by another user (on the same project/branch).
All options under Project -> JBoss Tools are disabled except for "Add Struts Capability". [see screenshot]
This prevents the registration of new TLDs, such as IceFaces, through the Pallette Library.
I was able to successfully accomplish both of these tasks when I initially upgraded to JBoss Tools 2.0GA from Exadel Studio Pro. Now, it seems some settings under .settings is being loaded by other users trying to migrate to JBoss Tools/Eclipse and are now unable to add a new JSF capability, nor register any new TLDs.
Also see the attached snippets from the eclipse log below:
{code}
eclipse.buildId=M20071023-1652
java.version=1.6.0_02
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -clean
!ENTRY org.jboss.tools.vpe 4 0 2008-01-18 11:10:28.473
!MESSAGE
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:56)
at org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:39)
at org.jboss.tools.vpe.editor.context.VpePageContext.registerTaglibs(VpePageContext.java:416)
at org.jboss.tools.vpe.editor.context.VpePageContext.rebuildTaglibMap(VpePageContext.java:180)
at org.jboss.tools.vpe.editor.context.VpePageContext.setTaglib(VpePageContext.java:155)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addTaglib(VpeVisualDomBuilder.java:1912)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createXmlns(VpeVisualDomBuilder.java:1868)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:362)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:221)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:470)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:192)
at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:221)
at org.jboss.tools.vpe.editor.VpeEditorPart$5.load(VpeEditorPart.java:512)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:461)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$1(MozillaEditor.java:456)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$4.onLoadWindow(MozillaEditor.java:217)
at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:389)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2265)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3291)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:801)
at org.eclipse.ui.internal.Workbench$25.runWithException(Workbench.java:1342)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
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:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309)
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.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
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 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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
{code}
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1655) Cannot add new files to Seam project
by Chris Simons (JIRA)
Cannot add new files to Seam project
------------------------------------
Key: JBIDE-1655
URL: http://jira.jboss.com/jira/browse/JBIDE-1655
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: core
Affects Versions: 2.0.0.GA
Environment: Windows XP SP2
JBoss Tools 2.0GA with Eclipse 3.3 Europa
Reporter: Chris Simons
Attachments: unable to create XHTML file.jpg
Since upgrading to Seam 2.0 runtimes within JBoss Tools, I am only able to create new XHTML files by copying an existing file and renaming it.
Please see screenshot.
I can specify the folder by using "Browse" or typing it in myself; I then type in a file name.
The messages is always: "Cannot create file in specified folder."
--
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, 2 months
[JBoss JIRA] Commented: (JBIDE-772) New Hibernate Project
by Dima Geraskov (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-772?page=comments#action_12397672 ]
Dima Geraskov commented on JBIDE-772:
-------------------------------------
I can't understand that comment.
"we need to get a common story for all these libraries that are in there...." what does this mean?
I imagine this in the following form:
if user wants to add hibernate capabilities to his project he right-clicks on the project and select "Add hibernate capabilitie". Dialog shows to him and offers to select libraries from the list (the libraries are situated into our plugin). He selects libraries, press OK. We copy the libraries to the project and add them to the classpath, add hibernate nature to the project. Also we can run dialog:
______________________________________
|Dialog________________________________|
| Select wizard you want to be run. |
| |
| o New Hibernate Configuration File wizard |
| o New Reverse Engeneering File wizard |
| [OK] [Cancel] |
|_____________________________________|
> New Hibernate Project
> ---------------------
>
> Key: JBIDE-772
> URL: http://jira.jboss.com/jira/browse/JBIDE-772
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate, libmanagement
> Reporter: Max Andersen
> Assigned To: Dima Geraskov
> Priority: Minor
> Fix For: 2.1
>
>
> Provide a New Hibernate project wizard that setups the basics. Libraries etc.
--
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, 2 months
[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-719?page=comments#action_12397654 ]
Max Andersen commented on JBIDE-719:
------------------------------------
The idea is that hibernate.cfg.xml does not know about this. This is basically only for the Hibernate Console configuration to have a setting that allows the user to use the DTP provided connection details/info instead of what is in cfg.xml and jpa persistence.xml
Because in the configuration files it might be a datasource which we do not know anything about and thus users have to maintain 2 versions of cfg.xml or persistence.xml. Today we avoid that by having the option to override the settings via a properties file (see how that is done for seam generated projects via the hibernate-tools.properties)
What we need is that Hibernate Console configuration can point to a named DTP connection and then IFF that name is specified it should be looked up in DTP and we should get the connection information from there and use that instead of the ones specifed by default.
> Hibernate Tools should be able to use a named Eclipse provided connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-719
> URL: http://jira.jboss.com/jira/browse/JBIDE-719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate
> Reporter: Max Andersen
> Assigned To: Vitali Yemialyanchyk
> Priority: Optional
> Fix For: 2.1
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml
> Users should be able to say to use a named WTP provided database connection.
--
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, 2 months