[snip]
Luciano Resende wrote:
Thanks for checking Sebastien, most is in SVN now, and I have already
cleaned up the classLoader issue you mentioned. Indeed, I have couple
questions...
- We need a better extensible way to handle the matching of
import/export to proper initialize the resolvers. I have looked into
using the ArtifactProcessor.resolve to handle part of this (as
suggested on the code comments), but I could think about couple issues
: the processor might bot have all the required dependencies to proper
find the matching import/export and to initialize the resolvers, also
the processors might be contributed by the not really be tied together
with the module that implementing the import/export support (java
case). So, any ideas are welcome... For now, TUSCANY-1488 [1] shows a
workaround that is working on top of svn.
Ok, ArtifactProcessor.resolve is probably not the right method to do
that then, as it doesn't have the correct context.
ContributionPostProcessor.visit seems more promising, but it is not
given the list of available contributions. I'll take a look at what
you've done and see if I can come up with any ideas.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
