Ah right, that one.
Have a look at this issue, that's the change I was referring to:
http://issues.castleproject.org/issue/DYNPROXY-96
Krzysztof
On 27/11/2011 1:11 AM, Tomek Pluskiewicz wrote:
Let me quote:
You don’t specify which mixin interfaces you want to forward to
which mixin. This is implicit – if mixin implements an interface,
it will be forwarded to that mixin instance, unless someone else
implements it as well. You can’t have two mixins that implement
the same interface. You can’t have mixin implement same interface
as target, nor can you have a mixin implementing one of additional
interfaces to proxy. In any of these cases when trying to create a
proxy you will get an error.
This is not a very serious issue though, and I think in most cases
it should be enough. In case you need more power, Dynamic Proxy
v2.2 will have better support for mixin, allowing scenarios that
are not possible in current version.
I specifically address the statetement that DP 2.2 will have better
support for mixnis. I wonder what has actually changed recently.
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/castle-project-devel/-/kJPfLg6dOXYJ.
To post to this group, send email to
[email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
