Hi,<div><br></div><div>I'm using the OpenSAML library to use single-sign-on in my web application. I noticed that OpenSAML has a dependency on Apache Velocity, and is initializing it when calling DefaultBootstrap.bootstrap(). </div>
<div><br></div><div>The problem is that my web application also uses Velocity, and that Velocity is initialized in a static way; that is, it can be initialized only once per VM. The result is that OpenSAML "hijacks" Velocity, and the initialization performed by my web application is ignored, which effectively breaks my application! In other words, it looks like OpenSAML can't be used in applications that use Velocity.</div>
<div><br></div><div>I way quite surprised to learn that OpenSAML is using Velocity; for the purpose I'm using OpenSAML (generating AuthRequest and verifying Assertions), I can't really think of a reason to use Velocity. Maybe it is used by a specific part of the library that I don't use? Then, it would be highly recommended to make the dependency on Velocity optional. I don't think that is possible now?</div>
<div><br></div><div>Is there a way to use or configure OpenSAML in such a way that it doesn't conflict with my own Velocity configuration?</div><div><br></div><div><br></div><div>Many thanks,</div><div><br></div><div>
Tom</div>