Re: planning release, Re: updating license headers - what's next?

Shouldn't we go for broke and move to 1.5 ? 1.5 has a bunch of language
features that very nice, and has been out sense 2004-09-29

Todd

On 3/6/07, Vadim Gritsenko <[email protected]> wrote:
>
> Georg Sauer-Limbach wrote:
> >
> >>> Speaking of next version... Are there any plans for new release?...
> >> There are also other loose ends - like document caching, meta data
> >> handling, etc - which is good to have fixed before release.
> >
> > There is the problem that changes to the database that are made
> > via the local interface (command line) are not reflected in a
> > running server instance, i.e. in Tomcat. Maybe this makes a
> > candidate for nice-to-fix?
>
> No, this one does not. But bring in other suggestions :)
>
> Regarding your problem. You should never attempt to open database files
> from two
> processes, such as Tomcat & command line tool with -l switch, since that
> will
> corrupt your database. If you are running instance of db in Tomcat, use db
> URL
> in the command line to access this running instance, instead of -l switch
> [1]:
>
>    ./bin/xindice lc -c xmldb:xindice://localhost:8080/db
>
> BTW, have you tried the latest trunk? If you are using windows it should
> prevent
> you from concurrently accessing same database files from different
> processes. It
> does not work for me in OS X though... When Xindice drops minimum java 1.3
> requirement, we could use java 1.4's new file I/O to make file locking
> work on
> all platforms.
>
> Regards,
> Vadim
>
> [1] http://wiki.apache.org/xindice/XindiceFAQ/XindicePort
>