geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan <>
Subject Re: wired-bundle cache problem in the BundleClassLoader
Date Fri, 05 Nov 2010 01:03:37 GMT
The resource is a js file in the myfaces-core package, there is no failure
in the deployment, the error occurs while accessing the pages. Adding the
import might work, but I am thinking that we would get other similiar
problems, as dynamic import * is used currently, so there should be a
solution for the potenial cache problem. For this issue, it seems that bval
tries to find the xml configuration file eariler, and that action causes the
cache is created.

2010/11/5 Jarek Gawor <>

> Ivan,
> What resource is it? Does it fail during deployment or just on first start
> up? This might work. Update the myfaces deployer to add import package
> statement for a package that myfaces-core bundle provides. That way you will
> always have a static bundle wire and the resource should always be found.
> Jarek
> On Nov 3, 2010, at 3:34 AM, Ivan <> wrote:
> > Hi,
> >     While looking at the left JSF TCK fail cases, I found that the wired
> bundle cache in the BundleClassLoader causes some problems. The scenario is
> that the MyFaces codes look up a resource file by classloader.getResource,
> it always fails on the first deployment, but after restarting the
> application, it finds it. Finally, I added a breakpoint in the
> BundleClassLoader, and find it is caused by old wired bundle cache. Anyone
> has a good solution for it ?
> >
> > --
> > Ivan


View raw message