This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 91183 - Context path changes are not propagated to the application
Summary: Context path changes are not propagated to the application
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: EAR (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-18 10:22 UTC by Kirill Sorokin
Modified: 2016-07-07 08:55 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kirill Sorokin 2006-12-18 10:22:25 UTC
I have a Java EE Application Project with a Web Module. Once I added the module,
its context path was written to application.xml. However if I change the context
path in Web Module's properties later, the change is not propagated to
application.xml. 

This results in a somewhat unexpected behavior when deploying the application (I
thought that I did not need to change context root twice)

--
I'm working with 
NetBeans IDE Dev (Build 200610231500, C/C++ Pack 20061122)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251
Comment 1 Tomas Mysik 2007-06-19 09:54:47 UTC
I'm not sure if I can agree with this. I can imagine this case: you have WAR that is "independent" (I mean it can be 
deployed without any EJB or EAR) - if you change the context path of this module, should it be changed the context 
path in any application.xml as well? I'm really not sure... What to do if the context path in application.xml was 
edited manually before (I mean one set it to any value by hand)? I think that this would be confusing...

Any comments/opinions? If not, I will close it as invalid...
Comment 2 Petr Jiricka 2007-06-19 15:55:53 UTC
I am adding Petr Pisl so he can comment.
Comment 3 Petr Pisl 2007-06-19 17:31:03 UTC
I think both usecases are valid. Even I think that ksorokin's usecase is more often, but I don't have any data for this
and it's just my feeling. 

The IDE should ask, when user changes the context path in the web project, whether she wants to changed it also in the
java ee application. The web module can be part of more ear projects, so user should be able to select in which of them
it should be changed. 

Unfortunately we are not able to implement this in NetBeans 6.0 timeframe. There is missing infrastructure, which allow
to find out all the ear applications, which contain the web module. I wouldn't close the issue, but probably switch to
enhancement.  
Comment 4 Tomas Mysik 2007-06-20 14:39:00 UTC
So marking as ENHANCEMENT with target milestone future - ok?
Comment 5 Martin Balin 2016-07-07 08:55:52 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss