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 52033 - Do not modify context.xml and don't create Tomcat.dpf
Summary: Do not modify context.xml and don't create Tomcat.dpf
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords: TOMCAT
Depends on:
Blocks:
 
Reported: 2004-12-02 19:54 UTC by zikmund
Modified: 2006-03-24 10:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Example pair of generated Tomcat5.dpf and meta-inf/context.html files (606 bytes, application/octet-stream)
2004-12-02 20:16 UTC, manawiz 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description zikmund 2004-12-02 19:54:08 UTC 
Build 200412011810 (RC2)

1) Create new WebApp
2) Run project
3) ERROR:
META-INF/context.xml is copied to Tomcat5.dpf file
(should not be) and is modified by adding docBase
attribute with absolute path (shouldn't)!
Comment 1 manawiz 2004-12-02 20:16:34 UTC 
Created attachment 19113 [details]
Example pair of generated Tomcat5.dpf and meta-inf/context.html files
Comment 2 manawiz 2004-12-02 20:20:40 UTC 
My generated Tomcat5.dpf and meta-inf/context.html have a different
symptom pattern (see the files in the attached files.zip).  Both have
absolute paths for docBase.  The one in context.html appears to be
correct, but one is Tomcat5.dpf is very strange.  This path does not
exist in my file system!  The path used to exist some time ago when I
had a single project.  Now I have multiple projects that are all under
a Projects directory.  I'm really curious how Netbeans is acquiring
this old path.

In addition to old vs. new, the Tomcat5.dpf path is into the source
tree (in its old location), while the context.html path is into the
build tree (in its current location).
Comment 3 Sherold Dev 2004-12-08 13:22:34 UTC 
Setting TM to 4.1.
Comment 4 Petr Jiricka 2005-03-15 13:15:02 UTC 
The absolute path problem in Tomcat may be related to the following Tomcat issue:

http://issues.apache.org/bugzilla/show_bug.cgi?id=27916
Comment 5 Sherold Dev 2005-03-22 15:50:10 UTC 
F. 
 
Checking in src/org/netbeans/modules/tomcat5/TomcatManagerImpl.java; 
/cvs/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/TomcatManagerImpl.java,v  
<--  TomcatManagerImpl.java 
new revision: 1.39; previous revision: 1.38 
done 
Checking in TargetServer.java; 
/cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/TargetServer.java,v  
<--  TargetServer.java 
new revision: 1.40; previous revision: 1.39 
done
Comment 6 Petr Jiricka 2005-03-22 17:22:25 UTC 
So after the fix, the war file will contain context.xml that does not contain
the absolute path, correct? Will it be possible to deploy this war file to
Tomcat manually? And redeploy? (I know there were problems that deploy sort of
worked, but redeployment using Tomcat manager did not.)
Comment 7 Sherold Dev 2005-03-22 17:39:56 UTC 
> will contain context.xml that does not contain the absolute path
Positive

> deploy this war file to Tomcat manually
I tested this by copying the war file to webapps dir and it worked.

> And redeploy?
Did not tested this yet, will try it out.
Comment 8 zikmund 2005-03-31 13:38:57 UTC 
Verified in 200503301800.