Bug #922
Eclipsoid component is not started when some other web app fails
100%
Description
Steps to reproduce:
Create new z2 web project using the Eclipsoid wizard and arm it.
It will create a new project with an "invalid" webapp.path property inside web/z.properties
Leave the invalid webapp.path value and start the server. Starting the new web app will fail because of the invalid context name.
However Eclipsoid isn't started as well!
Updated by
Updated by Henning Blohm almost 12 years ago
More specifically:
When adding a component as dependency to a worker target state and that component fails, any other participation to that state will not be followed.
Root cause is that the core-level dependency preparation already fails and so the prepare step of the state component itself will not be run.
Updated by Henning Blohm almost 12 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset z2-core:245505b67f2dd092e2672817aef19cf887e0ab51.
Updated by Henning Blohm almost 12 years ago
- Status changed from Resolved to In Progress
- there is too many query activities when looking for generic participation,
- there is a lot of semantics creeping into component resource wrapper, in particular about IDependencyComponent
Updated by Henning Blohm almost 12 years ago
- Status changed from In Progress to Resolved
Applied in changeset z2-core:09b75f0a173a9fc9db6f3279c4b0d471fd7bb0b0.