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.
Summary: | tomcat 4 module can't be installed as a system module | ||
---|---|---|---|
Product: | ide | Reporter: | Rich Unger <richunger> |
Component: | Internal Server | Assignee: | Rich Unger <richunger> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | jglick |
Priority: | P3 | Keywords: | ARCH |
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Rich Unger
2002-04-25 01:40:34 UTC
Maybe I don't understand, but it seems likely that no special code should be required for something like this. Use Repository.getDefault().findResource("httpwork/whatever") to get a suitable FileObject, and translate with FileUtil.toFile if you need to. If any such files are fixed and just come with the module, the NBM format takes care of this. There probably ought to be no "installation code" at all, and no direct references to ${netbeans.user} or ${netbeans.home}. Ask on nbdev if unsure. Agreed. However, now there is an additional issue. Modules which depend on httpserver4 and install .war files containing servlets for use by the IDE will copy their .war files to netbeans/system/httpwork/webapps. If httpserver4 is installed as a system module, and the new module is a user module, tomcat will be unable to find the new module's .war file. Set target milestone to TBD Set target milestone to TBD Setting target milestone to future. Will this issue be fixed? Is it even after 2 years valid? This is an issue with an experimental httpserver module using tomcat4 that never really got off the ground. |