[Riyad Kalla]

It should be out this week or early next. Testing is going really smoothly, closing out the last set of TODOs.

[cnrindia]

I downloaded and installed ME 5.1 and I still see the same issue. So I am still stuck with ME 4.11 with Eclipse 3.1.x. I am not sure what to do at this point. It is very frustrating that things that worked in previous release do not work any more.

I am not sure what to do at this point but am seriously considering looking for some other plugin.

Any help would be appreciated.

Thanks

Divyesh

[Riyad Kalla]

Divyesh,
Did you try and app web capabilities to this project where your WebRoot is equal to “/” (project root)? I cannot reproduce this locally. Keep in mind that your project must have web capabilities added to it in order for MyEclipse to understand it.

[cnrindia]

Riyad,

I tried almost every possible combination that i could think of to get this to work for me including the one you suggested above in your last reply.

I am at the end of the road having wasted way too much time to get this to work for me.

Can you look at the folder structure i have described in my previous posts and the method for including the jsps and see if you can reproduce this issue?

Does ME4.1.1 work with ecl 3.2.1?

I unfortunately do not have control over making radical changes to get this to work for me in the the current code base, which means that i may not renew my subscription if this does not work since going forward i will need to switch to ecl 3.2 and it will be soon.

Thanks

Divyesh

[Riyad Kalla]

Divyesh,
4.1 is not compatible with Eclipse 3.2. Also I’ve tried the layout you gave and couldn’t reproduce the problem, but I will continue to try and break things on my end and see if I can find a corner case that is possibly causing the problem .

[cnrindia]

Riyad,

I was trying out Bea Workshop, with the same settings and it so happened that I had the .classpath and .project files for the project that was giving me trouble in ME 5.1, it worked with fine similar settings in Bea. I then closed Bea and restarted ME 5.1, and lo behold, it worked this time with the modified entries by Bea.

Upon investigating I found that Bea had created WEB-INF and META-INF folders under the project root. I am still investigating if this was the only change that caused everything to work with ME 5.1 or if it was something else.

Divyesh

[Riyad Kalla]

Divyesh,
When you add web capabilities to your project, MyEclipse creates the WEB-INF/classes directory forcibly under your webroot, in this case, under your project root. So that must be why I wasn’t seeing the problem and you were.

And yes, this would be a problem, MyEclipse expects your webroot to have the form of an exploded WAR, wether it’s under the root of the project, or down one level in a “WebRoot” directory.

I’m glad to hear things are getting closer to working, keep me posted please.

[cnrindia]

Riyad,

After having gone through the install of Bea, I decided to uninstall Bea and completely reinstall eclipse 3.2.1 and ME 5.1 and setup the projects all over again.

I followed your instructions/tips above in trying to recreate the web project and now it does not work anymore.

The problem is when I try creating the project with a dummy webroot under the project root with an exploded war structure I get an error during project creation that the context root url must include the project name. So for instance if my project name is jsp, which is the name of the folder containing the jsps in sub-folders, which I have as the project root as well, then the context root url must include “jsp” as a sub-folder underneath. This causes the dialog box to hang up until the workspace is rebuilt whic takes a rather long time and even with the error the project does get created, but with the same issues as before where the content assist does not resolve vars that are declared in included jsps.

Any ideas how to workaround this?

Thanks

Divyesh

[Riyad Kalla]

Divyesh,
This might just be a misunderstanding. These terms are sort of confusing.

The “Web root directory” is the directory, in your project, that MyEclipse wants to treat as the root of your web application when it’s deployed. In your case it will be “/”, in most cases it’s some subdirecotry under the project root, normally named “WebRoot” but can be named anything you want. So it looks like this:

+ MyWebApplication <-- Project root
  + /docs <-- Some documentation/license files
  + /src <-- Java source and properties files
  + /WebRoot <-- Web root that MyEclipse knows about
    + index.jsp <-- Some index file and other JSPs
    + /WEB-INF <-- the necessary WEB-INF dir
...

Now the “web context root” is the name of the web application as it will be deployed under your app server, for example, on Tomcat, this will be the directory it’s deployed under the <Tomcat directory>/webapps directory. Every application needs it’s own context root. By default MyEclipse makes this the name of your project, but you can name it anything, like “/myapp”, in which case this will get deployed to <Tomcat 5 install dir>/webapps/myapp, and you can access it using the URL:
http://localhost:8080/myapp/index.jsp (notice the myapp part)

Did that help clear things up?

[cnrindia]

Riyad,

The above simple picture did it finally! I gues I was just confused by the terminology. I seem to have gotten it configured finally to the point that most of the errors are gone and the content assist seems to work fine. I do see some errors with content assist, but that may have to do with the way the code is organized that I may have to do some trial-and-error to resolve.

I think the expectations or tutorial ought to include the above diagram – that should clarify how a web project should be setup.

Thanks a lot for your help.

I will keep you posted if I hit any more issues.

[Riyad Kalla]

I’m really glad to hear that it’s working now. It can be so frustrating at times battling with a tool.

Yes do please keep me posted. Also I think you are right, we should integrate this into our introductory tutorials, I’ll make a note to do that when we refresh them.

[Author]

Posts