Add Managed Bean From Config Editor [message #474951] |
Tue, 31 July 2007 08:39 |
Eclipse User |
|
|
|
Originally posted by: gurkanerdogdu.yahoo.com
Hi;
When I want to add written managed bean from JSF config editor, I get the
following exception when I hit the Next button;
Scenario:
I used the option "Using an existing Java Class" and browse my class and
hit the Next button;
Exception : Unhandled Event Loop Exception
java.lang.ClassCastException:
org.eclipse.jst.j2ee.webapplication.internal.impl.WebAppReso urceImpl
at
org.eclipse.jst.jee.model.internal.Web25ModelProvider.getMod elObject(Web25ModelProvider.java:35)
at
org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getMode lObject(JEE5ModelProvider.java:113)
at
org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigUtils.getC onfigFilesFromContextParam(JSFAppConfigUtils.java:220)
at
org.eclipse.jst.jsf.core.jsfappconfig.ContextParamSpecifiedJ SFAppConfigLocater.getFilenames(ContextParamSpecifiedJSFAppC onfigLocater.java:154)
at
org.eclipse.jst.jsf.core.jsfappconfig.WebContentRelativeJSFA ppConfigLocater.locateProviders(WebContentRelativeJSFAppConf igLocater.java:45)
at
org.eclipse.jst.jsf.core.jsfappconfig.ContextParamSpecifiedJ SFAppConfigLocater.startLocating(ContextParamSpecifiedJSFApp ConfigLocater.java:47)
at
org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager.st artConfigLocaters(JSFAppConfigManager.java:240)
at
org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager.in itialize(JSFAppConfigManager.java:201)
at
org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager.<init >(JSFAppConfigManager.java:170)
at
org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager.ge tInstance(JSFAppConfigManager.java:102)
at
org.eclipse.jst.jsf.facesconfig.ui.util.ManagedBeanUtil.isBe anDuplicate(ManagedBeanUtil.java:41)
at
org.eclipse.jst.jsf.facesconfig.ui.util.ManagedBeanUtil.getD efaultManagedBeanName(ManagedBeanUtil.java:81)
at
org.eclipse.jst.jsf.facesconfig.ui.wizard.ManagedBeanPropert yPage.initialize(ManagedBeanPropertyPage.java:244)
at
org.eclipse.jst.jsf.facesconfig.ui.wizard.ManagedBeanPropert yPage.setPreviousPage(ManagedBeanPropertyPage.java:217)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog. java:1112)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDial og.java:820)
at
org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.jav a:616)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:227)
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.ja va:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3293)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.jst.jsf.facesconfig.ui.section.ManagedBeanMaster Section.addButtonSelected(ManagedBeanMasterSection.java:123)
at
org.eclipse.jst.jsf.facesconfig.ui.section.FacesConfigMaster Section$1.widgetSelected(FacesConfigMasterSection.java:150)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:227)
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.ja va:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
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(Work bench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.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(EclipseS tarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:176)
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.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)
|
|
|
|
Re: Add Managed Bean From Config Editor [message #474954 is a reply to message #474952] |
Wed, 01 August 2007 06:52 |
Eclipse User |
|
|
|
Originally posted by: gurkanerdogdu.yahoo.com
Hi Jessler;
I have created the project using Dynamic Web Project with JSF Facet
"1.2". But I did not select the JSF implementation library used in the
project, just selected check box "Server Supplied JSF Implementation", and
adding some component libraries.
In fact the problem(exception) also appears when using the other choice
of managed bean creation; ie "Create a new Java Class" option.
I am using the Eclipse JEE Europa.
But if I added the managed bean descriptions into the faces-config.xml
"Source" tab by hand written, then these beans appeared in "ManagedBean"
tag; but this is very time consuming as you created this editor for easy
manage configuration;
Your help is very appreciated, otherwise I will abondon the use of plugin
and swtich to another options.
Thanks for advance;
Gurkan
|
|
|
|
|
Re: Add Managed Bean From Config Editor [message #613260 is a reply to message #474952] |
Wed, 01 August 2007 06:52 |
Eclipse User |
|
|
|
Originally posted by: gurkanerdogdu.yahoo.com
Hi Jessler;
I have created the project using Dynamic Web Project with JSF Facet
"1.2". But I did not select the JSF implementation library used in the
project, just selected check box "Server Supplied JSF Implementation", and
adding some component libraries.
In fact the problem(exception) also appears when using the other choice
of managed bean creation; ie "Create a new Java Class" option.
I am using the Eclipse JEE Europa.
But if I added the managed bean descriptions into the faces-config.xml
"Source" tab by hand written, then these beans appeared in "ManagedBean"
tag; but this is very time consuming as you created this editor for easy
manage configuration;
Your help is very appreciated, otherwise I will abondon the use of plugin
and swtich to another options.
Thanks for advance;
Gurkan
|
|
|
|
Powered by
FUDForum. Page generated in 0.03534 seconds