[JBoss JIRA] Created: (JBIDE-5839) Hibernate session factory - open - java.lang.NoSuchMethodError
by Vitali Yemialyanchyk (JIRA)
Hibernate session factory - open - java.lang.NoSuchMethodError
---------------------------------------------------------------
Key: JBIDE-5839
URL: https://jira.jboss.org/jira/browse/JBIDE-5839
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.CR2
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
1) create Seam web project with Seam 1.2 & JBoss-4.2.3.GA & BIRT Classic Models Sample Database;
2) Hibernate perspective -> Hibernate view -> open session factory for generated console config -> exception:
stacktrace:
java.lang.NoSuchMethodError: org.hibernate.cfg.ExtendedMappings.getReflectionManager()Lorg/hibernate/reflection/ReflectionManager;
at org.hibernate.search.event.FullTextIndexEventListener.initialize(FullTextIndexEventListener.java:82)
at org.hibernate.event.EventListeners$1.processListener(EventListeners.java:198)
at org.hibernate.event.EventListeners.processListeners(EventListeners.java:181)
at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:194)
at org.hibernate.cfg.Configuration.getInitializedEventListeners(Configuration.java:1352)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:549)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:98)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:544)
at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:234)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
I can't identify version of hibernate-annotations.jar which is used by the server JBoss-4.2.3.GA, it's size 444509...
Possible workaroud - is use the server JBoss-5.0.0.GA
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-5836) jst.jar not put on build-path by JBoss tools server adapter
by henk de boer (JIRA)
jst.jar not put on build-path by JBoss tools server adapter
-----------------------------------------------------------
Key: JBIDE-5836
URL: https://jira.jboss.org/jira/browse/JBIDE-5836
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR1
Environment: Mac OS X 10.5.7 / Ubuntu 9.10 (JDK 6u18) / JBoss AS 5.1
Reporter: henk de boer
Assignee: Rob Stryker
The WTP adapter provided by JBoss Tools 3.1.0.CR1 (via JBossAS Tools 2.1.0.v200912250601M-H198-CR1) fails to put the jar "jstl.jar" on the build-path for projects targeting the "JBoss Community/JBoss 5.1 Runtime".
This particular jar is located in [JBoss AS install dir]/server/default/deploy/jbossweb.sar for the default config.
The omission of this jar file on the build-path is particularly troublesome, since it contains interfaces required by the Java EE 5 specification. Many projects will likely need this jar for the definition of the "http://java.sun.com/jsp/jstl/core" URI in the core JSTL .tld. Without the jstl.jar being present, every JSP page using JSTL will be flagged as containing errors by WTP.
I tested the omission of this jar on both a large existing WTP project as well as a new project created in a new workspace. I also tested with the JBoss server adapter that's bundled with WTP and this one indeed does put jstl.jar correctly on the build-path.
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-5816) NPE -> edit Hibernate Console configuration then Open Mapping file
by Vitali Yemialyanchyk (JIRA)
NPE -> edit Hibernate Console configuration then Open Mapping file
------------------------------------------------------------------
Key: JBIDE-5816
URL: https://jira.jboss.org/jira/browse/JBIDE-5816
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.CR2
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Fix For: 3.1.0.CR2
1) create workable Hibernate core console config - with hibernate configured connection;
2) expand configuration tree;
3) edit console config -> setup configuration file - press apply, press ok;
4) try to open mapping file, as result -> npe;
stack trace:
java.lang.NullPointerException
at org.hibernate.eclipse.console.utils.OpenMappingUtils.searchInMappingFiles(OpenMappingUtils.java:452)
at org.hibernate.eclipse.console.utils.OpenMappingUtils.searchFileToOpen(OpenMappingUtils.java:619)
at org.hibernate.eclipse.console.actions.OpenMappingAction.run(OpenMappingAction.java:123)
at org.hibernate.eclipse.console.actions.OpenMappingAction.run(OpenMappingAction.java:104)
at org.hibernate.eclipse.console.actions.OpenMappingAction.run(OpenMappingAction.java:72)
at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-5792) Problems installing JBossTools-ALL-linux-gtk-x86_64-3.0.3.v200910211631N-H194-GA.zip on linux
by Francesca Ovi (JIRA)
Problems installing JBossTools-ALL-linux-gtk-x86_64-3.0.3.v200910211631N-H194-GA.zip on linux
---------------------------------------------------------------------------------------------
Key: JBIDE-5792
URL: https://jira.jboss.org/jira/browse/JBIDE-5792
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: Linux 64 bit
Reporter: Francesca Ovi
Priority: Minor
I downloaded JBossTools-ALL-linux-gtk-x86_64-3.0.3.v200910211631N-H194-GA.zip and I tried to install it on linux system.
I was unable to generate rpm files from file .spec (rpmbuild -tb ) in the section %files.
The error I get is:
"errore: Due file su di una riga: /opt/six/share/eclipse/plugins/org.mozilla.xulrunner.carbon.macosx_1.8.1.3-20070904/xulrunner/plugins/Default
errore: Il file deve iniziare con "/": Plugin.plugin"
The problem seems to be the presence of a folder named "Default Plugin.plugin" inside the "plugins\org.mozilla.xulrunner.carbon.macosx_1.8.1.3-20070904\xulrunner\plugins" folder. I suppose folder's name causes the problem. I removed this folder and the generation of rpm completed without errors.
I do not understand the necessity of such folder that seems relative to MAC OS, considering that the plugin is for linux environment.
Here is the .spec file I used:
# ---- !!!!! DO NOT EDIT THE FOLOWING CCA 20 LINES !!!!! ----
%define six_root /opt/six
%define __check_files %{nil}
Summary: Prodotto per la configurazione
Name:eclipse
Version: 3.0
Release: 1
License: xxx
Group: SIX
Source: eclipse.tgz
Buildroot: %{_tmppath}/%{name}-%{version}-%{release}
Vendor: xxx
Distribution: xxx
Packager: xxxx
AutoReqProv:No
#############################
Provides: eclipse
###### ridefinisce la macro per i diritti di default
%define inst_root %{six_root}/share
%define inst_plugin_inside %{inst_root}/pluginInsideEclipse
%define inst_plugin_outside %{inst_root}/pluginOutsideEclipse
####
%prep
%setup -c -n %{name}
%install
# crea la bulidroot se non esiste
[ ! -d %{buildroot} ] && mkdir -p %{buildroot}
# crea la dir dove fare l'installazione se non esiste
[ ! -d %{buildroot}%{inst_root} ] && mkdir -p %{buildroot}%{inst_root}
# Copio i file nella build root
for I in noarch; do
[ ! -d $I ] && continue;
/bin/cp -a $I/* %{buildroot}%{inst_root}/
done
unset I
cd %{buildroot}%{inst_root}
# Scompatto il file .tar.gz nella inst_root
for I in $(ls *.tar.gz); do
[ ! -f $I ] && continue;
gtar xzvf $I
# elimino i file. tar.gz dalla inst_root
rm -f $I
done
unset I
cd %{buildroot}%{inst_plugin_inside}
# Scompatto i file .zip nella inst_root/pluginInsideEclipse da usare per i plugins che non hanno cartella eclipse
for I in $(ls *.zip); do
[ ! -f $I ] && continue;
unzip -q -o -u $I -d %{buildroot}%{inst_root}/%{name}
done
unset I
cd %{buildroot}%{inst_plugin_outside}
# Scompatto i file .zip nella inst_root/pluginOutsideEclipse per i plugins che hanno cartella eclipse
for I in $(ls *.zip); do
[ ! -f $I ] && continue;
unzip -q -o -u $I -d %{buildroot}%{inst_root}
done
unset I
# Rimozione delle cartelle che contengono i plugin
rm -rf %{buildroot}%{inst_plugin_inside}
rm -rf %{buildroot}%{inst_plugin_outside}
# crea lista dei files
%{six_root}/bin/rpmhelper -f %{buildroot} > %{_builddir}/%{name}/%{name}.files
# Clean
%clean
[ %{buildroot} != "/" ] && rm -rf %{buildroot}
[ %{_builddir}/%{name} != "/" ] && rm -rf %{_builddir}/%{name}
rm -f %{_sourcedir}/%{name}.tgz
# definisce lista di file da istallare
%files -f %{_builddir}/%{name}/%{name}.files
%description
Istallazione ambiente eclipse e relativi plugin.
--
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, 1 month
[JBoss JIRA] Created: (JBIDE-5822) ASTestSuite.testJira (org.jboss.ide.eclipse.as.test.publishing.JBIDE4184Test.testJira(JBIDE4184Test.java:46)) throws AssertionFailedError
by Nick Boldt (JIRA)
ASTestSuite.testJira (org.jboss.ide.eclipse.as.test.publishing.JBIDE4184Test.testJira(JBIDE4184Test.java:46)) throws AssertionFailedError
-----------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-5822
URL: https://jira.jboss.org/jira/browse/JBIDE-5822
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Boldt
Stacktrace
junit.framework.AssertionFailedError
at org.jboss.ide.eclipse.as.test.publishing.JBIDE4184Test.testJira(JBIDE4184Test.java:46)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
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.test.UITestApplication.runApplication(UITestApplication.java:138)
at org.eclipse.test.UITestApplication.run(UITestApplication.java:60)
at org.eclipse.test.UITestApplication.start(UITestApplication.java:210)
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 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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
at org.eclipse.core.launcher.Main.main(Main.java:34)
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3...
Test has been failing for 4 builds.
--
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, 1 month