From: Max Muller <maxmuller@ma...> - 2004-07-22 17:15:57
The warning you are seeing is actually a spurious error message. I
spent a few hours tracking it down into the bowels of component
definition caching. The issue is related to not having a top level .wo
component in ERExtensions.framework/Resources instead the default
component is in ERExtensions.framework/Resources/Nonlocalized.lproj. We
had to do the Nonlocalized trick to work around a bug way back with
ProjectBuilder where you couldn't have a top level default component
and also localized variants. In the post-2.0 release of Wonder we are
considering moving all of the components in Nonlocalized.lproj out of
the lproj directory as this isn't needed anymore. However without
subversion that is a whole lotta deletes and removes where we would
loose cvs history.
So long story short, the error is spurious and doesn't actually cause
any issues as the correct component definition is loaded. I haven't
seen the speed hit that you are seeing.
On Jul 22, 2004, at 9:46 AM, Joseph Larson wrote:
> I'm getting the following error:
> er.extensions.ERXNSLogLog4jBridge DEBUG [WorkerThread2]
> jpl@... -
> <com.webobjects.appserver._private.WOComponentDefinition> No template
> found for component WOIFrame at
> This error occurs on objects found in ERExtensions and
> JavaWOExtensions, but doesn't appear for any components found in other
> frameworks. There is a significant delay involved with the components
> from JavaWOExtensions. I get one instance of the error message for
> any particular component.
> The application appears to run just fine. The components with missing
> templates appear to operate properly -- I just end up with a very slow
> app the first time I load a window containing any of these wayward
> Any clues?
> WebObjects-dev mailing list