If so it means that you need to enforce the dependency of ExoKernelIntegration with org.exoplatform.services.jcr.config.RepositoryServiceConfiguration, since it is the service that is in charge of creating JCR repositories and workspaces, so If you enforce the dependency, you will ask PicoContainer to create and start this component before your component. To do so just add RepositoryServiceConfiguration in your constructor as below:<div>
..</div><div>public ExoKernelIntegration(RepositoryServiceConfiguration rsc)</div><div>{</div><div>...</div><div>}</div><div>..</div><div><br></div><div>Please note that RepositoryServiceConfiguration will create all the repositories and workspaces in its start method </div>
<div><br><div class="gmail_quote">On Tue, Feb 23, 2010 at 4:20 PM, Matthew Wringe <span dir="ltr"><<a href="mailto:mwringe@redhat.com">mwringe@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, 2010-02-23 at 16:02 +0100, Nicolas Filotto wrote:<br>
> Could you please fully describe the problem you met, to allow us to<br>
> give you the best solution.<br>
<br>
</div>WSRP is setup using the ExoKernelIntegration. This is a java class that<br>
hardcodes the wsrp wiring. As part of the wiring it needs to get access<br>
to the 'repository' jcr repository.<br>
<br>
The 'repository' jcr repo is setup in an external-plugin-configuration<br>
(portal/src/main/webapp/WEB-INF/conf/jcr/component-plugins-configuration.xml).<br>
<br>
If we use the Sun JDK then everything works fine and the<br>
external-plugin-configuration gets called before the<br>
ExoKernelIntegration. WSRP can find the jcr repository it needs.<br>
<br>
If we use the IBM JDK, then the ordering is different and the wsrp<br>
ExoKernelIntergration will fail because it can't find the jcr<br>
'repository' repo.<br>
<br>
I want to be able to tell the wsrp setup to wait until after the jcr<br>
specific external-plugin-configuration has been called. Right now we<br>
don't specify that, and its probably just by chance that it works with<br>
the Sun JDK right now.<br>
<div><div></div><div class="h5"><br>
<br>
> On Tue, Feb 23, 2010 at 3:42 PM, Matthew Wringe <<a href="mailto:mwringe@redhat.com">mwringe@redhat.com</a>><br>
> wrote:<br>
> In WSRP we need to depend on an external-plugin-configuration<br>
> to setup<br>
> the 'repository' repo in jcr. WSRP is configured using the<br>
> ExoKernelIntergration.<br>
><br>
> Is there anyway to make the wcrp configuration happen after<br>
> the<br>
> external-plugin-configuration has occured?<br>
><br>
> The issue only occurs when using the IBM jdk and not the Sun<br>
> one.<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>
><br>
> --<br>
> Nicolas Filotto<br>
> JCR Product Manager<br>
> Project Manager<br>
> eXo Platform SAS<br>
> <a href="mailto:nicolas.filotto@exoplatform.com">nicolas.filotto@exoplatform.com</a><br>
> +33 (0)6 31 32 92 19<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Nicolas Filotto<br>JCR Product Manager<br>Project Manager<br>eXo Platform SAS<br><a href="mailto:nicolas.filotto@exoplatform.com">nicolas.filotto@exoplatform.com</a><br>
+33 (0)6 31 32 92 19 <br>
</div>