Thinking a little more, using the ImplementationProcessor mechanisms
seems like a better way to tackle this. One major advantage would be
that we could add metadata to the service contract based on data type
or annotations (e.g. adding metadata saying that a parameter should
be bound using
JavaServiceContract introspection should use the ImplementationProcessor
mechanism
--
Key: TUSCANY-616
URL: http://issues.apache.org/jira/browse/TUSCANY-616
Project:
Hi Jeremy / Jim,
Thanks for continuing to guide me on this :-)
- Jim, the concern you raised about the business interface not inheriting
from Remote and the need to do some sort of mediation has been a primary
concern to me since M1. I have been able to get that working now. Now
there is no
