Forum OpenACS Q&A: Running OpenACS with Naviserver 4.99.0

Hi all,

has anyone experience with running OpenACS with Naviserver?

I downloaded the src from sourceforge and the modules from the AOLServer project at sourceforge. Compilation worked without any problem.

Also the sever starts without any error.

But when I open the browser I get the following error:

[21/Dec/2005:19:30:50][13702.1092311984][-conn:oacs-5-2::0] Error: wrong # args: should be "rp_filter why"
wrong # args: should be "rp_filter why"
while executing
"rp_filter {} preauth"
[21/Dec/2005:19:30:50][13702.1092311984][-conn:oacs-5-2::0] Error: wrong # args: should be "rp_invoke_filter conn filter_info why"
wrong # args: should be "rp_invoke_filter conn filter_info why"
while executing
"rp_invoke_filter {0 0 3 ds_trace_filter {}} trace"

Also there seems to be a scheduled proc running called search::indexer with results in a error:

[21/Dec/2005:19:31:19][13702.1136438192][-sched:14-] Error: invalid command name ""
invalid command name ""
while executing
"{}"
("eval" body line 1)
invoked from within
"eval [concat [list $proc] $args]"
(procedure "ad_run_scheduled_proc" line 42)
invoked from within
"ad_run_scheduled_proc {{t f 60 search::indexer {} 1135189819 0 f}}"
while executing callback
ns:tclschedproc ad_run_scheduled_proc {{t f 60 search::indexer {} 1135189819 0 f}}

More on this later.

The argument passing for filters is different in naviserver, in addition, the useless conn arguments are removed. The removal of the useless arguments is certainly an improvement, the argument passing of aolserver for filters is something one has to read a couple of times to understand it partially (most probably the docs are wrong). The argument passing for filters is much simpler with naviserver, but i am not completely happy with this (will talk to the naviserver people about this).

Only very few changes in request-processor-procs.tcl and utilities-procs.tcl were necessary. I have placed these into conditional code that is only executed under naviserver. Since the change can hardly break existing code (famous last words?) i have committed the changes to oacs-5-2.

Packages with their own filters will need similar changes. I have locally updated the request monitor accordingly, i will release it in a couple of days.