|Re: Servers View - Provide Public ServerBehaviour Types [message #765811 is a reply to message #765753]
||Wed, 14 December 2011 18:00
| Larry Isaacs
Registered: July 2009
On 12/14/2011 10:59 AM, Ivan wrote:|
> I guess "Tomcat support" means the availability to work with an Apache
> Tomcat server from the Servers view.
> I know that the support of the Apache Tomcat server extends the
> ServerDelegate, where they also implement a whole bunch of other classes
> to support their server type. In my case I want to use the
> ExternalServerBehaviour (also a "generic" type), which suits me perfect
> and extend it with a couple of more methods. As far as I understand, it
> is recommended to implement the whole server behaviour functionality by
> myself and avoid the dependency to the "generic" server types. Then the
> question which arises to me is: Why these "generic" types are meant to
> be used for?
> Do I get it right?
The "generic" server code supports a minimal level of integration.
Primarily this means that publishing a project to the server involves
building a WAR or EAR file and copying to some folder where the server
is assumed to auto-serve that file. If you modify a JSP file and want
to publish that change to the server, it involves building a whole new
WAR are EAR file and replacing the file previously copied. It is
assumed the server will notice the change and redeploy the file.
The Tomcat server code supports a much higher level of integration.
Publishing a project involves copying individual files. If you modify a
JSP file, publishing that change to the server only involves copying
that JSP file. There is also more support for changing the actual
configuration of the server within Eclipse.
If you are intending to provide a higher level of integration, you may
find example code in the Tomcat source more useful in certain cases.
Powered by FUDForum
. Page generated in 0.02017 seconds