Bug #922
Eclipsoid component is not started when some other web app fails
Added by Udo Offermann about 12 years ago.
Updated over 11 years ago.
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!
- Priority changed from High to Urgent
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.
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to In Progress
re-opening. dependency handling is not clean when done generically on component level as:
- 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
- Status changed from In Progress to Resolved
- Status changed from Resolved to Closed
- Target version changed from 6 to 2.2
Also available in: Atom
PDF
Updated by 
Updated by