I may be stepping on toes here a little bit, but I ran into this very
problem when working on the port of the Santuario library [1] to use
GenXDM [2]. In my case, if the library had to be endorsed, it would drag
along a whole bevy of additional libraries that were utterly
inappropriate to endorse in that way.
I solved this problem by renaming all the packages that in the official
version are called org.jcp.... In the ported version, they're now called
"org.apache.jcp...".
This eliminates the need for "endorsing", as it can now be used along
side the implementation in the JVM.
I just finished porting the latest 1.4.6 changes (and haven't even had a
chance to announce them).
http://code.google.com/a/apache-extras.org/p/santuario-genxdm/downloads/list
[1] http://code.google.com/a/apache-extras.org/p/santuario-genxdm/
[2] http://code.google.com/p/genxdm/
So at least there's something you could try that doesn't have the same
problem with endorsement.
-Eric.
On 11/2/11 9:59 PM, Chad La Joie wrote:
This is pretty suboptimal. Classes (or JARs of classes) within the
endorsed directory are visible on the classpath and obviously logging
frameworks are one of those things where there is a lot of
variability.
On Wed, Nov 2, 2011 at 12:50, Sean Mullan<[email protected]> wrote:
On 11/2/11 12:40 PM, Chad La Joie wrote:
I've been planning to move our Shib code over to use the JSR105 APIs
for signature work. One of our testers today was trying to use SHA256
within their signatures and received the error that this wasn't
supported by the JVM-shipped implementation of those APIs. So, I
figured we'd just endorse xmlsec in order to use it at the JVM's
JSR105 impl.
However, when we tried this, we received the error that Apache
Common's Logging was not available. This, of course, is true. That
library isn't available in the JVM's internal classpath.
So, the question is, should it be possible to use xmlsec as a JVM's
JSR105 implementation?
Yes, but you need to also put commons-logging.jar in the endorsed dir. See my
blog for more info:
http://blogs.oracle.com/mullan/entry/using_more_recent_apache_xml
--Sean
