<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.web.catalyst.general">
    <title>gmane.comp.web.catalyst.general</title>
    <link>http://blog.gmane.org/gmane.comp.web.catalyst.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19851"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19850"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19847"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19840"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19826"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19818"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19807"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19801"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19788"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19785"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19781"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19780"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19778"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19776"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19767"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19765"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19762"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19760"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19757"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.catalyst.general/19745"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19851">
    <title>Catalyst::Authentication::Credential::OpenID update;2.0 + SREG</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19851</link>
    <description>http://search.cpan.org/perldoc? 
Catalyst::Authentication::Credential::OpenID

Catalyst::Authentication::Credential::OpenID now supports -- thanks  
to Martin Atkins -- OpenID 2.0 as well as 1.1. Thanks to a patch from  
Menno Blom, C::A::C::OpenID also loads Simple Registration (SREG)  
data when it's present/configured.

I am not using this in the wild right now so I'd really appreciate  
any bug/problem tickets or Pod patches. If there are OpenID  
extensions other than SREG which anyone is using, please let me know  
so I can look at them and see if/how they can be supported.

-Ashley


_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Ashley</dc:creator>
    <dc:date>2008-12-02T19:38:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19850">
    <title>Creating a schema class for just one table</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19850</link>
    <description>Hi,

I'm wondering if there's a possibility of using the create helper script
to create a schema class for just one table. We're developing a site
with a cms and adding tables as they are specified, so the old schemas
really don't need to be updated. Besides, there are some cms-specific
tables that don't need to be used at all. (Yes, I know that they should
be in a different db altogether, but that's another issue.)

Also, the helper script regenerates a model class, which is completely
unnecessary.

Thanks in advance,
Alex

</description>
    <dc:creator>Alexander Tamm</dc:creator>
    <dc:date>2008-12-02T19:00:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19847">
    <title>Extra characters inserted into PDF output</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19847</link>
    <description>
Ive been working for a while to try to diagnose a problem with PDF display; i sent some messages to the list with the title "PDF upload problems (probably OT)", and Tom Doran has helped me a lot offlist.

After a lot of work and help from other people, ive sort of figured out what seems to be happening but still have no idea why, and if anyone has an idea im very eager to hear it!

My PDF files are being uploaded and saved in the database apparently correctly. Then what seems to be happening is that somewhere in the binary stream of PDF, there is a (random) sequence of "&lt;!", and somewhere later there is a "&gt;". And something is inserting a "--" before the "&gt;".

In other words something is apparently interpreting this as XML or HTML and trying to be 'helpful' by fixing malformed comments.

But i cant tell where this is happening. Ive now looked at it with four different browsers on three different operating systems and two different PDF renderers, and in all cases the output has those extra bytes, these dashes inserted as if to close HTML comments. 

My debugging statements show that Catalyst is outputting the correct size of the file, which suggests that the insertion is happening elsewhere. My view method looks like this:

sub view_document : Local {
  my ( $self, $c, $id ) = &lt; at &gt;_;
  my $source = $c-&gt;model-&gt;find($id);
  my $document = $source-&gt;document; # overloaded to $document-&gt;document
  $c-&gt;log-&gt;debug("Document contents were " . length($document) . " bytes");
  $c-&gt;res-&gt;output($document);
  $c-&gt;res-&gt;headers-&gt;content_type($document-&gt;type); # this is 'application/pdf' but setting this manually has no effect
  $c-&gt;res-&gt;headers-&gt;header('Content-Disposition' =&gt; "attachment; filename=".$document-&gt;filename); # dropping this also has no effect
}

Any ideas?

Thanks!

Jen


      

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Dr. Jennifer Nussbaum</dc:creator>
    <dc:date>2008-12-02T16:02:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19840">
    <title>Advent calendar</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19840</link>
    <description>Hi all,

The 2008 Catalyst advent calendar has started.  In general this year  
we will aim to have articles up by 12:00 UTC each day.

