Hi Jeremy,
> 1. As long as the paths are on the classpath when Jetty/RIFE
> starts, then we should be good to go right? As for adding/removing/
> reordering participants, will this be necessary with the Jumpstart
> or should that be part of the bigger rife-ide plugin and the
> functionality for this plugin only allows for quick/easy RIFE
> development?
It's not exactly the same, a servlet container has a hierarchy of
classloaders. RIFE's classloader automatically instruments all the
classes in the web application. It doesn't instrument anything
outside since that would be a needlessly high performance hit. That's
where the rife.webapp.path java property comes into play, to indicate
to RIFE which paths are to be considered part of the webapp when the
classes are not situated in a classic WEB-INF hierarchy.
> 3. Really depends on question 1 and since deployment is handled by
> RIFE, there is no need to use the Server Type if we do not have
> reason.
I think we discussed and decided this on IRC now.
> 4. This plugin will not extend any part of WTP if we decide not to
> create a Server Type. That being said, this plugin will not affect
> WTP in any way.
>
> I think the concensus is to create our own approach for handling
> RIFE in Eclipse instead of creating a WTP Server Type. I'll start
> a new thread on the new questions that follow with the new approach
> unless we change our mind.
Ok, sounds like a good approach.
Take care,
Geert
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
