On 9/9/2005 4:55 AM, Rick McGuire wrote:
I've taken a look at both solutions for the openejb ASN1 usage. The
ASN1 bouncy castle code is realatively selfcontained, and can be
separated out an repackaged relatively quickly. I've already managed
to build a version of the BC code that contains just the classes
necessary to get the asn1 subdirectory to compile, and am working on a
"pruned" version that removes support not likely to be required for
openejb/geronimo. Once that is done, the changes to openejb are
pretty trivial (mostly just changing package names). Right now, I'm
planning on creating a util module in Geronimo for this to live.
The Directory stuff is a little trickier. The Directory ASN1 support
doesn't include support for different types of objects that use ASN1
encodings (in this case X509 names). I took a crack at writing the
equivalent, and found the Directory ASN1 support to be incomplete
enough that you'd end up reimplementing a lot of the bc classes in the
Directory. A "quick-and-dirty" approach just implementing X509 name
parsing in the openejb Util module look doable, but was still a fairly
tricky bit of code AND required some enhancements to the Directory
ans1 support to implement. Right now, the bc subset version looks
like the best route to take.
Let's go with the former. Toss it up on the Jira issue and I'll get to
it immediately.
Thanks for all your help on this.
Regards,
Alan