If you want to contribute an article, contact me (kd) on irc or via  
email.

Kieren

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Kieren Diment</dc:creator>
    <dc:date>2008-12-01T21:01:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19826">
    <title>ANNOUNCE: Progressive authentication attempts</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19826</link>
    <description>Hello All,

A new version of the Catalyst Authentication plugin is winging it's
way to CPAN (0.100091.)  This update includes the excellent
'Catalyst::Authentication::Realm::Progressive' realm written by J.
Shirley.

The Progressive Realm allows you to, with a single call to $c-
 &gt;authenticate(), make multiple authentication attempts one at a time,
until one of them succeeds (or they all fail.)  This allows you to
check multiple authentication realms to attempt to authenticate a user.

Some samples of how you might use this are:

1) Legacy authentication / migration to new system.  If you can't
merge the db's for whatever reason, you could try to authenticate
against the new system, followed by the legacy system.

2) Temporary passwords - If you have a separate auth method for
'temporary' auth - forgot password - initial confirmation, etc, you
can attempt to auth against the temporary password realm, then the
main db.  (or the other way around)

3) Auth against a local system, followed by a remote system if the
user is not found.

I'm sure you can come up with hundreds of other uses.

Please thank J. Shirley for his excellent module.

Jay

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Jason Kuri</dc:creator>
    <dc:date>2008-11-29T18:56:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19818">
    <title>Dispatching inCatalyst::Controller::SOAP::DocumentLiteralWrapped</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19818</link>
    <description>The POD for C::C::S::DLW says:

       A Document/Literal service is supposed to have one operation
per bind, as it's not techically possible
       to dispatch on the content of the Body. In fact, as the Body is
used as "literal" the dispatching should
       not even look at it, it should be based on the port that
received the request.

       RPC/Literal, on the other hand, supports the use of several
operations per bind, and the dispatching of
       this operations is based on the first and only child element of
the message body, which defines the
       operation. The arguments are set as the parts of the message in the WSDL.

       Document/Literal-Wrapped is a deviation of both, as the message
should be interpreted as Document/Lit-
       eral, but the dispatching requires an additional step of
looking at the SOAPAction HTTP header, which
       will identify the proper operation to be dispatched.

I am rather new to this SOAP affair - but according to
http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/ -
the dispaching in Document/Literal-Wrapped should be done on the first
and only child element of the message body, which defines the
operation just like in the RPC/Literal case.

Then formally you when you have a function of type A -&gt; ( B -&gt; C ) -
i.e. the RPC/Literal case - where the first parameter defines what
function is applied to the rest of arguments. Then you can always
uncurry it to (A, B) -&gt; C - that is you can have a function that takes
both parameters and returns the end result.  So if you treat the
dispatching as an internal affair in the server you can always say
that the function is of the right type for Document/Literal.


</description>
    <dc:creator>Zbigniew Lukasiak</dc:creator>
    <dc:date>2008-11-28T10:16:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19807">
    <title>OT Apache question</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19807</link>
    <description>
A few weeks ago I asked a series of questions about caching,
at the end of which discussion it was suggested that I use
Apache, instead of Cat with the Static::Simple plugin, to
serve my static files. I had tried this once before and ran
into problems and given up, so, the question:

I'd prefer to keep my current directory setup, in which I have
my Cat applications, in the usual configuration, under
/usr/local/www/modules. So, for example, my "incomings"
database is at /usr/local/www/modules/Incomings, its
templates are at /usr/local/www/modules/Incomings/root (so
Static::Simple serves them normally), the controllers are at
(for example)
/usr/local/www/modules/Incomings/lib/Incomings/Controller/Search.pm,
and so forth.

However my document root is at /usr/local/www/data, which
obviously does not include /usr/local/www/modules. So, if I
try to follow the Static::Simple suggestion of adding, say,

&lt;Location /Incomings/static&gt;
SetHandler default-handler
&lt;/Location&gt;

