July 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBIDE-538) first time open of visual editor is slooow

by Sergey Vasilyev (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-538?page=comments#action_12369702 ] Sergey Vasilyev commented on JBIDE-538: --------------------------------------- Work on this task will be started after replacing mozilla with xulrunner. > first time open of visual editor is slooow > ------------------------------------------ > > Key: JBIDE-538 > URL: http://jira.jboss.com/jira/browse/JBIDE-538 > Project: JBoss Tools > Issue Type: Feature Request > Components: integration > Affects Versions: ExadelStudioPro4 > Reporter: Max Andersen > Assigned To: Sergey Vasilyev > Priority: Critical > > First time a visual editor is opened Eclipse freezes and in the worst case it turns all white. > I assume this is because of the first start of the mozilla engine. > We should investigate if it wouldn't be possible to start this in the background; showing a "Starting visual editor...." in the visual part of the editor until it is ready. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-541) web.xml editor and others does not work unless inside WTP project

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-541?page=comments#action_12369682 ] Max Andersen commented on JBIDE-541: ------------------------------------ sounds good - good ui's are all about "downgrading gracefully" if certain information is not available. > web.xml editor and others does not work unless inside WTP project > ----------------------------------------------------------------- > > Key: JBIDE-541 > URL: http://jira.jboss.com/jira/browse/JBIDE-541 > Project: JBoss Tools > Issue Type: Task > Components: integration > Reporter: Max Andersen > Assigned To: Viacheslav Kabanovich > > web.xml editing is not avaialbe without WTP project; which is prominent for seam-gen'ed projects. > xhtml seem to be ok; same with faces-config.xml. -- 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

18 years, 8 months

1
0
0 / 0

XDoclet broken with JBoss 4.2.1GA, Eclipse 3.3 and JBoss IDE plugin 1.6.0GA

by Mark Jeghers

All, Using JBoss 4.2.1GA, Eclipse 3.3, and the JBoss Eclipse IDE plugin 1.6.0.GA, I have tried to follow the tutorial example, making a Fibo calculating session bean. I have XDoclet 1.2.3 and have pointed Eclipse to it in the Window->Preferences->XDoclet config screen. But no matter what I do (including re-installing various ways) when I get to the XDoclet-related steps (chap 5), I get runtime errors and the XDoclet config page in the properties dialog is missing most of it's data entry components. A dialog says "The currently displayed page contains invalid values." The log attached below shows several exceptions that occurred. Something is broken and I am stuck since XDoclet is central to getting the code to run. Plz advise and thanx in advance, /Mark !SESSION 2007-07-22 14:54:30.156 ----------------------------------------------- eclipse.buildId=I20070625-1500 java.version=1.5.0_12 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.ui 4 4 2007-07-22 15:24:52.718 !MESSAGE Could not create action delegate for id: org.eclipse.jst.j2ee.ejb.annotations.internal.xdoclet.action.RunXDocletAction !ENTRY org.eclipse.ui 4 4 2007-07-22 15:24:52.734 !MESSAGE Internal plug-in action delegate error on creation. !STACK 0 java.lang.NullPointerException at org.eclipse.jem.workbench.utility.JemProjectUtilities.getJavaProject(JemProjectUtilities.java:201) at org.eclipse.jst.j2ee.internal.project.J2EEProjectUtilities.getSourcePathOrFirst(J2EEProjectUtilities.java:435) at org.eclipse.jst.j2ee.internal.project.J2EEProjectUtilities.getSourceFolderOrFirst(J2EEProjectUtilities.java:396) at org.eclipse.jst.j2ee.ejb.annotations.internal.xdoclet.action.XDocletActionDelegate.getFirstSourceFile(XDocletActionDelegate.java:70) at org.eclipse.jst.j2ee.ejb.annotations.internal.xdoclet.action.RunXDocletAction.selectionChanged(RunXDocletAction.java:60) at org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:211) at org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:126) at org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:280) at org.eclipse.ui.internal.PluginAction.(PluginAction.java:112) at org.eclipse.ui.internal.ObjectPluginAction.(ObjectPluginAction.java:51) at org.eclipse.ui.internal.ActionDescriptor.createAction(ActionDescriptor.java:266) at org.eclipse.ui.internal.ActionDescriptor.(ActionDescriptor.java:170) at org.eclipse.ui.internal.ActionDescriptor.(ActionDescriptor.java:100) at org.eclipse.ui.internal.ObjectActionContributor.createActionDescriptor(ObjectActionContributor.java:200) at org.eclipse.ui.internal.PluginActionBuilder.readElement(PluginActionBuilder.java:158) at org.eclipse.ui.internal.ObjectActionContributor.readElement(ObjectActionContributor.java:279) at org.eclipse.ui.internal.registry.RegistryReader.readElements(RegistryReader.java:138) at org.eclipse.ui.internal.registry.RegistryReader.readElementChildren(RegistryReader.java:127) at org.eclipse.ui.internal.ObjectActionContributor.readConfigElement(ObjectActionContributor.java:250) at org.eclipse.ui.internal.ObjectActionContributor.isApplicableTo(ObjectActionContributor.java:216) at org.eclipse.ui.internal.ObjectContributorManager.isApplicableTo(ObjectContributorManager.java:294) at org.eclipse.ui.internal.ObjectActionContributorManager.contributeObjectActions(ObjectActionContributorManager.java:82) at org.eclipse.ui.internal.PopupMenuExtender.addObjectActions(PopupMenuExtender.java:261) at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:337) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:290) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:395) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:391) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:417) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943) at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:3981) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3698) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:291) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1584) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1753) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351) at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:228) at org.eclipse.swt.widgets.Display.runPopups(Display.java:3708) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3287) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) !ENTRY org.eclipse.jface 4 2 2007-07-22 15:26:28.171 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/ui/viewsupport/ListContentProvider at org.jboss.ide.eclipse.xdoclet.run.ui.ConfigurationListViewer.(ConfigurationListViewer.java:115) at org.jboss.ide.eclipse.xdoclet.run.ui.properties.ConfigurationPropertyPage.createContents(ConfigurationPropertyPage.java:329) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1456) at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1213) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:857) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:193) at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1207) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:433) at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:698) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:842) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:857) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:193) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:840) at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1153) at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1178) at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:250) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:244) at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:418) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:156) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169)

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-583) setHiden is misspelled

