On Tue, 2010-02-23 at 16:02 +0100, Nicolas Filotto wrote:WSRP is setup using the ExoKernelIntegration. This is a java class that
> Could you please fully describe the problem you met, to allow us to
> give you the best solution.
hardcodes the wsrp wiring. As part of the wiring it needs to get access
to the 'repository' jcr repository.
The 'repository' jcr repo is setup in an external-plugin-configuration
(portal/src/main/webapp/WEB-INF/conf/jcr/component-plugins-configuration.xml).
If we use the Sun JDK then everything works fine and the
external-plugin-configuration gets called before the
ExoKernelIntegration. WSRP can find the jcr repository it needs.
If we use the IBM JDK, then the ordering is different and the wsrp
ExoKernelIntergration will fail because it can't find the jcr
'repository' repo.
I want to be able to tell the wsrp setup to wait until after the jcr
specific external-plugin-configuration has been called. Right now we
don't specify that, and its probably just by chance that it works with
the Sun JDK right now.
> On Tue, Feb 23, 2010 at 3:42 PM, Matthew Wringe <mwringe@redhat.com>
> wrote:
> In WSRP we need to depend on an external-plugin-configuration
> to setup
> the 'repository' repo in jcr. WSRP is configured using the
> ExoKernelIntergration.
>
> Is there anyway to make the wcrp configuration happen after
> the
> external-plugin-configuration has occured?
>
> The issue only occurs when using the IBM jdk and not the Sun
> one.
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
>
>
> --
> Nicolas Filotto
> JCR Product Manager
> Project Manager
> eXo Platform SAS
> nicolas.filotto@exoplatform.com
> +33 (0)6 31 32 92 19