this obviously won't work because /Incomings/static isn't in
fact under my document root, it's in the filesystem at
/usr/local/www/modules/Incomings/root/static/. Trying this
just gives me 404's for all of the static stuff (CSS, images,
JS).

How do I configure Apache to serve these files, without
reorganizing what is by now a rather complicated directory
structure?

Thanks.

Jesse

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Jesse Sheidlower</dc:creator>
    <dc:date>2008-11-28T02:45:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19801">
    <title>Catalyst::Controller::SOAP "no operation `index' forportType" error</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19801</link>
    <description>Hi,

I have a SOAP controller based on WSDL.   Maybe I confused something
but I understood that I need to add

    # this is the endpoint from where the RPC operations will be
    # dispatched. This code won't be executed at all.
    # See Catalyst::Controller::SOAP::RPC.
    sub index :Local SOAP('RPCEndpoint') {}

to the controller (as described in the Synopsis).  And then  the
client will be allowed to call the root address and be despatched to
the right action based on the SOAP message (instead of using different
addresses for each action).

But with this addition compilation fails with the "error: no operation
`index' for portType {urn:calculator}SMSPortType, pick from ...".
Strictly speaking the message is true - there is no 'index' operation
defined in the WSDL - but I thought that this RPCEndpoint action would
be treated differently.


</description>
    <dc:creator>Zbigniew Lukasiak</dc:creator>
    <dc:date>2008-11-27T15:40:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19788">
    <title>Catalyst install failure due to Mouse.pm on Debian Etch</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19788</link>
    <description>Hi guys,
I'm having trouble getting Catalyst to install (via CPAN) on a fresh 
Debian Etch install.
The problem is the dependency Mouse (0.11) fails its unit tests there.
(I'd guess due to the older versions of some core packages).

I've raised http://rt.cpan.org/Ticket/Display.html?id=41254.

Catalyst::Action::RenderView (first module which was wanting Mouse) 
itself seems to pass its own unit tests after Mouse is force-installed, 
though.

Toby

</description>
    <dc:creator>Toby Corkindale</dc:creator>
    <dc:date>2008-11-27T00:47:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19785">
    <title>Plugin dependencies best practices</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19785</link>
    <description>_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
</description>
    <dc:creator>Eric Wright</dc:creator>
    <dc:date>2008-11-26T21:45:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19781">
    <title>Catalyst &amp; Chained talk at Orlando Perl Oasis - January17th, 2009</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19781</link>
    <description>Hello Catalysters,

I will be giving a talk on Catalyst and Chained, and how to best
design your applications using that technique.

You can give information on the conference at http://perloasis.org/opw/

Talk abstract is at http://perloasis.org/opw2009/talk/1691

Hope to see some folks there.

-J

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>J. Shirley</dc:creator>
    <dc:date>2008-11-26T20:14:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19780">
    <title>FormValidator and FV_eq_with constraint method</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19780</link>
    <description>
Hi,

I am relatively new to Catalyst and am having trouble getting the FV_eq_with
constraint method of Data::FormValidator to work.

my $f = $c-&gt;form(
        required =&gt; [qw/email password/],
        constraint_methods =&gt; {
        email =&gt; [ 
email()
],
password =&gt; FV_eq_with('confirm_password')
        },
        filters=&gt; ['trim']
    );

Data::Dumper output of the form method return value:

[debug] $VAR1 = bless( {
                 'profile' =&gt; {
                                'dependencies' =&gt; {},
                                'filters' =&gt; [
                                               'trim'
                                             ],
                                'defaults_regexp_map' =&gt; {},
                                'constraint_method_regexp_map' =&gt; {},
                                'constraint_methods' =&gt; {
                                                          'email' =&gt; [
                                                                       sub {
"DU
MMY" }
                                                                     ],
                                                          'password' =&gt; sub
{ "D
UMMY" }
                                                        },
                                'dependency_groups' =&gt; {},
                                'constraint_regexp_map' =&gt; {},
                                'constraints' =&gt; {},
                                'required' =&gt; [
                                                'email',
                                                'password'
                                              ],
                                'require_some' =&gt; {},
                                'field_filter_regexp_map' =&gt; {},
                                'field_filters' =&gt; {}
                              },
                 'validate_invalid' =&gt; [
                                         [
                                           'email',
                                           'email'
                                         ],
                                         'password'
                                       ],
                 '__FILTERED_DATA' =&gt; {},
                 '__INPUT_DATA' =&gt; {
                                     'email' =&gt; 'sa',
                                     'password' =&gt; 'a',
                                     'confirm_password' =&gt; 'a',
                                     'security_image' =&gt; '',
                                     'submit' =&gt; 'submit'
                                   },
                 'missing' =&gt; {},
                 '__CURRENT_CONSTRAINT_FIELD' =&gt; 'password',
                 '__CURRENT_CONSTRAINT_VALUE' =&gt; 'a',
                 'valid' =&gt; {},
                 '__CURRENT_CONSTRAINT_NAME' =&gt; 'eq_with',
                 '__UNTAINT_THIS' =&gt; 0,
                 'unknown' =&gt; {
                                'confirm_password' =&gt; 'a',
                                'submit' =&gt; 'submit'
                              },
                 'invalid' =&gt; {
                                'email' =&gt; [
                                             'email'
                                           ],
                                'password' =&gt; [
                                                'eq_with'
                                              ]
                              }
               }, 'Data::FormValidator::Results' );

I went into the Data::FormValidators Constraints.pm and found the constraint
routine.



sub FV_eq_with {
    my ($other_field) = &lt; at &gt;_;
    return sub {
        my $dfv = shift;
        $dfv-&gt;name_this('eq_with');

        my $curr_val  = $dfv-&gt;get_current_constraint_value;

        my $data = $dfv-&gt;get_filtered_data;
        # Sometimes the data comes through both ways...
        my $other_val = (ref $data-&gt;{$other_field}) ?
$data-&gt;{$other_field}[0] : $data-&gt;{$other_field};

        return ($curr_val eq $other_val);
    }

}


By hacking around in here, i can see that the reference to the
Data::FormValidator $dfv is not being passed. 

Does anyone have any pointers to help me get this working.

Many Thanks.
Darren.
</description>
    <dc:creator>darrenferguson</dc:creator>
    <dc:date>2008-11-26T16:12:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19778">
    <title>$c-&gt;request-&gt;params empty in Internet Explorer</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19778</link>
    <description>
Hello all,

I'm new to Catalyst and am loving the framework.

Using the built in development server and internet explorer
$c-&gt;request-&gt;params seems to be an empty hash - it works fine in firefox.

I am doing a $c-&gt;log-&gt;debug(Dumper($c-&gt;request-&gt;parameters)); in my
controller and the result looks like:

[debug] $VAR1 = {};


for the same post in FireFox I get:

[debug] $VAR1 = {
          'item' =&gt; 'dasda',
          'submit' =&gt; 'Submit Query'
        };

Which is what I would expect. I've used Charles HTTP monitor to ensure that
IE is posting correctly.

Any ideas?

Thanks.
Darren. 
</description>
    <dc:creator>darrenferguson</dc:creator>
    <dc:date>2008-11-26T14:16:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19776">
    <title>new catalyst features</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19776</link>
    <description>_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
</description>
    <dc:creator>Angel Kolev</dc:creator>
    <dc:date>2008-11-26T09:52:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19767">
    <title>"Can't call method "user_is_restorable"</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19767</link>
    <description>Hello,

I've encountered a problem with Catalyst::Plugin::Authentication
0.10008 that I can't seem to resolve.

When logging in or out now I get these error messages:

Caught exception in TCLegal::Controller::Logout-&gt;index "Can't call
method "user_is_restorable" on an undefined value at
/usr/local/libdata/perl5/site_perl/Catalyst/Plugin/Authentication.pm
line 169."

and

An error has occurred. We're terribly sorry about that, but it's one
of those things that happens from time to time. Let's just hope the
developers test everything properly before release...

Here's the error message, on the off-chance that it means something to
you: undef error - Can't call method "user_is_restorable" on an
undefined value at
/usr/local/libdata/perl5/site_perl/Catalyst/Plugin/Authentication.pm
line 169.

What am I doing wrong? I've updated all the modules I can think of,
and nothing seems to fix this problem.

It happens under mod_perl with an Apache Virtualhost configuration,
and also under the test server.


use parent qw/Catalyst/;
use Catalyst qw/-Debug
                ConfigLoader
                Static::Simple
                StackTrace

                Authentication
                Authorization::Roles
                Authorization::ACL

                Session
                Session::Store::FastMmap
                Session::State::Cookie

                /;

and here's the code around my -&gt;authenticate call:

sub index :Path :Args(0) {
    my ($self, $c) = &lt; at &gt;_;

    # Get the username and password from form
    my $username = $c-&gt;request-&gt;params-&gt;{username} || "";
    my $password = $c-&gt;request-&gt;params-&gt;{password} || "";

    # If the username and password values were found in form
    if ($username &amp;&amp; $password) {
        # Attempt to log the user in
        if ($c-&gt;authenticate({ username =&gt; $username,
                               password =&gt; $password} )) {
            # If successful, then let them use the application
            $c-&gt;response-&gt;redirect($c-&gt;uri_for('/'));
            return;
        } else {
            # Set an error message
            $c-&gt;stash-&gt;{error_msg} = "Bad username or password.";
        }
    }



Thanks for any advice,

- Mark Beihoffer

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Mark Beihoffer</dc:creator>
    <dc:date>2008-11-25T17:35:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19765">
    <title>[Announce] MojoMojo 0.999023</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19765</link>
    <description>_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
</description>
    <dc:creator>Marcus Ramberg</dc:creator>
    <dc:date>2008-11-24T20:24:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19762">
    <title>Moosified Form::Processor</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19762</link>
    <description>I've Moosified Form::Processor and will eventually release it as a 
development release to CPAN, followed by an "official" release at some 
point.

If anybody would like to investigate the package now, let me know and 
I'll send you a copy. It has a number of additional features, some doc 
improvements, and more tests. I also have a Catalyst base controller (to 
use instead of the plugin) which will be released in a separate package 
that I'll make available later this week.

On my systems it required no changes to existing code to use. Feedback 
would be welcome.

Gerda Shank



_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Gerda Shank</dc:creator>
    <dc:date>2008-11-24T17:45:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19760">
    <title>Making subrequests in views</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19760</link>
    <description>Hi,

I'm pretty new to Catalyst and new to this mailing list. In other words, 
my apologies if this question has been frequently answered or if I've 
missed the relevant documentation.

My basic setup is a Catalyst application running under FastCGI, using 
View::Mason for my views. I need to include a navigation component in 
most - not all - views, so I'm thinking about what strategy I should use 
to populate the stash with the correct data. As I see it, I have at 
least three options, but I'm not sure how smart they are.

1) I could always populate the stash in auto() and call the 
corresponding Mason component when needed. This means fetching some data 
even if it isn't needed.

2) Calling $c-&gt;forward( '/navi' ) in my navi view

3) Using Catalyst::Plugin::Subrequest and doing a subrequest-call from 
the view that needs to include the navi component.

Are these all equeally smart/stupid, or is there a best practice for this?

Thanks in advance,
Alex

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Alexander Tamm</dc:creator>
    <dc:date>2008-11-23T09:29:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19757">
    <title>Mapping CGI scripts URLs</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19757</link>
    <description>Hi Everybody,

I have ported an old CGI-script based application to Catalyst, and would
like to continue to support the old interface, which means that I have
URLs such as:

    http://server/cgi-bin/script.cgi

which now should get mapped to '/cgi/script', which is handled by my Cgi
Controller and it's script function (have multiple of these scripts).

I know how to use for instance Apache with RewriteEngine to get this
done, however, then the Catalyst own server does not work; which I use a
lot for development.
Thus, I though I could just define a similar rewriting in the default
method of the Root-Controller, which kind of works, but not if I use
URLs that end on '.cgi'. For everything else (.CGI, .pl, ...), default
is called, but just not for '.cgi'. Which apparently immediately closes
the connection with no reply (also no debug message is created, or
anything).

I assume this is some kind of strange safety feature? 
Unfortunately, I was not yet able to find where in the code this happens
and how I turn this off.
Can anyone out there help me with this?

Googling for variations of 'catalyst dispatcher .cgi close' was not very
successful (too many unrelated hits) as was a find/grep through the
Catalyst sources for '.cgi'.

Christian


_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Christian Lackas</dc:creator>
    <dc:date>2008-11-21T18:57:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19745">
    <title>need to patch Test::WWW::Mechanize::Catalyst</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19745</link>
    <description>My recent patch to 5.80 trunk (svn rev 8612) enables the setting of a
default virtual hostname via import:

   use Catalyst::Test 'MyApp', { default_host =&gt; 'virtual.com' };

Based on my reading of the Test::WWW::Mech::Catalyst source, some minor
changes would need to be made there in order to use the same semantics
with Mech::Cat. Should I try to patch this myself, or is there a 
maintainer out there who can make it happen?

Thanks!
Jason

--
Jason Gottshall
jgottshall&lt; at &gt;capwiz.com




_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Jason Gottshall</dc:creator>
    <dc:date>2008-11-19T20:21:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.catalyst.general/19742">
    <title>One App, multiple databases</title>
    <link>http://comments.gmane.org/gmane.comp.web.catalyst.general/19742</link>
    <description>Hello,

This question has been asked a couple of times on the list, and I have 
found yet another solution to it, but I would like to hear if maybe I'm 
doing something wrong, or I will suffer serious pain by doing it my way :)

We have an app that will connect to one database or another depending on 
the logged in user.

My solution:

package App::Model::DB;

use strict;
use base 'Catalyst::Model::DBIC::Schema';
...
sub ACCEPT_CONTEXT {
     my ($self, $c) = &lt; at &gt;_;

     my $user_db = $c-&gt;lookup_the_users_db();
     $self-&gt;config-&gt;{'connect_info'}-&gt;[0] =~ s/#DATABASE#/$user_db/;
     $self-&gt;schema-&gt;connection(&lt; at &gt;{$self-&gt;config-&gt;{'connect_info'}});

     return $self;
}


1;

I've done the same with Catalyst::Model::DBI:

package App::Model::AnotherDB;

use strict;
use base 'Catalyst::Model::DBI';

sub ACCEPT_CONTEXT {
     my ($self, $c) = &lt; at &gt;_;

     my $user_db = $c-&gt;lookup_the_users_db();
     $self-&gt;{'dsn'} =~ s/#DATABASE#/$user_db/;

     return $self;
}

1;

And the two seem to be working OK, but I'm worried about what will 
happen when we fire it up in a FastCGI environment (I suspect the 
connection to  user1's database will be kept live, and the next user 
will get the connection to it). Am I right? Any pointers?

Does this way of using the models trigger any warning lights to Catalyst 
gurus?

Thanks in advance,

Jose Luis Martinez
jlmartinez&lt; at &gt;capside.com

_______________________________________________
List: Catalyst&lt; at &gt;lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst&lt; at &gt;lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

</description>
    <dc:creator>Jose Luis Martinez</dc:creator>
    <dc:date>2008-11-19T17:54:01</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.catalyst.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.catalyst.general</link>
  </textinput>
</rdf:RDF>
