[MGNLDATA-77] the module fails to startup if the workflow module is not installed Created: 08/Oct/09 Updated: 16/Dec/13 Resolved: 16/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | 1.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Mikaël Geljić |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
The activation configuration should depend on the presence of the workflow module 2009-10-08 16:27:48,376 WARN gnolia.content2bean.impl.Content2BeanProcessorImpl: can't resolve class for node /modules/data/commands/data/activate/startFlow java.lang.ClassNotFoundException: info.magnolia.module.workflow.commands.ActivationFlowCommand at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1360) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374) |
| Comments |
| Comment by Jan Haderka [ 08/Oct/09 ] |
|
Or better, this should not get installed/bootstrapped if the workflow is not installed same as the tree configuration/commit dialog |