I've been in the same boat. The deployment.cache file is not particularly
interesting, since it doesn't contain the source. When creating the
wrappers, Orion generates the source and compiles it in the root of the
Orion installation. When done compiling, it places the class files in the
"zip-file-ish" deployment.cache, and deletes everything it generated from
the root of the Orion installation. Removing the filesystem delete
permission from the root of the Orion installation means the source files
stick around, so adding them to the path of your debugger is then a
possibility. Of, course, they're not compiled with debugging info, so you
can't get fancy with watches and the like, but you _can_ step through the
code, actually seeing what's going on - and spot any bugs in Orion's code
generation. ;)
P. Pontbriand
Canlink Interactive Technologies, Inc.
----- Original Message -----
From: "Adam Cassar" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Thursday, April 19, 2001 10:34 PM
Subject: deployment.cache and wrapper classes
>
> Hey guys,
>
> I desperately need to have a look what's going on inside of orion's
> wrapper classes. How can I access them? Previously on the list it is
> mentioned that they are in the deployment.cache file, however when
> I attempt to unjar that file, I only get one or two classes, not the
> entire lot.
>
> Any idea on how to debug these wrappers? They are constantly producing
> Stack Overflow exceptions
> and it would be nice to see what is happening.
>
> --
>
> Adam Cassar
> Technical Development Manager
> ___________________________________________
> NetRegistry http://www.netregistry.au.com
> Tel: +61 2 9641 8609 | Fax: +61 2 9699 6088
> PO Box 270 Broadway NSW 2007 Australia
>
>
>
