Bug #11366
Invalid configuration option "factoryClassName"
Status: | Closed | Start date: | 2010-12-09 | |
---|---|---|---|---|
Priority: | Must have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - |
Description
Invalid configuration option "factoryClassName" in Objects.yaml in the blog example
Correct setting is "factoryObjectName". Found this here [1].
History
#1 Updated by Stefano Kowalke over 4 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.
#2 Updated by Robert Lemke almost 4 years ago
- Status changed from New to Closed