|CommandHandler and HandlerProxy [message #1090474]
||Tue, 20 August 2013 07:24
| Marc-Florian Wendland
Registered: January 2013
I migrating our software from Indigo to Kepler and have encountered a
deviating behavior regarding IHandler and HandlerProxy.
In Indigo I could get the IHandler from a Command and resolve the IHandler
to a concrete Handler-Implementation. We used this as a pattern to
parametrize the corresponding Handler instead of the Command directly. This
worked well in Indigo.
Now, giong to Kepler, the IHandler I retrieve from a Command is no longer a
HandlerProxy, thus, I cannot cast it to my IHandler-Implementation. Does
anybody know how to circumvent this? The main idea behind this is to reuse
the very same handler (which in turn configures a complex EMF command) from
all possible situations, but under slightly different circumstances.
Any help would be highly appreciate, because otherwise this would mean for
us to change large parts of a complex and working functionality, which we
would like to avoid, of course.
Powered by FUDForum
. Page generated in 0.10709 seconds