I did not have codebase, nor security manager at first until my friend's assignment was automatically failed because cannot find the stub!
Originally posted by Erick Reid:
Cathy,
Mark et al can correct if I misstate this, but yes, you are correct. The codebase, security managers and policy files are meant to facilitate dynamic downloading of _stub files from server to client. There is no need for dynamic downloading if the _stubs are already available to the client because you explicitly included them in the client jar.
Mark's previous post gives sound justification. I like the approach because it really cuts down on the number of moving parts (possible points of failure)
Originally posted by Erick Reid:
My head is not inside your design, so it is harder to comment, but some things came to mind when reading your post:
- why does the server need a stub for something? the client is the guy who needs to stream requests to/from the server.
- you probably don't need skel files.
- is your dataagent stub indeed physically included in the server jar? dump the contents and see if it is indeed present in the jar.
Originally posted by Erick Reid:
Cathy,
Try a commandline with no codebase specified, and an absolute classpath.
Originally posted by Erick Reid:
Dunno what else to offer. Not knowing your design and wondering about why your server wants a stub makes it difficult to suggest alternatives. Check other threads in the SCJD forum for "codebase". It's a popular topic. Hopefully one will come to light that applies to your setup.
Don't get me started about those stupid light bulbs. |