by Max Andersen (JIRA)

setHiden is misspelled ---------------------- Key: JBIDE-583 URL: http://jira.jboss.com/jira/browse/JBIDE-583 Project: JBoss Tools Issue Type: Bug Components: Hibernate Reporter: Max Andersen Assigned To: Mikle Dryakhlenkov setHiden should be setHidden -- 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

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Resolved: (JBIDE-541) web.xml editor and others does not work unless inside WTP project

by Viacheslav Kabanovich (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-541?page=all ] Viacheslav Kabanovich resolved JBIDE-541. ----------------------------------------- Resolution: Done UI tabs for Red Hat xml editors are made accessible even if required natures are missing. Most of their functionality will work. However, without wtp, Faces Config editor may not be able to find references to pages, so user will be prompted to add jsfnature. > web.xml editor and others does not work unless inside WTP project > ----------------------------------------------------------------- > > Key: JBIDE-541 > URL: http://jira.jboss.com/jira/browse/JBIDE-541 > Project: JBoss Tools > Issue Type: Task > Components: integration > Reporter: Max Andersen > Assigned To: Viacheslav Kabanovich > > web.xml editing is not avaialbe without WTP project; which is prominent for seam-gen'ed projects. > xhtml seem to be ok; same with faces-config.xml. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-567) Fileds color in Create new Struts/JSF project

