Eclipse Community Forums: Web Tools Project (WTP) » Servers View

Home » Eclipse Projects » Web Tools Project (WTP) » Servers View - Provide Public ServerBehaviour Types(Currently all ServerBehaviour types are placed in an internal package)

Show: Today's Messages :: Show Polls :: Message Navigator

Servers View - Provide Public ServerBehaviour Types [message #761574]

Tue, 06 December 2011 12:18

Ivan
Messages: 2
Registered: December 2011

Junior Member

Hi,

I want to define new server types in the Servers view. In my implementation I need to inherit the classes org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour and org.eclipse.jst.server.generic.core.internal.ExternalServerBehaviour. They both reside in the internal package org.eclipse.jst.server.generic.core.internal, which is not meant to be a real API. Do you plan to change it in the future? Could there be some ServerBehaviour types in the API?

Thanks in advance,
Ivan

Report message to a moderator

Re: Servers View - Provide Public ServerBehaviour Types [message #764939 is a reply to message #761574]

Tue, 13 December 2011 00:59

Nitin Dahyabhai
Messages: 2089
Registered: July 2009

Senior Member

I'm not an expert on the Server Tools, but the "generic" server support isn't something you use if you're going to write extensive supporting code. You'd create something more traditional like the Tomcat support, and those are the classes you should look at.

---
Nitin Dahyabhai
Eclipse WTP, IBM

Report message to a moderator

Re: Servers View - Provide Public ServerBehaviour Types [message #765753 is a reply to message #764939]

Wed, 14 December 2011 10:59

Ivan
Messages: 2
Registered: December 2011

Junior Member

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?

Thanks,
Ivan

Report message to a moderator

Re: Servers View - Provide Public ServerBehaviour Types [message #765811 is a reply to message #765753]

Wed, 14 December 2011 13:00

Larry Isaacs
Messages: 1284
Registered: July 2009

Senior Member

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?
>
> Thanks,
> Ivan

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.

Cheers,
Larry

Report message to a moderator

Previous Topic:	Remote Rhino debugging - Exception inside eclipse when evaluating JavaScript
Next Topic:	EL content assist and auto-complete in jsp editor?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Mar 10 18:08:27 EDT 2014