facebook

Error When creating a Web Module project

  1. MyEclipse Archived
  2.  > 
  3. Old Posts
Viewing 15 posts - 1 through 15 (of 20 total)
  • Author
    Posts
  • #196147 Reply

    peterjb
    Member

    When I attempt to create a Web Module Project, I get an error
    !NewProjectCreationWizard.op_error.message! – Sere error log for more details.

    The log contains :

    !SESSION May 08, 2003 07:33:47.828 ———————————————
    java.version=1.3.1_05
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_AU
    Command-line arguments: -os win32 -ws win32 -arch x86 -data h:\projects\eclipse -showlocation -install file:F:/eclipse/
    !ENTRY org.eclipse.ui 4 4 May 08, 2003 07:33:47.843
    !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions
    !ENTRY org.eclipse.ui 4 4 May 08, 2003 07:33:47.843
    !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions.server
    !ENTRY org.eclipse.ui 4 4 May 08, 2003 07:33:47.843
    !MESSAGE Unable to find Action Set: com.genuitec.myeclipse.actions.webtools
    !SESSION May 08, 2003 07:34:48.406 ———————————————
    java.version=1.3.1_05
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_AU
    Command-line arguments: -os win32 -ws win32 -arch x86 -data h:\projects\eclipse -showlocation -install file:F:/eclipse/
    !ENTRY org.eclipse.jdt.ui 4 10001 May 08, 2003 07:34:48.406
    !MESSAGE Internal Error
    !STACK 0
    java.lang.reflect.InvocationTargetException: java.lang.NoSuchMethodError
    at com.genuitec.eclipse.j2eedt.core.J2EEProjectUtil.makeJavaName(Unknown Source)
    at com.genuitec.eclipse.j2eedt.core.WebProject.getDefaultArchiveName(Unknown Source)
    at com.genuitec.eclipse.j2eedt.core.J2EEProject.getArchiveName(Unknown Source)
    at com.genuitec.eclipse.j2eedt.core.J2EEProject.?(Unknown Source)
    at com.genuitec.eclipse.j2eedt.core.WebProject.?(Unknown Source)
    at com.genuitec.eclipse.j2eedt.core.J2EEProject.?(Unknown Source)
    at com.genuitec.eclipse.j2eedt.core.J2EEProject.saveMetaData(Unknown Source)
    at com.genuitec.eclipse.j2eedt.core.builder.WebProjectBuilder.create(Unknown Source)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewWebProjectWizard.finishPage(Unknown Source)
    at org.eclipse.jdt.internal.ui.wizards.NewElementWizard$2.run(NewElementWizard.java:89)
    at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:34)
    at org.eclipse.jdt.internal.core.JavaModelOperation.execute(JavaModelOperation.java:365)
    at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:684)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:2711)
    at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:42)
    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
    at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
    at org.eclipse.jdt.internal.ui.wizards.NewElementWizard.performFinish(NewElementWizard.java:96)
    at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
    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:845)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    at java.lang.reflect.Method.invoke(Native Method)
    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)

    Am I doing something wrong?

    Cheers

    Peter

    #196151 Reply

    support-michael
    Keymaster

    You’re not doing anything wrong. There is a JDK 1.4 dependent API in this method. I have entered a bug report in our tracking system and the problem will be remedied in the next EA release. Until then you can circumvent this problem by using JDK 1.4. Please Note it is not our intention to require use of JDK 1.4. MyEclispe goal is to operate with JDK 1.3+, only that hot-swap debugging doesn’t work with JDK 1.3.

    Michael,
    MyEclipse Support

    #196182 Reply

    Scott Anderson
    Participant

    The JDK 1.4 dependency has been removed in our internal builds. The first release that will be 1.3-compliant will be 2.0.3 EA.

    –Scott
    MyEclipse Support

    #196186 Reply

    jimisola
    Member

    @scott wrote:

    The JDK 1.4 dependency has been removed in our internal builds. The first release that will be 1.3-compliant will be 2.0.3 EA.

    –Scott
    MyEclipse Support

    Hi,

    I’m trying to create a New J2EE Web Project but keep getting “!NewProjectCreationWizard.op_error.message!” (see end of this post for error log output).

    I use ant and we have separate src and build directories under the cvsroot.

    cvsroot/src contains:

    src/se/* (holds our source code for Beans and our own tag lib)
    src/webroot

    src/webroot contains:

    webroot/META-INF
    webroot/WEB-INF
    webroot/images
    jsp code exists under roots directory as well as in subdirectories.

    Note: our webroot/WEB-INF directory does ONLY contain a lib directory – NO classes directory exists. The classes for the classes directory is “copied” into the war file by from build/se/* (i.e. class files created from src/se/*) when needed.

    When I tried to create a new J2EE WP the following was entered:

    Project Name: AdminConsole
    Location: unchecked
    Directory: …/cvsroot/src/webroot
    Context URL: /tracker

    So, What am I doing wrong?
    I’m using JDK 1.4.1_01, so it can’t be 1.3-thing or?
    Can this have anything to do with the fact that I’ve had some problems with install/uninstall of MyEclipseIde and therefore had to it manually before reinstalling?

    Any help appreciated.

    Sincerely,
    Jimisola

    !ENTRY org.eclipse.jdt.ui 4 10001 maj 18, 2003 19:11:40.560
    !MESSAGE Internal Error
    !STACK 0
    java.lang.reflect.InvocationTargetException
    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:313)
    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
    at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
    at org.eclipse.jdt.internal.ui.wizards.NewElementWizard.performFinish(NewElementWizard.java:96)
    at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
    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.NewWizardAction.run(NewWizardAction.java:136)
    at org.eclipse.ui.internal.NewWizardDropDownAction.run(NewWizardDropDownAction.java:96)
    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:845)
    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)
    Caused by: java.lang.NullPointerException
    at org.eclipse.jface.dialogs.ErrorDialog.<init>(ErrorDialog.java:117)
    at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:353)
    at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:317)
    at com.genuitec.eclipse.j2eedt.ui.wizard.NewWebProjectWizard.finishPage(Unknown Source)
    at org.eclipse.jdt.internal.ui.wizards.NewElementWizard$2.run(NewElementWizard.java:89)
    at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:34)
    at org.eclipse.jdt.internal.core.JavaModelOperation.execute(JavaModelOperation.java:365)
    at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:684)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:2711)
    at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:42)
    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
    … 35 more

    #196190 Reply

    Scott Anderson
    Participant

    Jimisola,

    We believe this problem is most likely caused by the issue you reported when you tried to uninstall and then reinstall. Before we look into this any further, please read my reply to your post in the installation forum and let’s ensure that you have a correct installation of 2.0.3 EA before proceeding with this issue.

    –Scott

    MyEclipse Support

    #196193 Reply

    support-michael
    Keymaster

    We have been able to reproduce behavior similar to that indicated in the stacktrace you provided. The problem we observe appears to be cause by an error with custom project location. Yet the resulting system dialog is not properly opening to reveal the system error message.

    Can you help us isolate your problem by trying to create a temporary Java project using the same project name and location? If you experience an error dialog please send us the error message. I suspect the custom project location is problematic. Looking forward to see your feedback.

    Michael,
    MyEclipse Support

    #196195 Reply

    jimisola
    Member

    I created an ordinary Java Project with the same properties as you asked for. But, then I got an error because of overlaping. (I not that this does not work for ordinary Java projects but I (and other to, I guess) need to have a J2EE WP overlaping a Java Project since I don’t want to change the file/directory structure used by ant.)

    I tried another time I got “Invalid project description”.

    Anyway, I then closed the overlaping Java Project and tried creating a _J2EE Web Project_ again. This time I received “Invalid project description” again. This seems a little odd, because I was only able to produce it once – even though I used the exact same description. The following tries I kept getting the error that I orginally posted first time.

    Well, hope that this can be of some kind of help.

    Jimisola

    Stack traces:

    #1 Ordinary Java Project

    !ENTRY org.eclipse.jdt.ui 4 10001 maj 19, 2003 10:07:50.476
    !MESSAGE Internal Error
    !STACK 1
    Java Model Exception: Core Exception [code 77] Invalid project description.
    at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:45)
    at org.eclipse.jdt.internal.core.JavaModelOperation.execute(JavaModelOperation.java:365)
    at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:684)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:2711)
    at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:42)
    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
    at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
    at org.eclipse.jdt.internal.ui.wizards.NewElementWizard.performFinish(NewElementWizard.java:96)
    at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
    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:845)
    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)
    !ENTRY org.eclipse.core.resources 4 77 maj 19, 2003 10:07:50.476
    !MESSAGE Invalid project description.
    !SUBENTRY 1 org.eclipse.core.resources 0 0 maj 19, 2003 10:07:50.476
    !MESSAGE OK.
    !SUBENTRY 1 org.eclipse.core.resources 4 77 maj 19, 2003 10:07:50.476
    !MESSAGE C:/Documents and Settings/Jimisola Laursen/My Documents/_cvsroot/src/webroot and C:/Documents and Settings/Jimisola Laursen/My Documents/_cvsroot overlap.

    #196197 Reply

    support-michael
    Keymaster

    Great feedback. I suspected the project creation problem was due to overlapping project paths. Fundamentally overlapping projects introduce problems that are difficult to manage in a general manner. If the desire is to have projects whose source directories overlap then you can setup non-overlapping Java/Web projects and use source folders with exclusion patterns to reference their respective source.

    Let me give your project setup requirements more thought and I’ll provide more feedback.

    Michael
    MyEclipse Support

    #196204 Reply

    jimisola
    Member

    My directory setup is pretty much standard for those of use that use Ant:

    build/
    src/com/jimisola/<some code>
    src/webroot
    javadoc/
    lib/
    tools/ (tomat, ant, jdepend etc)

    If it comes to the fact that I need to change my directory structure I’m sad to say that MyEclipseIDE won’t be something for me and my developer team. I’ve never liked when a developer (or developer team) has do make adaptations because of a IDE.

    There is an, too me, obvious need for project to be able to overlap.
    If I may ask, why does this limitation exist at all?

    Hope that you can resolve the problem. I would love to use the JSP-editor in MyEclipseIDE – it looks neat! 🙂

    Keep up the good work,
    Jimisola

    #196222 Reply

    support-michael
    Keymaster

    I understand your concerns regarding an IDE’s imposition of a specific project structure. We want to minimize MyEclipse project structure requirements but our application server integration and deployment tooling must honor the J2EE packaging models, i.e., WAR & EAR. Thus the more closely a project layout is to that of its respective J2EE deployment model then the simpler it will be to use with standards based tools.

    Today I was assisting an organization that recently revised its project model after several years of struggling with a proprietary project model that was orthoganal to the J2EE deployment model. Their early model prohibited its direct use with J2EE tools unless transformed using Ant. After revising their project model to one congruent with their deployment model they have found more tools including MyEclipse to be directly useful to their efforts while simplifying one aspect of their process.

    I will describe a solution that I created for your structure in a follow up message.

    Michael
    MyEclipse Support

    #196223 Reply

    support-michael
    Keymaster

    I was able to create a MyEclipse web project for your structure that does not violate Eclipse’s overlapping project restriction.

    The process involves creating a basic Java project and then configuring it as a MyEclipse web project.

    Step-1: create a Java project “MyProject”, above your “src” folder
    Step-2: select MyProject->Properties->Build Properties->Source tab and add “src” as a project source folder and remove MyProject as an implicit source folder
    Step-3: select MyProject->MyEclipse->WebProject Configuration…
    Step-3a: select “Browse” for the Web Root field followed by “Create New Folder…”
    Step-3b: enter webroot as the folder name followed by selecting the “Advanced” button
    Step-3c: choose “Link to folder in file system”
    Step-3d: select “Browse” and naviage to the “…/src/webroot” folder
    Step-3e: select OK repeatedly until you are back to Web Project Configuration Wizard
    Step-4: Enter your context root
    Step-5: Select “OK” to complete web configuration process.

    At this point you should be able to use the JSP editor with its code completion capabilities. Also your project output directory is now …/webroot/WEB-INF/classes. So any former ouptut folder can be ignored or deleted. The tradeoff for getting this working is that the link technique causes the copy of your src/webroot contents to the WEB-INF/classes folder.

    Michael
    MyEclipse Support

    #196236 Reply

    jimisola
    Member

    Thanks, but I’m a newbie to WebApps so I need some clearifications…

    First of all, I must have done something wrong since I now get:

    “/Documents and Settings/Jimisola Laursen/My Documents//_cvsroot/build/webroot/server/status.jsp) not in base path (C:/Documents and Settings/Jimisola Laursen/My Documents/_cvsroot/src/webroot/)”

    I think that me I setting the context root to the project’s top folder (i.e. _cvsroot) caused this. What should it be – “src/webroot” or is this just the name that is used be e.g. Tomcat like “/manager”, “/admin” etc?

    I cab’t get ride of it even after I removed used the MyEclipse -> WebApp Configuration menu option. Why is this?

    Second of all, which files does an MyEclipseIDE Web Project need (web.xml, context.xml) and where should they be located? Is read something about custom taglibs and syntax highlightning. If I’m not mistaking it needs a tld-file where should this be located?

    It would have been really nice if one could point out files in the WebApp configuration instead of needing to have multiple versions of the same file.

    @support wrote:

    Step-2: select MyProject->Properties->Build Properties->Source tab and add “src” as a project source folder and remove MyProject as an implicit source folder

    First of all, just so that I’m at the right place. You meant MyProject->Properties->Java Build Path >Source tab” – am I correct?

    “and remove MyProject as an implicit source folder”?
    I assume you mean “MyProject” on its on.
    The only two source folders that I have are “MyProject/src” and “MyProject/test” (test being for JUnit tests).

    @support wrote:

    Step-4: Enter your context root

    See above. Is this “MyProject/src/webroot”?

    @support wrote:

    At this point you should be able to use the JSP editor with its code completion capabilities. Also your project output directory is now …/webroot/WEB-INF/classes. So any former ouptut folder can be ignored or deleted. The tradeoff for getting this working is that the link technique causes the copy of your src/webroot contents to the WEB-INF/classes folder.

    Since, I haven’t been able to set it up yet I wonder if the output directory is used by my whole project (includng “src/se/*” and “test/*”)? I have some problems with that because of the interaction with ant. I really need to share output folders.

    For now this will work, but it’s seems as a little hack (work-around) will there be a better solution to this in the future say setting output folder, point out tld files etc.

    Last of all, when I work on my webroot I need to be using the link “MyProject/webroot” and not “MyProject/src/webroot”. Correct?

    Thanks in advance. Your support has been great.
    I hope I’m not aksing to much hopefully it will come to use for someone else as well.

    Sincerely,
    Jimisola

    #196242 Reply

    support-michael
    Keymaster

    “/Documents and Settings/Jimisola Laursen/My Documents//_cvsroot/build/webroot/server/status.jsp) not in base path (C:/Documents and Settings/Jimisola Laursen/My Documents/_cvsroot/src/webroot/)”

    I must have missed the “build” in your previous msg. I was assuming that you had 2 src dirs: …/src/se* and …/src/webroot. The model I laid out will support JSP editing on …/src/webroot/*.jsp files located above …/src/webroot/WEB-INF.

    I think that me I setting the context root to the project’s top folder (i.e. _cvsroot) caused this. What should it be – “src/webroot” or is this just the name that is used be e.g. Tomcat like “/manager”, “/admin” etc?

    Web Root is a the folder that serves as the root folder of an exploded WAR folder structure. Context root is the URL used to access the application. Context root is not very useful in EA1. It will make a lot of sense in EA2 with deployment and debugging.

    First of all, just so that I’m at the right place. You meant MyProject->Properties->Java Build Path >Source tab” – am I correct?

    yes

    “and remove MyProject as an implicit source folder”?
    I assume you mean “MyProject” on its on.
    The only two source folders that I have are “MyProject/src” and “MyProject/test” (test being for JUnit tests).

    Yes, eliminate MyProject as a source folder; otherwise you will encounter problems due to Eclipse restrictions re: overlapping src folders.

    Since, I haven’t been able to set it up yet I wonder if the output directory is used by my whole project (includng “src/se/*” and “test/*”)? I have some problems with that because of the interaction with ant. I really need to share output folders.

    Under your project build-path properties inspect the output location. It should be MyProject/<webroot>/WEB-INF/classes. If yes and your project has a bin or other output directory this other directory is no longer used and can be deleted. Note MyEclipse is configuring your project to conform to an exploded WAR structure.

    For now this will work, but it’s seems as a little hack (work-around) will there be a better solution to this in the future say setting output folder, point out tld files etc.

    We actually started with an extremely flexible model but found that it led to very complex setup procedures that most developers had difficulty managing. It was a flexibility<->complexity tradeoff. Thus we narrowed our focus to standards based installations. We have not found many project instances where we could not configure Eclipse to support but the complexity of flexing the tool was much more awkward than flexing the project structure.

    Michael
    MyEclipse Support

    #196244 Reply

    jimisola
    Member

    @support wrote:

    I must have missed the “build” in your previous msg. I was assuming that you had 2 src dirs: …/src/se* and …/src/webroot. The model I laid out will support JSP editing on …/src/webroot/*.jsp files located above …/src/webroot/WEB-INF.

    Ok. Does that change anything? The jsp files under src/webroot/* will need (I think) files under src/se (we have custom servlets, beans and taglibs here).

    Web Root is a the folder that serves as the root folder of an exploded WAR folder structure. Context root is the URL used to access the application. Context root is not very useful in EA1. It will make a lot of sense in EA2 with deployment and debugging.

    I thought so – looking forward to 2.0.2EA.

    We actually started with an extremely flexible model but found that it led to very complex setup procedures that most developers had difficulty managing. It was a flexibility<->complexity tradeoff. Thus we narrowed our focus to standards based installations. We have not found many project instances where we could not configure Eclipse to support but the complexity of flexing the tool was much more awkward than flexing the project structure.

    Well, complexity is what I’m experiencing now… because I still can’t get it to work. I have created the linked webroot folder (linked to src/webroot)under project top level directory.

    The “Web Creation Conversion” dialog Web Root Dir set to “webroot”. For the rest of three inputs (context root, create.xml and “J2EE 1.3[default] or None”) I’ve tried all kinds of combinations.

    Either MyEclipse ruins my Java Project totally or, as now, pressing “Finish” in “Web Creation Conversion” dialog either hangs Eclipse or nothing happens at all (I can still change inputs though).

    Why is not this working? I even tried extracting our (working w/ Tomcat ) web.xml into src/webroot/WEB-INF – still nothing.
    I’m starting to loose it – can’t put much more time into this 🙁

    /Jimisola

    #196245 Reply

    jimisola
    Member

    Yet another update:

    The “Web Creation Conversion” dialog came through finally.
    Checked “build web.xml” and “None”.

    However, all jsp files (under the linked webroot directory) show up in the task list with the following error:

    …/_cvsroot/src/webroot/WEB-INF/classes/webroot/WEB-INF/classes/webroot/WEB-INF/classes/webroot/index.jsp) not in base path (…/_cvsroot/Web Root/).

    The content/context assistant does not work with standard and jstl tags. Do they need tld files as well or aren’t they suppose to be “well-known” out of the box?

    /Jimisola

Viewing 15 posts - 1 through 15 (of 20 total)
Reply To: Error When creating a Web Module project

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