[
https://issues.apache.org/jira/browse/TUSCANY-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Rineholt updated TUSCANY-1076:
-----------------------------------
Attachment: TUSCANY-1076.012807.patch
This is a patch I've been working on for this. It attempts to create not only
the inbound but also an outbound wire and then run in it through the wiring
connecting stage allowing for an needed interceptors such data binding. I have
tested on the slightly modified helloworldSamplewsClient locating the reference
directly. I would have checked it in directly, but there were some aspects
that I didn't care for but couldn't seem to get around. For example the new
ing of the JavaInterfaceProcessorRegistryImpl ideally I'd like to use the same
instance that deployed the application but at the time locateService is being
called a lot of these types of artifacts seem to be not conveniently available
from what I could tell.
> Dynamic outbound wire for CompositeContext.locateService
> --------------------------------------------------------
>
> Key: TUSCANY-1076
> URL: https://issues.apache.org/jira/browse/TUSCANY-1076
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-SCA-M3
> Reporter: Rick Rineholt
> Fix For: Java-SCA-M3
>
> Attachments: TUSCANY-1076.012807.patch
>
>
> CompositeContext.locateService requires an outbound wire to be created so
> for cases where bindings from the component/reference it locates are
> different from Java a databinding interceptor can be used to resolve
> difference in the expect data format.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
