-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

View unanswered posts | View active topics


Board index » Projects » Search, Validator, Shards

All times are UTC - 5 hours [ DST ]


Forum locked This topic is locked, you cannot edit posts or make further replies.  Page 1 of 1
  [ 9 posts ] 
  Previous topic | Next topic 
Author Message
olobolo
 Post subject: Problem with connection parameters configuration
PostPosted: Sun Feb 26, 2006 8:57 pm 
Beginner
Beginner

Joined: Mon Feb 13, 2006 8:34 pm
Posts: 27
I have just added all necessary plug-ins to my Eclipse SDK 3.1.1 which I use with Windows XP. It looks like everything is ok, I have persistence perspective and all persistence views but there is something strange...

I start with "Add persistence to project"->"Connection parameters"
When I set all parameters to my database connection, I choose "Test connection" and connection is ok! After that I choose "Next" and I have "filter" dialog box and after that I choose "Finish" and...nothing change when I choose "Finish", all I can do in that moment is "Cancel" and of course I do not have my connection configured...

I really do not know what can be wrong. Can anybody help my with that...thx
Top
 Profile  
 
silvaran
 Post subject: Persistence plug-in
PostPosted: Mon Feb 27, 2006 4:32 pm 
Regular
Regular

Joined: Wed Feb 15, 2006 9:09 pm
Posts: 76
What plug-in are you using to provide the persistence perspective and support?
Top
 Profile  
 
olobolo
 Post subject: JSR220-ORM-M2
PostPosted: Mon Feb 27, 2006 5:07 pm 
Beginner
Beginner

Joined: Mon Feb 13, 2006 8:34 pm
Posts: 27
I use JSR220-ORM-M2 plug-in
Top
 Profile  
 
silvaran
 Post subject:
PostPosted: Mon Feb 27, 2006 6:21 pm 
Regular
Regular

Joined: Wed Feb 15, 2006 9:09 pm
Posts: 76
This is definitely a bug in the way JSR220 opens the connection properties pane. There is, however, a workaround:

1. Go to Window->Show View->Other
2. Expand "Data", and select "Database Explorer", and click OK.
3. In the new tab, right-click "Connections" and select "New Connection..."
4. Enter all the stuff like before, and if you don't need to specify anything on the next wizard page (the filters part), just click "Finish" after you've successfully tested your database connection instead of going "Next".

Essentially we're just creating a new database connection outside of the persistence dialog to bypass the bug.

Now when you go back to "Add Persistence to Project", you'll be able to select this connection from the Connection drop-down (without actually having to create it from within this dialog and encountering the bug) and continue with the settings like before.

You should definitely submit a bug report to the JSR-220 project and let them know that their "new connection" wizard handling is broken from within the "Add Persistence" dialog.
Top
 Profile  
 
silvaran
 Post subject:
PostPosted: Mon Feb 27, 2006 6:26 pm 
Regular
Regular

Joined: Wed Feb 15, 2006 9:09 pm
Posts: 76
Just to let you know, there is already a bug logged against this issue, but apparently it's not with JSR:

JSR220 bug #109242

Which leads you to this:

Web Tools RDB bug #107700

It hasn't been fixed yet, but there's a second workaround: Make sure the "Database Explorer" pane is open when you create new connections through the persistence component like you described above.
Top
 Profile  
 
