October 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBIDE-321) When running code generation, it sometimes goes into an endless loop (Eclipse)

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-321?page=all ] Rob Stryker updated JBIDE-321: ------------------------------ Component/s: Hibernate This is an old issue. It may need to be closed if not enough information is given but I thought I'd forward it to your box just in case. > When running code generation, it sometimes goes into an endless loop (Eclipse) > ------------------------------------------------------------------------------ > > Key: JBIDE-321 > URL: http://jira.jboss.com/jira/browse/JBIDE-321 > Project: JBoss Tools > Issue Type: Bug > Components: Hibernate > Environment: winXP, Eclipse RC6, JBoss Hibernate Plugin Beta5 > Reporter: Etienne Lacombe > Assigned To: Steve Ebersole > > When I start the code generation, it sometimes just hang and never finishes. The CPU goes to 100% usage on the java process and I have to kill Eclipse. > The progress indicator is "launching ..." and stays at 50%. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-293) Improper attribute name in xdoclet-build.xml in utilobject tag (parameter kind)

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-293?page=all ] Rob Stryker closed JBIDE-293. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues Old versions of JBoss IDE are no longer supported. If this issue was closed in error, please re-open. > Improper attribute name in xdoclet-build.xml in utilobject tag (parameter kind) > ------------------------------------------------------------------------------- > > Key: JBIDE-293 > URL: http://jira.jboss.com/jira/browse/JBIDE-293 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5.1 > Environment: WinXP Professional, Java 1.5 > Reporter: Piotr Kochanski > Priority: Minor > > When you add in the XDoclet configuration for utilobject "kind" attribute, then generated (and used) build file contains > <utilobject Kind="physical" includeGUID="true" cacheHomes="true" > > the problem is "Kind" instead of "kind", and value of this attribute is ignored -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-334) JBossIDE 2.0 Art Tasks

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-334?page=all ] Rob Stryker closed JBIDE-334. ----------------------------- Resolution: Done All sub-tasks have been done > JBossIDE 2.0 Art Tasks > ---------------------- > > Key: JBIDE-334 > URL: http://jira.jboss.com/jira/browse/JBIDE-334 > Project: JBoss Tools > Issue Type: Task > Reporter: Marshall Culpepper > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-333) Create a new JBossIDE logo

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-333?page=all ] Rob Stryker closed JBIDE-333. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > Create a new JBossIDE logo > -------------------------- > > Key: JBIDE-333 > URL: http://jira.jboss.com/jira/browse/JBIDE-333 > Project: JBoss Tools > Issue Type: Feature Request > Reporter: Marshall Culpepper > Assigned To: James Cobb > Attachments: old-jbosside-logo.jpg > > > a new JBossIDE logo that more closely matches our color scheme/font would be awesome.. our current logo is attached as a screenshot -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-291) Cannot assign key combination to packaging inside project,

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-291?page=all ] Rob Stryker closed JBIDE-291. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > Cannot assign key combination to packaging inside project, > ---------------------------------------------------------- > > Key: JBIDE-291 > URL: http://jira.jboss.com/jira/browse/JBIDE-291 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5.1 > Environment: Jboss IDE 1.5.1GA + WTP 1.0.0 Eclipse 3.2 + JBoss 4.0.4 > Reporter: Grigoras Cristinel > Priority: Minor > > Hi all, > In old version of plugin, the packaging action was active in Package Explorer anyware, > (example: select the ear file , and pres Ctrl-Shift+F2, file was rebuild, and after press Ctrl-Shift+F1 and deployed. ). > Now the packaging command is enabled only on the project name. How i can change that ? > I have tried old key configuration (key active in window+dialog, or java file) and no chance. > Is very hard to find in project explorer the project name, and after search for ear name to make deploy, when you have 200 files... > Secondo, Why not exist the posibility to create a default deploy configuration for a project. > Select some files, deploy them , and after when you press a key combination to redeploy that file group, in current project. > Thanks, > Cristi -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-319) JBoss IDE 1.6 download bundle for linux is for 32 bit processors (fails on AMD64)

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-319?page=all ] Rob Stryker closed JBIDE-319. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues Old versions of JBoss IDE are no longer supported. If this issue was closed in error, please re-open. > JBoss IDE 1.6 download bundle for linux is for 32 bit processors (fails on AMD64) > --------------------------------------------------------------------------------- > > Key: JBIDE-319 > URL: http://jira.jboss.com/jira/browse/JBIDE-319 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.6 > Environment: Linux Amd Athlon 64 > Reporter: Andrew Redhead > Priority: Minor > > The version of Eclipse shipped with the full JBoss IDE download bundle for linux is only suitable for 32 bit processors. > There is a 64 bit version of Eclipse for linux, so it might be nice to have a 64 bit bundle as well - failing that then a note on the download page saying 32bit only would be handy. > A workaround is to install the the 64 bit version of eclipse and then install just the jboss ide tools... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-181) Can't configure debug JBoss server

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-181?page=all ] Rob Stryker closed JBIDE-181. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > Can't configure debug JBoss server > ---------------------------------- > > Key: JBIDE-181 > URL: http://jira.jboss.com/jira/browse/JBIDE-181 > Project: JBoss Tools > Issue Type: Bug > Environment: Win XP, jdk-1_5_0_03 (but also tried 1.4_2_08), Eclipse 3.1M6 (also tried Eclipse 3.1M7), JBoss 4 (also tried JBoss 3) > Reporter: j s > > I select Run->Debug and can see the four different types of JBoss servers in the left-hand column (JBoss 2.4.x, JBoss 3.0.x, JBoss 3.2.x, JBoss 4.0.x). > I set up a new configuration under JBoss 4.0 ok. I go back to the normal window and then go to Window->Preferences->JBoss-IDE->Launcher and select the Server I have just configured. I then go back to the main window and then to Default Server->Start Server but the option is greyed out. > When I restart Eclipse, the 'Start Server' option is no longer greyed out - i can press it but it comes up with: "The chosen operation is not enabled." and then it goes grey. > When I go back to check the configuration under "Run->Debug" I get - "An error has occurred. See error log for more details." The Error Log has the following in it -- > Error 2005-05-24 16:13:27.749 Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.NullPointerException > at org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.updateServerConfigurations(HomeTab.java:328) > at org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.access$1(HomeTab.java:311) > at org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab$1.modifyText(HomeTab.java:138) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:187) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:866) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:847) > at org.eclipse.swt.widgets.Text.wmCommandChild(Text.java:2019) > at org.eclipse.swt.widgets.Control.WM_COMMAND(Control.java:3155) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:3032) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:3466) > at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) > at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1549) > at org.eclipse.swt.widgets.Text.callWindowProc(Text.java:127) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:3114) > at org.eclipse.swt.widgets.Text.windowProc(Text.java:1742) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:3466) > at org.eclipse.swt.internal.win32.OS.SetWindowTextW(Native Method) > at org.eclipse.swt.internal.win32.OS.SetWindowText(OS.java:2315) > at org.eclipse.swt.widgets.Text.setText(Text.java:1562) > at org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.updateHomedirFromConfig(HomeTab.java:286) > at org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.initializeFrom(HomeTab.java:219) > at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:86) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:538) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$5.run(LaunchConfigurationTabGroupViewer.java:471) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:488) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:452) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:788) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:600) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:680) > at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1021) > at org.eclipse.core.runtime.Platform.run(Platform.java:757) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:40) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:678) > at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:949) > at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:969) > at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:231) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:226) > at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:392) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:118) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2871) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2530) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:803) > at org.eclipse.jface.window.Window.open(Window.java:781) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:438) > at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:356) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:360) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:302) > at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:80) > at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:99) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246) > at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:220) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2894) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2527) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1570) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1534) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:306) > 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:228) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:156) > 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:315) > at org.eclipse.core.launcher.Main.basicRun(Main.java:268) > at org.eclipse.core.launcher.Main.run(Main.java:942) > at org.eclipse.core.launcher.Main.main(Main.java:926) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-228) java.lang.reflect.InvocationTargetException on project configuration

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-228?page=all ] Rob Stryker closed JBIDE-228. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues JBIDE 1.5 no longer supported > java.lang.reflect.InvocationTargetException on project configuration > -------------------------------------------------------------------- > > Key: JBIDE-228 > URL: http://jira.jboss.com/jira/browse/JBIDE-228 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 2 > Environment: WIN32 - XP, i386 > Reporter: Johann Evans > > When I try to edit the project properties or simply switch to the XDoclet or Packaging nodes and then try to save by pressing OK, Eclipse reports a java.lang.reflect.InvocationTargetException exception. > On Linux this did not happen however, but when I moved this project onto Linux with the JBoss-IDE 1.5.M2, it updated the config files and worked fine, now when I move it back to Win32 environment, it is throwing this exception as per above... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-289) Produce an install package not bundled with the wtp plugins

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-289?page=all ] Rob Stryker closed JBIDE-289. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > Produce an install package not bundled with the wtp plugins > ----------------------------------------------------------- > > Key: JBIDE-289 > URL: http://jira.jboss.com/jira/browse/JBIDE-289 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Final > Reporter: Gabriele Garuglieri > Priority: Minor > > Jboss ide package is bundled with required wtp plugins, but if you already have in eclipse a full wtp installation equal or newer than that jbide was released for, you have to strip away wtp plugins from jboss ide package before installing it, to avoid duplicate or conflicting plugins. > It would be nice to have a released package without bundled wtp plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-271) Missing service-point task in @ejb xdoclet

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-271?page=all ] Rob Stryker closed JBIDE-271. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > Missing service-point task in @ejb xdoclet > ------------------------------------------ > > Key: JBIDE-271 > URL: http://jira.jboss.com/jira/browse/JBIDE-271 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Final > Environment: Windows XP and 2K sp 2, Eclipse 3.1, JBOSS IDE 1.5 > Reporter: Emile > Attachments: screenshot-1.jpg > > > It is not possibe to specify the service-point task for @ejb xdoclet in the Xdoclet configuration of a java project properties. > In my case, the workaround that I used was to create manually the service-point task in th xdoclet-build.xml file that is created automatically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

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 October 2007