facebook

Minor problem with JSF Managed Bean Wizard

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #249141 Reply

    DANTEUK
    Member

    Dear MyEclipse Team,

    Sometimes I have problems with JSF Managed Bean Wizard, after creation of JSP file using graphical JSF config editor.

    To reproduce the problem:

    1. Create a WebProject

    2. Add JSF Capabilities

    3. Open JSF config file

    4. Create a JSP file into JSF config file’s graphical editor

    5. Try to create a new managed bean with wizard.

    I’ve noticed, that if I didn’t save JSF config file between step 4 & 5, the Wizard wouldn’t work. If I did, everything would work correctly.

    My configuration and log message are below:

    
    *** Date: Thu Mar 23 11:10:00 GMT 2006
    
    *** System properties:
    OS=WindowsXP
    OS version=5.1
    Java version=1.5.0_06
    
    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    
    Version: 4.1.1 GA
    Build id: 20060309-4.1.1-GA
    
    *** Eclipse details:
    Eclipse SDK
    
    Version: 3.1.2
    Build id: M20060118-1600
    
    Eclipse Platform
    
    Version: 3.1.2
    Build id: M20060118-1600
    
    Eclipse RCP
    
    Version: 3.1.2
    Build id: M20060118-1600
    
    Eclipse Java Development Tools
    
    Version: 3.1.2
    Build id: M20060118-1600
    
    Eclipse Plug-in Development Environment
    
    Version: 3.1.2
    Build id: M20060118-1600
    
    Eclipse Project SDK
    
    Version: 3.1.2
    Build id: M20060118-1600
    
    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -launcher
    C:\Work\eclipse-MyEclipse\eclipse\eclipse.exe
    -name
    Eclipse
    -showsplash
    600
    -exitdata
    bac_68
    -vm
    C:\WINDOWS\system32\javaw.exe
    

    The log messages:

    
    !SESSION 2006-03-23 10:57:53.54 ------------------------------------------------
    eclipse.buildId=M20060118-1600
    java.version=1.5.0_06
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
    Command-line arguments:  -os win32 -ws win32 -arch x86
    
    !ENTRY org.eclipse.ui 4 4 2006-03-23 10:59:50.863
    !MESSAGE Unhandled event loop exception
    
    !ENTRY org.eclipse.ui 4 0 2006-03-23 10:59:50.863
    !MESSAGE java.lang.NullPointerException
    !STACK 0
    java.lang.NullPointerException
        at com.genuitec.eclipse.jsf.wizards.WizardPageWithCodegenSupport.select(WizardPageWithCodegenSupport.java:261)
        at com.genuitec.eclipse.jsf.wizards.WizardPageWithCodegenSupport.createConfigSelectionCombos(WizardPageWithCodegenSupport.java:243)
        at com.genuitec.eclipse.jsf.wizards.WizardPageWithCodegenSupport.createControl(WizardPageWithCodegenSupport.java:279)
        at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:179)
        at com.genuitec.eclipse.jsf.wizards.JSFWizardWithCodegenSupport.createPageControls(JSFWizardWithCodegenSupport.java:43)
        at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:611)
        at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:965)
        at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1016)
        at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1013)
        at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1003)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
        at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1001)
        at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:753)
        at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:345)
        at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
        at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
        at org.eclipse.jface.window.Window.open(Window.java:787)
        at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:181)
        at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
        at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:117)
        at org.eclipse.core.commands.Command.execute(Command.java:311)
        at org.eclipse.core.commands.ParameterizedCommand.execute(ParameterizedCommand.java:396)
        at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:459)
        at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:781)
        at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:828)
        at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:550)
        at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:493)
        at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:117)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Display.filterEvent(Display.java:919)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:867)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:852)
        at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:880)
        at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:876)
        at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1190)
        at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3135)
        at org.eclipse.swt.widgets.Control.windowProc(Control.java:3038)
        at org.eclipse.swt.widgets.Display.windowProc(Display.java:3751)
        at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
        at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1656)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2756)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
        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:226)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
        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:334)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
        at org.eclipse.core.launcher.Main.run(Main.java:973)
        at org.eclipse.core.launcher.Main.main(Main.java:948)
    
    #249168 Reply

    Riyad Kalla
    Member

    Thank you for the report, we will look into this ASAP.

    #249178 Reply

    bilbek,
    I’ve reproduced the problem by copying some JSF config file and editing it with the MyEclipse editor (and filed a bug for it). Is the config file you are editing not registered in the web.xml?

    #249281 Reply

    DANTEUK
    Member

    @support-eugene wrote:

    bilbek,
    I’ve reproduced the problem by copying some JSF config file and editing it with the MyEclipse editor (and filed a bug for it). Is the config file you are editing not registered in the web.xml?

    Eugene,

    The answer is I edited the file registered in web.xml.

    I did exactly what I wrote in my first post, i.e I created a new project and edited a JSF file created by the Wizard.

    Waldemar.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Minor problem with JSF Managed Bean Wizard

You must be logged in to post in the forum log in