Re: Feedback panel inherits parent panel feebdack?
all feedback panels get all feedback messages. use ifeedbackmessagefilter provided impls or your own to filter messages that panels consume... -igor On Mon, Sep 26, 2011 at 10:51 PM, Arjun Dhar dhar...@yahoo.com wrote: Hey, i guess i was sleeping when this one was taught. I have a Feetback panel on the parent panel. Then in a WebMarkupContainer, have added another feedback panel. When I add .info(...) or .error(...) to feedback panel in parent it appears in both. Must be some component hierarchy trickle down effect but Weird right? And if this is intentional why is it needed? - Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Feedback-panel-inherits-parent-panel-feebdack-tp3846252p3846252.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Feedback panel inherits parent panel feebdack?
I've hit this too. You're not the first to be surprised by this behavior. http://apache-wicket.1842946.n4.nabble.com/Page-and-compoenent-level-feedback-are-mixing-together-td1846435.html I agree that there's something unintuitive about all FeedbackPanels rendering all messages, but I haven't devised an alternate strategy that works universally well. For example, any exclusive FeedbackPanel selection criterion gets difficult when only one FeedbackPanel or another is rendered in an AJAX response. ContainerFeedbackMessageFilter might be a good fit for your inner FeedbackPanel. I'd be interested to hear what you or others use for their catch all FeedbackPanels. Dan On Mon, Sep 26, 2011 at 10:51 PM, Arjun Dhar dhar...@yahoo.com wrote: Hey, i guess i was sleeping when this one was taught. I have a Feetback panel on the parent panel. Then in a WebMarkupContainer, have added another feedback panel. When I add .info(...) or .error(...) to feedback panel in parent it appears in both. Must be some component hierarchy trickle down effect but Weird right? And if this is intentional why is it needed? - Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Feedback-panel-inherits-parent-panel-feebdack-tp3846252p3846252.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Servlet and Wicket
On Monday, September 26, 2011 8:39 PM, koha...@gmail.com koha...@gmail.com wrote: We have to have the Servlets in front due to current connection from IIS and Apache. That doesn't make any sense. For IIS and Apache it really doesn't matter at all. Here is what the architecture of my implementation looks like: Dispatcher Servlet (awaiting incoming httpservletRequest) | Wicket Components On the Application Service layer, I have EJB Beans And then on the Data Layer I have JPA/Entity My question is what should I be concerned about in accessing Wicket Components from the Servlets since the URL would be connecting directly to servlets. I would never advice to do it this way. If you want to keep your application in a request-based dispatcher kind of architecture, than don't use wicket. If your reason for moving to wicket is to have better maintainable software, then by all means, don't rebuild everything exactly the same in wicket. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicket 1.5.0 and ResourceReferences
How do I avoid the -ver-XXX version number from my resource reference
in Wicket 1.5.0?
More details:
I want to use Scriptaculous, and have a AbstractDefaultAjaxBehavior
that does a renderHead(...) { response.renderJavaScriptReference(new
JavaScriptResourceReference(this.getClass(), scriptaculous.js); }
This adds the script src ... to the header section, however, the
url to the scriptaculous includes the Wickek -ver-XXX rewrite. This in
turn results in the scriptaculous auto include
builder,effects,dragdrop etc not to load properly, due to how the
script determines the base path.
I can of course fix the way scriptaculous determines the path, but the
best way would be to have wicket serve this up as scriptaculous.js.
What am I doing wrong? Can it be fixed?
I've looked at the FilenameWithVersionResourceCachingStrategy, and I
know I can change that for the application, but won't I then change it
for all the resources? I would like only this to _not_ have the
version information.
Thanks in advance.
A
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 1.5.0 and ResourceReferences
Override
org.apache.wicket.request.resource.caching.FilenameWithVersionResourceCachingStrategy.decorateUrl(ResourceUrl,
IStaticCacheableResource) and call super only if this is not the
Prototype resource.
Use ResourceUrl to get the name of the resource.
On Tue, Sep 27, 2011 at 12:03 PM, Arne And arne@gmail.com wrote:
How do I avoid the -ver-XXX version number from my resource reference
in Wicket 1.5.0?
More details:
I want to use Scriptaculous, and have a AbstractDefaultAjaxBehavior
that does a renderHead(...) { response.renderJavaScriptReference(new
JavaScriptResourceReference(this.getClass(), scriptaculous.js); }
This adds the script src ... to the header section, however, the
url to the scriptaculous includes the Wickek -ver-XXX rewrite. This in
turn results in the scriptaculous auto include
builder,effects,dragdrop etc not to load properly, due to how the
script determines the base path.
I can of course fix the way scriptaculous determines the path, but the
best way would be to have wicket serve this up as scriptaculous.js.
What am I doing wrong? Can it be fixed?
I've looked at the FilenameWithVersionResourceCachingStrategy, and I
know I can change that for the application, but won't I then change it
for all the resources? I would like only this to _not_ have the
version information.
Thanks in advance.
A
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
wicket-spring version
Hello, Very new to Wicket. Trying to integrate an existing Spring application with the latest Wicket release. Versions: Wicket - 1.5.0 SpringFramework - 2.5.6 I am following the annotations based approach mentioned here - https://cwiki.apache.org/WICKET/spring.html. Now, which version of wicket-spring-annot do I use? In the maven repo, the latest version is 1.3.7. So, do I need to use 1.3.7 version of wicket-spring jar too? When I use 1.3.7 for both wicket-spring and wicket-spring-annot, I get this error when I start up jetty server: :2432011-09-27 11:12:58.635::WARN: failed BCWicketFilter java.lang.NoSuchMethodError: org.apache.wicket.MetaDataKey.init(Ljava/lang/Class;)V at org.apache.wicket.spring.injection.annot.SpringComponentInjector$1.init(SpringComponentInjector.java:58) at org.apache.wicket.spring.injection.annot.SpringComponentInjector.clinit(SpringComponentInjector.java:55) at com.inceptor.bcWicket.app.BCWicketApplication.init(BCWicketApplication.java:19) at org.apache.wicket.Application.initApplication(Application.java:805) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286) at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:99) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:570) at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846702.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-spring version
Don't use wicket-spring-annot, just wicket-spring. On Tuesday, September 27, 2011 3:15 AM, boy_oh_boy muralih...@gmail.com wrote: Hello, Very new to Wicket. Trying to integrate an existing Spring application with the latest Wicket release. Versions: Wicket - 1.5.0 SpringFramework - 2.5.6 I am following the annotations based approach mentioned here - https://cwiki.apache.org/WICKET/spring.html. Now, which version of wicket-spring-annot do I use? In the maven repo, the latest version is 1.3.7. So, do I need to use 1.3.7 version of wicket-spring jar too? When I use 1.3.7 for both wicket-spring and wicket-spring-annot, I get this error when I start up jetty server: :2432011-09-27 11:12:58.635::WARN: failed BCWicketFilter java.lang.NoSuchMethodError: org.apache.wicket.MetaDataKey.init(Ljava/lang/Class;)V at org.apache.wicket.spring.injection.annot.SpringComponentInjector$1.init(SpringComponentInjector.java:58) at org.apache.wicket.spring.injection.annot.SpringComponentInjector.clinit(SpringComponentInjector.java:55) at com.inceptor.bcWicket.app.BCWicketApplication.init(BCWicketApplication.java:19) at org.apache.wicket.Application.initApplication(Application.java:805) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286) at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:99) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:570) at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846702.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-spring version
See wicket-examples-1.5.0.war. It comes with the full Wicket distro and contains a demo of a Spring application. Or you can download it from Maven too. On Tue, Sep 27, 2011 at 12:39 PM, Pointbreak pointbreak+wicketst...@ml1.net wrote: Don't use wicket-spring-annot, just wicket-spring. On Tuesday, September 27, 2011 3:15 AM, boy_oh_boy muralih...@gmail.com wrote: Hello, Very new to Wicket. Trying to integrate an existing Spring application with the latest Wicket release. Versions: Wicket - 1.5.0 SpringFramework - 2.5.6 I am following the annotations based approach mentioned here - https://cwiki.apache.org/WICKET/spring.html. Now, which version of wicket-spring-annot do I use? In the maven repo, the latest version is 1.3.7. So, do I need to use 1.3.7 version of wicket-spring jar too? When I use 1.3.7 for both wicket-spring and wicket-spring-annot, I get this error when I start up jetty server: :2432011-09-27 11:12:58.635::WARN: failed BCWicketFilter java.lang.NoSuchMethodError: org.apache.wicket.MetaDataKey.init(Ljava/lang/Class;)V at org.apache.wicket.spring.injection.annot.SpringComponentInjector$1.init(SpringComponentInjector.java:58) at org.apache.wicket.spring.injection.annot.SpringComponentInjector.clinit(SpringComponentInjector.java:55) at com.inceptor.bcWicket.app.BCWicketApplication.init(BCWicketApplication.java:19) at org.apache.wicket.Application.initApplication(Application.java:805) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286) at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:99) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:570) at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846702.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-spring version
Thanks. That fixed it. The jetty and the application starts up. But when I
try to access the first page, it fails at:
public LoginService(){
Injector.get().inject(this); -- failing line
}
With the following stackTrace:
Root cause:
java.lang.NoSuchMethodError:
org.springframework.beans.factory.config.BeanDefinition.isPrimary()Z
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getBeanNameOfClass(AnnotProxyFieldValueFactory.java:232)
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getBeanName(AnnotProxyFieldValueFactory.java:164)
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getFieldValue(AnnotProxyFieldValueFactory.java:112)
at org.apache.wicket.injection.Injector.inject(Injector.java:111)
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector.inject(SpringComponentInjector.java:124)
at test.LoginService.init(LoginService.java:22)
I have checked the mvn dependency:tree to be sure that it is not referring
to different versions of spring framework. From the dependency tree, I see
the version 2.5.6 being referred and no other versions. What could be the
problem?
Thanks.
On Tue, Sep 27, 2011 at 11:40 AM, pointbreak+wicketstuff [via Apache Wicket]
ml-node+s1842946n3846753...@n4.nabble.com wrote:
Don't use wicket-spring-annot, just wicket-spring.
On Tuesday, September 27, 2011 3:15 AM, boy_oh_boy
[hidden email] http://user/SendEmail.jtp?type=nodenode=3846753i=0
wrote:
Hello,
Very new to Wicket. Trying to integrate an existing Spring application
with
the latest Wicket release.
Versions:
Wicket - 1.5.0
SpringFramework - 2.5.6
I am following the annotations based approach mentioned here -
https://cwiki.apache.org/WICKET/spring.html.
Now, which version of wicket-spring-annot do I use? In the maven repo,
the
latest version is 1.3.7. So, do I need to use 1.3.7 version of
wicket-spring jar too? When I use 1.3.7 for both wicket-spring and
wicket-spring-annot, I get this error when I start up jetty server:
:2432011-09-27 11:12:58.635::WARN: failed BCWicketFilter
java.lang.NoSuchMethodError:
org.apache.wicket.MetaDataKey.init(Ljava/lang/Class;)V
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector$1.init(SpringComponentInjector.java:58)
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector.clinit(SpringComponentInjector.java:55)
at
com.inceptor.bcWicket.app.BCWicketApplication.init(BCWicketApplication.java:19)
at org.apache.wicket.Application.initApplication(Application.java:805)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286)
at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:99)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:570)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372)
at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846702.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=1
For additional commands, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=2
-
To unsubscribe, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=3
For additional commands, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=4
--
If you reply to this email, your message will be added to the discussion
below:
http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846753.html
To unsubscribe from wicket-spring version, click
herehttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=3846702code=bXVyYWxpaGVyZUBnbWFpbC5jb218Mzg0NjcwMnwxMDcyNTUzNzAz.
--
View this message in context:
Re: wicket-spring version
Wicket is built against Spring 3.0.x. Maybe this method has been added
in 3.x or its signature has changed since 2.x
On Tue, Sep 27, 2011 at 12:54 PM, boy_oh_boy muralih...@gmail.com wrote:
Thanks. That fixed it. The jetty and the application starts up. But when I
try to access the first page, it fails at:
public LoginService(){
Injector.get().inject(this); -- failing line
}
With the following stackTrace:
Root cause:
java.lang.NoSuchMethodError:
org.springframework.beans.factory.config.BeanDefinition.isPrimary()Z
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getBeanNameOfClass(AnnotProxyFieldValueFactory.java:232)
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getBeanName(AnnotProxyFieldValueFactory.java:164)
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getFieldValue(AnnotProxyFieldValueFactory.java:112)
at org.apache.wicket.injection.Injector.inject(Injector.java:111)
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector.inject(SpringComponentInjector.java:124)
at test.LoginService.init(LoginService.java:22)
I have checked the mvn dependency:tree to be sure that it is not referring
to different versions of spring framework. From the dependency tree, I see
the version 2.5.6 being referred and no other versions. What could be the
problem?
Thanks.
On Tue, Sep 27, 2011 at 11:40 AM, pointbreak+wicketstuff [via Apache Wicket]
ml-node+s1842946n3846753...@n4.nabble.com wrote:
Don't use wicket-spring-annot, just wicket-spring.
On Tuesday, September 27, 2011 3:15 AM, boy_oh_boy
[hidden email] http://user/SendEmail.jtp?type=nodenode=3846753i=0
wrote:
Hello,
Very new to Wicket. Trying to integrate an existing Spring application
with
the latest Wicket release.
Versions:
Wicket - 1.5.0
SpringFramework - 2.5.6
I am following the annotations based approach mentioned here -
https://cwiki.apache.org/WICKET/spring.html.
Now, which version of wicket-spring-annot do I use? In the maven repo,
the
latest version is 1.3.7. So, do I need to use 1.3.7 version of
wicket-spring jar too? When I use 1.3.7 for both wicket-spring and
wicket-spring-annot, I get this error when I start up jetty server:
:2432011-09-27 11:12:58.635::WARN: failed BCWicketFilter
java.lang.NoSuchMethodError:
org.apache.wicket.MetaDataKey.init(Ljava/lang/Class;)V
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector$1.init(SpringComponentInjector.java:58)
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector.clinit(SpringComponentInjector.java:55)
at
com.inceptor.bcWicket.app.BCWicketApplication.init(BCWicketApplication.java:19)
at org.apache.wicket.Application.initApplication(Application.java:805)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286)
at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:99)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:570)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372)
at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846702.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=1
For additional commands, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=2
-
To unsubscribe, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=3
For additional commands, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846753i=4
--
If you reply to this email, your message will be added to the discussion
below:
http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846753.html
To unsubscribe from wicket-spring version, click
Re: Wicket 1.5.0 and ResourceReferences
Hmm. I see. This is not the solution I hoped for. I liked the
public Time getLastModified() {
return null;
}
method on the ResourceReference...
oh well...
A
On Tue, Sep 27, 2011 at 12:06 PM, Martin Grigorov mgrigo...@apache.org wrote:
Override
org.apache.wicket.request.resource.caching.FilenameWithVersionResourceCachingStrategy.decorateUrl(ResourceUrl,
IStaticCacheableResource) and call super only if this is not the
Prototype resource.
Use ResourceUrl to get the name of the resource.
On Tue, Sep 27, 2011 at 12:03 PM, Arne And arne@gmail.com wrote:
How do I avoid the -ver-XXX version number from my resource reference
in Wicket 1.5.0?
More details:
I want to use Scriptaculous, and have a AbstractDefaultAjaxBehavior
that does a renderHead(...) { response.renderJavaScriptReference(new
JavaScriptResourceReference(this.getClass(), scriptaculous.js); }
This adds the script src ... to the header section, however, the
url to the scriptaculous includes the Wickek -ver-XXX rewrite. This in
turn results in the scriptaculous auto include
builder,effects,dragdrop etc not to load properly, due to how the
script determines the base path.
I can of course fix the way scriptaculous determines the path, but the
best way would be to have wicket serve this up as scriptaculous.js.
What am I doing wrong? Can it be fixed?
I've looked at the FilenameWithVersionResourceCachingStrategy, and I
know I can change that for the application, but won't I then change it
for all the resources? I would like only this to _not_ have the
version information.
Thanks in advance.
A
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: DecimalFormatLabel (proposed)
I have submitted a patch https://issues.apache.org/jira/browse/WICKET-4085 Wicket-4085 . for a formatted label. I cant figure what would be the best way to handle an IllegalArgumentException which is thrown when the supplied format object in not valid for the underlying data object. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/DecimalFormatLabel-proposed-tp3834813p3847356.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-spring version
Thanks. I was able to update the Spring version to 3.0+ and that has fixed
it (I also had to update the hibernate dependency to 3.2+ version).
Everything working as expected.
On Tue, Sep 27, 2011 at 11:58 AM, Martin Grigorov-4 [via Apache Wicket]
ml-node+s1842946n3846797...@n4.nabble.com wrote:
Wicket is built against Spring 3.0.x. Maybe this method has been added
in 3.x or its signature has changed since 2.x
On Tue, Sep 27, 2011 at 12:54 PM, boy_oh_boy [hidden
email]http://user/SendEmail.jtp?type=nodenode=3846797i=0
wrote:
Thanks. That fixed it. The jetty and the application starts up. But when
I
try to access the first page, it fails at:
public LoginService(){
Injector.get().inject(this); -- failing line
}
With the following stackTrace:
Root cause:
java.lang.NoSuchMethodError:
org.springframework.beans.factory.config.BeanDefinition.isPrimary()Z
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getBeanNameOfClass(AnnotProxyFieldValueFactory.java:232)
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getBeanName(AnnotProxyFieldValueFactory.java:164)
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getFieldValue(AnnotProxyFieldValueFactory.java:112)
at org.apache.wicket.injection.Injector.inject(Injector.java:111)
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector.inject(SpringComponentInjector.java:124)
at test.LoginService.init(LoginService.java:22)
I have checked the mvn dependency:tree to be sure that it is not
referring
to different versions of spring framework. From the dependency tree, I
see
the version 2.5.6 being referred and no other versions. What could be the
problem?
Thanks.
On Tue, Sep 27, 2011 at 11:40 AM, pointbreak+wicketstuff [via Apache
Wicket]
[hidden email] http://user/SendEmail.jtp?type=nodenode=3846797i=1
wrote:
Don't use wicket-spring-annot, just wicket-spring.
On Tuesday, September 27, 2011 3:15 AM, boy_oh_boy
[hidden email] http://user/SendEmail.jtp?type=nodenode=3846753i=0
wrote:
Hello,
Very new to Wicket. Trying to integrate an existing Spring application
with
the latest Wicket release.
Versions:
Wicket - 1.5.0
SpringFramework - 2.5.6
I am following the annotations based approach mentioned here -
https://cwiki.apache.org/WICKET/spring.html.
Now, which version of wicket-spring-annot do I use? In the maven repo,
the
latest version is 1.3.7. So, do I need to use 1.3.7 version of
wicket-spring jar too? When I use 1.3.7 for both wicket-spring and
wicket-spring-annot, I get this error when I start up jetty server:
:2432011-09-27 11:12:58.635::WARN: failed BCWicketFilter
java.lang.NoSuchMethodError:
org.apache.wicket.MetaDataKey.init(Ljava/lang/Class;)V
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector$1.init(SpringComponentInjector.java:58)
at
org.apache.wicket.spring.injection.annot.SpringComponentInjector.clinit(SpringComponentInjector.java:55)
at
com.inceptor.bcWicket.app.BCWicketApplication.init(BCWicketApplication.java:19)
at org.apache.wicket.Application.initApplication(Application.java:805)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:99)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:570)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:139)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372)
at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/wicket-spring-version-tp3846702p3846702.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [hidden email]
http://user/SendEmail.jtp?type=nodenode=3846753i=1
For additional commands, e-mail: [hidden email]
http://user/SendEmail.jtp?type=nodenode=3846753i=2
-
To
Re: DecimalFormatLabel (proposed)
wrap it in a wicket runtime exception -igor On Tue, Sep 27, 2011 at 6:32 AM, Pranav kacholia pranav.kacho...@gmail.com wrote: I have submitted a patch https://issues.apache.org/jira/browse/WICKET-4085 Wicket-4085 . for a formatted label. I cant figure what would be the best way to handle an IllegalArgumentException which is thrown when the supplied format object in not valid for the underlying data object. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/DecimalFormatLabel-proposed-tp3834813p3847356.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 1.5.0 and ResourceReferences
switch to QueryStringWithVersionResourceCachingStrategy, it does not
modify file names
-igor
On Tue, Sep 27, 2011 at 3:03 AM, Arne And arne@gmail.com wrote:
How do I avoid the -ver-XXX version number from my resource reference
in Wicket 1.5.0?
More details:
I want to use Scriptaculous, and have a AbstractDefaultAjaxBehavior
that does a renderHead(...) { response.renderJavaScriptReference(new
JavaScriptResourceReference(this.getClass(), scriptaculous.js); }
This adds the script src ... to the header section, however, the
url to the scriptaculous includes the Wickek -ver-XXX rewrite. This in
turn results in the scriptaculous auto include
builder,effects,dragdrop etc not to load properly, due to how the
script determines the base path.
I can of course fix the way scriptaculous determines the path, but the
best way would be to have wicket serve this up as scriptaculous.js.
What am I doing wrong? Can it be fixed?
I've looked at the FilenameWithVersionResourceCachingStrategy, and I
know I can change that for the application, but won't I then change it
for all the resources? I would like only this to _not_ have the
version information.
Thanks in advance.
A
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: DecimalFormatLabel (proposed)
Updated the patch and resubmitted. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/DecimalFormatLabel-proposed-tp3834813p3847952.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How to handle errors in RequestCycle.onEndRequest
I was thinking about something like that too, but this does look like a dangerous task. And I think in the long run migrating to 1.5.0 is a better solution. The Sanity Resort http://sanityresort.blogspot.com/ Am 27.09.2011 07:50, schrieb Hans Lesmeister 2: Hi, maybe you can override WebRequestCycleProcessor.respond: but I did not try if that's too late as well -
AbstractComponentEventSender
I was going through the wicket code and i think a lot of the code that is
available in ComponentEventSender should be made reuseable. Right now it is
final, which makes sense since i cant see any real extension points in it.
Perhaps the following change:- (alongside making ComponentEvent non-final)
(the following probably wont compile, but you get the idea)
final class ComponentEventT extends AbstractComponentEventSender{
/
@Override
public ComponentEventT generateEvent(IEventSink sink, Broadcast type, T
payload) {
return new ComponentEventT(sink, source, type, payload);
}
}
public abstract class AbstractComponentEventSenderT implements
IEventSource{
// all code remains the same as existing ComponentEventSender
public T void send(IEventSink sink, Broadcast type, T payload)
{
ComponentEvent?event =generateEvent();
// ComponentEvent? event = new ComponentEventT(sink,
source, type,
payload);
Args.notNull(type, type);
switch (type)
{
case BUBBLE :
bubble(event);
break;
case BREADTH :
breadth(event);
break;
case DEPTH :
depth(event);
break;
case EXACT :
dispatcher.dispatchEvent(event.getSink(),
event, ((sink instanceof
Component)
? (Component)sink : null));
break;
}
}
abstract public ComponentEvent generateEvent(IEventSink sink, Broadcast
type, T payload) ;
}
///
Doing this would enable everyone to extend AbstractComponentEventSender to
use new Events which would be extensions of ComponentEvent.
I would have preferred to use IEvent, but the interface only has 'set'
methods for all its variables, and no get' methods, so we cant really use
that.
Ithink it would increase the flexibility and prevent people from having to
copy-paste componenteventsender which is more complicated to rebuild from
scratch than writing a new IEventDispatcher..
In Wicket.next i think the get methods should be included int the IEvent
interface.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/AbstractComponentEventSender-tp3848238p3848238.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: creating a textarea with a radiobutton using Listview
BTW, i just figured out that changing selected checkbox removed the data in the textareas. First you need to save and then change the selected checkboxes. Rendering form in each ajax update behaviour deletes the model value..How can we solve this? Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/creating-a-textarea-with-a-radiobutton-using-Listview-tp3829602p3848282.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AbstractComponentEventSender
What other specializations of AbstractComponentEventSender do you need ?
On Tue, Sep 27, 2011 at 7:06 PM, Pranav kacholia
pranav.kacho...@gmail.com wrote:
I was going through the wicket code and i think a lot of the code that is
available in ComponentEventSender should be made reuseable. Right now it is
final, which makes sense since i cant see any real extension points in it.
Perhaps the following change:- (alongside making ComponentEvent non-final)
(the following probably wont compile, but you get the idea)
final class ComponentEventT extends AbstractComponentEventSender{
/
@Override
public ComponentEventT generateEvent(IEventSink sink, Broadcast type, T
payload) {
return new ComponentEventT(sink, source, type, payload);
}
}
public abstract class AbstractComponentEventSenderT implements
IEventSource{
// all code remains the same as existing ComponentEventSender
public T void send(IEventSink sink, Broadcast type, T payload)
{
ComponentEvent?event =generateEvent();
// ComponentEvent? event = new ComponentEventT(sink,
source, type,
payload);
Args.notNull(type, type);
switch (type)
{
case BUBBLE :
bubble(event);
break;
case BREADTH :
breadth(event);
break;
case DEPTH :
depth(event);
break;
case EXACT :
dispatcher.dispatchEvent(event.getSink(),
event, ((sink instanceof
Component)
? (Component)sink : null));
break;
}
}
abstract public ComponentEvent generateEvent(IEventSink sink, Broadcast
type, T payload) ;
}
///
Doing this would enable everyone to extend AbstractComponentEventSender to
use new Events which would be extensions of ComponentEvent.
I would have preferred to use IEvent, but the interface only has 'set'
methods for all its variables, and no get' methods, so we cant really use
that.
Ithink it would increase the flexibility and prevent people from having to
copy-paste componenteventsender which is more complicated to rebuild from
scratch than writing a new IEventDispatcher..
In Wicket.next i think the get methods should be included int the IEvent
interface.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/AbstractComponentEventSender-tp3848238p3848238.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Servlet and Wicket
Are you saying that I can either use Wicket without Servlet or use Servlet with JSP/JSF just like our previous implementation? I thought Wicket components would work under a Servlet environment. If Wicket cannot run under Servlet then, I would like to know now so that we can consider JSF instead. Your response is appreciated. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Servlet-and-Wicket-tp3844944p3848610.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AbstractComponentEventSender
you are not meant to provide your own implementations of IEvent, rather it is IEvent#getPayload() that contain different representations of the event. -igor On Tue, Sep 27, 2011 at 12:16 PM, Pranav kacholia pranav.kacho...@gmail.com wrote: It is more about the ability to choose which class of event you are despatching. In this case they will be all extending ComponentEvent. Maybe there is someway of having a generic IEvent child class sent. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AbstractComponentEventSender-tp3848238p3848687.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AbstractComponentEventSender
Alright. Thank you :) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AbstractComponentEventSender-tp3848238p3849133.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
