your right, it seems to have something todo with the connection. If I
change it to "~" or just an arbitary string, it works. But with the
"default" setting it creates the infinite loop.

Looking at the container I think I can see the problem, gt

    [aliases:protected] => Array
        (
            [security.acl.dbal.connection] =>
Symfony\Component\DependencyInjection\Alias Object
                (
                    [id:protected] => doctrine.dbal.default_connection
                    [public:protected] => 1
                )

           [ ... ]

            [doctrine.dbal.default_connection] =>
Symfony\Component\DependencyInjection\Alias Object
                (
                    [id:protected] => security.acl.dbal.connection
                    [public:protected] => 1
                )

        )

As the second alias is generated with "doctrine.dbal.%s_connection" so
"default" conflicts with the doctrine default_connection entry and
creates the inifinte loop ... I think. A "working" version looks like
this:

    [aliases:protected] => Array
        (
            [security.acl.dbal.connection] =>
Symfony\Component\DependencyInjection\Alias Object
                (
                    [id:protected] => doctrine.dbal.default_connection
                    [public:protected] => 1
                )

            [ ... ]

            [doctrine.dbal.foo_connection] =>
Symfony\Component\DependencyInjection\Alias Object
                (
                    [id:protected] => security.acl.dbal.connection
                    [public:protected] => 1
                )

        )


On 19 January 2011 09:18, stof <[email protected]> wrote:
> On Wed, 19 Jan 2011 09:06:00 +0000, Dan Leech <[email protected]>
> wrote:
>> I am trying out the ACL functionality and having some difficulties...
>>
>> 1. The documentation specifies that you specify the connection in
>> `app/config/security.yml` as follows
>>
>> security.acl:
>>     connection: default
>>
>> But this has no effect -- Im guessing that it should be in
>> `config.yml`, error in the docs?
>>
>
> Defining it in security.yml or config.yml is exactly the same as
> security.yml is imported in config.yml.
> The only purpose of the security.yml file is to separate the security
> config from your other config but you could put all the security config in
> config.yml.
>
> The connection parameter links to a DBAL connection so check it is
> correctly defined.
>
> --
> Christophe | Stof
>
> --
> If you want to report a vulnerability issue on symfony, please send it to 
> security at symfony-project.com
>
> You received this message because you are subscribed to the Google
> Groups "symfony developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
>



-- 
Dan Leech

Web Developer
www.dantleech.com

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en

Reply via email to