Navigation

RSS 2.0 New Entries Syndication Feed Atom 0.3 New Entries Syndication Feed

Show blog menu v

 

General

Use it

Documentation

Support

Sibling projects

RIFE powered

Valid XHTML 1.0 Transitional

Valid CSS!

Blogs : Archives

< Slides for "Web continuations in Java with RIFE"   Flaky file URL objects with JDK 1.4 on windows >
RIFE 1.3.1 released

Below are the highlights:

  • Workaround for JDK 1.4 bug on Windows [ more ]
  • Bug-fixes to some new features that 1.3 offered [ more ]
  • Support for Derby network driver [ more ]

You can read the full changelog for more details.

If you are upgrading from a pre-1.3 release, it's a good idea to also read the 1.3 release announcement.

Workaround for JDK 1.4 bug on Windows

It turned out that people that were using RIFE on Windows with JDK 1.4 experienced very slow startup times and sometimes applications didn't even complete the startup sequence at all. Since nobody of the development team actually uses this OS and JDK combination, we never were aware of this issue until users reported it this week. It turned out that URLs with the syntax: file://C:/path/file cause JDK 1.4 to lookup C as a hostname. Of course this fails, but the timeout for doing so is by default 5 minutes. Imagine what happens when there's a number of entries like this ...

Anyway, we implemented a workaround and this issue is now a thing of the past.

[ top ]

Bug-fixes to some new features that 1.3 offered

Small bugs were fixed in new features of the previous release.

[ top ]

Support for Derby network driver

The Derby network driver is now supported alongside with the embedded JDBC driver.

[ top ]

Full changelog

2005-12-23  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * RELEASE 1.3.1

2005-12-22  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * Workaround to force JDK 1.4 on Windows to correctly interpret
  file://C:/location URL specs.

2005-12-20  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * Added support for Derby network client JDBC driver+

  * RIFE-259 : clearOutput pathinfo input doesn't clear the output
  This bug only appeared for flowlinks that targeted their originating element

2005-12-19  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * Fix to content syndication framework where the Entry ID property didn't
  have the appropriate meaning.

2005-12-18  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * Fixed auto-templating bug

2005-12-15  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * Added getInputSerialized method to ElementSupport.

2005-12-09  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * Minor build file fix

2005-12-09  Geert Bevin  <gbevin[remove] at uwyn dot com>

  * RELEASE 1.3

[ top ]

posted by Geert Bevin in RIFE on Dec 22, 2005 4:32 PM : 2 comments [permalink]
 

Comments

Re: RIFE 1.3.1 released
Geert,

I found this site from your exchanges on a comment thread discussing ruby.

I just watched the rife swf walkthrough and browsed a lot of the documentation material. It's very impressive. But I'm having a hard time figuring out if the rife developer community is just you, and if it's been used on large projects that didn't include you. Are there others?

Also, if there's some material about how rife integrates with any of the dozens of other webapp frameworks and technologies (JSP, JSF, etc.,) , I'd be keen to know that as well.

There are so many frameworks already, the head spins...
Re: RIFE 1.3.1 released
Hi Alexis, I suggest that you join the mailing list and ask the other users about what they use RIFE for. We can discuss the integration there too.

Add a new comment

Comments on this blog entry have been closed.

< Slides for "Web continuations in Java with RIFE"   Flaky file URL objects with JDK 1.4 on windows >
 
 
 
Google
rifers.org web