[LogicException] Container extension "jms_serializer" is not registered

[minixxie]

Hi Johannes,

with Symfony2.0.x, I've followed the doc: http://jmsyst.com/bundles/JMSSerializerBundle
from Installation, Configuration...

and I got this when running "php bin/vendor install":

[LogicException]
Container extension "jms_serializer" is not registered

Could you pls help give some advice? Thanks.
I've also added the sample configuration into app/config/config.yml

[stof]

Did you register the JMSSerializerBundle in your kernel ?

[schmittjoh]

Please use the 0.9 tag for Symfony2.0.

The master branch is not compatible with 2.0 anymore.

[minixxie]

Yes, already registered the bundle in kernel.

And I have added a tag 0.9.0:

[JMSSerializerBundle]
git=git://github.com/schmittjoh/JMSSerializerBundle.git
target=bundles/JMS/SerializerBundle
version=0.9.0

And then got another problem:
Fatal error: Class 'Metadata\Driver\LazyLoadingDriver' not found in /path/to/appDevDebugProjectContainer.php on line 1206

And inside the Metadata\Driver\ I couldn't find the LazyLoadingDriver.php, but I followed the doc to specify 1.1.0 for meta:

[metadata]
git=http://github.com/schmittjoh/metadata.git
version=1.1.0

and this is the git log inside metadata:

commit 8717ad2a5689480765d9ffafe925cd8a2457e582
Author: Johannes Schmitt [email protected]
Date: Sat Jul 9 09:34:18 2011 +0200

release 1.0.0

commit c060e62ace2c75a18e8a64f0febd166cced2027c
Author: Johannes Schmitt [email protected]
Date: Sat Jul 9 09:33:51 2011 +0200

added version file

commit aa04872c6f0e2b32128b62dd075e8cf97a8d93da
Author: Johannes M. Schmitt [email protected]
Date: Thu Jun 16 14:57:43 2011 +0200

added a test for cache invalidation

Sorry, I'm still new to sf2 framework, could you pls give me some advice? Thanks.

[minixxie]

wow, I have it fixed. Thanks. That's my fault that I haven't fixed deps.lock

It worked after removing:
metadata 8717ad2a5689480765d9ffafe925cd8a2457e582

this is always a question to me why deps.lock and the version=??? work together. They seem to be the same thing to control the version.

[stof]

@minixxie The version= in deps specifies the version used when running bin/vendors update (which is then locked in deps.lock). So when using a branch, deps will reference the branch name whereas deps.lock will reference a commit (which was the state of the branch at the time it was locked)

[minixxie]

thank you very much ;)
It still seem no luck after this fix. The memory is exhausted. I have opened another issue.