Re: [Mason] creating an ApacheHandler with a Resolver object

[Kwindla H. K. <kw...@al...>]

Dave Rolsky writes:

 > I think the problem is that you're passing comp_root, not resolver.  You
 > should be passing comp_root to the resolver when you create it.  If you
 > pass an object (resolver) instead of a class name (resolver_class) then
 > the ApacheHandler won't accept parameters for the resolver's class.
 > 

I tried that, too, and get a different error on startup:

#

my $resolver = HTML::Mason::Resolver::File::ApacheHandler->new
  (
   comp_root      => '/allafrica/webtree',
  );

my $ah_show_error = HTML::Mason::ApacheHandler->new
  (
   resolver       => $resolver,
   data_dir       => '/usr/local/apache/mason_data',
   error_mode     => 'output',
  );

#

[Thu Feb 13 16:27:40 2003] [error] The following parameter was passed in the call to HTML::Mason::ApacheHandler->new() but was not listed in the validation options: resolver_class
Compilation failed in require at (eval 4) line 1.

Syntax error on line 72 of /usr/local/apache/conf/httpd.conf:
The following parameter was passed in the call to HTML::Mason::ApacheHandler->new() but was not listed in the validation options: resolver_class
Compilation failed in require at (eval 4) line 1.

--

There's some complexity to the code path that ApacheHandler goes
through at initialization. I don't completely understand what's going
on -- perhaps this is my cue to sit down and become conversant with
how Class::Container works. I tried every combination of parameter
passing to Resolver, Interp and ApacheHandler, and am able to create
several different kinds of error, but no working test case.

Is this something that folks have actually done, or has
'resolver_class' sufficed thus far? (It might also be worth mentioning
that 'resolver_class' is no longer mentioned as a valid parameter in
the HTML::Mason::ApacheHandler POD.)

Kwin