> Is there a workaround for this issue? Would it be possible to use > something like asm to dynamically modify X509CRLImpl and make it implement > Serializable?
I would discourage against bytecode manipulation unless you have both engineering and support experience with it. It's a fairly arcane art and should not be undertaken lightly. An alternative that is much more straightforward would be caching the encoded bytes of the CRL, which is accessible via X509CRL#getEncoded(). Since byte arrays are perfectly serializable, this would work for both memory and persistent caches. I hadn't considered persistent caches in the original design, but it's a perfectly reasonable use case. I'm open to a Jira improvement of caching the encoded representation. It's worth noting that such a change comes at the cost of additional CPU work to decode the bytes on every cache hit. That said it's likely a worthwhile tradeoff generally since I would imagine most CRLs are sizable and caching them in memory may be prohibitive. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