olobolo
 Post subject: Some new error :(
PostPosted: Tue Feb 28, 2006 10:08 am 
Beginner
Beginner

Joined: Mon Feb 13, 2006 8:34 pm
Posts: 27
So is there any other plug-in with JSR220 without this bug?
When I open Database Explorer I'm able after that to create connection but I still have some error working with persistence perspective:

Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench"

Code:
java.lang.NoClassDefFoundError
   at org.eclipse.jsr220orm.ui.internal.mapping.NewEntityComposite.getText(NewEntityComposite.java:160)
   at org.eclipse.jsr220orm.ui.internal.mapping.NewEntityComposite.setCompilationUnit(NewEntityComposite.java:67)
   at org.eclipse.jsr220orm.ui.internal.views.MappingView.unknownUnitSelected(MappingView.java:150)
   at org.eclipse.jsr220orm.ui.internal.views.MappingView.unknownPartSelected(MappingView.java:131)
   at org.eclipse.jsr220orm.ui.internal.views.MappingView.doUpdate(MappingView.java:76)
   at org.eclipse.jsr220orm.ui.internal.views.AbstractMetadataView.doUpdateImpl(AbstractMetadataView.java:111)
   at org.eclipse.jsr220orm.ui.internal.views.AbstractMetadataView.doUpdate(AbstractMetadataView.java:78)
   at org.eclipse.jsr220orm.ui.internal.views.AbstractMetadataView.installWorkbenchPage(AbstractMetadataView.java:192)
   at org.eclipse.jsr220orm.ui.internal.views.AbstractMetadataView.partActivated(AbstractMetadataView.java:197)
   at org.eclipse.ui.internal.PartListenerList$1.run(PartListenerList.java:72)
   at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
   at org.eclipse.core.runtime.Platform.run(Platform.java:783)
   at org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:58)
   at org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:70)
   at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:73)
   at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:171)
   at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:56)
   at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:117)
   at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:2910)
   at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:2512)
   at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:249)
   at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:214)
   at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
   at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
   at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:867)
   at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:848)
   at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:998)
   at org.eclipse.swt.widgets.Shell.WM_MOUSEACTIVATE(Shell.java:1635)
   at org.eclipse.swt.widgets.Control.windowProc(Control.java:3079)
   at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1582)
   at org.eclipse.swt.widgets.Display.windowProc(Display.java:3706)
   at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
   at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1651)
   at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
   at org.eclipse.swt.widgets.Control.windowProc(Control.java:3123)
   at org.eclipse.swt.widgets.Display.windowProc(Display.java:3706)
   at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
   at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1651)
   at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
   at org.eclipse.swt.widgets.Control.windowProc(Control.java:3123)
   at org.eclipse.swt.widgets.Display.windowProc(Display.java:3706)
   at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
   at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1651)
   at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
   at org.eclipse.swt.widgets.Control.windowProc(Control.java:3123)
   at org.eclipse.swt.widgets.Display.windowProc(Display.java:3706)
   at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
   at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1651)
   at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
   at org.eclipse.swt.widgets.Control.windowProc(Control.java:3123)
   at org.eclipse.swt.widgets.Display.windowProc(Display.java:3706)
   at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
   at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1651)
   at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:203)
   at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:2389)
   at org.eclipse.swt.widgets.Display.windowProc(Display.java:3706)
   at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native Method)
   at org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:2111)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2708)
   at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
   at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
   at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
   at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
   at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
   at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
   at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
   at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
   at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
   at org.eclipse.core.launcher.Main.run(Main.java:973)
   at org.eclipse.core.launcher.Main.main(Main.java:948)
Top
 Profile  
 
emmanuel
 Post subject:
PostPosted: Thu Mar 02, 2006 12:22 am 
Hibernate Team
Hibernate Team

Joined: Sun Sep 14, 2003 3:54 am
Posts: 7256
Location: Paris, France
did you try the Hibernate Tools?

_________________
Emmanuel

Top
 Profile  
 
olobolo
 Post subject:
PostPosted: Thu Mar 02, 2006 4:49 am 
Beginner
Beginner

Joined: Mon Feb 13, 2006 8:34 pm
Posts: 27
Yes I did, but for some reasons I need to use JSR-220 now :)
Top
 Profile  
 
olobolo
 Post subject: Solution
PostPosted: Thu Mar 02, 2006 7:55 am 
Beginner
Beginner

Joined: Mon Feb 13, 2006 8:34 pm
Posts: 27
I have been working with Eclipse SDK 3.1.1 and it looks like it was the reason. I have just installed Eclipse SDK 3.1.0 and everything is fine, so far :), thx for advices...
Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  Page 1 of 1
  [ 9 posts ] 

Board index » Projects » Search, Validator, Shards

All times are UTC - 5 hours [ DST ]

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.