On 11/8/05, Kieren Diment <[EMAIL PROTECTED]> wrote:
>
>
> According to my docs (I suppose 2.10, although I'm not suer) I'm
> supposed to:
>
> package Foo;
> use base 'Maypole::Application';
> use Foo::SomeTable;
> use Foo::Other::Table;
>
> Foo->config->model("Maypole::Model::CDBI::Plain");
> Foo->setup([qw/ Foo::SomeTable Foo::Other::Table /]);
>
>
That is the synopsis. I wonder if the Namespace is significant. I
bet it is not. As there is Foo::SomeTable and Foo::Other::Table.
Probably all that may be significant and in a small (tiny template
finding) way is the moniker of the classes should be unique.
> >
> >
> >> My brief experiment showed me that the untaint statements don't work
> > [snip]
> > ... How about Exported actions though? What
> > if you have Exported actions before setup is called ? does it die?
>
>
> Maybe this is symptomatic of the whole problem. Indeed, when I add
It definitely is. What happens when you require your classes as in
solution A that i suggested?
--
pjs
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Maypole-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-users
