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
/
IOC-89.xml
63 lines (57 loc) · 1.8 KB
/
IOC-89.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
53
54
55
56
57
58
59
60
61
62
63
<?xml version="1.0" encoding="utf-8"?>
<issues>
<issue>
<field name="Priority">
<value>Normal</value>
</field>
<field name="Type">
<value>Task</value>
</field>
<field name="State">
<value>Fixed</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>89</value>
</field>
<field name="summary">
<value>Make DefaultKernel implement IServiceProvider</value>
</field>
<field name="description">
<value>DefaultKernel can easily implement System.IServiceProvider:
object GetService(Type serviceType)
using its Resolve method:
object Resolve(Type service)
That would allow a class that would normally request an IKernel for additional service lookups to request IServiceProvider and not have a dependency on Castle.MicroKernel.
The attached patch uses an explcit interface definition so the GetService method isn't readily accessible on the object (i.e. users are encouraged to use Resolve instead of GetService).
Should IKernel extend IServiceProvider?</value>
</field>
<field name="created">
<value>1184956887000</value>
</field>
<field name="updated">
<value>1283220838885</value>
</field>
<field name="reporterName">
<value>rgrabowski</value>
</field>
<field name="updaterName">
<value>xtoff</value>
</field>
<field name="resolved">
<value>1282142068963</value>
</field>
<field name="watcherName">
<value>User: id = 20-18[up-to-date]</value>
</field>
<field name="permittedGroup">
<value>All Users</value>
</field>
</issue>
</issues>