Let me further explain the trouble that I'm struggling...
When I was still using ResourceStreamLocator, everything works fine. The I
just renamed ResourceStreamLocator to ResourceStreamFactory because it seems
that that's the only change to do in my part. Just renaming didn't work. I
did a
Just renaming doesn't work. ResourceStreamFactory implements Wickets
default implementation. I guess you forgot to call super.locate(...)
in your factory?
regards
Juergen
On 1/22/07, Otan [EMAIL PROTECTED] wrote:
Let me further explain the trouble that I'm struggling...
When I was still using
On 22/01/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Just renaming doesn't work. ResourceStreamFactory implements Wickets
default implementation. I guess you forgot to call super.locate(...)
in your factory?
Ok. It's a mistake in my part. That refactoring in wicket made me
aggressively
having my code refactored to use ResourceStreamFactory (from using
ResourceStreamLocator before), my program no longer works and I now receive
a MarkupNotFoundException. Could someone clarify to me how is the proper use
of ResourceStreamFactory and what new things to understand regarding custom
Please see CustomResourceStreamFactory in the custom resource loading
examples for how it works, or OsgiResourceStreamFactory as another
example. You simply extend ResourceStreamFactory, subclass the
appropriate locate() method (you usually must not forget to call
super.locate()) and register your
juergen, if it's a factory, shouldn't it be newResourceStream?
Juergen Donnerstag wrote:
Please see CustomResourceStreamFactory in the custom resource loading
examples for how it works, or OsgiResourceStreamFactory as another
example. You simply extend ResourceStreamFactory, subclass the
juergen, if it's a factory, shouldn't it be newResourceStream?
Juergen Donnerstag wrote:
Please see CustomResourceStreamFactory in the custom resource loading
examples for how it works, or OsgiResourceStreamFactory as another
example. You simply extend ResourceStreamFactory, subclass the
May be. The reason why I didnt change it is because we are still
searching for the resource by iterating over (component hierarchy),
class hierarchy, style, variation, locale and sometime extensions and
only if the find the resource we create a resource stream for it. Not
sure which I like better
juergen, if it's a factory, shouldn't it be newResourceStream?
Juergen Donnerstag wrote:
Please see CustomResourceStreamFactory in the custom resource loading
examples for how it works, or OsgiResourceStreamFactory as another
example. You simply extend ResourceStreamFactory, subclass the
yeah, my feeling is that it should be newX if it's a factory method.
the purpose of a factory is to create something...
Juergen Donnerstag wrote:
May be. The reason why I didnt change it is because we are still
searching for the resource by iterating over (component hierarchy),
class
On 14/01/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Just out of curiosity, what are you using it for? How and why did you
change/extend the default behavior?
Sometimes, I put markups in the folder like:
/WEB-INF/wicket.html/com.mycompany.packedge/
or
11 matches
Mail list logo
