April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19743) Execution of criteria query shows <null> result

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-19743: ------------------------------------ Summary: Execution of criteria query shows <null> result Key: JBIDE-19743 URL: https://issues.jboss.org/browse/JBIDE-19743 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.3.0.Beta1 Environment: JBDS 9.0.0.Beta1 - nightly 20150430, L64 Reporter: Jiri Peterka Priority: Blocker Fix For: 4.3.0.Beta1 There is null result after executing Criteria query: {code} !ENTRY org.jboss.tools.hibernate.runtime.common 4 0 2015-04-30 15:16:16.562 !MESSAGE org.hibernate.impl.CriteriaImpl.setMaxResults() !STACK 0 java.lang.NoSuchMethodException: org.hibernate.impl.CriteriaImpl.setMaxResults() at java.lang.Class.getMethod(Class.java:1773) at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:39) at org.jboss.tools.hibernate.runtime.common.AbstractCriteriaFacade.list(AbstractCriteriaFacade.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at bsh.Reflect.invokeMethod(Unknown Source) at bsh.Reflect.invokeObjectMethod(Unknown Source) at bsh.BSHPrimarySuffix.doName(Unknown Source) at bsh.BSHPrimarySuffix.doSuffix(Unknown Source) at bsh.BSHPrimaryExpression.eval(Unknown Source) at bsh.BSHPrimaryExpression.eval(Unknown Source) at bsh.Interpreter.eval(Unknown Source) at bsh.Interpreter.eval(Unknown Source) at bsh.Interpreter.eval(Unknown Source) at org.hibernate.eclipse.console.common.JavaPage.setSession(JavaPage.java:73) at org.hibernate.eclipse.console.common.HibernateExtension$3.execute(HibernateExtension.java:127) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189) at org.hibernate.eclipse.console.common.HibernateExtension.executeCriteriaQuery(HibernateExtension.java:123) at org.hibernate.console.ConsoleConfiguration.executeBSHQuery(ConsoleConfiguration.java:313) at org.hibernate.eclipse.criteriaeditor.CriteriaEditor.executeQuery(CriteriaEditor.java:142) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:82) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1346) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1331) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1116) at org.jboss.reddeer.core.handler.WidgetHandler$4.run(WidgetHandler.java:332) at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:193) at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1) at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:159) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3790) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19697: ---------------------------------------- The preference in oomph are probably not stored in the regular preference format, so looking for the file may not be enough. There are 2 parts of Oomph: recording and storing preferences, and applying them to a new instance. Disabling the preference recorder only covers the first part. I don't know whether the part about restoring preferences can be controlled. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Attachments: preference-recorder.png > > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3431: --------------------------------- I can't view the minutes yet (and no sound on BlueJeans) so just confirming, [~mmusaji]: * I'm adding 6.4 to the list of 6.x versions of EAP supported for JBDS 8.0 and 8.1 under "Platforms & Runtime Servers" here: https://access.redhat.com/articles/427493 Was there any other requirement for this issue? > Update JBDS support matrix to include only major version of EAP > --------------------------------------------------------------- > > Key: JBDS-3431 > URL: https://issues.jboss.org/browse/JBDS-3431 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 8.1.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Update this page https://access.redhat.com/articles/427493 > So that we only include the major versions of EAP supported > I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19463: --------------------------------------- I just came across this today when testing EAP 6.4 - this was JBDS 8.1. But just wanted to let you know that it's still relevant ;) > Cannot connect to remote server in JMX Navigator > ------------------------------------------------ > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19463: ---------------------------------- Fix Version/s: 4.3.0.Beta1 > Cannot connect to remote server in JMX Navigator > ------------------------------------------------ > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-3431: ------------------------------------ Summary: Update JBDS support matrix to include only major version of EAP Key: JBDS-3431 URL: https://issues.jboss.org/browse/JBDS-3431 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation Affects Versions: 8.1.0.GA Reporter: Mustafa Musaji Assignee: Misha Ali Update this page https://access.redhat.com/articles/427493 So that we only include the major versions of EAP supported I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work with remote server docs missing

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-620: ------------------------------------ ACK, thank you, Max. > How to work with remote server docs missing > ------------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19742) Change color of B in batch Icon

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-19742: ----------------------------------- Summary: Change color of B in batch Icon Key: JBIDE-19742 URL: https://issues.jboss.org/browse/JBIDE-19742 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: batch Affects Versions: 4.3.0.Alpha2 Reporter: Fred Bricon Priority: Minor My brains keeps processing the red B of !https://raw.githubusercontent.com/jbosstools/jbosstools-javaee/03d08a6ffea565dca1207dc37d8ff1d213f4ab28/batch/plugins/org.jboss.tools.batch.ui/images/batch_icon16.png! as an error marker every time I see it. Could we please use another color? Blue or dark Green, nothing too bright. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18782) Usage: Too long wizard names look ugly in usage stats

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18782?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18782. ------------------------------ Verified in JBDS 9.0.0.Alpha2. Closing. > Usage: Too long wizard names look ugly in usage stats > ----------------------------------------------------- > > Key: JBIDE-18782 > URL: https://issues.jboss.org/browse/JBIDE-18782 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.2.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > We track wizard IDs used in JBDS/JBT but some IDs can be too long (because of obfuscation or other reasons). > Let's make such labels shorter so they won't make the GA page look ugly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOCUS-35) Add jboss-dmr 1.2.2.Final to locus

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/LOCUS-35?page=com.atlassian.jira.plugin.s... ] Fred Bricon commented on LOCUS-35: ---------------------------------- So I tested 1.3 and it worked. I suggest with use it instead of 1.2.2 > Add jboss-dmr 1.2.2.Final to locus > ---------------------------------- > > Key: LOCUS-35 > URL: https://issues.jboss.org/browse/LOCUS-35 > Project: JBoss Tools Locus > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 1.2.0 > > > We need to have provide jboss-dmr 1.2.2.Final as part of locus http://search.maven.org/#artifactdetails%7Corg.jboss%7Cjboss-dmr%7C1.2.2.... > {noformat}<dependency> > <groupId>org.jboss</groupId> > <artifactId>jboss-dmr</artifactId> > <version>1.2.2.Final</version> > </dependency>{noformat} > This will be consumed by foundation, server, central and probably other components -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015