|Re: [jetty-users] New user best practice: getting started w/ spring|
Could someone give me a quick rundown of the best practice for starting
Jetty as a standalone app/web server? I’m migrating an app that uses the
I was confused with the docs regarding startup, they all seem to refer to
start.config, but in looking at the 7.1.6 build from Codehaus (I guess this
is the right package since it includes some Spring support) all I see is a
start.ini which appears very different.
It seems like using the start.jar is a fine way of doing things (especially
with easy support for kicking off the spring framework), but using it is a
little awkward with regards to where everything should reside, paths, etc.
Should I build my project under the directory structure that the jetty
package creates by default?
How’d you all go about it? Tomcat’s more structured and easier to follow,
but I have a low memory requirement so I thought I’d give Jetty a go here.
Also, the codehaus site and the eclipse site disagree about the status of
Jetty 7, codehaus suggesting it is “Almost Stable”, and eclipse labeling it
“Stable”. What should a new user think? Docs mostly seem to support 6 as
I’ve seen so far.
Thanks for some help pointing the newbie in the right direction out of the
jetty-users mailing list
Back to the top