by Viacheslav Kabanovich (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-567?page=all ] Viacheslav Kabanovich resolved JBIDE-567. ----------------------------------------- Resolution: Done > Fileds color in Create new Struts/JSF project > --------------------------------------------- > > Key: JBIDE-567 > URL: http://jira.jboss.com/jira/browse/JBIDE-567 > Project: JBoss Tools > Issue Type: Bug > Components: JSF > Affects Versions: ExadelStudioPro4 > Environment: WindowsXP SP2 > rhds-win32-1.0.0.alpha.jar > Red Hat Developer Studio > Version: 1.0.0 > Build: build 20070702-nightly > Reporter: Aliaksey Nis > Assigned To: Viacheslav Kabanovich > Priority: Trivial > Attachments: CreateWizard.JPG > > > Create new Struts or JSF project from Web Projects View > Some fields colored in background color - this usually used when this fields are unchangeable. > Needed to change field color back to white. > Look at screenshot for more info. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-579) seam components without scope shows up as a UNSPECIFIED instead of using default scope assignment

by Max Andersen (JIRA)

seam components without scope shows up as a UNSPECIFIED instead of using default scope assignment ------------------------------------------------------------------------------------------------- Key: JBIDE-579 URL: http://jira.jboss.com/jira/browse/JBIDE-579 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen If I add @Name("test") public class Test { } it shows up in UNSPECIFIED category instead of following the rules for default scope. See org.jboss.seam.ComponentType.getDefaultScope() for the rules -- 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

18 years, 8 months

4
4
0 / 0

[JBoss JIRA] Commented: (JBIDE-546) Content Assist for JSP in jsf 1.1 is shown hints for jsf 1.2

by Alexey Kazakov (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-546?page=comments#action_12369409 ] Alexey Kazakov commented on JBIDE-546: -------------------------------------- This bug reproduced only in facelets XHTML pages. JSP works fine. It's known old bug of Exadel Studio. If namespace version is not specified in XHTML then CA uses the last version that is available in Knowledgebase. But we should check version of tld which project has. > Content Assist for JSP in jsf 1.1 is shown hints for jsf 1.2 > ------------------------------------------------------------ > > Key: JBIDE-546 > URL: http://jira.jboss.com/jira/browse/JBIDE-546 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Reporter: Anton Klimkovich > Assigned To: Alexey Kazakov > Attachments: screenshort1.jpg > > > 1. Project on jsf 1.1 > 2. Content Assist for JSP in jsf 1.1 with facelets project is shown hints for jsf 1.2. See screenshot 1: footerClass and headerClass attributes for h:column is not from jsf 1.1, but from jsf 1.2 -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-513) code assist for action attribute

by Alexey Kazakov (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-513?page=all ] Alexey Kazakov resolved JBIDE-513. ---------------------------------- Resolution: Done > code assist for action attribute > -------------------------------- > > Key: JBIDE-513 > URL: http://jira.jboss.com/jira/browse/JBIDE-513 > Project: JBoss Tools > Issue Type: Feature Request > Components: Seam > Reporter: Carsten H?hne > Assigned To: Alexey Kazakov > Priority: Critical > > So now it is in the jira:-) > I am missing code assist for action. > code assist for propertys work well. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-557) Xmodel classloading should "obey" osgi classloading

by Viacheslav Kabanovich (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-557?page=all ] Viacheslav Kabanovich resolved JBIDE-557. ----------------------------------------- Resolution: Done This is already fixed by means of extension point org.jboss.tools.common.model.classes, and ModelFeatureFactory that created instance of model class by id using createExecutableExtension method. No cache for loaded classes is used now. > Xmodel classloading should "obey" osgi classloading > --------------------------------------------------- > > Key: JBIDE-557 > URL: http://jira.jboss.com/jira/browse/JBIDE-557 > Project: JBoss Tools > Issue Type: Task > Reporter: Max Andersen > Assigned To: Viacheslav Kabanovich > > currently xmodel keeps a global cache of classes in ClassLoaderUtil and has a hidden binding to other plugins. > e..g it refers to jsf.web.ui via strings. That is a bad coupling; should be the other way around. -- 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

18 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2007