<div dir="ltr"><div><div>Anil,<br><br>I surely can, will have two POC environments (PL cluster + MySQL cluster) for many weeks.<br><br></div>Thank you very much for the attention to the issue, I really appreciated it.<br><br>
</div>Regards,<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 12:54 PM, Anil Saldhana <span dir="ltr"><<a href="mailto:Anil.Saldhana@redhat.com" target="_blank">Anil.Saldhana@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="https://issues.jboss.org/browse/PLINK2-101" target="_blank">https://issues.jboss.org/<u></u>browse/PLINK2-101</a><br>
<a href="https://issues.jboss.org/browse/PLINK2-102" target="_blank">https://issues.jboss.org/<u></u>browse/PLINK2-102</a><br>
<br>
I hope Fernando can help test this. :)<br>
<br>
On 08/06/2013 10:30 AM, Anil Saldhana wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi All,<br>
<a href="http://lists.jboss.org/pipermail/wildfly-dev/2013-August/000574.html" target="_blank">http://lists.jboss.org/<u></u>pipermail/wildfly-dev/2013-<u></u>August/000574.html</a><br>
(thanks to Jason, Bill and Scott Marlow for the discussion)<br>
<br>
Jason has provided some objections to the JPA usage in PicketLink that<br>
can affect Wildfly boot time performance. He had raised this concern<br>
last time for the JPAIdentityStore implementation in PicketLink v2.5<br>
which we have been trying to mitigate via the implementation of a JDBC<br>
driven Identity Store.<br>
<br>
The discussion happening in the thread above however is for the<br>
JPABasedTokenRegistry and JPABasedRevocationRegistry part of v2.1.x<br>
which predates PicketLink v2.5<br>
<a href="https://github.com/picketlink2/federation/blob/master/picketlink-core/src/main/java/org/picketlink/identity/federation/core/sts/registry/JPABasedTokenRegistry.java" target="_blank">https://github.com/<u></u>picketlink2/federation/blob/<u></u>master/picketlink-core/src/<u></u>main/java/org/picketlink/<u></u>identity/federation/core/sts/<u></u>registry/<u></u>JPABasedTokenRegistry.java</a><br>
<a href="https://github.com/picketlink2/federation/blob/master/picketlink-core/src/main/java/org/picketlink/identity/federation/core/sts/registry/JPABasedRevocationRegistry.java" target="_blank">https://github.com/<u></u>picketlink2/federation/blob/<u></u>master/picketlink-core/src/<u></u>main/java/org/picketlink/<u></u>identity/federation/core/sts/<u></u>registry/<u></u>JPABasedRevocationRegistry.<u></u>java</a><br>
<br>
I think we should also implement a straight JDBC based token registry<br>
and revocation registry to avoid the Wildfly boot drag.<br>
<br>
Regards,<br>
Anil<br>
</blockquote>
</blockquote></div><br><br clear="all"><br>-- <br>Fernando Ribeiro<br><div>Upic</div><div>+55 11 9 8111 4078</div>
</div>