Mike, >Right now I can live without streams because its easy enough to create a >method like byte[] read() that you can call multiple times. This is what >we have been doing with EJB for awhile. > :-) Thouh we are not giving up on stream support per se, just pushing it way doen the list.
>I don't use callbacks in any of my current projects, but that may be >because most envrionments dont support it. I bet there are other people >who could really use that. > There are, but we need to multiplx over streams to do it. The impl we tried meant a 90% performance drop which was not acceptable. >One thing that will need to be fixed is that in java 1.4 exceptions now >can wrap another exception to get a it's stack trace. The problem comes >up when an exception that a remote method can throw wraps an exception >that the client dosent have. Example: server side code throws a >SybaseSQLException, which the server wraps into some ServerException. >When the client gets the exception it creates the ServerException no >problem, but gets a NoClassDefFound when it tries to create the wrapped >SybaseSQLException. > > >The fix would be to override the serialization of exceptions to just >include the text of the wrapped exceptions. > A better solution would be to have adaptable code? Ant has an <available> target that would help with building issues, at runtime we could just have adaptive code to handle improved exceptions. I think in the end with your example is that SybaseSQLException is not in the classloader of your client side application. Two observations: 1) You could just unpack it from sybase.jar and zip it into the client side jar (not a great crime). 2) Alternatively hide not wrap the causing exception in your own ServerException ( thout sounds very generic, I hope you don;t have it on every method, unless it is Runtime derived. Questions, - your client side app Swing or a webapp? - AltRMI supports (or appears that it does) object publishing as opposed to interface publishing. We are thinking of droppping that frivilous claim. It will mean that a fair few arg names get renamed from "classesOrInterfacesToExpose" to "interfacesToExpose". How say you....(given you are the only user of AltRMI that I know about on projects I am not a committer to)? - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
