Re: Resource loading

2007-01-07 Thread Eelco Hillenius

Simplifying sounds *very* good to me. Thanks for giving it a try.

Eelco

On 1/7/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:

In an attempt to simplify (more readable) resource loading I
- renamed IResourceStreamLocator to IResourceStreamFactory
- combined what used to be AbstractResourceStreamLocator,
ClassResourceStreamLocator, ResourceFinderResourceStreamLocator and
CompoundResourceStreamLocator in a single class ResourceStreamFactory.
Everything that used to be possible should be possible but slightly
different. Instead implementing a IResourceStreamLocator and adding it
to ComponentResouceStreamLocator you now must subclass
ResourceStreamFactory and replace the appropriate
ResourceStreamFactory method. There are only few, so don't worry.

This is meant to be the first step to make properties searching more
readable/simply as well.

WDYT?

Juergen



Re: Resource loading

2007-01-07 Thread Igor Vaynberg

yes, sounds cleaner

-igor


On 1/7/07, Eelco Hillenius [EMAIL PROTECTED] wrote:


Simplifying sounds *very* good to me. Thanks for giving it a try.

Eelco

On 1/7/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:
 In an attempt to simplify (more readable) resource loading I
 - renamed IResourceStreamLocator to IResourceStreamFactory
 - combined what used to be AbstractResourceStreamLocator,
 ClassResourceStreamLocator, ResourceFinderResourceStreamLocator and
 CompoundResourceStreamLocator in a single class ResourceStreamFactory.
 Everything that used to be possible should be possible but slightly
 different. Instead implementing a IResourceStreamLocator and adding it
 to ComponentResouceStreamLocator you now must subclass
 ResourceStreamFactory and replace the appropriate
 ResourceStreamFactory method. There are only few, so don't worry.

 This is meant to be the first step to make properties searching more
 readable/simply as well.

 WDYT?

 Juergen




hangman exception: attach

2007-01-07 Thread Juergen Donnerstag

Hangman doesnt work anymore

WicketMessage: Error attaching this container for rendering:
[MarkupContainer [Component id = 0, page =
wicket.examples.hangman.Guess, path = 1:letters:0.ListItem, isVisible
= true, isVersioned = false]]

Root cause:

java.lang.IllegalStateException: wicket.Component has not been
properly attached. Something in the hierarchy of
wicket.examples.hangman.Guess$2$1 has not called super.onAtach() in
the override of onAttach() method
at wicket.Component.attach(Component.java:2799)
at wicket.MarkupContainer.attachChildren(MarkupContainer.java:372)
at wicket.Component.attach(Component.java:2807)
at wicket.markup.html.list.ListView.onGenerateItems(ListView.java:614)
at wicket.markup.html.list.ListView.onAttach(ListView.java:548)
at wicket.Component.attach(Component.java:2796)
at wicket.MarkupContainer.attachChildren(MarkupContainer.java:372)
at wicket.Component.attach(Component.java:2807)
at wicket.Page.renderPage(Page.java:1082)
at wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:171)
at 
wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:61)
at 
wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:53)
at 
wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:65)
at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:944)
at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:973)
at wicket.RequestCycle.step(RequestCycle.java:1054)
at wicket.RequestCycle.steps(RequestCycle.java:1125)
at wicket.RequestCycle.request(RequestCycle.java:470)
at wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:232)
at wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:122)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:354)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:687)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at 
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

Complete stack:


junit error due to radiobox changes

2007-01-07 Thread Juergen Donnerstag

There are junit test failure dues to changes to RadioBoxes?

Juergen


Re: hangman exception: attach

2007-01-07 Thread Igor Vaynberg

fixed

-igor


On 1/7/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:


Hangman doesnt work anymore

WicketMessage: Error attaching this container for rendering:
[MarkupContainer [Component id = 0, page =
wicket.examples.hangman.Guess, path = 1:letters:0.ListItem, isVisible
= true, isVersioned = false]]

Root cause:

java.lang.IllegalStateException: wicket.Component has not been
properly attached. Something in the hierarchy of
wicket.examples.hangman.Guess$2$1 has not called super.onAtach() in
the override of onAttach() method
at wicket.Component.attach(Component.java:2799)
at wicket.MarkupContainer.attachChildren(MarkupContainer.java:372)
at wicket.Component.attach(Component.java:2807)
at wicket.markup.html.list.ListView.onGenerateItems(ListView.java:614)
at wicket.markup.html.list.ListView.onAttach(ListView.java:548)
at wicket.Component.attach(Component.java:2796)
at wicket.MarkupContainer.attachChildren(MarkupContainer.java:372)
at wicket.Component.attach(Component.java:2807)
at wicket.Page.renderPage(Page.java:1082)
at wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java
:171)
at wicket.request.target.component.PageRequestTarget.respond(
PageRequestTarget.java:61)
at wicket.request.compound.DefaultResponseStrategy.respond(
DefaultResponseStrategy.java:53)
at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(
AbstractCompoundRequestCycleProcessor.java:65)
at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:944)
at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:973)
at wicket.RequestCycle.step(RequestCycle.java:1054)
at wicket.RequestCycle.steps(RequestCycle.java:1125)
at wicket.RequestCycle.request(RequestCycle.java:470)
at wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:232)
at wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:122)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
ServletHandler.java:1041)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java
:354)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java
:226)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java
:627)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java
:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
HttpConnection.java:687)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:492)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:199)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339)
at org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java
:270)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(
BoundedThreadPool.java:475)

Complete stack:



Re: junit error due to radiobox changes

2007-01-07 Thread Igor Vaynberg

doh, fixed :) i made a trivial change and didnt bother to run the tests,
shame on me.

-igor


On 1/7/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:


There are junit test failure dues to changes to RadioBoxes?

Juergen