Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 77493 - httpserver is using some modified acient version of tomcat
httpserver is using some modified acient version of tomcat
Status: RESOLVED INVALID
Product: ide
Classification: Unclassified
Component: Internal Server
6.x
All All
: P3 (vote)
: TBD
Assigned To: issues@ide
issues@ide
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-07 07:44 UTC by Jaroslav Tulach
Modified: 2016-05-25 05:56 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2006-06-07 07:44:33 UTC
The httpserver module contains some old and obsolete copy of tomcat. I guess 
tomcat 3. Given the fact that the IDE also contains tomcat 5.5.x this is a 
very nice example of duplicated bits - e.g. bigger download size, outdated 
functionality, poor architecture.

The httpserver shall share the most recent tomcat version.
Comment 1 _ rkubacki 2006-06-20 14:03:30 UTC
We internally use in the IDE some simplified version of Tomcat 3.x.y (+ related
Servlet API) to make internal HTTPserver functional. We also internally use some
bits from Tomcat5 in web support (JSP parsing) and bundle whole Tomcat5. It is
possible that we also depends on something from Tomcat4. 

As far as I understand it the goal is to simplify these dependecies and make
building of packages easier. Here in HTTPserver we can 
1) update it to recent Tomcat3 version. We need to be carefull here as noone
remembers what we needed and how we repackaged this in the past. OTOH patch in
http://www.zarb.org/cgi-bin/viewvc.cgi/rpms/devel/netbeans/netbeans-modules.patch?root=jpackage&view=markup&rev=1.2
can help us
2) migrate to newer version of Tomcat. We can use Rich's contribution of update
to Tomcat 4 and try to update it to Tomcat 5 (change between 3 and 4 was much
bigger). I am afraid that the result will be much bigger beast than we have now
with all deps on things like commons-*, catalina-{core|bootstrap|...}
3) similar like 2) but migrate to GlassFish
Comment 2 Petr Jiricka 2006-06-23 11:16:27 UTC
I don't see why this is a DEFECT, definitely not according to the bug priority
guidelines. The biggest reason to use Tomcat 3.x (besides the fact that it is a
lot of work to migrate to a newer one and I don't see any end user value in this
work) is that Tomcat 3.x can be used as a very lightweight container, which is
not the case with Tomcat 4 and 5. Also, the copy of Tomcat 5.5 that we have has
to be very easy to decouple from the IDE (ideally, the integration should be
done by the installer). If we use it in the embedded HTTP server, it would be
much harder to decouple. 


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo