On 20/01/2011 21:17, ant elder wrote:
On Thu, Jan 20, 2011 at 9:10 PM, Scott Kurz<[email protected]> wrote:
I recreated that MediatorImpl.copyInput failure now... Maybe the
problem was that earlier I ran "offline" and had something stale in my
mvn repo???
Anyway..looking into both problems now..
What was a module you used to notice the 2nd problem with
JavaInterfaceImpl.isAsyncServerOperation?
One example is testing\itest\async-services
...ant
Scott,
Yes, Ant identifies cases that are still failing.
I suspect that your interface handling changes don't account properly for Java interfaces that have
the "async server" format, where a regular method like:
String someOperation( Int input )
is mapped to this:
void someOperationAsync( Int input, ResponseDispatch<String> response )
So far it looks like the type of the output parameter is being mapped incorrectly now - I see some
instances where the output parameter has a type of idl:input associated with it rather than
idl:output. The code that does this is a bit dense and I cannot pin it down yet.
Yours, Mike.