This repository has been archived by the owner on Dec 14, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
FACILITIES-87.xml
52 lines (50 loc) · 1.67 KB
/
FACILITIES-87.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
<?xml version="1.0" encoding="utf-8"?>
<issues>
<issue>
<field name="Priority">
<value>Major</value>
</field>
<field name="Type">
<value>Bug</value>
</field>
<field name="State">
<value>Duplicate</value>
</field>
<field name="Assignee" />
<field name="Subsystem">
<value>No subsystem</value>
</field>
<field name="Fix versions" />
<field name="Affected versions" />
<field name="Fixed in build" />
<field name="numberInProject">
<value>87</value>
</field>
<field name="summary">
<value>factory facility doesn't get to launch until all component dependencies are resolved</value>
</field>
<field name="description">
<value>if X component has dependency on Y in constructor, kernel throws unresolved dependency exception when I try to request the component. I have component created with a factory and Y dependency is resolved at run-time.
the only way around this right now is to move depedency to a property, which is not always possible.
if this is a limitation of castle architecture (all dependency get resolved for a component before facility gets a chance to work with it) then it needs to be documented</value>
</field>
<field name="created">
<value>1181056361000</value>
</field>
<field name="updated">
<value>1181854971000</value>
</field>
<field name="reporterName">
<value>ornus</value>
</field>
<field name="updaterName">
<value>ornus</value>
</field>
<field name="resolved">
<value>1282141197354</value>
</field>
<field name="permittedGroup">
<value>All Users</value>
</field>
</issue>
</issues>