[JBoss JIRA] Created: (JBIDE-5806) ClassNotFoundException for enum at Mapping diagramm occurs
by Dmitry Geraskov (JIRA)
ClassNotFoundException for enum at Mapping diagramm occurs
----------------------------------------------------------
Key: JBIDE-5806
URL: https://jira.jboss.org/jira/browse/JBIDE-5806
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.CR1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.CR2
java.lang.ClassNotFoundException: auction.model.Rating
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:112)
at org.hibernate.type.EnumType.setParameterValues(EnumType.java:286)
at org.hibernate.type.TypeFactory.injectParameters(TypeFactory.java:339)
at org.hibernate.type.CustomType.<init>(CustomType.java:67)
at org.hibernate.type.TypeFactory.heuristicType(TypeFactory.java:245)
at org.hibernate.mapping.SimpleValue.getType(SimpleValue.java:260)
at org.hibernate.mapping.Column.getSqlTypeCode(Column.java:138)
at org.hibernate.mapping.Column.getSqlType(Column.java:182)
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-5779) Could not open the Visual Page Editor: XPCOM error -2147467259
by Igor Jacy Lino Campista (JIRA)
Could not open the Visual Page Editor: XPCOM error -2147467259
--------------------------------------------------------------
Key: JBIDE-5779
URL: https://jira.jboss.org/jira/browse/JBIDE-5779
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.CR1
Reporter: Igor Jacy Lino Campista
Attachments: shot2.PNG, shot3.PNG, shot4.PNG, shot5.PNG
After reinstalling eclipse 3.5.1 and installing the latest the visual editor (3.1.0 CR1) as I usually do I got the following exception opening any XHTML page
eclipse.buildId=M20090917-0800
java.version=1.5.0_19
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -plugincustomization C:\calypso_tools\eclipse\calypso_preferences.ini -product org.eclipse.epp.package.rcp.product
Command-line arguments: -os win32 -ws win32 -arch x86 -plugincustomization C:\calypso_tools\eclipse\calypso_preferences.ini -product org.eclipse.epp.package.rcp.product
Error
Tue Feb 02 09:12:14 CET 2010
Could not open the Visual Page Editor: XPCOM error -2147467259
org.eclipse.swt.SWTError: XPCOM error -2147467259
at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2068)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:457)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:119)
at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:88)
at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:153)
at org.jboss.tools.vpe.editor.mozilla.XulRunnerEditor2.<init>(XulRunnerEditor2.java:23)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:585)
at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:879)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:212)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:413)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:778)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:677)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2854)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:344)
at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:192)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
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.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 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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
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, 2 months
[JBoss JIRA] Created: (JBDS-1033) Selections on deployment screen get undone after saving project
by Aaron Pestel (JIRA)
Selections on deployment screen get undone after saving project
---------------------------------------------------------------
Key: JBDS-1033
URL: https://jira.jboss.org/jira/browse/JBDS-1033
Project: JBoss Developer Studio
Issue Type: Bug
Environment: JBDS 3.0 M4
Reporter: Aaron Pestel
1.) Create a new jBPM project.
2.) Save it
3.) Click on the jBPM editor "Deployment" tab
4.) select the "src/java/main" check box in the Java Class and Resources area of the panel
5.) select the "Source" tab
6.) add a space anywhere in the process file (just to trigger it needing a save)
7.) click back on the "Deployment" tab
8.) click the "Save" toolbar icon
9.) watch your "src/java/main" checkbox get unchecked.
The same thing happens for the "Files and Folders" section of the panel. Clicking "save" will revert to the default of selecting everything in that panel.
It might seem like this is a minor bug - and technically it probably is. But, it's a major pain when you actually have jBPM Java Actions in your process and you have to remember to select that check box every time you deploy after having saved the project (basically every time you would ever deploy). If you don't, you won't get an error - until you run the process and get a ClassNotFound error because your class was was not actually deployed in the process archive.
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-5790) Sources are not available in debug mode for JBoss AS Servers
by Denis Golovin (JIRA)
Sources are not available in debug mode for JBoss AS Servers
-------------------------------------------------------------
Key: JBIDE-5790
URL: https://jira.jboss.org/jira/browse/JBIDE-5790
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Environment: JBossTools JBossAS 2.1.0.v201001140901N-H132-CR2
Reporter: Denis Golovin
Assignee: Rob Stryker
I started in a new workspace and used a new JBoss AS 5.1 instance. I added the JBoss -> JBoss v5.0 runtime (the ones that comes bundled with WTP) and deployed my simple hello world test app to it. I added a break-point in a .java file that's within the project and when it hit, I could see the source of this class as expected.
I then removed the project from the server and also manually removed the .ear file from the JBoss AS deploy directory (the standard runtime doesn't do that unfortunately).
Then I added the JBoss Community -> JBoss AS 5.1 runtime (the one from JBoss AS tools) and again deployed my simple hello world test app to it. Added the break point again, but when I hit I didn't get to see the source this time. Just the default white editor with the red "Source not found." and the single button "Edit Source Lookup Path...".
I inspected the lauch configuration of both servers. When I have nothing deployed to the JBoss -> Jboss v5.0 runtime, the source tab shows an entry called "Default", which contains only the base JDK jars. However, as soon as I add (publish/deploy) my project to the JBoss v5.0 runtime, the "Default" entry in the source tab contains all JBoss jars and folders for both the web module and the ejb module of my test project.
The JBoss Community -> JBoss AS 5.1 runtime however in both cases (nothing deployed to it and my test project deployed to it) shows the same standard JDK classes under "Default" and nothing else.
--
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, 2 months