Not an expert, but an advice nonetheless ;)<div><br></div><div>Login module is an AS thing, and your extension is registering an already existing login module, so JBoss throws an Exception. That's expected.</div><div><br>
</div><div>To deploy portlets you don't need to create an extension. But if you want to register it in GateIn's portlet repository then, yes, creating an extension is the way to go. Even if you do that, and you create an extension, you shouldn't need a new login module.</div>
<div><br></div><div>But if you really need this new login module for some reason, you need to give it another name and modify the realmName in your <font class="Apple-style-span" face="'courier new', monospace">org.exoplatform.container.definition.PortalContainerConfig</font> of your extension accordantly. AFAIK that's all you need.</div>
<div><br><div class="gmail_quote">On Mon, Feb 7, 2011 at 6:32 PM, Prabhat Jha <span dir="ltr"><<a href="mailto:pjha@redhat.com">pjha@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br>
<br>
Can we get some expert advice on this pls?<br>
<br>
Thanks,<br>
<font color="#888888">Prabhat<br>
</font><div><div></div><div class="h5"><br>
----- Original Message -----<br>
> Hi everyone,<br>
><br>
> I have an important question about login modules in GateIn/EPP5.<br>
><br>
> Now there is a gatein-jboss-beans.xml file which contains definition<br>
> of 3 login modules for gatein-domain (default realmName).<br>
><br>
> Think of this situation:<br>
> - we have a set of new portlets and we need to add new login module<br>
> - we are using an extension mechanism to deply everything and<br>
> initialize new portal (we don't want to touch gatein.ear at all)<br>
> - we add a new gatein-jboss-beans.xml in extension .ear (with old +<br>
> new login modules defined), now it means that both<br>
> gatein-jboss-beans.xml (from gatein.ear and from extension .ear) are<br>
> used<br>
><br>
> But it's a problem because you will get an error during startup:<br>
> IllegalStateException: gatein-domain is already installed.<br>
><br>
> Now I know about these options:<br>
> 1) replace gatein-jboss-beans.xml in gatein.ear with new file<br>
> 2) have new gatein-jboss-beans.xml in extension .ear and rename file<br>
> in gatein.ear to something like: gatein-jboss-beans.xml-backup (it<br>
> means that only the one from extension is used)<br>
> 3) create new portal container with new realmName and define all login<br>
> modules in new domain (but in our case we want to extend default<br>
> portal container)<br>
><br>
> So the question is if there is some other way how to define new login<br>
> modules (without touching gatein.ear)?<br>
><br>
> Thanks for any help or ideas!<br>
><br>
> Best regards,<br>
> Michal Vančo, JBoss QA<br>
><br>
> (I have it temporarily done with second option, but I'd like to<br>
> improve it - I want only to deploy new .ear and that's all)<br>
><br>
> _______________________________________________<br>
> gatein-dev mailing list<br>
> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
<br>
_______________________________________________<br>
gatein-dev mailing list<br>
<a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Rafael Liu<br>+55 61 9608-7722<br><a href="http://rafaelliu.net">http://rafaelliu.net</a><br>
</div>