Have you started to work on this? I'm interested in working on
implementing a Jetty 6 HTTP service.
As some background we are working on making Cocoon OSGi based. This far
we use the Equinox framework and bundles as we rely heavily on
declarative services, which hasn't been part of Felix until recently.
The HTTPservice in Equinox that we have used until now take a
fundamentalistic view on spec compliance and use servlet 2.1, while this
have worked well during prototyping it is more or less unusable in a
modern web framework. I have tried to switch to the current Felix HTTP
service to be able to use servlet 2.3 but have got all kinds of
classloading problems (unfortunately I'm not able to give any concise
bug report as I don't have any clue about what happens). I have also
tried the Oscar and Knopflerfish services who both works in my setting,
but doesn't implement e.g. contextpath in a meaningful way.
Jetty 6 seem to be designed for embedding and doesn't seem to require
context classloader tricks.
/Daniel
Rob Walker skrev:
I'm interested in views on updating our http to a newer Jetty version
- a 5.x release will probably be a fairly painless move, since the
architecture hasn't changed much
- a 6.x will probably take more effort, but also mean we catch the
"next wave" of Jetty optimisations early
Anyone got any views/preferences - not sure I'll get time to do both,
and although it's riskier since 6.0 is still in alpha it also seems to
have more long term mileage in it. Anyone wanting a "stable" http can
still use the current 4.x if they're not ready for the change.
Thoughts?
-- Rob
Ascert - Taking systems to the Edge
[EMAIL PROTECTED]
+44 (0)20 7488 3470
www.ascert.com
