Okay, I will reply with an update when we have tried this. Thanks.
-Eskil
On 4/13/07, Geert Bevin <[EMAIL PROTECTED]> wrote:
> Just remove the old RIFE jar and put the new one in.
>
> On 13 Apr 2007, at 11:19, Eskil Lauritsen wrote:
>
> > We're using the jumpstart project on the main download page.
How can
> > we update the RIFE version of the jumpstart project?
> >
> > Sincerely
> > Eskil Lauritsen
> >
> >
> >
> > On 4/13/07, Geert Bevin <[EMAIL PROTECTED]> wrote:
> >> Hi Eskil,
> >>
> >> would you mind sending me an archive of your sources in
private. Then
> >> I can try this out. What you're describing just works for me,
nothing
> >> hangs here.
> >>
> >> Take care,
> >>
> >> Geert
> >>
> >> PS.: which version of RIFE are you using? You might want to
try a
> >> nightly snapshot, they're much more advanced than the 1.5.1
release
> >>
> >> On 13 Apr 2007, at 09:32, Eskil Lauritsen wrote:
> >>
> >> > Hi again
> >> >
> >> > We have an example now:
> >> >
> >> > If we try to use view a page when we have omitted the lines
> >> >
> >> > import
> >> >
com.uwyn.rife.authentication.credentialsmanagers.RoleUserIdentity;
> >> > import com.uwyn.rife.authentication.elements.Identified;
> >> >
> >> > from our Home.java file, we get the problem with the
browser just
> >> > hanging and no errors being outputted in Eclipse nor by RIFE.
> >> >
> >> > Sincerely,
> >> > Eskil Lauritsen
> >> >
> >> > On 4/13/07, Eskil Lauritsen <[EMAIL PROTECTED]> wrote:
> >> >> Hello, Geert
> >> >>
> >> >> We're on Windows XP SP2 and 2003 (using terminal clients),
JVM
> >> >> 1.5.0_06
> >> >>
> >> >> We have figured out that RIFE only compiles Elements on
the fly
> >> (we
> >> >> had a problem with an executor class not compiling), and
we don't
> >> >> have
> >> >> any of these problems at the moment. I just asked the
question in
> >> >> preparation of our continued coding. I will reply to this
> >> thread when
> >> >> we have new occurrence of this problem.
> >> >>
> >> >> Thanks for your continued patience.
> >> >>
> >> >> -Eskil
> >> >>
> >> >> On 4/13/07, Geert Bevin <[EMAIL PROTECTED]> wrote:
> >> >> > Hi Eskil,
> >> >> >
> >> >> > can you tell me which OS you're using and which JVM? Also,
> >> can you
> >> >> > give an example of the Java compilation error that
doesn't show
> >> >> up in
> >> >> > the browser? RIFE only recompiles your elements on-the-fly,
> >> not any
> >> >> > other Java code. However, if there are compilation
errors for
> >> any
> >> >> > elements, it should show up in your browser.
> >> >> >
> >> >> > As Mork says, you can of course have written some code that
> >> creates
> >> >> > an endless loop and simply hangs the JVM.
> >> >> >
> >> >> > With a real example we can say more.
> >> >> >
> >> >> > Take care,
> >> >> >
> >> >> > Geert
> >> >> >
> >> >> > On 13 Apr 2007, at 02:00, Eskil Lauritsen wrote:
> >> >> >
> >> >> > > Hi!
> >> >> > >
> >> >> > > I was wondering if it is possible to have RIFE output
not only
> >> >> RIFE-
> >> >> > > related
> >> >> > > errors but also java compilation errors. We use the
latest
> >> rife-
> >> >> > > jumpstart
> >> >> > > Eclipse project that is linked to under Downloads on
> >> rifers.org.
> >> >> > >
> >> >> > > Now if we have a pure java error (that is, an error not
> >> >> related to
> >> >> > > RIFE),
> >> >> > > the browser only hangs.
> >> >> > >
> >> >> > > This is my third attempt at sending this to the list. I
> >> hope this
> >> >> > > change of email address will do the trick!
> >> >> > >
> >> >> > > Sincerely
> >> >> > > Eskil Lauritsen
