| Custom Server Adapters [message #159685] |
Wed, 08 February 2006 11:48  |
Eclipse User |
|
|
|
WTP supports two methods for defining J2EE servers, the Generic Server
Adapter, and Custom Server Adapters.
I would like to know if there is any documentation, blogs, ... that I
might refer to for a comparison of the pros/cons of each approach.
Specifically, a list of features that are not available when using the
generic server adapter, and/or suggestions for the types of features
that might be present in custom server adapters.
In other words, why would one want to write a custom adapter at all?
Thanks
Michael Giroux
|
|
|
| Re: Custom Server Adapters [message #160148 is a reply to message #159685] |
Fri, 10 February 2006 11:15  |
| Eclipse User |
|
|
|
Originally posted by: gorkem.ercan.nospam.nokia.com
Basically generic server framework is itself a custom server implementation
that can be customized with the help of the .serverdef files. Although
generic servers can accomplish almost everything custom servers can, there
are limitations in the generic servers. Some of those limitations will be
removed in the coming releases.
First generic servers support J2EE servers at the moment. Although it is
possible to start/stop non j2ee servers using generic server framework. (I
had experimented with apache httpd and apache derby). Publishing non j2ee
module types presents problems. Also this is one of the reasons most vendors
choose to implement custom servers because they need to be able to control
the publishing mechanism for their custom module types such that product
specific artifacts are created/updated. But this is not a big issue since if
your need is to heavily customize publish time then generic server framework
can be extended with a custom publisher. A generic server publisher is an
extension point where you can register a publisher to be called on publish
time. The publisher that comes with the WTP, the ant based publisher is in
fact an implementation of this. There are commercial products that use
custom publishers to introduce custom publishing methods and modules(as long
as the custom module type is a descendant of j2ee module )
Another reason to have custom servers is control over server. The generic
server framework has no way of changing the configuration of the server. The
UI of generic server framework is a means to gather info about existing
configurations not to create new ones. Also with generic servers, you do not
get the info about the state and events of the running server through JMX or
some other means.
Another option with the WTP server framework is to have a hybrid server
implementation. A good example of such is Geronimo adapter from apache. It
is basically GenericServer that overrides the functionality of the server
when needed.
--
Gorkem Ercan
"Michael Giroux" <michael.giroux@bull.com> wrote in message
news:dsd7df$g89$1@utils.eclipse.org...
> WTP supports two methods for defining J2EE servers, the Generic Server
> Adapter, and Custom Server Adapters.
>
> I would like to know if there is any documentation, blogs, ... that I
> might refer to for a comparison of the pros/cons of each approach.
> Specifically, a list of features that are not available when using the
> generic server adapter, and/or suggestions for the types of features that
> might be present in custom server adapters.
>
> In other words, why would one want to write a custom adapter at all?
>
> Thanks
> Michael Giroux
|
|
|
Powered by
FUDForum. Page generated in 0.09680 seconds
Home