[JBoss JIRA] (JBIDE-15174) Improved work with datatools connection profiles for various projects using hibernate/jpa
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15174?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-15174:
----------------------------------
Assignee: Koen Aers
> Improved work with datatools connection profiles for various projects using hibernate/jpa
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-15174
> URL: https://issues.jboss.org/browse/JBIDE-15174
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.1.0.Beta2
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.5.0.AM1
>
>
> When working with JPA projects or examples from Central it's necessary to create JPA connection profile. I assume I already have some kind of configuration - either hibernate configuration, or connection directly defined in persistence.xml or defined data source. Still hibernate tooling and eclipse.datatools is complaining that it needs to define connection profile. You have to create a connection configuration again for connection profile to have working tooling. It leads to multiple configurations or you have to reconfigure a project to use eclipse.datatools connection profiles.
> What I would like to see is some mechanism howto easily create connection profiles:
> * the seamless way would be some support for our examples to generate connection profiles when they are imported (or at least to help with that)
> * and some support for hibernate configuration, persistence.xml and ds when creating connection profiles.
> Both features might need some eclipse.datatools contributions. But currently these two worlds (hibernate/jpa tooling and datatools are not very well integrated each other).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (JBIDE-15174) Improved work with datatools connection profiles for various projects using hibernate/jpa
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15174?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-15174:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.3.x)
> Improved work with datatools connection profiles for various projects using hibernate/jpa
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-15174
> URL: https://issues.jboss.org/browse/JBIDE-15174
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.1.0.Beta2
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.5.0.AM1
>
>
> When working with JPA projects or examples from Central it's necessary to create JPA connection profile. I assume I already have some kind of configuration - either hibernate configuration, or connection directly defined in persistence.xml or defined data source. Still hibernate tooling and eclipse.datatools is complaining that it needs to define connection profile. You have to create a connection configuration again for connection profile to have working tooling. It leads to multiple configurations or you have to reconfigure a project to use eclipse.datatools connection profiles.
> What I would like to see is some mechanism howto easily create connection profiles:
> * the seamless way would be some support for our examples to generate connection profiles when they are imported (or at least to help with that)
> * and some support for hibernate configuration, persistence.xml and ds when creating connection profiles.
> Both features might need some eclipse.datatools contributions. But currently these two worlds (hibernate/jpa tooling and datatools are not very well integrated each other).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (JBIDE-14632) Explorer: "could not store password" logged whenever right clicking user/navigating tree
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14632?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-14632:
-------------------------------
Fix Version/s: LATER
(was: 4.4.x)
> Explorer: "could not store password" logged whenever right clicking user/navigating tree
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-14632
> URL: https://issues.jboss.org/browse/JBIDE-14632
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Max Rydahl Andersen
> Priority: Minor
> Labels: explorer, openshift_v2
> Fix For: LATER
>
>
> created connection.
> get bunch of these stacktraces - especially when right clicking on the node.
> {code}
> org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStoreException: Could not store password
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.storeInPreferences(SecurePasswordStore.java:102)
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.update(SecurePasswordStore.java:56)
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.setPassword(SecurePasswordStore.java:50)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.saveOrClearPassword(Connection.java:441)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.save(Connection.java:430)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:196)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.getDefaultDomain(Connection.java:332)
> at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction.validate(DeleteDomainAction.java:47)
> at org.jboss.tools.openshift.express.internal.ui.explorer.actionProvider.AbstractOpenShiftExplorerViewerActionProvider.fillContextMenu(AbstractOpenShiftExplorerViewerActionProvider.java:50)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:221)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:216)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:173)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:260)
> at org.eclipse.ui.navigator.CommonNavigatorManager$4.menuAboutToShow(CommonNavigatorManager.java:275)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:343)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:475)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:470)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:500)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4164)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:806)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5606)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:278)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4087)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3642)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> Caused by: org.eclipse.equinox.security.storage.StorageException: No password provided.
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferences.put(SecurePreferences.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put(SecurePreferencesWrapper.java:110)
> at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.storeInPreferences(SecurePasswordStore.java:99)
> ... 52 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-13799:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.2.x)
> Source Lookup enhancements
> --------------------------
>
> Key: JBIDE-13799
> URL: https://issues.jboss.org/browse/JBIDE-13799
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.5.0.AM1
>
>
> The PR includes the following enhancements:
> - AS 7.2/EAP 6.1 are now recognized correctly
> - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
> - the fix for the ConcurrentModificationException exception
> - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
> - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
> - JBoss Java Project Source Container
> See http://screencast.com/t/39LHqYx5m
> Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
> Note:
> You have to have some deployment on the servers in order the WeldBootstrap class to be created.
> You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
> The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-13799:
----------------------------------
Assignee: Fred Bricon (was: Snjezana Peco)
> Source Lookup enhancements
> --------------------------
>
> Key: JBIDE-13799
> URL: https://issues.jboss.org/browse/JBIDE-13799
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.5.0.AM1
>
>
> The PR includes the following enhancements:
> - AS 7.2/EAP 6.1 are now recognized correctly
> - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
> - the fix for the ConcurrentModificationException exception
> - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
> - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
> - JBoss Java Project Source Container
> See http://screencast.com/t/39LHqYx5m
> Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
> Note:
> You have to have some deployment on the servers in order the WeldBootstrap class to be created.
> You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
> The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months