I found the problem and it wasn't RIFE, Maven or Jetty's fault. I install the rife jar into my Maven repository wrongly...
Take care,
Jeremy
P.S. - What do you expect when it is 2:00 a.m.. .
On 10/6/06, Geert Bevin <[EMAIL PROTECTED]> wrote:
Hi Jeremy,
are you sure that the RIFE jar is copied also to the staging directory? I
really think that this is a very simple case of the jar not being part of
the classpath, you just have to eliminate all the possible culprits.
Take care,
Geert
Jeremy Whitlock wrote:
>
> This will build a
> staging directory and will run Jetty aware of this staging directory. I
> am
> not passing the rife.webapp.path . It shouldn't matter since the web app
> is
> being found and it is up to the servlet container to load RIFE and to the
> servlet container, everything is setup properly.
>
--
View this message in context: http://www.nabble.com/RifeFilter-Not-Found-tf2396742.html#a6688309
Sent from the RIFE - users mailing list archive at Nabble.com.
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
_______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
