Bug #11366
Invalid configuration option "factoryClassName"
Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-12-09
Due date:
% Done:
0%
Estimated time:
Description
Invalid configuration option "factoryClassName" in Objects.yaml in the blog example
Correct setting is "factoryObjectName". Found this here [1].
Updated by Stefano Kowalke over 11 years ago
I just realized, that I used an outdated version of the blog example which I downloaded as mentioned in the Getting Started tutorial. So this issue can be closed.