[Max Mirabito]

I am experiencing a problem and would appreciate a workaround

I am working with an EAR. When I right-click on the EAR Module I able to modify the “context-root” and It appears that MyEclipse allows me to do it.

However, when I go back and view and verify the mods were accepted it reverts back to the original WEB module name.

I noticed that the .mymetadata file of the EAR module has the updated entry but it’s not reflected on the GUI side.

How can I fix this problem?

Here is my environment
OS: Win 2K sp4
JDK: 1.4.2_03
IDE: Eclipse 2.12
PLUGINS:
MyEclipse 2.7.1 – Build id: 200403241200-2.7.1-G
Omondo 1.2.1 – Build id: 20031103
Systinet 2.5.1 – Version: 4.5.0 Build id: 4000
eSpell – Spell Checker 2.2.0

Thanks for any help in this matter

Max

[Riyad Kalla]

Max,
Do you mean a Web Module? There aren’t any EAR Modules in ME, and I just tried checking the properties page for a EAR project, and it doesn’t mention anything about a context root… so I’m guessing you mean Web Module…

Try refreshing then closing and reopening your project.

Regardless of what the GUI says, is the new context-root value honored when you deploy the app?

[Max Mirabito]

Hi Riyad,

Thanks for the quick repply I was not expecting any word from support till Monday 😉
and you are right I mean to say Web Module within a EAR project right-clik on the EAR project MyEclipse>Add Remove Module.

The information is retained when I build the EAR. But when I try to deploy to weblogic MyEclipse tells me that the context is already in use. So I have to delete the EAR project witht he duplicate module name in order to deploy a new EAR project.

Opening and closing Eclipse does not help

You see, I have 2 EAR projects.

1) Each EAR has 2 web modules.
2) One of the web modules is in the both EARs (WaspClient)
3) I am thinking that if I rename the context-root of the duplicate module (WaspClient) to (WASP1 and WASP2) I will not have any conflicts when I use myEclipse to deploy to a WLS

Following is my EAR structure

EAR1
WaspClient –> context-root WASP1
MyWebApp1

EAR2
WaspClient –> context-root WASP2
MyWebApp2

Thanks in advance for your help

Max

[Scott Anderson]

Max,

I just tried this in 3.8 Beta 1 and see what you mean that the GUI is reporting the ‘old’ context root. However, the application.xml file is being updated so inspite of this GUI problem the deployment should have the web root you specified. I’ve entered a problem report to fix the GUI in the next release.

[rws@templarcorp.com]

Scott – though you’re right that application.xml gets changed, the change doesn’t “stick”. If you add a new J2EE module to the EAR project, the context tends to get set back to the default (same as the webapp module name). Still possible to do a manual edit, but still a pain.

[Scott Anderson]

We tracked it down and fixed it thanks to the bug reports posted here. The fix will be available in 3.8 Beta 2 in a couple of days. Thanks to all!

[Riyad Kalla]

Fixed in 3.8Beta2.

[Author]

Posts