Re: Sevak / Jetty / Serviceable

[Paul Hammant]

Greg,

"Paul" == Paul Hammant <[EMAIL PROTECTED]> writes:

Paul> Folks, The Jetty implementation of Sevak (not released yet as
Paul> a download) now supports Serviceable servlets.

Confirmed to work here. Thanks a lot for this great work! And the timing
is perfect: I was just going to move our app to Phoenix-Jetty combo.
Now I can run real services in Phoenix and export them to servlets
without any hassle!

:-)

A small nit common to all components running in Phoenix that are
Serviceable on behalf of the components that they contain: that service
(JettySevak) .xinfo needs to declare dependencies on all services that
are used by contained servlets. I solved this by extending JettySevak
with a dummy class whose sole purpose was to contain correct @phoenix:
directives. Anybody know of a neater solution?

That is a good technique, however, I'd probably replace the .xinfo in the sevak-jetty.jar as part of mu build process. <jar> supports replace, we use it at work for various.

In EOB, I am using the second deploy() method which allows a ServiceManager to be specified for *each* webapp being deployed rather than the whole servlet container.

Finally, to avoid being total leech, a small patch to
build.xml. Dependency change allows using "ant clean demo-jar" and
excludes change makes exclude really work and suppresses the warning
from war-task and excludes the .java files from deployment.

Kewl.

Mailing list software interracts weirdly with attachments sent from
GNUS/mml. It used to remove the patches, now it chose to remove the
body of the message instead.

No probs.

Question, would you like any of the other Avalon-Framework lifecycle interfaces to be honoured for servlets ?

- Paul


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>