Hey Stefan,
as you see the the ldap gives me the correct result, till the Dancer module is not loaded.
I think it is a Dancer error not an ldap.
I created a more simple test case:
battila@igornb:~$ dancer -a MyWeb::App
...
battila@igornb:~$ cd MyWeb-App
battila@igornb:~/MyWeb-App$ vi lib/ChrachterMistake.pm
#!/usr/bin/perl -w
package ChrachterMistake;
use strict;
use warnings;
sub gimmySomething {
return "Bárdi Attila";
}
1;
battila@igornb:~/MyWeb-App$ vi lib/MyWeb/App.pm
package MyWeb::App;
use Dancer ':syntax';
use ChrachterMistake;
our $VERSION = '0.1';
get '/' => sub {
return ChrachterMistake::gimmySomething();
};
true;
battila@igornb:~/MyWeb-App$ perl ./bin/
app.pl
[9950] core @0.000010> loading Dancer::Handler::Standalone handler in /usr/share/perl5/Dancer/Handler.pm l. 45
[9950] core @0.000181> loading handler 'Dancer::Handler::Standalone' in /usr/share/perl5/Dancer.pm l. 474
>> Dancer 1.311 server 9950 listening on
http://0.0.0.0:3000== Entering the development dance floor ...
With browser I connect to the
http://localhost:3000/ and the result is:
Bárdi Attila
The Dancer does something with the return value of the function.
No ldap in the chain at all.
Best regards,
Attila