facebook

Creating J2EE Project – J2EE Library Missing

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #198214 Reply

    Hi,

    I initially had this on versin 2.6 and then went back to 2.5.1 and it also happened.

    java.version=1.4.1_02
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Eclipse:Version: 2.1.1
    Build id: 200306271545
    Clean install of eclipse (only used to evaluate MyEclipse).
    MyEclipseIde:2.5.1

    I am compiling a large project (>4000 classes, > 1300 JSP). At some point during adding libraries the J2EE 1.3 Container library becomes lost. Once that happens I am not able to create a new J2EE/EJB/Web project.

    To fix this, I have to edit the MyEclipse preferences and hit a few of the entries (not sure which ones). The last exception in the log files is as follows:
    !ENTRY org.eclipse.core.runtime 4 2 Sep 01, 2003 09:32:13.657
    !MESSAGE Plug-in “com.genuitec.eclipse.j2eedt.core” was unable to instantiate class “com.genuitec.eclipse.j2eedt.ui.wizard.NewEARProjectWizard”.
    !STACK 0
    java.lang.NullPointerException
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewJ2EEProjectDetailsWizardPage.ā(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewJ2EEProjectDetailsWizardPage.setProjectGroupEnabled(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewJ2EEProjectDetailsWithSpecWizardPage.Ę(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewJ2EEProjectDetailsWithSpecWizardPage.ā(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewJ2EEProjectDetailsWizardPage.Ă(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewJ2EEProjectDetailsWizardPage.Ċ(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewEARMainProjectWizardPage$B.dialogFieldChanged(Unknown Source)
    at org.eclipse.jdt.internal.ui.wizards.dialogfields.DialogField.dialogFieldChanged(DialogField.java:67)
    at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.dialogFieldChanged(ListDialogField.java:471)
    at org.eclipse.jdt.internal.ui.wizards.dialogfields.CheckedListDialogField.dialogFieldChanged(CheckedListDialogField.java:106)
    at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.setElements(ListDialogField.java:547)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewEARMainProjectWizardPage.<init>(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewEARProjectWizard.<init>(Unknown Source)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    at java.lang.Class.newInstance0(Class.java:306)
    at java.lang.Class.newInstance(Class.java:259)
    at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:138)
    at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:167)
    at org.eclipse.core.internal.plugins.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:103)
    at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:151)
    at org.eclipse.ui.internal.dialogs.WorkbenchWizardElement.createExecutableExtension(WorkbenchWizardElement.java:83)
    at org.eclipse.ui.internal.dialogs.NewWizardNewPage$2.createWizard(NewWizardNewPage.java:294)
    at org.eclipse.ui.internal.dialogs.WorkbenchWizardNode$2.run(WorkbenchWizardNode.java:88)
    at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
    at org.eclipse.core.runtime.Platform.run(Platform.java:413)
    at org.eclipse.ui.internal.dialogs.WorkbenchWizardNode$1.run(WorkbenchWizardNode.java:85)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at org.eclipse.ui.internal.dialogs.WorkbenchWizardNode.getWizard(WorkbenchWizardNode.java:83)
    at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:96)
    at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:677)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
    at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
    at org.eclipse.jface.window.Window.open(Window.java:563)
    at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:107)
    at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
    at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
    at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    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:324)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)

    Thanks

    Michael

    #198216 Reply

    Scott Anderson
    Participant

    Michael,

    My first thought is that due to the size of your project you might be running out of memory, thus causing Eclipse to behave irradically once that occurs. Do you start Eclipse with arguments to increase the amount of memory it receives? You can do this by creating an alias to the eclipse.exe application and pass it arguments like:
    -vmargs -Xms128M -Xmx256M

    If you’re not doing this, could you give it a try and see if it changes the behavior?

    –Scott
    MyEclipse Support

    #198219 Reply

    You can do this by creating an alias to the eclipse.exe application and pass it arguments like:
    -vmargs -Xms128M -Xmx256M

    I actually use -vmargs -Xmx512M. Have had to do this because of the size with normal eclipse. It seems that any out of memory errors that occur come from the JSPCC. As it stands right now, I can not start eclipse (it wants to build the project and runs out of memory before I can change any settings). It then ask me to shutdown eclipse because of the memory problem. I might be able to not shutdown….

    Michael

    #198221 Reply

    support-michael
    Keymaster

    My first concern is to get your workbench started. Here are a couple of ideas that you may wish to try to get Eclipse started up without your large project being auto-built.

    The JSP editor can be configured to disable JSP compilation but in your case the project auto-build feature is causing your mega project to be compiled on startup. What your can try is to manually set the plugin preference that will disable JSP compilation. Try this:

    0) Stop Eclipse if it is running (doesn’t sound like this is your case)
    1) Open <workspace>/.metadata/.plugins/de.bb.bje.eclipse/pref_store.ini in an text editor.
    2) Set or add the following properties

                     compile-disable=true

    3) Save the pref_store.ini file
    4) Start Eclipse/MyEclipse; JSP compilation should not be invoked

    To manually disable workbench auto-build and “refresh on startup” do the following:
    0) Again Eclipse should be stopped/shutdown
    1) Open <workspace>/.metadata/.plugins/org.eclipse.ui.workbench/pref_store.ini in an text editor.
    2) Set or add the following properties

      
                  AUTO_BUILD=false
                  REFRESH_WORKSPACE_ON_STARTUP=false

    3) Save the pref_store.ini file
    4) Start Eclipse/MyEclipse; project build should not be invoked

    Once your workbench is up and running you will want to consider resetting these values using the Eclipse Preference UI.

    Michael K.
    MyEclipse Support

    #198240 Reply

    Michael,

    0) Stop Eclipse if it is running (doesn’t sound like this is your case)
    1) Open <workspace>/.metadata/.plugins/de.bb.bje.eclipse/pref_store.ini in an text editor.
    2) Set or add the following properties
    Code:
    compile-disable=true

    This worked.

    Thanks!

    Michael

    #198244 Reply

    support-michael
    Keymaster

    I am searching for an explanation for the “LibrarySet/classpath-container lost” issue. After disabling JSP compilation do you experience this problem when compiling just the Java classes.

    Michael
    MyEclipse Support

    #198246 Reply

    Michael,

    I am not 100% sure. I know that the problem happens when it can not do a complete build. I get errors that some type is referenced that can not be found. Basically, class A uses class B and B refers to some class not in the path. Class B is a 3rd party class.

    It might have to do with memory too.

    If you want, I have the entire log file from when this happened. It is huge 2.3 MB.

    Michael

    #198248 Reply

    support-michael
    Keymaster

    Yes, please send me the log to my attention for further research, support@genuitec.com

    Michael
    MyEclipse Support

Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: Creating J2EE Project – J2EE Library Missing

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