[Jerry D. Jasperson]

I’m using the latest 3.0 release of MyEclipse. Unfortunately, I can not deploy a packaged *.war to my WebSphere 5.1 server due to the web.xml existing in the web-inf whereas everything else exists in the WEB-INF dir.

I see that this bug was addressed in the 2.8 version…what about 3.x?

thanks for your help!

Regards,
Jerry

System Setup ——————————-
Operating System and version: Windows XP Pro (Dev), Solaris (Deployment)
Eclipse version: 3.0.0 stable release
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.7.200
Eclipse JDK version: 1.4.2_04
Application Server JDK version: 1.4.2_04
Are there any exceptions in the Eclipse log file? Don’t see a log file

– Message Body ——————————-

[Riyad Kalla]

Jerry does exploded deployment work for you as a workaround?

Also when you open this JAR file with WinZIP or WinRAR (or other compression program) how does the WEB-INF directory look? Is it lower case? What happens when you use jar to uncompress it, are two directories (web-inf and WEB-INF created?) what happens when you use jar to list the contents? Do you see two web-inf DIRS?

[Jerry D. Jasperson]

I haven’t tried to use the exploded deployment…typically run into translation issues from Windows to Unix when I do…but I will try.

When I examing the archive, the listing shows two distinct directories, 1) web-inf which contains only the web.xml descriptor, and 2) WEB-INF which contains all other applicable/appropriate files.

Thanks for your prompt response Riyad, I sincerely appreciate it!

-jerry

[Riyad Kalla]

Jerry we had someone else complain recently about this some situation, its very strange. Let me check with the devs and see if we ever figured anything out about this…

Out of curiosity, what is your locale?

[Jerry D. Jasperson]

I’m located in the Boston Area, MA.

Oddly, I just installed MyEclipse 2.8 (using Eclipse 2.1) and am having the EXACT same problem…this is very confounding.

I had uninstalled the 3.x versions of Eclipse/MyEclipse, as well.

I also performed a search of the workspace looking for any hint of a configuration/descriptor file that specifies web-inf over WEB-INF and was unable to find ANY reference to web-inf (lower-case).

As if this wasn’t enought of a problem, it also appears that this may be a dynamic issue as I was deploying this application with no issues just a few days ago. I guess the question is, “What has changed since then?” I don’t think you’ll like the answer: I installed the MyEclipse 3.0.8Beta1 over the June 25, 2004 release of Eclipse 3.0.

It hasn’t worked since, and it appears that it may have affected the 2.x versions, as well.

Thanks again!

-jerry

[Scott Anderson]

Jerry,

Can you please upgrade to 3.8 Beta 2 and see if this addresses the issue? I’ve done a cursory search of the entire codebase and web-inf never appears in lowercase anywhere so this is a bit of a puzzle. If you still have a problem on the latest build I’ll open a bug report for further investigation so we can get it fixed for the GA release.

[Jerry D. Jasperson]

Riyad,

I did try the 3.8Beta 2 release…still no resolution.

OK, so here’s something even odder:

I exploded the project and conducted a command line
:> jar cvfM myproject.war *

and the end result STILL had the lower-cased web-inf for the web.xml descriptor, but not the remaining files despite the fact that the directory was upper-cased WEB-INF.

Something odd is at hand. This tells me that it may be completely unrelated to the IDE!!?? Go figure…

I’ve installed/re-installed so many times that I don’t feel that this is a productive endeavor. Somehow, somewhere, things are not as they should be and I’m at my ropes end as to what could be causing this odd problem.

I’m going to do a global file search overnight and see what pops up…hopefully I’ll have more info tomorrow.

Cheers,
Jerry

[Riyad Kalla]

Ahhh very strange! Jerry I appreciate you doing that so we could narrow down if it was us or something else.

Can you restart your machine and see if that helps? Can you try and create the war file with Windows XP (right click on folder, Send To > compressed folder), did that work Ok? I wonder if there is something going on with NTFS/JAR…

Can you try and upgrade, however incremental, to 1.4.2_05?

[Riyad Kalla]

Hey also, double check the perms on the WEB-INF folder before its compressed… is there anything funky about it?

[Jerry D. Jasperson]

Riyad,

OK…I feel like a total dumb-ass for wasting your time. Here’s the problem:

Apparently, one of my associates had added some new information to the web.xml descriptor file without first checking with me. This new info was causing the problem with the deployment of the *.war archive.

As to the lower-cased web-inf vs. WEB-INF, since the application server was indicating that a corrupted WEB-INF/web.xml file was the problem, correctly, I immediately opened the archive using WinZip.

WinZip has this lovely little feature that will “guess?” what the directory will be and was erroneously creating a lower-cased web-inf directory for the web.xml file but not all others…very odd behavior. Oddly, this interpretation would actually CHANGE THE DIR CASE!

This “feature” can be disabled by checking the menu item Options –> View (tab) –> General (group) –> “Allow all upper case file names”

I sincerely apologize for making you and your associates scramble on this one. However, I do appreciate your aid and efforts!

Warm Regards,
Jerry

[Riyad Kalla]

OK…I feel like a total dumb-ass for wasting your time. Here’s the problem:

No problem, this is more relief to me than you discovering some huge bug 🙂

WinZip has this lovely little feature that will “guess?” what the directory will be and was erroneously creating a lower-cased web-inf directory for the web.xml file but not all others… This “feature” can be disabled by checking the menu item Options –> View (tab) –> General (group) –> “Allow all upper case file names”

I didn’t know this, thanks for the heads up incase other users have this problem!

Actually I”m really glad you ran this down, we had a nother user that had a problem like this, and he was using WinZip for testing as well and was seeing the lowercase dir problem, so this is very applicable. I’ll send this to the rest of the support team.

[qalanirl]

Had exactly the same problem and this one did it for me -thanks! 🙂

[Author]

Posts