Well, what's you suggestion? Currently, I'm hand-syncing with the
webapps directory of Resin. I'd prefer to do a `ln -s PATH1/exploded
PATH2/resin/webapps' to avoid the handwork...
What's the best practice here? Do you all have an embedded Jetty?
That's
not feasible for me in the end, as I'm going to use some of Resin's
features.
Jetty is not embedded into the jumpstart, it's just shipped with it
and set up so that the source dirs are a top-level dir (http://
rifers.org:8088/browse/rifers/rife-jumpstart/branches/jdk15/
jetty-5.1.4/etc/jetty.xml?r=3260#l156 and http://rifers.org:8088/
browse/rifers/rife-jumpstart/branches/continuations-example/build.xml?
r=3317#l268). The additional rife.webapp.path JVM property is needed
so that RIFE can determine which classes in the classpath are part of
the webapp (instead of checking for a resource to be inside WEB-INF).
The easiest way to setup a development environment for another
servlet container is to just develop inside WEB-INF/classes. You will
have to setup nothing then, not even the rife.webapp.path JVM property.
Hope this helps,
Geert
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
