Yes it's indeed a bug. Fixed by https://github.com/symfony/symfony/pull/7424
Thanks.

Am Freitag, 15. März 2013 10:56:13 UTC+1 schrieb Arthur Purnama:
>
> Hi,
>
> I am a newbie in Symfony 2 Right now i'm testing symfony 2.2.0. Im using 
> PhpStorm IDE to support my work.
> I like using XML instead of YAML because of the Autocompletion in this 
> case. Thats why i'm trying to convert the YAML config files to XML.
>
> You can see the result here:
> https://github.com/purnama/kateglo/tree/master/app/config
>
> during my test i discover an error as i try to run the application.
> THE XSD file symfony-1.0.xsd have an attribute definition 
> strict-parameters.
> symfony 2.2.0 doesn't recognize this attribute. if i change the attribute 
> definition to strict-requirements everything is fine.
>
> is this a bug on symfony 2.2.0?
>
> My next question is. is there any xsd for security configuration and the 
> jms bundle? my security.xml that i define here
> https://github.com/purnama/kateglo/tree/master/app/config
>
> is running fine ( or i just not find the problem yet). But i can not use 
> autocompletion in this case and the xml example in the website about 
> security is not really helpful.
> The example is not showing the xsd to.
>
> regards,
> Arthur Purnama
>

-- 
-- 
If you want to report a vulnerability issue on Symfony, please read the 
procedure on http://symfony.com/security

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Symfony developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to symfony-devs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to