Could you add a method to TestInterface that illustrates the bug? The problem is almost certainly to do with a return type (or param) that is not supported (yet). If the AbstractHelloTestCase is modified to contain a method that tests that TestInterface method, then we should know whether I have a reproducable situation.
If that is too hard, just let me know see the complete code for the interface model (you can rename some things to protect proprietary nature).
Regards,
- Paul
Hi,
so I've come a bit further now. Still generated the proxies with Ant upfront.
When I used a ClientSideClassFactory then I got a
IlleagalArgumentException in the constructor of the generated proxy class
AltrimiGenerated*_Main.java.
When I swiched back to ServerSideClassFactory as in this code snipplet
try {
HostContext hc = new SocketObjectStreamHostContext(host, port);
Factory factory = new ServerSideClassFactory(false);
factory.setHostContext(hc);
datasource = (SIMONDataSource)factory.lookup("server");
assertNotNull(datasource);
} catch (ConnectionException e)
{
fail("Cannot get datasource component");
}
I got the component so the lookup was successful now, but then this
exception:
---
18:25:48.682 [threads ] (): Retrieving a
org.apache.avalon.excalibur.thread.impl.WorkerThread from the pool
DEBUG 2003-01-21 18:25:48.683 [connecti] (): Starting connection on
127.0.0.1
INFO 2003-01-21 18:25:51.818 [server ] (): output from the component!
WARN 2003-01-21 18:25:51.820 [connecti] (): Error handling connection
java.lang.NullPointerException
at
org.apache.excalibur.altrmi.server.impl.adapters.InvocationHandlerAdapter.doMethodFacadeRequestNonArray(InvocationHandlerAdapter.java:316)
at
org.apache.excalibur.altrmi.server.impl.adapters.InvocationHandlerAdapter.doMethodFacadeRequest(InvocationHandlerAdapter.java:227)
at
org.apache.excalibur.altrmi.server.impl.adapters.InvocationHandlerAdapter.handleInvocation(InvocationHandlerAdapter.java:128)
at
org.apache.excalibur.altrmi.server.impl.AbstractServer.handleInvocation(AbstractServer.java:138)
at
org.apache.excalibur.altrmi.server.impl.StreamServerConnection.run(StreamServerConnection.java:88)
at
org.apache.excalibur.altrmi.server.impl.socket.AbstractPartialSocketStreamServer.handleConnection(AbstractPartialSocketStreamServer.java:65)
at
org.apache.excalibur.altrmi.blocks.publishing.PartialSocketStreamConnectionHandler.handleConnection(PartialSocketStreamConnectionHandler.java:45)
DEBUG 2003-01-21 18:25:51.835 [threads ] (): Returning a
org.apache.avalon.excalibur.thread.impl.WorkerThread to the pool
And about exceptions, exceptions are also serialized to the client side?
Could I create a interface and a proxy for a exception class if I don't
want a certain exception to be serialized to the client side due to JNI
for example?
Then finally there are various host context classes, which ones are most
preferable, stable and fully functional? Can anybody give some overview or
advice on which to take? I just looked in the examples and took the
SocketObjectStreamHostContext but some examples use s
CustomSocketObjectStreamHostContext and others.
Regards, Peter
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
