Re: wicketstuff gmap GInfoWindow with Component content
Hi Dieter,
There is an example to:
https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/gmap3-parent/gmap3-examples/src/main/java/org/wicketstuff/examples/gmap/info/advanced
Thijs
On 22-3-2013 9:10, Dieter Tremel wrote:
Hello,
I would like to show an info window on clicking on a map marker with
detailed information about an entity, including links and so on. I coded
a special panel for this.
I think therefor I should use the Constructor
public GInfoWindow(GLatLng latLng, Component content)
As I read from the Code
this.content = document.getElementById(' + markupId + ');
contentIsNode = true;
only the id of the component is used and the placement in the window is
done by some javascript, referencing the id in a json structure.
As I didn't find an example and i do not understand where the component
should be rendered in fact, I ask here. Should there be one panel
supported with data by a model of the entity, rendered somehow hidden in
another place?
Any hint for way to do it or a solution welcome.
Thank You
Dieter Tremel
-
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: how to fix this error in wicket app
Have you ever fixed this problem? We are seeing the same issues with our application. Thijs On 28-11-2012 0:03, saty wrote: continued from above... /wicket:panel/div div class=imxt-a imxt-nowrap0/div div class=imxt-a imxt-nowrap0.2001/div div class=imxt-a imxt-nowrap/div div class=imxt-a imxt-nowrap0.4771/div div class=imxt-a imxt-nowrap/divdiv wicket:id=item class=imxt-a imxt-nowrapwicket:panel ./wicket/resource/com.apollo.pricematrix.web.pricing.priceview.PriceIndicatorPanel/up-ver-1354055622963.gif?antiCache=1354056400520 nbsp; 0.2001 /wicket:panel/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel xmlns:wicket=http://wicket.apache.org; div class=imxt-select-container input type=checkbox wicket:id=checkbox onchange=return false class=imxt-select id=checkbox3e2/ /div /wicket:panel/div div class=imxt-a imxt-nowrap21/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel div wicket:id=label id=label43d3MO LIBOR IR CAP 8% 6/13/div /wicket:panel/div div class=imxt-a imxt-nowrap/divdiv class=imxt-a imxt-nowrapUSD/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel div wicket:id=detailsWindow id=detailsWindow43e style=display:nonewicket:panel xmlns:wicket=http://wicket.apache.org; /wicket:panel/div span wicket:id=label id=label43f # 1 ./wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/indicator-ver-1352317451197.gif /wicket:panel/div div class=imxt-a imxt-nowrap-0.0807/div div wicket:id=item class=imxt-a imxt-nowrapwicket:panel ./wicket/resource/com.apollo.pricematrix.web.pricing.priceview.DayChangePriceIndicatorPanel/up-ver-1354055622963.gif?antiCache=1354056400520 nbsp; 0.0807 /wicket:panel/div div class=imxt-a imxt-nowrap0/div div class=imxt-a imxt-nowrap0.0807/div div class=imxt-a imxt-nowrap/div div class=imxt-a imxt-nowrap0./div div class=imxt-a imxt-nowrap/divdiv wicket:id=item class=imxt-a imxt-nowrapwicket:panel ./wicket/resource/com.apollo.pricematrix.web.pricing.priceview.PriceIndicatorPanel/up-ver-1354055622963.gif?antiCache=1354056400520 nbsp; 0.0807 /wicket:panel/div /wicket:panel /div /div /fieldset/div div class=imxt-bottom-toolbar-container wicket:panel xmlns:wicket=http://wicket.apache.org; div class=imxt-navigator-toolbar style=overflow: hidden; _height: 1%; padding-right: 0.5em; padding-left: 0.5em; div style=float: left; padding-top: 0.2em; div wicket:id=navigationLabelShowing 1 to 78 of 78/div /div div style=float: right; div wicket:id=navigator id=navigator234wicket:panel div class=imxt-paging-navigator emlt;lt;/em em/em em1/em em/em emgt;gt;/em /div /wicket:panel/div /div /div /wicket:panel /div /div /wicket:panel/div]]/componentheader-contribution encoding=wicket1 /header-contributionpriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority-evaluate/priority-evaluatepriority
Re: how to fix this error in wicket app
That's great! Thanks On 16/1/13 17:25, saty wrote: Yes, this has been fixed in wicket 6.4.0 See below for more on this fix. http://apache-wicket.1842946.n4.nabble.com/understanding-ajax-response-td4654310.html#a4654715 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-fix-this-error-in-wicket-app-tp4653954p4655431.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: Expiration page not shown in case of back button usage
Hi, I'm still battling this issue. I have a working quickstart that demonstrates the issue we have. Should I open a ticket? Kind regards Thijs On 12-12-2012 15:07, Thijs wrote: No it doesn't hit the browser cache. It's actually recreating a new Page. We've put breakpoints in Wicket to establish that. In PageProvider is trying to create a new Instance see the stacktrace. The following stacktrace is taken when we use the 'backspace' or 'back button' in the browser after a session has expired. [2012-12-12 14:42:11,535 TP-Processor11 ERROR org.apache.wicket.DefaultExceptionMapper:$L] Unexpected error occurred org.apache.wicket.WicketRuntimeException: Unable to create page from class org.bar.bla.FooPage. Class does not have a visible default contructor. at org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:79) at org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:133) at org.apache.wicket.core.request.handler.PageProvider.resolvePageInstance(PageProvider.java:278) at org.apache.wicket.core.request.handler.PageProvider.getPageInstance(PageProvider.java:166) at org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78) at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:94) at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:244) at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:165) at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:814) at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:253) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:210) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:281) at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:245) Not that in this case we have a page mounted with no Default Constructor or Constructor with page parameters because we only want a 'nice' url for this page. We also have situations where we have multiple entry points for a Web application where one page can be reached with page parameters or through a constructor taking an object. In both cases we don't want these pages to be recreated when the session is expired. Thijs On 12-12-2012 9:40, Martin Grigorov wrote: It seems that the browser tries to load the page from its cache. I think you need to set proper cache headers to always ask the server instead of using the local data. On Tue, Dec 11, 2012 at 6:59 PM, Rob Sonker...@tigrou.nl wrote: Yes I know but by using the back button it seems to be ignored. Like it tries to serve the same page no matter we have a session or not. On Tue, Dec 11, 2012 at 9:59 AM, Martin Grigorov mgrigo...@apache.org wrote: On Mon, Dec 10, 2012 at 9:04 AM, Rob Sonker...@tigrou.nl wrote: Last week we fixed an issue with Wicket 6 where mounted pages were being reconstructed after the session expired. That was due to this (new) setting which we set to false now: getPageSettings().setRecreateMountedPagesAfterExpiry(false); This worked perfectly for clicking on (ajax) links but, this doesn't seem to work when I use the back button of the browser after the session expired. What happens is that Wicket tries to reconstruct the previous (mounted bookmarkable) page. But that's failing in our case because we dont support that as every page needs session information. Am I doing something wrong? As I would expect a PageExpiredException in this case. If you need PEE then this is the correct setting. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: Expiration page not shown in case of back button usage
Done: https://issues.apache.org/jira/browse/WICKET-4932 Thanks in advance for looking On 19-12-2012 13:47, Martin Grigorov wrote: Yes, please. On Wed, Dec 19, 2012 at 2:16 PM, Thijs vonk.th...@gmail.com wrote: Hi, I'm still battling this issue. I have a working quickstart that demonstrates the issue we have. Should I open a ticket? Kind regards Thijs On 12-12-2012 15:07, Thijs wrote: No it doesn't hit the browser cache. It's actually recreating a new Page. We've put breakpoints in Wicket to establish that. In PageProvider is trying to create a new Instance see the stacktrace. The following stacktrace is taken when we use the 'backspace' or 'back button' in the browser after a session has expired. [2012-12-12 14:42:11,535 TP-Processor11 ERROR org.apache.wicket.**DefaultExceptionMapper:$L] Unexpected error occurred org.apache.wicket.**WicketRuntimeException: Unable to create page from class org.bar.bla.FooPage. Class does not have a visible default contructor. at org.apache.wicket.session.**DefaultPageFactory.newPage(** DefaultPageFactory.java:79) at org.apache.wicket.**DefaultMapperContext.**newPageInstance(** DefaultMapperContext.java:133) at org.apache.wicket.core.**request.handler.PageProvider.** resolvePageInstance(**PageProvider.java:278) at org.apache.wicket.core.**request.handler.PageProvider.** getPageInstance(PageProvider.**java:166) at org.apache.wicket.request.**handler.render.PageRenderer.** getPage(PageRenderer.java:78) at org.apache.wicket.request.**handler.render.** WebPageRenderer.renderPage(**WebPageRenderer.java:94) at org.apache.wicket.request.**handler.render.**WebPageRenderer.respond(* *WebPageRenderer.java:244) at org.apache.wicket.core.**request.handler.**RenderPageRequestHandler.** respond(**RenderPageRequestHandler.java:**165) at org.apache.wicket.request.**cycle.RequestCycle$** HandlerExecutor.respond(**RequestCycle.java:814) at org.apache.wicket.request.**RequestHandlerStack.execute(** RequestHandlerStack.java:64) at org.apache.wicket.request.**cycle.RequestCycle.execute(** RequestCycle.java:253) at org.apache.wicket.request.**cycle.RequestCycle.** processRequest(RequestCycle.**java:210) at org.apache.wicket.request.**cycle.RequestCycle.** processRequestAndDetach(**RequestCycle.java:281) at org.apache.wicket.protocol.**http.WicketFilter.** processRequest(WicketFilter.**java:188) at org.apache.wicket.protocol.**http.WicketFilter.doFilter(** WicketFilter.java:245) Not that in this case we have a page mounted with no Default Constructor or Constructor with page parameters because we only want a 'nice' url for this page. We also have situations where we have multiple entry points for a Web application where one page can be reached with page parameters or through a constructor taking an object. In both cases we don't want these pages to be recreated when the session is expired. Thijs On 12-12-2012 9:40, Martin Grigorov wrote: It seems that the browser tries to load the page from its cache. I think you need to set proper cache headers to always ask the server instead of using the local data. On Tue, Dec 11, 2012 at 6:59 PM, Rob Sonker...@tigrou.nl wrote: Yes I know but by using the back button it seems to be ignored. Like it tries to serve the same page no matter we have a session or not. On Tue, Dec 11, 2012 at 9:59 AM, Martin Grigorov mgrigo...@apache.org wrote: On Mon, Dec 10, 2012 at 9:04 AM, Rob Sonker...@tigrou.nl wrote: Last week we fixed an issue with Wicket 6 where mounted pages were being reconstructed after the session expired. That was due to this (new) setting which we set to false now: getPageSettings().**setRecreateMountedPagesAfterEx**piry(false); This worked perfectly for clicking on (ajax) links but, this doesn't seem to work when I use the back button of the browser after the session expired. What happens is that Wicket tries to reconstruct the previous (mounted bookmarkable) page. But that's failing in our case because we dont support that as every page needs session information. Am I doing something wrong? As I would expect a PageExpiredException in this case. If you need PEE then this is the correct setting. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Question about UrlRenderer and WebServletResponse
Hi, I'm trying to revive Wicket Portlets support and I'm running into a small issue. For Liferay i've got my old 1.4 portlets working 90% with Wicket 6 but I'm hitting a small problem with the UrlRenderer and WebServletResponse WebServletResponse does an optimization for tomcat in the sendRedirect method. it strips the ./ from the url. However in the case of portlet this causes a endless loop in some scenarios. Would it be possible to put this optimization in the UrlRenderer? So that we can choose to override this by providing a custom PortletUrlRenderer. While digging into this I also came a cross another thing. WebServletResponse.encodeRedirectURL(url) uses new UrlRenderer(webRequest) while WebServletResponse. encodeUrl(url) uses the RequestCycle.get().getUrlRenderer(). Why doesn't WebServletResponse.encodeRedirectURL(url) use RequestCycle.get().getUrlRenderer(). As this last method gives the custom UrlRenderer back that we use in the PortletRequestCylce instead of just the default. Kind regard Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Expiration page not shown in case of back button usage
No it doesn't hit the browser cache. It's actually recreating a new Page. We've put breakpoints in Wicket to establish that. In PageProvider is trying to create a new Instance see the stacktrace. The following stacktrace is taken when we use the 'backspace' or 'back button' in the browser after a session has expired. [2012-12-12 14:42:11,535 TP-Processor11 ERROR org.apache.wicket.DefaultExceptionMapper:$L] Unexpected error occurred org.apache.wicket.WicketRuntimeException: Unable to create page from class org.bar.bla.FooPage. Class does not have a visible default contructor. at org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:79) at org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:133) at org.apache.wicket.core.request.handler.PageProvider.resolvePageInstance(PageProvider.java:278) at org.apache.wicket.core.request.handler.PageProvider.getPageInstance(PageProvider.java:166) at org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78) at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:94) at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:244) at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:165) at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:814) at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:253) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:210) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:281) at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:245) Not that in this case we have a page mounted with no Default Constructor or Constructor with page parameters because we only want a 'nice' url for this page. We also have situations where we have multiple entry points for a Web application where one page can be reached with page parameters or through a constructor taking an object. In both cases we don't want these pages to be recreated when the session is expired. Thijs On 12-12-2012 9:40, Martin Grigorov wrote: It seems that the browser tries to load the page from its cache. I think you need to set proper cache headers to always ask the server instead of using the local data. On Tue, Dec 11, 2012 at 6:59 PM, Rob Sonke r...@tigrou.nl wrote: Yes I know but by using the back button it seems to be ignored. Like it tries to serve the same page no matter we have a session or not. On Tue, Dec 11, 2012 at 9:59 AM, Martin Grigorov mgrigo...@apache.org wrote: On Mon, Dec 10, 2012 at 9:04 AM, Rob Sonke r...@tigrou.nl wrote: Last week we fixed an issue with Wicket 6 where mounted pages were being reconstructed after the session expired. That was due to this (new) setting which we set to false now: getPageSettings().setRecreateMountedPagesAfterExpiry(false); This worked perfectly for clicking on (ajax) links but, this doesn't seem to work when I use the back button of the browser after the session expired. What happens is that Wicket tries to reconstruct the previous (mounted bookmarkable) page. But that's failing in our case because we dont support that as every page needs session information. Am I doing something wrong? As I would expect a PageExpiredException in this case. If you need PEE then this is the correct setting. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: Wicket as portlet
Hi Colin, How much I hate to tell you, but your mostly on your own. We are currently on Wicket 1.4 for our portlets and also planning an upgrade to Wicket 6. But portlet support is at your own risk as non of the core committers is comfortable with portlets so it's no longer a core feature. Most information on the portlet stuff can be found here [1] and here[2] is a working but not fully tested code base for Wicket 6. Most of the people (that I know of) using Wicket portlet use Liferay. I don't know of any people using IBM portal. Hope this helps. Thijs [1] https://issues.apache.org/jira/browse/WICKET-4019 [2] https://github.com/matthiasgasser/wicket-portlet On 28-11-2012 8:52, Colin Chalmers wrote: Hello all, We currently have a wicket-1.5.9 application running at a client and next year they want to migrate this to IBM Portal based on JSR-286. I have read some mixed messages on the maillist concerning wicket support for portlets and specifically the IBM Portal container so I am unsure of the current status. Before embarking on this I'd like to verify the current portlet support and am interested in hearing from anyone who has experience with Wicket portlets running inside the IBM Portal conatiner. rgds Colin - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
When Ajax precondition fails no post event handler is called
Hi,
We have an overlay that is triggered by a ajax global event listener. like:
Wicket.Event.subscribe('/ajax/call/before', function(jqEvent,
attributes, jqXHR, errorThrown, textStatus) {
showBusysignAjax();
});
Put when the precondition of the ajax call fails none of the
'/ajax/call/after|complete|failure|success is called causing the overlay
to keep being displayed.
When a precondition fails, doesn't the '/ajax/call/failure|complete'
need to be called?
Thijs
Re: Add an invisible component to an AjaxRequestTarget target
Revisiting this.
I'm still having some troubles with this.
Say I have:
Label a;
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
add(new AjaxLink(..){
onClick(AjaxRequestTarget t){t.add(a);}
};
In this case the debug window will start calling mayhem as clearly label
a is not on the page so it can't find the component to update.
So my question is:
Is it common practice to always do something like:
AjaxLink(){
onClick(AjaxRequestTarget t){
if(a.isVisibleInHierarchy())
t.add(a);
}
}
Or should I always do:
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
showPhoto.setOutputMarkupPlaceholderTag(true);
Or could the AjaxRequestTarget be modified to do the
isVisibleInHierarchy() before actually rendering the component?
Thanks
On 6-9-2012 22:47, Thijs Vonk wrote:
OK thnx will give it a try
On 6/9/12 22:39, Igor Vaynberg wrote:
isVisibleInHierarchy() will make sure all parents are visible as well
-igor
On Thu, Sep 6, 2012 at 1:27 PM, Thijs Vonk vonk.th...@gmail.com wrote:
Hi,
We have partial page updates all over a page. So panels and
components all
over the place that need Ajax updates.
We're using an Interface on those components and with an IVisitor we
traverse the component tree and add every component to the target
that has
this interface.
But during development we see that we get errors in the ajax debug
log when
these components have an invisible state. These components
themselves can
have this state but some of the times, the parent component is
invisible. In
these cases when such a hidden component is added to the
AjaxRequestTarget
we get an error in the ajax debug log.
Adding the isVisible check before adding the component to the target
could
save us in some situations but not all (as it might get visible or
invisible) at a later state.
How can I prevent these components from being added to the
AjaxRequestTarget? Or from the error being thrown? I had hoped that a
component being in an invisible state (somewhere in the tree)
wouldn't get
rendered. It's not really a problem in a 'deployment' situation, but
it's
not 'nice' either.
Thijs
-
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Add an invisible component to an AjaxRequestTarget target
On 17-10-2012 9:40, Martin Grigorov wrote:
Hi,
On Wed, Oct 17, 2012 at 9:27 AM, Thijs vonk.th...@gmail.com wrote:
Revisiting this.
I'm still having some troubles with this.
Say I have:
Label a;
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
add(new AjaxLink(..){
onClick(AjaxRequestTarget t){t.add(a);}
};
In this case the debug window will start calling mayhem as clearly label a
is not on the page so it can't find the component to update.
So my question is:
Is it common practice to always do something like:
AjaxLink(){
onClick(AjaxRequestTarget t){
if(a.isVisibleInHierarchy())
t.add(a);
}
}
Or should I always do:
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
showPhoto.setOutputMarkupPlaceholderTag(true);
I think you need : a.setOutputMarkupPlaceholderTag(true), not sure
what 'showPhoto' is.
Yes correct.
setOutputMarkupPlaceholderTag(true) calls setOutputMarkupId(true) for
you, so there is no need to call both of them.
Or could the AjaxRequestTarget be modified to do the isVisibleInHierarchy()
before actually rendering the component?
This is possible but it will lead to more confusion. In this case your
component wont be modified at all and there wont be any indication. We
can add a WARN in the logs but my experience shows that not many
developers actually follow the logs.
Not sure what the issue would be with this. As the component isn't
visible on the anyway.
But basically your answer is: Yes when you add a component to the
AjaxRequestTarget that might not be visible, make sure that
setOutputMarkupPlaceholderTag(true) is always called on that component?!
Thanks
On 6-9-2012 22:47, Thijs Vonk wrote:
OK thnx will give it a try
On 6/9/12 22:39, Igor Vaynberg wrote:
isVisibleInHierarchy() will make sure all parents are visible as well
-igor
On Thu, Sep 6, 2012 at 1:27 PM, Thijs Vonk vonk.th...@gmail.com wrote:
Hi,
We have partial page updates all over a page. So panels and components
all
over the place that need Ajax updates.
We're using an Interface on those components and with an IVisitor we
traverse the component tree and add every component to the target that
has
this interface.
But during development we see that we get errors in the ajax debug log
when
these components have an invisible state. These components themselves
can
have this state but some of the times, the parent component is
invisible. In
these cases when such a hidden component is added to the
AjaxRequestTarget
we get an error in the ajax debug log.
Adding the isVisible check before adding the component to the target
could
save us in some situations but not all (as it might get visible or
invisible) at a later state.
How can I prevent these components from being added to the
AjaxRequestTarget? Or from the error being thrown? I had hoped that a
component being in an invisible state (somewhere in the tree) wouldn't
get
rendered. It's not really a problem in a 'deployment' situation, but
it's
not 'nice' either.
Thijs
-
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
-
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: Add an invisible component to an AjaxRequestTarget target
Thanks Bas and Martin,
I'll have to update company rules then ;-)
Thijs
On 17-10-2012 9:56, Bas Gooren wrote:
Thijs,
We've been working with wicket for a number of years now, and yes, we
have two rules (that feel very natural after those years...):
- Do I need to replace this component over AJAX: call
setOutputMarkupId(true)
- Idem, but can the component itself be hidden (usually quite visible
as we override onConfigure() to control visibility): call
setOutputMarkupPlaceholderTag(true).
The beauty of wicket is that it is quite clear if you forget.
The AJAX Debug window in the bottom right of your browser window
will turn red, and once you open it, will say it cannot replace a
component since it's not in the markup.
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 17-10-2012 9:52, schreef Thijs:
On 17-10-2012 9:40, Martin Grigorov wrote:
Hi,
On Wed, Oct 17, 2012 at 9:27 AM, Thijs vonk.th...@gmail.com wrote:
Revisiting this.
I'm still having some troubles with this.
Say I have:
Label a;
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
add(new AjaxLink(..){
onClick(AjaxRequestTarget t){t.add(a);}
};
In this case the debug window will start calling mayhem as clearly
label a
is not on the page so it can't find the component to update.
So my question is:
Is it common practice to always do something like:
AjaxLink(){
onClick(AjaxRequestTarget t){
if(a.isVisibleInHierarchy())
t.add(a);
}
}
Or should I always do:
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
showPhoto.setOutputMarkupPlaceholderTag(true);
I think you need : a.setOutputMarkupPlaceholderTag(true), not sure
what 'showPhoto' is.
Yes correct.
setOutputMarkupPlaceholderTag(true) calls setOutputMarkupId(true) for
you, so there is no need to call both of them.
Or could the AjaxRequestTarget be modified to do the
isVisibleInHierarchy()
before actually rendering the component?
This is possible but it will lead to more confusion. In this case your
component wont be modified at all and there wont be any indication. We
can add a WARN in the logs but my experience shows that not many
developers actually follow the logs.
Not sure what the issue would be with this. As the component isn't
visible on the anyway.
But basically your answer is: Yes when you add a component to the
AjaxRequestTarget that might not be visible, make sure that
setOutputMarkupPlaceholderTag(true) is always called on that component?!
Thanks
On 6-9-2012 22:47, Thijs Vonk wrote:
OK thnx will give it a try
On 6/9/12 22:39, Igor Vaynberg wrote:
isVisibleInHierarchy() will make sure all parents are visible as
well
-igor
On Thu, Sep 6, 2012 at 1:27 PM, Thijs Vonk vonk.th...@gmail.com
wrote:
Hi,
We have partial page updates all over a page. So panels and
components
all
over the place that need Ajax updates.
We're using an Interface on those components and with an
IVisitor we
traverse the component tree and add every component to the
target that
has
this interface.
But during development we see that we get errors in the ajax
debug log
when
these components have an invisible state. These components
themselves
can
have this state but some of the times, the parent component is
invisible. In
these cases when such a hidden component is added to the
AjaxRequestTarget
we get an error in the ajax debug log.
Adding the isVisible check before adding the component to the
target
could
save us in some situations but not all (as it might get visible or
invisible) at a later state.
How can I prevent these components from being added to the
AjaxRequestTarget? Or from the error being thrown? I had hoped
that a
component being in an invisible state (somewhere in the tree)
wouldn't
get
rendered. It's not really a problem in a 'deployment' situation,
but
it's
not 'nice' either.
Thijs
-
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
-
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Add an invisible component to an AjaxRequestTarget target
Yes I know.
This is something we just silently ignored over the last years, as it
was not affecting any functionality.
But now with the red flashing debug window it's getting annoying. (So
some good has come from that ) And we were wondering if what we did was
actually wrong ;)
Thijs
On 17-10-2012 10:01, Bas Gooren wrote:
And to add to this: make sure you call
setOutputMarkupPlaceholderTag(true) before you render the (possibly
invisible) component for the first time.
Suppose your component is hidden (setVisible(false)) on the first render.
If you now call setOutputMarkupPlaceholderTag(true) in the ajax
request that needs to repaint the component, it still won't work as
there is no markup placeholder.
So call setOutputMarkupPlaceholderTag(true) when you create the
component :-)
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 17-10-2012 9:57, schreef Martin Grigorov:
On Wed, Oct 17, 2012 at 9:52 AM, Thijs vonk.th...@gmail.com wrote:
On 17-10-2012 9:40, Martin Grigorov wrote:
Hi,
On Wed, Oct 17, 2012 at 9:27 AM, Thijs vonk.th...@gmail.com wrote:
Revisiting this.
I'm still having some troubles with this.
Say I have:
Label a;
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
add(new AjaxLink(..){
onClick(AjaxRequestTarget t){t.add(a);}
};
In this case the debug window will start calling mayhem as clearly
label
a
is not on the page so it can't find the component to update.
So my question is:
Is it common practice to always do something like:
AjaxLink(){
onClick(AjaxRequestTarget t){
if(a.isVisibleInHierarchy())
t.add(a);
}
}
Or should I always do:
add(a = Label(...)
{ onConfigure(){setVisible(*false due to some condition*)}});
a.setOutputMarkupId(true);
showPhoto.setOutputMarkupPlaceholderTag(true);
I think you need : a.setOutputMarkupPlaceholderTag(true), not sure
what 'showPhoto' is.
Yes correct.
setOutputMarkupPlaceholderTag(true) calls setOutputMarkupId(true) for
you, so there is no need to call both of them.
Or could the AjaxRequestTarget be modified to do the
isVisibleInHierarchy()
before actually rendering the component?
This is possible but it will lead to more confusion. In this case your
component wont be modified at all and there wont be any indication. We
can add a WARN in the logs but my experience shows that not many
developers actually follow the logs.
Not sure what the issue would be with this. As the component isn't
visible
on the anyway.
Exactly! The component is invisible and your logic modifies something
in it and tries to repaint it. So it seems you actually want to make
it visible. But with your proposal to just ignore it if it is
invisible then this will be very confusing, IMO.
But basically your answer is: Yes when you add a component to the
AjaxRequestTarget that might not be visible, make sure that
setOutputMarkupPlaceholderTag(true) is always called on that
component?!
Right.
Thanks
On 6-9-2012 22:47, Thijs Vonk wrote:
OK thnx will give it a try
On 6/9/12 22:39, Igor Vaynberg wrote:
isVisibleInHierarchy() will make sure all parents are visible as
well
-igor
On Thu, Sep 6, 2012 at 1:27 PM, Thijs Vonk vonk.th...@gmail.com
wrote:
Hi,
We have partial page updates all over a page. So panels and
components
all
over the place that need Ajax updates.
We're using an Interface on those components and with an
IVisitor we
traverse the component tree and add every component to the
target that
has
this interface.
But during development we see that we get errors in the ajax
debug log
when
these components have an invisible state. These components
themselves
can
have this state but some of the times, the parent component is
invisible. In
these cases when such a hidden component is added to the
AjaxRequestTarget
we get an error in the ajax debug log.
Adding the isVisible check before adding the component to the
target
could
save us in some situations but not all (as it might get visible or
invisible) at a later state.
How can I prevent these components from being added to the
AjaxRequestTarget? Or from the error being thrown? I had hoped
that a
component being in an invisible state (somewhere in the tree)
wouldn't
get
rendered. It's not really a problem in a 'deployment'
situation, but
it's
not 'nice' either.
Thijs
-
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Problem with wicket-examples
Hi The wicket examples on the wicket.apache.org page keep going to some port. instead of staying on port 80. For example: Go to: http://www.wicket-library.com/wicket-examples/mappers and then try to do Source code, you'll be send to: http://www.wicket-library.com:10440/wicket-examples/mappers/wicket/bookmarkable/org.apache.wicket.examples.source.SourcesPage?SourcesPage_class=org.apache.wicket.examples.requestmapper.RequestMapperHomePage Kind regards, Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Add an invisible component to an AjaxRequestTarget target
Hi, We have partial page updates all over a page. So panels and components all over the place that need Ajax updates. We're using an Interface on those components and with an IVisitor we traverse the component tree and add every component to the target that has this interface. But during development we see that we get errors in the ajax debug log when these components have an invisible state. These components themselves can have this state but some of the times, the parent component is invisible. In these cases when such a hidden component is added to the AjaxRequestTarget we get an error in the ajax debug log. Adding the isVisible check before adding the component to the target could save us in some situations but not all (as it might get visible or invisible) at a later state. How can I prevent these components from being added to the AjaxRequestTarget? Or from the error being thrown? I had hoped that a component being in an invisible state (somewhere in the tree) wouldn't get rendered. It's not really a problem in a 'deployment' situation, but it's not 'nice' either. Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Add an invisible component to an AjaxRequestTarget target
OK thnx will give it a try On 6/9/12 22:39, Igor Vaynberg wrote: isVisibleInHierarchy() will make sure all parents are visible as well -igor On Thu, Sep 6, 2012 at 1:27 PM, Thijs Vonk vonk.th...@gmail.com wrote: Hi, We have partial page updates all over a page. So panels and components all over the place that need Ajax updates. We're using an Interface on those components and with an IVisitor we traverse the component tree and add every component to the target that has this interface. But during development we see that we get errors in the ajax debug log when these components have an invisible state. These components themselves can have this state but some of the times, the parent component is invisible. In these cases when such a hidden component is added to the AjaxRequestTarget we get an error in the ajax debug log. Adding the isVisible check before adding the component to the target could save us in some situations but not all (as it might get visible or invisible) at a later state. How can I prevent these components from being added to the AjaxRequestTarget? Or from the error being thrown? I had hoped that a component being in an invisible state (somewhere in the tree) wouldn't get rendered. It's not really a problem in a 'deployment' situation, but it's not 'nice' either. Thijs - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket portlet 1.5 and liferay 6.1
Hi Gabriel. Thanks for the heads up! At my work we're using portlets and are currently locked down at liferay 5.2 and wicket 1.4. But a migration to newer versions is on the Roadmap. So this is useful information. Thijs On 15-6-2012 0:09, Gabriel Landon wrote: For those who are having troubles making wicket-portlet works with liferay 6.1, here's the solution... I've many wicket 1.4 application that are just working fine in liferay 6.0. But when I put them in liferay 6.1, I get the following message : /20:49:12,379 ERROR [BasePortalLifecycle:45] java.lang.IllegalArgumentException: Error initializing WicketFilter - you have no filter-mapping element with a url-pattern that uses filter: TestApplication java.lang.IllegalArgumentException: Error initializing WicketFilter - you have no filter-mapping element with a url-pattern that uses filter: TestApplication / This is because liferay 6.1 remove the filter and filter-mapping from the web.xml. To prevent this behaviour, you have to add the following properties in your liferay-plugin-package.properties : *liferay-web-xml-enabled=false* By the way if you're using wicket 1.5, you will have the following error instead : /20:48:09,343 WARN [WebXmlFile:265] web.xml: No url-pattern found for 'filter' with name 'wicket.test' 20:48:09,343 INFO [WebXmlFile:113] web.xml: url mapping found for filter with name wicket.test: 20:48:09,343 WARN [WicketFilter:247] Unable to determine filter path from filter init-parm, web.xml, or servlet 3.0 annotations. Assuming user will set filter path manually by calling setFilterPath(String) / Good luck to all liferay users! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-portlet-1-5-and-liferay-6-1-tp4650001.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
problem using pre post ajax handlers
Hi, I have the following issue. I have a separate js that on window.onload calls: Wicket.Ajax.registerPreCallHandler(foo); Wicket.Ajax.registerPostCallHandler(bar); Wicket.Ajax.registerFailureHandler(bar); This works great however not on the first page load when there is no session yet. The session starts on the page visited so every resource gets ;sessionid=xyz appended http://localhost:8080/xyz/resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js;jsessionid=48703E4E37189E284112EA7A8CD6F8DB?w:lm=1299841674 Then on the first ajax-call it re-downloads all resources (including wicket-event.js and wicket-ajax.js) but this time without the ;sessionid appended. This seems to cause the registration of the pre and post handlers to be forgotten. And they are never called again. So I have 2 questions. 1. How can I prevent the resources from being downloaded twice (which would prevent the issue from happening in the first place). 2. If 1. can't be done. How can I re-register the pre and post handlers? So that subsequent ajax calls keep calling my Javascript in there pre and post calls? thanks Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: problem using pre post ajax handlers
I've been trying to create a quickstart displaying the problem all afternoon. But I can't seem to get it to generate resources links with ;sessionid's in them. While in my own application, when I do session.get().bind() on a stripped down page it does. So I'll be trying to get this to show up first... Thijs On 11-3-2011 12:33, Pedro Santos wrote: looks like a bug, open a ticket + quickstart please On Fri, Mar 11, 2011 at 8:08 AM, Thijsvonk.th...@gmail.com wrote: Hi, I have the following issue. I have a separate js that on window.onload calls: Wicket.Ajax.registerPreCallHandler(foo); Wicket.Ajax.registerPostCallHandler(bar); Wicket.Ajax.registerFailureHandler(bar); This works great however not on the first page load when there is no session yet. The session starts on the page visited so every resource gets ;sessionid=xyz appended http://localhost:8080/xyz/resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js;jsessionid=48703E4E37189E284112EA7A8CD6F8DB?w:lm=1299841674 Then on the first ajax-call it re-downloads all resources (including wicket-event.js and wicket-ajax.js) but this time without the ;sessionid appended. This seems to cause the registration of the pre and post handlers to be forgotten. And they are never called again. So I have 2 questions. 1. How can I prevent the resources from being downloaded twice (which would prevent the issue from happening in the first place). 2. If 1. can't be done. How can I re-register the pre and post handlers? So that subsequent ajax calls keep calling my Javascript in there pre and post calls? thanks Thijs - 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: problem using pre post ajax handlers
Looks like I found it. Turns out that somewhere between 1.4.10 and 1.4.16 something changed and jsessionid's get stripped from resources. I'll do some further testing but it seems to work ok now. Thanks Thijs On 11-3-2011 16:18, Pedro Santos wrote: you can disable the browser cookies, than the sessionid will show up On Fri, Mar 11, 2011 at 11:19 AM, Thijsvonk.th...@gmail.com wrote: I've been trying to create a quickstart displaying the problem all afternoon. But I can't seem to get it to generate resources links with ;sessionid's in them. While in my own application, when I do session.get().bind() on a stripped down page it does. So I'll be trying to get this to show up first... Thijs On 11-3-2011 12:33, Pedro Santos wrote: looks like a bug, open a ticket + quickstart please On Fri, Mar 11, 2011 at 8:08 AM, Thijsvonk.th...@gmail.com wrote: Hi, I have the following issue. I have a separate js that on window.onload calls: Wicket.Ajax.registerPreCallHandler(foo); Wicket.Ajax.registerPostCallHandler(bar); Wicket.Ajax.registerFailureHandler(bar); This works great however not on the first page load when there is no session yet. The session starts on the page visited so every resource gets ;sessionid=xyz appended http://localhost:8080/xyz/resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js;jsessionid=48703E4E37189E284112EA7A8CD6F8DB?w:lm=1299841674 Then on the first ajax-call it re-downloads all resources (including wicket-event.js and wicket-ajax.js) but this time without the ;sessionid appended. This seems to cause the registration of the pre and post handlers to be forgotten. And they are never called again. So I have 2 questions. 1. How can I prevent the resources from being downloaded twice (which would prevent the issue from happening in the first place). 2. If 1. can't be done. How can I re-register the pre and post handlers? So that subsequent ajax calls keep calling my Javascript in there pre and post calls? thanks Thijs - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Select All Non-Disabled Items in CheckBoxMultipleChoice
What Igor suggest is that you don't try to find the disabled checkboxes. You know up front by the logic you have implemented to decide that a checkbox is actually disabled. Use that same logic to update the model of all checkboxes that are not disabled. And have it update those modelsso that the checkboxes get the selected state. Thijs On 24-2-2011 16:21, eugenebalt wrote: When I try to call isDisabled() from another location, I get the error The method isDisabled(E,int,String) is not visible. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Different styles in different windows on same application
Hi. We have a use case where we have one Wicket application that has multiple styles (passed in through a page-parameter). These styles are put on the session and we have different css, html and properties based on those styles. This works as long as the user doesn't try to open 2 different styles in the same browser. Tab1 http://foo.bar/app/style/theme1 Tab2 http://foo.bar/app/style/theme1 As soon as you go back to tab1 and do something, the style changes. Is there a way to do this without putting the style on the session, but still be able to use the style and variation logic in Wicket? I was looking at setting something on a model that is passed around all to pages. But I can't figure out how to make this work with the resourceloading. Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket Portlets
For us this works in the Application class:
/**
* @see wicket.Application#getHomePage()
*/
public Class? extends Page getHomePage()
{
PortletRequestContext prc = (PortletRequestContext)
RequestContext.get();
if (PortletMode.EDIT.equals(prc.getPortletRequest().getPortletMode()))
{
return EditPage.class;
}
return HomePage.class;
}
On 19-7-2010 11:34, Gareth Western wrote:
Is anyone here using Wicket in a portal (i.e. for portlets)? I'm trying to
figure out how to switch pages when the user changes Portlet mode (e.g. VIEW
- EDIT).
Looking through the source, it looks like the responsible method
(WicketPortlet#getWicketConfigParameter(PortletRequest request, String
paramName, String defaultValue)) doesn't do anything except return the given
defaultValue, whereas I was expecting it to try and look up the page for the
given paramName...! :(
Has anyone got around this problem?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: SV: Wicket Portlets and Liferay
On 13-1-2010 14:20, Wilhelmsen Tor Iver wrote: We are running Wicket + Liferay (Webspace) in Glassfish 2, and experience no problems; IIRC Glassfish uses the same Catalina engine as Tomcat? For AJAX/resource requests, another supports element for mime-type text/xml is needed. This sounds like a Tomcat issue, our portlets use Ajax fine without such a mime-type setting. This is a Liferay issue, they don't support */* so when using ajax you need: supports mime-typetext/html/mime-type mime-typetext/xml/mime-type portlet-modeVIEW/portlet-mode /supports 2) Name congruence in deployment descriptors The name in the pattern under //filter-mapping/url-pattern in web.xml (e.g. /testPortlet/*) has to match with the value under //portlet/portlet-name in portlet.xml, otherwise the portlet will not be rendered, or you get StackOverflowExceptions in LR. Again, possibly a Tomcat issue, in Glassfish we use e.g. a name LocalMessagesPortlet with the filter-mapping /localmessages/* with no issues The requested resource (/hellowicket-portlet-1.0- SNAPSHOT/testPortlet/) is not available. instead of the actual portlet content. I would recommend using a more readable build/finalName pom.xml setting instead of the version-appended artifact name unless you want to deploy multiple versions. For the portlet naming check http://issues.liferay.com/browse/LPS-1911?focusedCommentId=52180#action_52180 and further the portet war should end with -portlet - Tor Iver - 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
ie6 HybridUrlCodingStrategy using ajax and an anchor results in a 404
I have the following setup: * Page mounted using a HybridUrlCodingStrategy * AjaxLink * And an anchor to jump to a certain section of page. When I jump to a section of the page using the anchor and then try to use the ajaxlink the page is not found. I've traced it down to IE6 appending the #anchor in the link. While other browsers don't So the requestUri in IE6 = /home.0%23anchor and in other browsers it is /home.0 Is this a known issue or should I open a JIRA issue? Thanks Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: ie6 HybridUrlCodingStrategy using ajax and an anchor results in a 404
He, I'm on your side. And I think the designer is even more. However the customer isn't :( They still have a 25 - 30% IE6 user base. And with the system we're building that is a LOT of money... If you don't want to fix it, where would I have look to fix it my self? In WicketFilter.getRelativePath()? Thijs On 30-6-2009 17:02, Igor Vaynberg wrote: do we still have to wreck our brains thinking about how to support a browser released in 2001? -igor On Tue, Jun 30, 2009 at 2:16 AM, Thijsvonk.th...@gmail.com wrote: I have the following setup: * Page mounted using a HybridUrlCodingStrategy * AjaxLink * And an anchor to jump to a certain section of page. When I jump to a section of the page using the anchor and then try to use the ajaxlink the page is not found. I've traced it down to IE6 appending the #anchor in the link. While other browsers don't So the requestUri in IE6 = /home.0%23anchor and in other browsers it is /home.0 Is this a known issue or should I open a JIRA issue? Thanks Thijs - 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 portlet into liferay
Take into account that you might be able to use the jquery that is already inside Liferay. So if you want to use jquery from wicketstuff you'll probably have to modify those components a bit. On 24-4-2009 18:45, Tonio Caputo wrote: Thanks Rob for taking care, I was just using the DatePicker that comes with wicket-extensions, I still need to get into wicket to see what to use and what not to, as I've told just my first steps guided by Wicket In Action. But it seems jquery and wicket is a very common couple I've seen looking at the e-mails, so probably begin looking how to integrate them. Thanks again tonio On Fri, Apr 24, 2009 at 2:07 AM, Rob Sonker...@tigrou.nl wrote: Hi, Nice to hear that everything seems to work now. About the datepicker, which one is that? Because I'm using one from the wicketstuff projects ( http://www.dynarch.com/static/jscalendar-1.0/index.html) and that one is working fine. But we're about to migrate to a jquery based one. Rob On 4/23/09 5:28 AM, Tonio Caputo wrote: Hi, After trying a lot I finally was able to show and work (more or less). A warning: Never call your appl/portlet-name with the same name as the url-mapping, if not it won't work that was the main problem. My new problem I'm using DatePicker from wicket-extensions/wicket-date in a form, the date picker is not working (I mean the button that shows the calendar and let you choose a date in a friendly way) Not found something useful in mailing-lists so I added supports mime-type: text/javascript and application/x-javascript to portlet.xml, but still not working. Any idea of what is happening, or a solution to this problem Thanks very much in advance tonio On Tue, Apr 21, 2009 at 5:33 PM, Rob Sonker...@tigrou.nl wrote: Hi, We're running wicket 1.4m2 on liferay 5.2.x and that's working fine. We only use the sun portlet container instead of the one from Liferay. Search the mailinglist and the liferay forum for the steps which you'll have to perform. Rob On 4/21/09 4:45 AM, Tonio Caputo wrote: Hi, I've tried with liferay 5.2.2 tomcat6/tomcat55/jetty6.1.14, and no success. In both tomcat, application is deployed, but when put into a page, the application is not shown. In jetty, the application doesn't get deployed. In all cases there is no log, or any message that let me know what is happening. Any help will be greatly welcome Wicket is really a nice framework (the nicer I've seen), and it would be wonderful if I can use it instead JSP framework provided by liferay. Thanks in advance tonio On Mon, Apr 20, 2009 at 12:21 PM, Tonio Caputoton...@exeo.com.ar wrote: Hi wicket users, I'm a newbie in wicket and portlets, I'm involved in trying to find a web framework to create portlets in a liferay portal, my duty is to try wicket and see if it works. Versions wicket 1-4-rc2 liferay 5.2 After reading Issue https://issues.apache.org/jira/browse/WICKET-1620 , it seems clear that this is possible. Reading wicket portlet examples, I realized there is a lot of stuff in WicketPortlet, that is a bit difficult to understand for a newbie for both things (wicket/portlet). I'll just like to know, if this is the correct example after WICKET-1620, or perhaps there is a simpler one. Thanks in advance tonio
Re: [poll] Interest in regular Deventer Wicket meetup?
I'd love to attend. so +1 However Amsterdam already being a problem (yes, zeeland is the other end of the world, esp. for the NS). Deventer is just a bit to far for an afternoon/evening. ( 3 - 3,5h travel one way). So I'd like to attend and probably would once in a while. It will certainly not be on a regular basis. Thijs On 17-4-2009 15:30, Martijn Dashorst wrote: I want to poll if there is an interest in a regular Wicket meetup in Deventer, the Netherlands. We can only host at most ~20 people, so I expect this to be much lower key than the Amsterdam meetups. If there is an interest, I'll prod my employer to see if they are willing to help with space, beamer and possibly pizza. The venue would be one of the Topicus buildings, which are conveniently located in the historical center of Deventer, very close to the train station. The types of presentations/discussions/etc. I'm looking for are rather simple: - show us your product and discuss where/how/why you used and extended wicket - show us how you integrated with hibernate/db4o/ibatis/cayenne/rome/spring/guice/jquery/gmap/opensocial/... - ask us a question for a problem (with code... ;-) - ... These events would start at ~18:30 with pizza, doors open at 18:00 and presentations starting at 19:00. I'd also like to keep the meetups short, about 90 minutes, or maybe 2 hours (max). This will give people the opportunity to return to home at an appropriate time. Afterwards we could visit one of the bars that serve Topicus Gifkikker. Is this an event you would like to visit? Martijn - 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: Should a form submit when sub-form has error's?
Created https://issues.apache.org/jira/browse/WICKET-2202 with a patch containing testcases to display the error. No fix as of yet. On 1-4-2009 14:42, Thijs wrote: If you are referring to org.apache.wicket.markup.html.form.validation.TestHomePage Those never run at least not when I call mvn clean package I had to change it to org.apache.wicket.markup.html.form.validation.HomePageTest to get it to work. (Which in my view could indicate that there are more tests not running) still checking the actual problem. Thijs On 31-3-2009 19:51, Igor Vaynberg wrote: not it shouldnt. there should already be unit tests that check for this, can you please check those and provide a patch if possible. -igor On Tue, Mar 31, 2009 at 4:34 AM, Thijsvonk.th...@gmail.com wrote: Hi, Should a Form submit when a subform has error's? I have a main-form where I add a panel that contains another form. This sub-form contains a formvalidator that gives the error. However the main-form is submitted, but the feedbackpanel does show the error message set in the sub-form's validator. Is this expected behavior using 1.4-snapshot? Because in wicket 1.3.x this does work and the mainform is not submitted. (I can provide a testcase if needed) Thijs - 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: Should a form submit when sub-form has error's?
If you are referring to org.apache.wicket.markup.html.form.validation.TestHomePage Those never run at least not when I call mvn clean package I had to change it to org.apache.wicket.markup.html.form.validation.HomePageTest to get it to work. (Which in my view could indicate that there are more tests not running) still checking the actual problem. Thijs On 31-3-2009 19:51, Igor Vaynberg wrote: not it shouldnt. there should already be unit tests that check for this, can you please check those and provide a patch if possible. -igor On Tue, Mar 31, 2009 at 4:34 AM, Thijsvonk.th...@gmail.com wrote: Hi, Should a Form submit when a subform has error's? I have a main-form where I add a panel that contains another form. This sub-form contains a formvalidator that gives the error. However the main-form is submitted, but the feedbackpanel does show the error message set in the sub-form's validator. Is this expected behavior using 1.4-snapshot? Because in wicket 1.3.x this does work and the mainform is not submitted. (I can provide a testcase if needed) Thijs - 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
Should a form submit when sub-form has error's?
Hi, Should a Form submit when a subform has error's? I have a main-form where I add a panel that contains another form. This sub-form contains a formvalidator that gives the error. However the main-form is submitted, but the feedbackpanel does show the error message set in the sub-form's validator. Is this expected behavior using 1.4-snapshot? Because in wicket 1.3.x this does work and the mainform is not submitted. (I can provide a testcase if needed) Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket Portlets in WebLogic Portal?
What version of liferay are you using? Wicket 1.3.x needs the portlet bridge implementation. (to cater for portlet1.0 spec). And for weblogic I think you'r on your own. This bridge implementation is portlet container specific. Wicket 1.4 you shouldn't need the portlet bridges any more but then Weblogic will need to fully support portlet 2.0 spec. I have no idea if they do. Thijs On 23-3-2009 16:00, jakewicket wrote: Just FYI, I was able to get a Wicket portlet to render initially in WebLogic Portal using Java portlets (the Pageables example from the Wicket Examples page - http://www.wicket-library.com/wicket-examples/ajax/pageables.1), but none of the links to page through the results work with no errors. I think that this may be related to the implementation of those two Apache Portals Bridges interfaces mentioned earlier. If anyone has tried this before please let me know. Thanks! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket Portlets in WebLogic Portal?
duh.. :-) I was just discussing a Liferay issue with a colleague and by mistake typed that instead of Wicket :-) Thijs On 23-3-2009 16:09, jakewicket wrote: Thanks for the quick reply. I'm using WebLogic Portal, not Liferay. I'll have to see if WebLogic Portal fully supports the portlet 2.0 spec, and try upgrading to Wicket 1.4 (I was trying this with Wicket 1.3.5). - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket-1.4-rc2 / Liferay 5.2.1 / Ajax: PortletServletRequestWrapper: java.lang.StringIndexOutOfBoundsException
This is probably an error in Liferays PortletRequestDispatcher. Use Liferay 5.2.x (head of liferay branch 5.2.x) and use the sun portlet container (put portlet.container.impl=sun in portlal-ext.properties) (See http://issues.liferay.com/browse/LPS-1911) and then apply the patches in these two lps's to fix some issues with the sun container http://issues.liferay.com/browse/LPS-2131 http://issues.liferay.com/browse/LPS-1909 Thijs On 20-2-2009 10:36, sauli_k wrote: Hi, I was using the AjaxLink in a portlet and I noticed that in case the portal url is shorter than the wicket filter path I get this error: 2009-02-20 11:07:40,765 ERROR [[MonitoringPortlet].invoke()] - Servlet.service() for servlet MonitoringPortlet threw exception java.lang.StringIndexOutOfBoundsException: String index out of range: -3 at java.lang.String.substring(String.java:1938) at java.lang.String.substring(String.java:1905) at org.apache.wicket.protocol.http.portlet.PortletServletRequestWrapper.init(PortletServletRequestWrapper.java:144) at org.apache.wicket.protocol.http.portlet.WicketFilterPortletContext.setupFilter(WicketFilterPortletContext.java:120) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:229) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:679) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:461) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:399) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:613) at com.liferay.portlet.InvokerPortletImpl.invokeResource(InvokerPortletImpl.java:722) at com.liferay.portlet.InvokerPortletImpl.serveResource(InvokerPortletImpl.java:496) at com.liferay.portal.action.LayoutAction.processPortletRequest(LayoutAction.java:663) at com.liferay.portal.action.LayoutAction.processLayout(LayoutAction.java:454) at com.liferay.portal.action.LayoutAction.execute(LayoutAction.java:195) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:159) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:505) at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:732) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:679) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:461) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:399) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.liferay.portal.servlet.FriendlyURLServlet.service(FriendlyURLServlet.java:143) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154) at com.liferay.portal.servlet.filters.strip.StripFilter.processFilter(StripFilter.java:178) at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154) at com.liferay.portal.servlet.filters.gzip.GZipFilter.processFilter(GZipFilter.java:149) at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91
Re: Portlet 2.0 and Events
They are based on wicket truck *before* WICKET-2058 was committed. Nobody has updated the patches since then. Thijs On 10-2-2009 10:25, Benjamin Ernst wrote: Hi, I am trying to get the Event-Support for Portlets working with the Patches I found in https://issues.apache.org/jira/browse/WICKET-1620;. But I am not able to apply any of the patches properly. Can anyone tell me on which revision of the trunk they base, or in which order I have to apply them? Thanks for any help! -- Benjamin - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Portlet 2.0 and Events
That last one contains all the functionality, but a large part of the 2.0 spec that was also added in this patch does not match the one that went into trunk via WICKET-2058. That has been altered rather drastically so you'll have to do some major re-factoring to get everything back in. On 10-2-2009 12:07, Benjamin Ernst wrote: Hi Thijs, do I have to apply all Patches, or is the WICKET-1620-portlet2.0-tight.patchhttps://issues.apache.org/jira/secure/attachment/12396786/WICKET-1620-portlet2.0-tight.patch enough? Thanks, -- Benjamin On Tue, Feb 10, 2009 at 11:07 AM, Thijsvonk.th...@gmail.com wrote: They are based on wicket truck *before* WICKET-2058 was committed. Nobody has updated the patches since then. Thijs On 10-2-2009 10:25, Benjamin Ernst wrote: Hi, I am trying to get the Event-Support for Portlets working with the Patches I found in https://issues.apache.org/jira/browse/WICKET-1620;. But I am not able to apply any of the patches properly. Can anyone tell me on which revision of the trunk they base, or in which order I have to apply them? Thanks for any help! -- Benjamin - 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: Using Eclipse Wicket for Modular Webapps
Looks really interresting, I've read the pdf. but it seems that there is a part missing at the end... On 2/6/09 6:02 PM, Thomas Mäder wrote: Hi Folks, I've been experimenting with getting the Eclipse plugin engine up inside a wicket application. The idea is to build Wicket applications out of plugins. You can find an article about my experiences (+sample code) here: http://devotek-it.ch/stuff.html I'm grateful for any feedback, both concerning the Eclipse/OSGI and the Wicket part. enjoy the weekend Thomas - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems Ajax with Portlet 2.0 in Liferay 5.2.1
This is an issue with Liferay (see
http://issues.liferay.com/browse/LPS-1911)
You can probably fix it by making sure that portlet-name (in
portlet.xml) and the wicketfilter mapping url-pattern are identical
(portlet.xml web.xml)
On 2/5/09 4:30 PM, Benjamin Ernst wrote:
Hi,
I am Testing the new Portlet 2.0 with Liferay and have some problems with
Ajax-calls.
I am using wicket 1.4-SNAPSHOT(Revision 741130) and Liferay Portal Standard
Edition 5.2.1 (Augustine / Build 5201 / February 3, 2009).
I have a simple page with one label and one Ajaxlink:
public HomePage(final PageParameters parameters) {
final Label label = new Label(label, new
PropertyModelInteger(this, value));
label.setOutputMarkupId(true);
add(label);
AjaxLink link = new AjaxLink(link)
{
@Override
public void onClick(AjaxRequestTarget target) {
value = value + 1;
target.addComponent(label);
}
};
add(link);
}
The portlet is shown correctly but when I click the Ajaxlink nothing
happens. In the Ajax-Debug-Log appears the following text:
INFO:
INFO: Initiating Ajax POST request on
http://localhost:8080/web/guest/home?random=0.9410006487742066
INFO: Invoking pre-call handler(s)...
INFO: Received ajax response (84 characters)
INFO:
The requested resource (/ACE_PortletTest-1.0-SNAPSHOT/portlettest/) is not
available
ERROR: Error while parsing response: Could not find rootajax-response
element
INFO: Invoking post-call handler(s)...
INFO: Invoking failure handler(s)...
This is the log form Java when the Ajax-Link is clicked:
DEBUG - 0-SNAPSHOT]- servletPath=/ACETEST, pathInfo=/invoke,
queryString=null, name=null
DEBUG - 0-SNAPSHOT]- Path Based Forward
DEBUG - WicketPortlet - Portlet RESOURCE_PHASE for wicket
url:/portlettest/?wicket:interface=:0:link::IBehaviorListener:0:
DEBUG - 0-SNAPSHOT]- servletPath=/portlettest/,
pathInfo=null, queryString=wicket:interface=:0:link::IBehaviorListener:0:,
name=null
DEBUG - 0-SNAPSHOT]- Path Based Include
DEBUG - WicketPortlet - redirect url after inclusion:null
DEBUG - WicketPortlet - end of request, wicket
url:/portlettest/?wicket:interface=:0:link::IBehaviorListener:0:
DEBUG - 0-SNAPSHOT]- Disabling the response for futher
output
DEBUG - 0-SNAPSHOT]- The Response is vehiculed using a
wrapper: com.liferay.portal.servlet.AbsoluteRedirectsResponse
Here is my web.xml and my portlet.xml:
?xml version=1.0 encoding=ISO-8859-1?
web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
version=2.4
display-nameACE_PortletTest/display-name
context-param
param-nameorg.apache.wicket.detectPortletContext/param-name
param-valuetrue/param-value
/context-param
context-param
param-nameconfiguration/param-name
param-valuedevelopment/param-value
!-- param-valuedeployment/param-value --
/context-param
filter
filter-namewicket.ACE_PortletTest/filter-name
filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class
init-param
param-nameapplicationClassName/param-name
param-valuede.acando.ace.WicketApplication/param-value
/init-param
/filter
filter-mapping
filter-namewicket.ACE_PortletTest/filter-name
url-pattern/portlettest/*/url-pattern
dispatcherREQUEST/dispatcher
dispatcherFORWARD/dispatcher
dispatcherINCLUDE/dispatcher
/filter-mapping
/web-app
?xml version=1.0 encoding=UTF-8?
portlet-app xmlns=http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; version=1.0
xsi:schemaLocation=http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd;
portlet
descriptionACE Test/description
portlet-nameACETEST/portlet-name
display-nameACETEST/display-name
portlet-classorg.apache.wicket.protocol.http.portlet.WicketPortlet/portlet-class
init-param
namewicketFilterPath/name
value/portlettest/value
/init-param
supports
mime-typetext/html/mime-type
portlet-modeVIEW/portlet-mode
portlet-modeEDIT/portlet-mode
/supports
supports
mime-typetext/xml/mime-type
portlet-modeVIEW/portlet-mode
portlet-modeEDIT/portlet-mode
/supports
portlet-info
titleACE Portlet Test/title
keywordsACE Portlet Test/keywords
/portlet-info
/portlet
container-runtime-option
namejavax.portlet.escapeXml/name
valuefalse/value
/container-runtime-option
/portlet-app
I have no idea whats
Re: Portlets (JSR-168) and Ajax
I have no experience with WSRP, but I do know that the portal should support a bit more then just jsr-168. See http://cwiki.apache.org/WICKET/portal-howto.html also the way DWR does it is different then the way wicket works. If I remember correctly DWR functions as a separate servlet next to te portal that catches the ajax requests. With wicket the portlet itself handles the ajax request and response, which officially isn't supported by jsr-168. Thijs On 11/22/08 5:42 PM, Adriano dos Santos Fernandes wrote: Hi! I'm trying to create portlets with Wicket, to use in Oracle Portal. Portlets on it is with JSR-168 via WSRP. And I'm having trouble... But before go further, I want to know, with JSR-168 can I use Ajax? On my environment, Oracle Portal and the portlets application runs in different servers, but on the Portal server there is a URL redirection to the application server. I have portlets using AJAX with DWR working there... Adriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Invalid URLPatternSpec for Ajax Calls in Wicket Portlet
https://issues.apache.org/jira/browse/WICKET-1620 (Though it's still a work in process) and not yet supported by the wicket core committers On 11/20/08 9:17 PM, krisNog wrote: which portlet 2 patch are you referring to? Where is it available? Thanks Thijs wrote: But does it also have a problem if it's running a standalone wicket application? Btw I've run wicket portlets (with the portlet 2 patch) in Glassfish open portal portlet container(v. rc2 then) and that worked just fine... So I don't know what the problem could be... Thijs On 11/19/08 8:44 PM, krisNog wrote: The difference appears to be : vs %3A (the URL encoded : ) in urls. For example wicket seems to be creating test:test2 in Firefox and test%3Atest2 in IE. Glassfish doesn't like the : Thijs wrote: Do you know what is send differently to the server in FF2 vs IE (WireShark?) And where the error is thrown, why it says that the URLPatternSpec is invalid... Thijs On 18-11-2008 22:57, prasana wrote: Hi all, We are running Wicket Portlet in Jetspeed Portal deployed in Glassfish. But whenever we make a Ajax calls, it results in There are some problems in the request: invalid URLPatternSpec|# in the server log file and Ajax Debug windows shows ERROR: Received Ajax response with code: 400 The above error happens only in Firefox 2 and not in IE 6/7 I greatly appreciate any help regarding on what I need to do to see the workflow actions for assets. Thanks Prasanna - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Invalid URLPatternSpec for Ajax Calls in Wicket Portlet
Do you know what is send differently to the server in FF2 vs IE (WireShark?) And where the error is thrown, why it says that the URLPatternSpec is invalid... Thijs On 18-11-2008 22:57, prasana wrote: Hi all, We are running Wicket Portlet in Jetspeed Portal deployed in Glassfish. But whenever we make a Ajax calls, it results in There are some problems in the request: invalid URLPatternSpec|# in the server log file and Ajax Debug windows shows ERROR: Received Ajax response with code: 400 The above error happens only in Firefox 2 and not in IE 6/7 I greatly appreciate any help regarding on what I need to do to see the workflow actions for assets. Thanks Prasanna - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to navigate from edit mode to view mode
You'll have to be more specific. What kind of problems. What works, what doesn't etc. Singh Mukesh wrote: Hi I have created a bookmark portlet using wicket. And the bookmark portlet includes two portlet- mode i.e. view and edit. I have deployed the basic portlet on sun portal. I have a problem with the navigation form edit mode to view mode. Do you have any good suggestion how to solve this problem? Thanks in advance Thanks and Regards, MUKESH SINGH CAPGEMINI Consultant Arrive AS T (+47) 46 47 90 16 E-post: [EMAIL PROTECTED] http://servicedesk.arrive.no - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Anybody tried Wicket with WebSphere portal?
Thats not completely correct. The current Wicket implementation depends on the PortletBridge implementation and is not 286 ready. Athough it has some 286 features like the resourceUrl, that part of the implementation depends on the PortletBridge implementation. Work is in progress to make Wicket more jsr-286 compliant, but at this point there is not a final solution or a timeframe for a final solution. Peter Eriksson wrote: Hello everybody, In my day job I use WebSphere Portal, working as a consultant, and I have been using JSF in portlet development and really found it quite painful. The version of WebSphere Portal is 6.0 and that uses JSF 1.1 and I know things have improved somewhat in more recent versions of JSF, but that is not really helping much. Now to my question, I have been trying out Wicket and I find it very nice to work with compared to JSF and I really would like to use it in WebSphere Portal, so is anybody out there using it with WebSphere Portal 6? I have read a few postings regarding portal support and understood that it depends on how and if the PortletBridge is implemented in the Portlet container of the vendor in question. WebSphere Portal 6.0 is JSR168 compliant and I know that the upcoming release WebSphere Portal 6.1 is going to be JSR286 compliant and that Wicket support should be working in a JSR286 environment without problem, or have I misunderstood something? Best Regards, /Peter Eriksson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket portles in Sun Portal
Ate Douma wrote: Wilhelmsen Tor Iver wrote: To dig up this old thread: I now use Ate Douma's patch for JSR-286 support from https://issues.apache.org/jira/browse/WICKET-1620 which has removed the need for the portal to implement the Apache portlet bridge's two interfaces. A small step for man etc. :) Well, credits for those patches go to Thijs Vonk, I'm just the assignee of that issue :) Note though: those patches *as such* still need quite some refactoring (as already discussed on this list before) and the final JSR-286 support very likely will turn out a little bit different... For those who haven't discovered this yet, I might have a nice news update: JSR-286 has finally landed! See: http://jcp.org/aboutJava/communityprocess/final/jsr286/index.html Finally :) There now is an issue - the same I had in JBoss - that it seems the bridge has a bug where the WicketFilterPortletContext call to ServletPortletSessionProxy.createProxy(filterRequestContext.getRequest() ) places a Double into the window-id propery that later will be cast to String... No. This is *not* a bug in the bridge, but one in their portlet container implementation. The method concerning this issue is o.a.p.bridges.util.PortletWindowUtils.getPortletWindowId(PortletSession) That method (which I wrote) is 100% following the JSR-168 specification, its just too bad JBoss Portal (and now it seems also Sun Portal) fail to follow those rules concerning this functionality. ... makes me wonder if they (now) share some common codebase ? ... Anyway, I know this is annoying and I could maybe fix this through a workaround (not sure yet though: this exception might indicate something more/worse is wrong, but I haven't debugged *their* engines yet). But... such a fix or workaround will take some time to formally land in a new release of bridges anyway, and maybe by that time this is moot if we have (basic) JSR-286 support in place for Wicket by then ... I tested on Sun Portlet container and ran into this problem as well. The 'QuickFix' I used was to alter the Bridges code and check if it was a String or not and depending I cast to String or to Double and then to String. I know it's dirty (as I didn't check if it actually is a worse problem as Ate indicated), but after I fixed that I haven't run into any other problems with it yet. Note though that you have to build a svn copy of the portlet-container. RC2 contains a bug I found which prevents Ajax to work correctly. Are there plans to completely disconnect the Wicket portlet impl. from the bridge (i.e. including this dependency to ServletPortletSessionProxy)? Yes/no. JSR-286 support will no longer need/depend on the two ServletContextProvider and PortletResourceURLFactory implementations. Additionally, the ServletPortletSessionProxy functionality *might* be replaced by a native JSR-286 feature but... that is an optional feature of the spec, so it depends if the underlying portlet container does support it or not. If not, the ServletPortletSessionProxy (which provides exactly the same functionality as this optional feature... wonder how come?) will still be needed. But in that case, the part you encountered the exception in comes from determining the Portlet WindowId, and *that* is now also formally provided by JSR-286 and thus can be resolved in a JSR-286 native way too. HTH, Ate - Tor Iver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Anchors in Wicket?
The component is any wicket component in the same page or next page if you know that component. What you are doing, an anchor in a different page, I've solved by writing my own subclass of link where I append the '#rsvp' myself. Michael Mehrle schreef: I don't get it - what is the 'component' in the setAnchor() method? If I set an anchor in a completely different page like this: a href=#rsvp / What do I set as the 'component' in the link's setAnchor? Thanks, Michael -Original Message- From: Thijs Vonk [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 12:39 PM To: users@wicket.apache.org Subject: Re: Anchors in Wicket? Michael Mehrle wrote: How do create a link that jumps to some anchor in a page? Is there a way to define this in Wicket or do I have to do this manually somehow? Michael yes. use link.setAnchor(Component) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Anchors in Wicket?
This is a bookmarkable link (the only place I use it with) but you get
the idea :)
import org.apache.wicket.PageParameters;
import org.apache.wicket.markup.ComponentTag;
import org.apache.wicket.markup.html.link.BookmarkablePageLink;
import org.apache.wicket.model.IModel;
public class AnchoredBookmarkablePageLink extends BookmarkablePageLink {
private static final long serialVersionUID = 1L;
private IModel stringAnchor;
public AnchoredBookmarkablePageLink(String id, Class pageClass, IModel
anchor) {
super(id, pageClass);
this.stringAnchor = anchor;
}
public AnchoredBookmarkablePageLink(String id, Class pageClass,
PageParameters params, IModel anchor) {
super(id, pageClass, params);
this.stringAnchor = anchor;
}
@Override
protected CharSequence appendAnchor(ComponentTag tag, CharSequence url) {
url = url + # + stringAnchor.getObject().toString();
return url;
}
}
Thijs
Michael Mehrle wrote:
Mind sharing that? ;-)
-Original Message-
From: Thijs [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 11:23 PM
To: users@wicket.apache.org
Subject: Re: Anchors in Wicket?
The component is any wicket component in the same page or next page if
you know that component.
What you are doing, an anchor in a different page, I've solved by
writing my own subclass of link where I append the '#rsvp' myself.
Michael Mehrle schreef:
I don't get it - what is the 'component' in the setAnchor() method? If
I
set an anchor in a completely different page like this:
a href=#rsvp /
What do I set as the 'component' in the link's setAnchor?
Thanks,
Michael
-Original Message-
From: Thijs Vonk [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 12:39 PM
To: users@wicket.apache.org
Subject: Re: Anchors in Wicket?
Michael Mehrle wrote:
How do create a link that jumps to some anchor in a page? Is there a
way
to define this in Wicket or do I have to do this manually somehow?
Michael
yes. use link.setAnchor(Component)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Anchors in Wicket?
Michael Mehrle wrote: How do create a link that jumps to some anchor in a page? Is there a way to define this in Wicket or do I have to do this manually somehow? Michael yes. use link.setAnchor(Component) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: users, please give us your opinion: what is your take on generics with Wicket
1) Generifying* Wicket [ X ] Can best be done in a limited fashion, where we only generify IModel but not components. I care more about what generifying can do for API clarity (declaring a component to only accept certain models for instance) than static type checking. 2) How strongly do you feel about your choice above? [ X ] Whatever choice ultimately made, I'll happily convert/ start Thijs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with Stress
Label label; add(label = new Label (name,Geacute;neacute;rer Document)); label.setEscapeModelStrings(false); Thijs Fabien D. schreef: Hi everybody, I'm french and unfortunately in french we have stresses! My server tomcat is using UTF-8, and all my files are encoding in UTF-8, and I want to use this standard. When I want to display a label : like this add(new Label (name,Générer Document)); It displays : Générer Document I try to use file.propertie and getString(), it is the same issue, I try to replace é by html caracter eacute; but it displays eacute; So I don't know where it is the problem with UTF-8 because if my file is encoding in ISO-8859-1 it woks well. If you have suggestion, thank you in advance. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: missing something: getting AjaxCheckBox to recheck value from model as its redrawn?
I'm not sure what you are saying here. But if it is what I'm thinking then you have misunderstood the meaning of .setDefaultFormProcessing. If your component is in a form, the 'defaultFormProcessing' will try to write any changes in the form to the model, and then call the onSubmit of the form, and finally the onSubmit of the button. If set to false it will skip all the form handling and call the onSubmit of the button directly. http://wicket.apache.org/docs/wicket-1.3.2/wicket/apidocs/org/apache/wicket/markup/html/form/Button.html#setDefaultFormProcessing(boolean) So if you are doing anything in the buttons 'onSubmit' that you don't want in certain cases, then calling setDefaultFormProcessing(false) won't have any affect. Thijs Kirk Israel wrote: the left/right moves ARE being done in the buttons onSubmit, I was hoping calling .setDefaultFormProcessing(false); when adding the button to the page would have prevented that? On Fri, May 23, 2008 at 4:50 AM, Thomas Mäder [EMAIL PROTECTED] wrote: Do the move left/move right controls do a submit? If so you might also be resubmitting the (old) check box value. Thomas We have a list view that iterates over manufacturers, and each manufacturer has a pallet control of devices (two list boxes w/ move selection to right list, move selection to left list buttons between) along with a all for manufacturer checkbox - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Portlets in Liferay 5
Hi Benjamin I'll see if I have some time left tomorrow, otherwise hopefully before next tuesday. Thijs Benjamin Ernst wrote: Hi Thijs, We are currently trying to integrate Liferay 5 with wicket 1.3. Can you give us the advise you offered? That would be very nice. Thank you in advance, Benjamin On Mon, May 5, 2008 at 11:33 PM, Thijs Vonk [EMAIL PROTECTED] wrote: Hi, Currently without building wicket against Liferay (using com.liferay.portlet.renderresponseimpl, instead of javax.portlet.renderresponse) it is not possible to run wicket without losing most of wickets functionality. I can, if you want, give you a patch and some instructions to get wicket working on liferay 5, but we are still modifying wicket and Liferay code to get things working as we want it. So I can't guaranty anything. Thijs Bobby Quninne wrote: Hi there, I am currently considering using wicket 1.3.3(and newer) with liferay 5. The site is going to be used for backend administration, standard CRUD stuff. How big a risk is it, using wicket portal and liferay? Thanks Thijs wrote: Hi, I'm working on getting wicket compatible with jsr-286 now. However while doing this I've noticed that Liferay has still some major issues regarding jsr-286. Especially regarding setting properties on the response (essentially setting response headers, cookies, etc) there is still some work to be done. They also don't support the MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice addition because of the CSS and JS files wicket adds to it's pages. Comment and vote on http://support.liferay.com/browse/LEP-5828. and track it to follow the property changes I'm also planning on opening a Wicket-jira issue so that you can track the progress of the wicket implementation. But we will have to wait at least until the portlet 2.0 specifications get official and added to a maven repository before we can add anything to the wicket code base. Besides that it's a lot of work and I'm doing this in my free hours so don't get over excited just jet :). I'll post a message on the list when I open the jira issue, and I'll attach patches to that issue as soon as I feel confident about the work I've been doing. I hope that answers your questions a bit. Thijs gaugat wrote: I've read in the forums, that it is better to wait for Liferay 5 (JSR 286) to develop portlets in Apache Wicket. So has anyone developed portlets using Wicket and deployed them in Liferay 5?. If you have, is there a sample wicket portlet posted somewhere that I could look at? Are there still issues with Wicket and Liferay? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: portlet examples?
What specifically are you looking for? I could send you a small portlet, that I use for testing if features like ajax/dynamic images/etc work on the portal we are using. What portal are you using? Because the portlet itself (aside from the web.xml/portlet.xml) is no different then any other wicket application. The fun part is in the implementation of the apache portal bridges ResourceUrlFactory and ServletContextProvider. (And in the case of Liferay also other parts of Wicket) Thijs Jonathan Locke schreef: does anyone out there have any wicket portlet examples i can look at? thanks, jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: portlet examples?
You can in that case also look in the wicket-examples (as there is a portlet-configuration in there). And then from the jetspeed svn check out /trunk/jetspeed-commons/src/main/java/org/apache/wicket/* /trunk/jetspeed-commons/src/main/java/org/apache/jetspeed/portlet/* Those should contain the relevent bits... And you can check the http://cwiki.apache.org/WICKET/portal-howto.html on the wiki :) I'll clean up the mess in my portlet and send you a war-file with sources, some time today/ this evening Thijs Jonathan Locke schreef: that would be great. i ran jetspeed once ;-) but i'm more interested in looking at the code (especially any portlet-specific stuff even if it's just configuration). i'll take your word for it that it works. Thijs wrote: What specifically are you looking for? I could send you a small portlet, that I use for testing if features like ajax/dynamic images/etc work on the portal we are using. What portal are you using? Because the portlet itself (aside from the web.xml/portlet.xml) is no different then any other wicket application. The fun part is in the implementation of the apache portal bridges ResourceUrlFactory and ServletContextProvider. (And in the case of Liferay also other parts of Wicket) Thijs Jonathan Locke schreef: does anyone out there have any wicket portlet examples i can look at? thanks, jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Portlets in Liferay 5
No, as described it depends on several factors 1. my/other people's time to commit to this 2. official release of the portlet 2 specifications Thijs Bobby Quninne schreef: You have a rough guess estimate as to a wicket release that will address JSR-268 compliance? Many thanks Thijs wrote: Hi, Currently without building wicket against Liferay (using com.liferay.portlet.renderresponseimpl, instead of javax.portlet.renderresponse) it is not possible to run wicket without losing most of wickets functionality. I can, if you want, give you a patch and some instructions to get wicket working on liferay 5, but we are still modifying wicket and Liferay code to get things working as we want it. So I can't guaranty anything. Thijs Bobby Quninne wrote: Hi there, I am currently considering using wicket 1.3.3(and newer) with liferay 5. The site is going to be used for backend administration, standard CRUD stuff. How big a risk is it, using wicket portal and liferay? Thanks Thijs wrote: Hi, I'm working on getting wicket compatible with jsr-286 now. However while doing this I've noticed that Liferay has still some major issues regarding jsr-286. Especially regarding setting properties on the response (essentially setting response headers, cookies, etc) there is still some work to be done. They also don't support the MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice addition because of the CSS and JS files wicket adds to it's pages. Comment and vote on http://support.liferay.com/browse/LEP-5828. and track it to follow the property changes I'm also planning on opening a Wicket-jira issue so that you can track the progress of the wicket implementation. But we will have to wait at least until the portlet 2.0 specifications get official and added to a maven repository before we can add anything to the wicket code base. Besides that it's a lot of work and I'm doing this in my free hours so don't get over excited just jet :). I'll post a message on the list when I open the jira issue, and I'll attach patches to that issue as soon as I feel confident about the work I've been doing. I hope that answers your questions a bit. Thijs gaugat wrote: I've read in the forums, that it is better to wait for Liferay 5 (JSR 286) to develop portlets in Apache Wicket. So has anyone developed portlets using Wicket and deployed them in Liferay 5?. If you have, is there a sample wicket portlet posted somewhere that I could look at? Are there still issues with Wicket and Liferay? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Portlets in Liferay 5
Bobby Quninne schreef: Are JSR-168 portlets also affected by this? Not sure what you are asking. The current JSR-168 implementation in wicket is pretty much final, and for wicket 1.3.x will probably not change. However newer versions of wicket probably will not be backwards compatible, with JSR 168, but I don't know for sure... If so, is there a version of wicket and liferay that are compatible? As described below. An out of the box wicket version will NOT work on any version of Liferay. So there is no Wicket version that is compatible. If you are willing to work with a patched version of wicket, then you can work with wicket 1.3.3 and LF5(as we are) Thijs Many thanks Thijs :-) Thijs wrote: No, as described it depends on several factors 1. my/other people's time to commit to this 2. official release of the portlet 2 specifications Thijs Bobby Quninne schreef: You have a rough guess estimate as to a wicket release that will address JSR-268 compliance? Many thanks Thijs wrote: Hi, Currently without building wicket against Liferay (using com.liferay.portlet.renderresponseimpl, instead of javax.portlet.renderresponse) it is not possible to run wicket without losing most of wickets functionality. I can, if you want, give you a patch and some instructions to get wicket working on liferay 5, but we are still modifying wicket and Liferay code to get things working as we want it. So I can't guaranty anything. Thijs Bobby Quninne wrote: Hi there, I am currently considering using wicket 1.3.3(and newer) with liferay 5. The site is going to be used for backend administration, standard CRUD stuff. How big a risk is it, using wicket portal and liferay? Thanks Thijs wrote: Hi, I'm working on getting wicket compatible with jsr-286 now. However while doing this I've noticed that Liferay has still some major issues regarding jsr-286. Especially regarding setting properties on the response (essentially setting response headers, cookies, etc) there is still some work to be done. They also don't support the MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice addition because of the CSS and JS files wicket adds to it's pages. Comment and vote on http://support.liferay.com/browse/LEP-5828. and track it to follow the property changes I'm also planning on opening a Wicket-jira issue so that you can track the progress of the wicket implementation. But we will have to wait at least until the portlet 2.0 specifications get official and added to a maven repository before we can add anything to the wicket code base. Besides that it's a lot of work and I'm doing this in my free hours so don't get over excited just jet :). I'll post a message on the list when I open the jira issue, and I'll attach patches to that issue as soon as I feel confident about the work I've been doing. I hope that answers your questions a bit. Thijs gaugat wrote: I've read in the forums, that it is better to wait for Liferay 5 (JSR 286) to develop portlets in Apache Wicket. So has anyone developed portlets using Wicket and deployed them in Liferay 5?. If you have, is there a sample wicket portlet posted somewhere that I could look at? Are there still issues with Wicket and Liferay? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Portlets in Liferay 5
Hi, I'm working on getting wicket compatible with jsr-286 now. However while doing this I've noticed that Liferay has still some major issues regarding jsr-286. Especially regarding setting properties on the response (essentially setting response headers, cookies, etc) there is still some work to be done. They also don't support the MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice addition because of the CSS and JS files wicket adds to it's pages. Comment and vote on http://support.liferay.com/browse/LEP-5828. and track it to follow the property changes I'm also planning on opening a Wicket-jira issue so that you can track the progress of the wicket implementation. But we will have to wait at least until the portlet 2.0 specifications get official and added to a maven repository before we can add anything to the wicket code base. Besides that it's a lot of work and I'm doing this in my free hours so don't get over excited just jet :). I'll post a message on the list when I open the jira issue, and I'll attach patches to that issue as soon as I feel confident about the work I've been doing. I hope that answers your questions a bit. Thijs gaugat wrote: I've read in the forums, that it is better to wait for Liferay 5 (JSR 286) to develop portlets in Apache Wicket. So has anyone developed portlets using Wicket and deployed them in Liferay 5?. If you have, is there a sample wicket portlet posted somewhere that I could look at? Are there still issues with Wicket and Liferay? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: VOTE: Generics of IDataProvider
[ ] IDataProviderI,T [ X ] IteratorIModelT , drop model [ ] Leave as is. Thijs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket portles in Sun Portal
Liferay is not really supported, We have it running but have hacked wicket to do so (in a combindation of a bridges implementation and a custom wicket version). Especially to get the Ajax stuff working correctly. We are hoping that with portlet 2.0 supported both by Liferay and wicket that the issues are going to be a lot less. Especially with resourceUrl's and HTTP header's / cookies Thijs Wilhelmsen Tor Iver schreef: We have (wisely :) ) chosen Wicket as web framework, but also chosen Sun Portal as the portal engine (not just Pluto but the commercial product). This causes a problem since Sun apparently haven't implemented the two interfaces required by Apache's bridge, so Wicket 1.3.x portlets do not work since the WicketPortlet appears to require the bridge. Are there anyone else who have used this combination successfully? As I see it, there are four possible solutions: 1) Provide implementations of the interfaces that hook into the Sun portlet engine 2) Make a custom WicketPortlet that does away with the bridge requirement and does all translation between the portlet world and the Wicket world. Has the disadvantage of effectively redoing work that the bridge already does 3) Make a custom Wicket Channel in the portlet server to (in effect) provide such a bridge (or wait for someone at Sun to write one :) ) which has the disadvantage of being tied to Sun's product 4) Serve the Wicket portlets from a second portlet container that _does_ support the bridge (Liferay, Jetspeed or JBoss if I am not mistaken), and use WSRP to show them in Sun's portal Which do you guys think is most likely to succeed? Med vennlig hilsen TOR IVER WILHELMSEN Senior systemutvikler Arrive AS T (+47) 48 16 06 18 E-post: [EMAIL PROTECTED] http://servicedesk.arrive.no - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bug in wicket-ajax.js introduced in Wicket 1.3.2?
See https://issues.apache.org/jira/browse/WICKET-1426 Meetesh Karia schreef: Hi all, We recently upgraded to Wicket 1.3.2 from Wicket 1.3.1 and we're seeing a bug with ajax behavior in Firefox (2.0.0.13 on Windows Vista). Basically, the following header is returned from an ajax call: ?xml version=1.0 encoding=UTF-8?ajax-responseheader-contribution encoding=wicket1 ![CDATA[head xmlns:wicket=http://wicket.apache.org; script src=/templates/mediaplayer/swfobject.js language=javascript/scriptscript type=text/javascript src=../../resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js/script script type=text/javascript src=../../resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js/script script type=text/javascript src=../../resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js/script script type=text/javascript id=wicket-ajax-debug-enable!--/*--![CDATA[/*!--*/ wicketAjaxDebugEnable=true; /*--]^]^*//script /head]]/header-contribution The page this is called from has a URL that looks like this http://host/2008/foo/bar In Wicket 1.3.1, the script /templates/mediaplayer/swfobject.js gets correctly loaded from http://host/templates/mediaplayer/swfobject.js However, in Wicket 1.3.2, it is incorrectly loaded from http://host/2008/foo//templates/mediaplayer/swfobject.js This appears to be related to one of these two changes: http://fisheye6.cenqua.com/browse/wicket/trunk/jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js?r1=614229r2=619539 http://fisheye6.cenqua.com/browse/wicket/trunk/jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js?r1=627225r2=628015 I haven't narrowed it down but replacing wicket-ajax.js with the version from 1.3.1 makes it work again. Should I file a bug for this? Or is this going to be the new behavior going forward for Firefox? Also, I'm guessing that the safest way to work around this problem is to remove those two changes and temporarily use a local build of wicket, right? Thanks, Meetesh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DataPicker problem
http://joda-time.sourceforge.net/
lienok schreef:
I did not.
I do not have that package. I do not use anything special. I supposed it
should be included in wicket jars. I tryied to find JodaTime package
through google, bo no success. :(
TonyVegas wrote:
Did you include the JodaTime package into your project?
lienok wrote:
Hello,
I am following book Enjoying web development with wicket, using Wicket
1.3.2.
Everythink worked fine till I added form.add(quoteDate).
Please check code and stack trace below and let me know any advice.
Thank you
public class GetQuoteSymbol extends WebPage {
private Model model;
private Model dateModel;
public GetQuoteSymbol() {
FeedbackPanel feedback = new FeedbackPanel(msgs);
add(feedback);
Form form = new Form(f) {
protected void onSubmit() {
String sym = (String) model.getObject();
Date date = (Date) dateModel.getObject();
int stockValue = (sym +
date.toString()).hashCode() % 100;
QuoteResult quoteResult = new
QuoteResult(stockValue);
setResponsePage(quoteResult);
}
};
model = new Model();
List symbols = new ArrayList();
symbols.add(MSFT);
symbols.add(IBM);
symbols.add(RHAT);
DropDownChoice symbol = new DropDownChoice(sym, model,
symbols);
symbol.setRequired(true);
form.add(symbol);
dateModel = new Model();
TextField quoteDate = new TextField(quoteDate, dateModel,
Date.class);
quoteDate.setRequired(true);
quoteDate.add(new DatePicker());
//HERE IS A PROBLEM
form.add(quoteDate);
add(form);
}
}
stack trace:
WicketMessage: Can't instantiate page using constructor public
com.myapp.stockquote.GetQuoteSymbol()
Root cause:
java.lang.ClassNotFoundException: org.joda.time.DateTime
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1363)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1209)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.wicket.extensions.yui.calendar.DatePicker.class$(DatePicker.java:86)
at
org.apache.wicket.extensions.yui.calendar.DatePicker.getDatePattern(DatePicker.java:438)
at
org.apache.wicket.extensions.yui.calendar.DatePicker.checkComponentProvidesDateFormat(DatePicker.java:296)
at
org.apache.wicket.extensions.yui.calendar.DatePicker.bind(DatePicker.java:129)
at org.apache.wicket.Component.add(Component.java:922)
at com.myapp.stockquote.GetQuoteSymbol.init(GetQuoteSymbol.java:57)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:149)
at
org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:58)
at
org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.newPage(BookmarkablePageRequestTarget.java:262)
at
org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.getPage(BookmarkablePageRequestTarget.java:283)
at
org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.processEvents(BookmarkablePageRequestTarget.java:210)
at
org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:91)
at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1166)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1243)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1330)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:358)
at
org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:124)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at
Re: [vote] Release 1.4 with only generics and stop support for 1.3
[X] +1, Wicket 1.4 is 1.3 + generics, drop support for 1.3 [ ] -1, I need a supported version running on Java 1.4 Thijs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Planning Wicket Next Generation
+1 to java 5 atul singh wrote: java 5 now definitely On Sun, Mar 16, 2008 at 7:48 PM, James Carman [EMAIL PROTECTED] wrote: On 3/16/08, Maarten Bosteels [EMAIL PROTECTED] wrote: +1 for moving to java 5 +1 for moving to Java 5 *quickly* :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PageParameter question
I'm having troubles with pageparameters.
when I use Page.getPageParameters() they are always null untill I call
super(paramters) in my constructor.
But when I then add a BookmarkablePageLink I get very strange behavior.
See the following example code:
public HomePage(final PageParameters parameters) {
super(parameters);
ArrayList list = new ArrayList();
list.add(aaa);
list.add(bbb);
list.add(ccc);
list.add(ddd);
add(new ListView(test, list ){
protected void populateItem(ListItem item) {
PageParameters p = item.getPage().getPageParameters(); //
getPage().getPageParameters();
if(p==null) p = new PageParameters();
String key = (String)item.getModelObject();
p.add(key, key);
BookmarkablePageLink lnk = new BookmarkablePageLink(link,
HomePage.class, p);
item.add(lnk);
}
});
}
this results in a page that constructs links that look like:
li wicket:id=test
a href=?key=aaa wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbb wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=ccc wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=cccamp;key=ddd
wicket:id=link test /a
/li
As you can see the pageparameters are added to the previously created
pageparameters.
While I was expecting that every link had it's own key, and that when I
click the link, the previous parameters would be added to the new link.
Debugging shows that for every loop over populateItem,
getPage().getPageParameters() returns the newly created PageParameters
instead of the current PageParameters.
Am I doing something wrong?
Thijs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: PageParameter question
because I want to use the already existing parameters and add them to
the link.
Thijs
Martijn Dashorst schreef:
Why don't you create a new PageParameters object in each populateItem?
Martijn
On 3/13/08, Thijs [EMAIL PROTECTED] wrote:
I'm having troubles with pageparameters.
when I use Page.getPageParameters() they are always null untill I call
super(paramters) in my constructor.
But when I then add a BookmarkablePageLink I get very strange behavior.
See the following example code:
public HomePage(final PageParameters parameters) {
super(parameters);
ArrayList list = new ArrayList();
list.add(aaa);
list.add(bbb);
list.add(ccc);
list.add(ddd);
add(new ListView(test, list ){
protected void populateItem(ListItem item) {
PageParameters p = item.getPage().getPageParameters(); //
getPage().getPageParameters();
if(p==null) p = new PageParameters();
String key = (String)item.getModelObject();
p.add(key, key);
BookmarkablePageLink lnk = new BookmarkablePageLink(link,
HomePage.class, p);
item.add(lnk);
}
});
}
this results in a page that constructs links that look like:
li wicket:id=test
a href=?key=aaa wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbb wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=ccc wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=cccamp;key=ddd
wicket:id=link test /a
/li
As you can see the pageparameters are added to the previously created
pageparameters.
While I was expecting that every link had it's own key, and that when I
click the link, the previous parameters would be added to the new link.
Debugging shows that for every loop over populateItem,
getPage().getPageParameters() returns the newly created PageParameters
instead of the current PageParameters.
Am I doing something wrong?
Thijs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: PageParameter question
Sorry I'm not sure I follow.
What I'm trying is to add a new PageParameter to the set that the
current page is created with. So I get the Page, get it's pageParameters
and add a new one to the existing set and feed that to the
bookmarkablepagelink.
If I would do:
protected void populateItem(ListItem item) {
PageParameters p = new PageParameters();
String key = (String)item.getModelObject();
p.add(key, key);
BookmarkablePageLink lnk = new BookmarkablePageLink(link, HomePage.class, p);
item.add(lnk);
}
the bookmarkablepagelink would only contain the new pageparameter, not
the already existing pageparameters
What happens now is that getPage().getPageParameters is not returning
the PageParameters from the current page, but is returning the
pageparameters I just added to the bookmarkablepagelink + the ones that
are already in getPage().getPageParameters.
So if you take the example below, and say I have clicked on the first
link. The output of HTML would then look like:
li wicket:id=test
a href=?key=mp;key=aaa wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=mp;key=bbb wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=mp;key=bbbamp;key=ccc
wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=mp;key=bbbamp;key=cccamp;key=ddd
wicket:id=linktest/a
/li
While I expect:
li wicket:id=test
a href=?key=mp;key=aaa wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=bbb wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=ccc wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=ddd wicket:id=linktest/a
/li
Thijs
Martijn Dashorst schreef:
So why don't you expect the loop to add them to the existing parameters?
Martijn
On 3/13/08, Thijs [EMAIL PROTECTED] wrote:
because I want to use the already existing parameters and add them to
the link.
Thijs
Martijn Dashorst schreef:
Why don't you create a new PageParameters object in each populateItem?
Martijn
On 3/13/08, Thijs [EMAIL PROTECTED] wrote:
I'm having troubles with pageparameters.
when I use Page.getPageParameters() they are always null untill I call
super(paramters) in my constructor.
But when I then add a BookmarkablePageLink I get very strange behavior.
See the following example code:
public HomePage(final PageParameters parameters) {
super(parameters);
ArrayList list = new ArrayList();
list.add(aaa);
list.add(bbb);
list.add(ccc);
list.add(ddd);
add(new ListView(test, list ){
protected void populateItem(ListItem item) {
PageParameters p = item.getPage().getPageParameters(); //
getPage().getPageParameters();
if(p==null) p = new PageParameters();
String key = (String)item.getModelObject();
p.add(key, key);
BookmarkablePageLink lnk = new BookmarkablePageLink(link,
HomePage.class, p);
item.add(lnk);
}
});
}
this results in a page that constructs links that look like:
li wicket:id=test
a href=?key=aaa wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbb wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=ccc wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=cccamp;key=ddd
wicket:id=link test /a
/li
As you can see the pageparameters are added to the previously created
pageparameters.
While I was expecting that every link had it's own key, and that when I
click the link, the previous parameters would be added to the new link.
Debugging shows that for every loop over populateItem,
getPage().getPageParameters() returns the newly created PageParameters
instead of the current PageParameters.
Am I doing something wrong?
Thijs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: PageParameter question
Stupid, I should have known that :'(
Thanks Martijn
Martijn Dashorst schreef:
You keep adding your new parameters to the parameters from the page.
Not a new page parameters object.
You should do something like:
PageParameters p = new PageParameters(getPage().getPageParameters());
p.add(key, value);
Martijn
On 3/13/08, Thijs [EMAIL PROTECTED] wrote:
Sorry I'm not sure I follow.
What I'm trying is to add a new PageParameter to the set that the
current page is created with. So I get the Page, get it's pageParameters
and add a new one to the existing set and feed that to the
bookmarkablepagelink.
If I would do:
protected void populateItem(ListItem item) {
PageParameters p = new PageParameters();
String key = (String)item.getModelObject();
p.add(key, key);
BookmarkablePageLink lnk = new BookmarkablePageLink(link, HomePage.class,
p);
item.add(lnk);
}
the bookmarkablepagelink would only contain the new pageparameter, not
the already existing pageparameters
What happens now is that getPage().getPageParameters is not returning
the PageParameters from the current page, but is returning the
pageparameters I just added to the bookmarkablepagelink + the ones that
are already in getPage().getPageParameters.
So if you take the example below, and say I have clicked on the first
link. The output of HTML would then look like:
li wicket:id=test
a href=?key=mp;key=aaa wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=mp;key=bbb wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=mp;key=bbbamp;key=ccc
wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=mp;key=bbbamp;key=cccamp;key=ddd
wicket:id=linktest/a
/li
While I expect:
li wicket:id=test
a href=?key=mp;key=aaa wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=bbb wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=ccc wicket:id=linktest/a
/li
li wicket:id=test
a href=?key=mp;key=ddd wicket:id=linktest/a
/li
Thijs
Martijn Dashorst schreef:
So why don't you expect the loop to add them to the existing parameters?
Martijn
On 3/13/08, Thijs [EMAIL PROTECTED] wrote:
because I want to use the already existing parameters and add them to
the link.
Thijs
Martijn Dashorst schreef:
Why don't you create a new PageParameters object in each populateItem?
Martijn
On 3/13/08, Thijs [EMAIL PROTECTED] wrote:
I'm having troubles with pageparameters.
when I use Page.getPageParameters() they are always null untill I call
super(paramters) in my constructor.
But when I then add a BookmarkablePageLink I get very strange behavior.
See the following example code:
public HomePage(final PageParameters parameters) {
super(parameters);
ArrayList list = new ArrayList();
list.add(aaa);
list.add(bbb);
list.add(ccc);
list.add(ddd);
add(new ListView(test, list ){
protected void populateItem(ListItem item) {
PageParameters p = item.getPage().getPageParameters(); //
getPage().getPageParameters();
if(p==null) p = new PageParameters();
String key = (String)item.getModelObject();
p.add(key, key);
BookmarkablePageLink lnk = new BookmarkablePageLink(link,
HomePage.class, p);
item.add(lnk);
}
});
}
this results in a page that constructs links that look like:
li wicket:id=test
a href=?key=aaa wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbb wicket:id=link test /a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=ccc wicket:id=link test
/a
/li
li wicket:id=test
a href=?key=mp;key=bbbamp;key=cccamp;key=ddd
wicket:id=link test /a
/li
As you can see the pageparameters are added to the previously created
pageparameters.
While I was expecting that every link had it's own key, and that when I
click the link, the previous parameters would be added to the new link.
Debugging shows that for every loop over populateItem,
getPage().getPageParameters() returns the newly created PageParameters
instead of the current PageParameters.
Am I doing something wrong?
Thijs
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail
Re: Mounting dynamic URLs
mount profile as a page and use the 'stiger' or 'wsmith' as a parameter to get the profile check IndexedParamUrlCodingStrategy Martijn Lindhout schreef: Hi All, How do I mount a friendly URL with a dynamic last part. I.e. I want the following URL's to be handled by a profile page which contents depends on the last part. Is this possible? http://localhost/myApp/profile/wsmith http://localhost/myApp/profile/stiger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: best practice for a wait page
Scott Swank wrote:
We have a page with a form and the form's onSubmit() method takes a
while. After it is complete the user is re-directed to another page.
We'd like to introduce a nice please wait while we process your
request page in between these pages. If anyone has done this, what
approach has worked well for you?
public class Page1 extends ...
{
...
add(new SomeForm()
{
public void onSubmit()
{
aBunchOfProcessing();
redirect(new Page2());
}
}
...
}
Thank you,
Scott
How about using a LazyLoadingPanel (or similar?) see wicket-extention
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicket + solr
This looks really good!!! I am looking into making something similar but I haven't really started yet. I'll defenitally look into your code and try to help out when and where I can. Thijs Ryan McKinley schreef: Hello- I've put together a little sample using wicket and solr. http://example.solrstuff.org/solr-voyager-example/ this uses solrj to hit: http://example.solrstuff.org/pvs/ Its still got some problems and I'm still stumbling through getting the models/structure correct, so if anyone is interested it would be great to get some feedback and direction. The source is all: http://solrstuff.org/svn/voyager/trunk/ To build the solr maven artifact, you will need: https://issues.apache.org/jira/browse/SOLR-19 The class I'm most concerned with getting correct is: http://solrstuff.org/svn/voyager/trunk/voyager/src/main/java/solrstuff/voyager/SolrQueryDataProvider.java All feedback is welcome! ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket 1.3 portlets in Liferay
Check also: http://issues.apache.org/jira/browse/WICKET-1132 http://www.liferay.com/web/guest/community/forums/message_boards/message/338111 But in short: it works a bit: If you implement a bridge like the one in http://www.nabble.com/Portlet-howto-tt13093514.html by charly You should get things working a bit. But Ajax won't work because your not allowed to set the text/xml contenttype header (what wicket does) Dynamic resources won't work because the response is not directly accessible (as portlet 1.0 spec) and there are some other issues... I've been trying to get some things working and I've had to alter some of the portal code. I have ajax working (a bit). But I'm constantly running into other things... Thijs racso wrote: How easy is it to use Wicket 1.3 application as a portlet in Liferay Portal 4.xx? As anyone tried it yet? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Which way to go? AjaxSubmitLink or AjaxLink? Neither does the job for me :)
Why not make it 2 separated forms? Edvin Syse wrote: Hi, I have a form where some of the components have validators (Required, EmailValidator etc). The form uses CompoundPropertyModel for my object. Upon entering some text in one input field and clicking a button, a ModalWindow opens and shows a searchresult based on the input. The button is a AjaxSubmitLink. The problem is that this operation is performed BEFORE the rest of the form is filled out, so validation fails (since lots of fields are missing input at this stage), and the ModalWindow doesn't open. If I turn off validation everything is good, but I need the validation for when the form is complete and finally submitted :) If I change to an AjaxLink, I can get the ModalWindow to open, but then the input data isn't propagated to the model, so I can't get hold of it in the ModalWindow. I have also tried overriding getDefaultFormProcessing() and returning false, but then obviously the model isn't updated either, so I'm stuck. Maybe I'm going about this the wrong way.. Any suggestions? Should I use another form without validation just for this one textfield? Sincerely, Edvin Syse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Which-way-to-go--AjaxSubmitLink-or-AjaxLink--Neither-does-the-job-for-me-%3A%29-tp14506161p14507376.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicket preloader
Why redirect? Use a lazyloading panel. Thijs tbt wrote: Hi I like to implement a preloader the wicket way. For example when a user does a search my code looks up the db and retrieves the relevent data. But this takes up a lot of time and i want to show a html page(preloader page) while the db search is done. When the search is completed it will automatically be redirected to a page displaying the results. Can anyone show me an example as how to do this using wicket. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wicket Portlets in Liferay
I'm trying to get wicket portlets to work in Liferay. As fas as I can tell there are at least 2 issues at the moment: 1.) A nullpointer exception in WebResponse due to an issue in de Liferay code that returns null in the encodeRedirectUrl (see http://www.liferay.com/web/guest/community/forums/message_boards/message/249501 ) To answer a question on the liferay forum I need to know why the encodeRedirectUrl is called. I think this is because of the REDIRECT_TO_RENDER setting done by the WicketFilterPortletContext. But can somebody confirm that?! 2.) https://issues.apache.org/jira/browse/WICKET-1132 I have no clue what causes this issue or where to look. Can somebody give me a push in the right direction? -- View this message in context: http://www.nabble.com/Wicket-Portlets-in-Liferay-tf4790149.html#a13703212 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Portlets in Liferay
Ate, your the man :) I'll try to dive into the parameter problem this week. Thnx Thijs Ate Douma wrote: Thijs wrote: I'm trying to get wicket portlets to work in Liferay. As fas as I can tell there are at least 2 issues at the moment: 1.) A nullpointer exception in WebResponse due to an issue in de Liferay code that returns null in the encodeRedirectUrl (see http://www.liferay.com/web/guest/community/forums/message_boards/message/249501 ) To answer a question on the liferay forum I need to know why the encodeRedirectUrl is called. I think this is because of the REDIRECT_TO_RENDER setting done by the WicketFilterPortletContext. But can somebody confirm that?! Hi Thijs, I've looked a bit deeper into this issue and it turned out that this is (or was) a JSR-168 conformance problem indeed. On Jetspeed-2 this didn't really cause any problems as we are more relaxed on this specific issue (in the end, redirects during rendering are not and will not ever be possible so allowing encoding doesn't hurt either). But clearly this needed to be resolved independently of Jetspeed, so I've created a new issue, https://issues.apache.org/jira/browse/WICKET-1155, as well as already resolved it :) Please do check if this now works for you too. 2.) https://issues.apache.org/jira/browse/WICKET-1132 I have no clue what causes this issue or where to look. Can somebody give me a push in the right direction? For this one, I really don't have a clue. You'll probably need a Liferay expert here as this goes into the internal url handling of the Liferay portlet container and is beyond Wicket itself. Regards, Ate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unsafe child warning
why do you use a negative number? Jan Kriesten wrote: Hi, I get this warning with my Repeater: ---8--- Child component of repeater TestPanel$2:componentlist has a non-safe child id of -501221721. Safe child ids must be composed of digits only. ---8--- I have to use Random generated ID's for a certain purpose. So, why does wicket insist on numbers (actually, this is one)? Best regards, --- Jan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache Wicket 1.3.0-rc1 released!
Martijn Dashorst wrote: First: congrats, Second: don't forget to change the link under 'Releases' on the website from 1.3-beta to 1.3-rc1 Thijs This is the first release candidate for Apache Wicket we have prepared for your pleasure. It contains over 80 fixes to issues with previous releases and todo items we have cleared. In this announcement: * Apache Wicket * This release * Migrating from 1.2 * Downloading the release * Validating the release * Reporting bugs * The distribution * Release Notes - Wicket - Version 1.3.0-rc1 Eager people click here to download the distribution, others can read further: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1 We thank you for your patience and support. The Wicket Team -= Apache Wicket =- Apache Wicket is a component oriented Java web application framework. With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Apache Wicket makes developing web-apps simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written with plain Java and HTML. Our migration to a top level project is now completed and you can find our website and documentation here: http://wicket.apache.org -= This release =- This release is the first in a series of release candidates releases until we feel confident to finalize Wicket 1.3. This is called a release candidate because we strive for API freeze. This means only bug fixes will be done on the 1.3 release from now on. -= Migrating from 1.2 =- If you are coming from Wicket 1.2, you really want to read our migration guide, found on the wiki: http://cwiki.apache.org/WICKET/migrate-13.html -= Downloading the release =- You can download the release from the official Apache mirror system, and you can find it through the following link: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/ For the Maven and Ivy fans out there: update your pom's to the following, and everything will be downloaded automatically: dependency groupIdorg.apache.wicket/groupId artifactIdwicket/artifactId version1.3.0-rc1/version /dependency Substitute the artifact ID with the projects of your liking to get the other projects. Please note that we don't prescribe a Logging implementation for SLF4J. You need to specify yourself which one you prefer. Read more about SLF4J here: http://slf4j.org -= Validating the release =- The release has been signed by Frank Bille, your release manager for today. The public key can be found in the KEYS file in the download area. Download the KEYS file only from the Apache website. http://www.apache.org/dist/wicket/1.3.0-rc1/KEYS Instructions on how to validate the release can be found here: http://www.apache.org/dev/release-signing.html#check-integrity -= Reporting bugs =- In case you do encounter a bug, we would appreciate a report in our JIRA: http://issues.apache.org/jira/browse/WICKET -= The distribution =- In the distribution you will find a README. The README contains instructions on how to build from source yourself and a list of all things that have been fixed, added and/or removed since the first beta release. -= Release Notes - Wicket - Version 1.3.0-rc1 =- Sub-task * WICKET-1022 - Created new bug - ValueMap set to null Bug * WICKET-330 - CheckBox incorrectly converts its model value when a custom Boolean converter is installed * WICKET-336 - Inheritable model cannot be a wrap model * WICKET-382 - Converter misusage/mangling in RadioChoice * WICKET-487 - Buggy behaviour in PageMap.access(IPageMapEntry,int). Wicket1.2.4 * WICKET-588 - continueToOriginalDestination / RestartResponseAtInterceptPageException with page parameters broken * WICKET-605 - Stateless form skips page parameters * WICKET-607 - Stateless forms don't work with QueryStringUrlCodingStrategy * WICKET-642 - Need to escape select html option value * WICKET-645 - Form with ajaxsubmitbutton won't submit after error * WICKET-702 - MockWebApplication doesn't redirect properly to mounted pages under RestartResponseAtInterceptPageException * WICKET-734 - Custom ILinkListener component causes error in cell on mounted page * WICKET-746 - Thread synchronization problems in FilePageStore * WICKET-855 - ModalWindow makes Internet Explorer 6 show an security warning dialog * WICKET-901 - DatePicker#getConfigureYUIBasePath() is useless or never called * WICKET-916 - inconsistent state after setting AjaxDebugModeEnabled to true in an AjaxRequest * WICKET-920 - ExternalLink produces invalid html * WICKET-950 - StatelessForm + QueryStringUrlCodingStrategy problem * WICKET-953 - Session invalidateNow() does not immediate remove the session from disk * WICKET-958 - Mounts ignored for PageExpiredErrorPage * WICKET-972 - IndexedParamUrlCodingStrategy seems to have problems handling resources * WICKET-988 - PropertyResolver map * WICKET-991 - StringIndexOutOfBoundsException in ServletWebRequest.getRelativePathPrefixToWicketHandler
Re: Wicket portlet newbie questions
Yeah I know Read http://www.liferay.com/web/guest/community/forums/message_boards/message/249501 Then there also is: https://issues.apache.org/jira/browse/WICKET-1132 So your not out of the woods jet... Thijs justment wrote: Ok now I already add wicket portlet page to liferay.But i have new problem :-) when i click in some wicket example i have error. 02:42:45,572 ERROR [jsp:52] java.lang.NullPointerException at org.apache.wicket.protocol.http.WebResponse.write(WebResponse.java:35 5) at org.apache.wicket.protocol.http.BufferedWebResponse.close(BufferedWeb Response.java:74) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java: 330) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.ja va:169) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:188) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:691) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:594) Can you pls help me. Thk you. Thijs wrote: Just download the source from SVN and build it. You'll have to change the portlet.xml anyway justment wrote: Hi Thijs,Please tell me about version of portlet wicket-exemples.war I can't find it on wicket site .Thank you Thijs wrote: Check out http://www.nabble.com/Portlet-howto-tf4587073.html#a13093514 justment wrote: I want to implements wicket portlet on liferay but I can't get any demo,documents from google :p Thanks in advance for any pointers and explanations thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket-portlet-newbie-questions-tf4751827.html#a13653300 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket meetup (the netherlands) ideas
+1 Orion Letizi wrote: If you think a talk on scaling Wicket with Terracotta would be interesting, we'd love to come... Cheers, Orion Johan Compagner wrote: Guys, we are already in the month of the great Wicket meetup in the netherlands So does anybody have idea's what you would like to see ? Do you want to see some short presentations? What would be good topics? Does anybody want to give a short presentation? johan On 10/16/07, Arje Cahn [EMAIL PROTECTED] wrote: -- View this message in context: http://www.nabble.com/Re%3A-Wicket-meetup-%28the-netherlands%29-ideas-tf4751271.html#a13603043 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket portlet newbie questions
Just download the source from SVN and build it. You'll have to change the portlet.xml anyway justment wrote: Hi Thijs,Please tell me about version of portlet wicket-exemples.war I can't find it on wicket site .Thank you Thijs wrote: Check out http://www.nabble.com/Portlet-howto-tf4587073.html#a13093514 justment wrote: I want to implements wicket portlet on liferay but I can't get any demo,documents from google :p Thanks in advance for any pointers and explanations thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Wicket-portlet-newbie-questions-tf4751827.html#a13622399 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket portlet newbie questions
Check out http://www.nabble.com/Portlet-howto-tf4587073.html#a13093514 justment wrote: I want to implements wicket portlet on liferay but I can't get any demo,documents from google :p Thanks in advance for any pointers and explanations thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet howto
I've tried to localize this.
It looks like the generated url s not correct.
this is the source for the ajax link example
href=# onclick=var
wcall=wicketAjaxGet('http://localhost:8080/web/guest/admin?p_p_id=AjaxApplicationp_p_action=1p_p_col_id=column-1p_p_col_count=1;',null,null,
function() {return Wicket.$$(this)}.bind(this));return !wcall; ...
notice the 'p_p_id=AjaxApplication' while this should be:
'p_p_id=AjaxApplication_WAR_wicketexamples'
I'm trying to find where the this javascript fragment URL is generated in
wicket because the normal, non ajax links do point to the correct location:
href=http://localhost:8080/web/guest/admin?p_p_id=AjaxApplication_WAR_wicketexamplesamp;p_p_action=1amp;p_p_state=normalamp;p_p_mode=view.
Can someone point me in the right direction?
Thijs
Thijs wrote:
Hello Charly,
Have you got any answer from Liferay jet?
We could put this in an issue in the Liferay support system. Or post a
message on the forum.
I tried something very ugly I implemented encodeRedirectURL as encodeURL
is implemented. (copied the code) This prevents the nullpointer of
showing up. But then I get this message:
13:08:40,375 WARN [PortletLocalServiceImpl:138] Portlet not found for 1
AjaxApplication
Which probably is logical :)
I'll try and dig some further.
Thijs
Charles CHAHBAZIAN wrote:
Hi Ate,
Ate Douma a écrit :
Charly
wrote:
Hello,
I have the beginning of a solution !
Cool !
My code is based on Liferay's struts support
with some adaptations.
At this time, Guestbook portlet sample is ok, and I've made a
modification in wicket to get Navomatic and other bookmarkablePage
working.
The main point is that Liferay want a new HttpServletRequest (from
theirs object) in ServletContextProvider implementation of
ServletContextProvider and we must copy the request's parameters from
the original request to the new one.
Weird, but I guess it is something Liferay specific.
You're right. Because if I keep the same HttpServletRequest, I have a
ClassCastException later because Liferay use these specific objects...
I translate also the _wu
(WicketPortlet.WICKET_URL_PORTLET_PARAMETER) parameter into differents
parameters
Why?
The WicketPortlet dispatches to the servlet/filter using this url, so
the underlying web container (e.g. catalina) should already provide the
query string parameters as request parameters (as required by the
servlet spec).
You can have a look to my 3 classes at the end of this mail.
I notice that you don't set the provided Map portletArg arguments on
the created PortletURLImpl in createResourceURL method.
You probably should...
I tried that solution first. In that case, the url looks like that :
http://localhost:8080/user/joebloggs/3?p_p_id=NavomaticApplication_WAR_wicketexamplesamp;p_p_action=0amp;p_p_state=normalamp;p_p_mode=viewamp;p_p_col_id=column-1amp;p_p_col_count=1amp;_NavomaticApplication_WAR_wicketexamples__wuview=%2Fnavomatic%2F%3Fwicket%3AbookmarkablePage%3D%253Aorg.apache.wicket.examples.navomatic.Page2
But the WebRequestCodingStrategy (at line : 518) use the
request.getParameter() and on my debug sessions i saw that the
portletArgs i've put in the PortletURLImpl parameters are available in
the queryString but not in the parameters of the request ... (looks
strange for me too, it seems to be a liferay's bug)
I've got a problem for all bookmarkablePage, because the argument are
encoded by Wicket, and Liferay encode it second time.
Liferay shouldn't be doing that: you should get back the parameters
previously set on a PortletURL exactly the same.
Seems like a Liferay bug to me.
About that question, as you can see in the sample url I've put, we have
wicket%3AbookmarkablePage%3D%253Aorg.apache.wicket.examples.navomatic.Page2
you can see that the there are 2 encoding :
1) wicket set the parameter from
:org.apache.wicket.examples.navomatic.Page2 to
%3Aorg.apache.wicket.examples.navomatic.Page2
2) Liferay encode the % character to %25
When Liferay get back the Encoded parameter, the %25 is set into %
but no Wicket Code transform back the %3A to :
Note : Wicket Encoding is done by :
org.apache.wicket.request.target.coding.WebRequestEncoder : line 86
escapedValue = URLEncoder.encode(escapedValue,
application.getRequestCycleSettings().getResponseRequestEncoding());
and I can't find a decode for this level in Wicket's code.
The parameter received is like
%3Aorg.apache.wicket.examples.navomatic.Page2. So I add a call to
decode function from org.apache.wicket.protocol.http.RequestUtils
Here is my code modification (it's maybe possible to find a another
solution too)
in the class
org.apache.wicket.protocol.http.request.WebRequestCodingStrategy,
method
Re: Add String which contains HTML markups
BatiB80 wrote: [EMAIL PROTECTED], I want to add some string to a HTML page which already contains some HTML markups. For example: add(new Label(component_id, some textwhich contains makups)); If I add the HTML Markups will be shown instead of interpreted. Does anybody knows what to do??? Thanks in advance, Sebastian see: (multiline)label..setEscapeModelStrings(false)); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet howto
Hello Charly, Have you got any answer from Liferay jet? We could put this in an issue in the Liferay support system. Or post a message on the forum. I tried something very ugly I implemented encodeRedirectURL as encodeURL is implemented. (copied the code) This prevents the nullpointer of showing up. But then I get this message: 13:08:40,375 WARN [PortletLocalServiceImpl:138] Portlet not found for 1 AjaxApplication Which probably is logical :) I'll try and dig some further. Thijs Charles CHAHBAZIAN wrote: Hi Ate, Ate Douma a écrit : Charly wrote: Hello, I have the beginning of a solution ! Cool ! My code is based on Liferay's struts support with some adaptations. At this time, Guestbook portlet sample is ok, and I've made a modification in wicket to get Navomatic and other bookmarkablePage working. The main point is that Liferay want a new HttpServletRequest (from theirs object) in ServletContextProvider implementation of ServletContextProvider and we must copy the request's parameters from the original request to the new one. Weird, but I guess it is something Liferay specific. You're right. Because if I keep the same HttpServletRequest, I have a ClassCastException later because Liferay use these specific objects... I translate also the _wu (WicketPortlet.WICKET_URL_PORTLET_PARAMETER) parameter into differents parameters Why? The WicketPortlet dispatches to the servlet/filter using this url, so the underlying web container (e.g. catalina) should already provide the query string parameters as request parameters (as required by the servlet spec). You can have a look to my 3 classes at the end of this mail. I notice that you don't set the provided Map portletArg arguments on the created PortletURLImpl in createResourceURL method. You probably should... I tried that solution first. In that case, the url looks like that : http://localhost:8080/user/joebloggs/3?p_p_id=NavomaticApplication_WAR_wicketexamplesamp;p_p_action=0amp;p_p_state=normalamp;p_p_mode=viewamp;p_p_col_id=column-1amp;p_p_col_count=1amp;_NavomaticApplication_WAR_wicketexamples__wuview=%2Fnavomatic%2F%3Fwicket%3AbookmarkablePage%3D%253Aorg.apache.wicket.examples.navomatic.Page2 But the WebRequestCodingStrategy (at line : 518) use the request.getParameter() and on my debug sessions i saw that the portletArgs i've put in the PortletURLImpl parameters are available in the queryString but not in the parameters of the request ... (looks strange for me too, it seems to be a liferay's bug) I've got a problem for all bookmarkablePage, because the argument are encoded by Wicket, and Liferay encode it second time. Liferay shouldn't be doing that: you should get back the parameters previously set on a PortletURL exactly the same. Seems like a Liferay bug to me. About that question, as you can see in the sample url I've put, we have wicket%3AbookmarkablePage%3D%253Aorg.apache.wicket.examples.navomatic.Page2 you can see that the there are 2 encoding : 1) wicket set the parameter from :org.apache.wicket.examples.navomatic.Page2 to %3Aorg.apache.wicket.examples.navomatic.Page2 2) Liferay encode the % character to %25 When Liferay get back the Encoded parameter, the %25 is set into % but no Wicket Code transform back the %3A to : Note : Wicket Encoding is done by : org.apache.wicket.request.target.coding.WebRequestEncoder : line 86 escapedValue = URLEncoder.encode(escapedValue, application.getRequestCycleSettings().getResponseRequestEncoding()); and I can't find a decode for this level in Wicket's code. The parameter received is like %3Aorg.apache.wicket.examples.navomatic.Page2. So I add a call to decode function from org.apache.wicket.protocol.http.RequestUtils Here is my code modification (it's maybe possible to find a another solution too) in the class org.apache.wicket.protocol.http.request.WebRequestCodingStrategy, method addBookmarkablePageParameters(final Request request, final RequestParameters parameters) (line : 521 / SVN revision : 585043) I change from final String[] components = Strings.split(requestString, Component.PATH_SEPARATOR); to final String[] components = Strings.split(RequestUtils.decode(requestString),Component.PATH_SEPARATOR); (Note: I test it with jetspeed and it works) The main remaining problem is about Ajax portlet. I have this Error : === 15:38:53,248 ERROR [[default]:731] Servlet.service() pour la servlet default a lancé une exception java.lang.NullPointerException at org.apache.wicket.protocol.http.WebResponse.redirect(WebResponse.java:204
Portlet howto
Hi (Ate?) Is there someone who could write a small wikipage on what I have to change in a Quickstart project to deploy it as a portlet? I'm trying to get the examples.war working on a liferay portal (liferay.com). But this is giving me so much trouble that I just want to work with an 'empty' quickstart. Because I'm not sure if it is Wicket that is giving me the headache's or Liferay (with their custom xml configs). Thijs -- View this message in context: http://www.nabble.com/Portlet-howto-tf4587073.html#a13093514 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Any interest in a Wicket User Group meeting in The Netherlands?
+1 looking forward to it!! Thijs Johan Compagner wrote: hi, I can organize one if there is enough interest Martijn and i will be there then. And for example if people are also interested in the wicket security i will also drag Maurice to the table. johan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating RSS feeds with Wicket
I'll see what I can come up with in the next few days/weeks. I just started a new job so that is eating a lot of my time. Unfortunately they're not running a project with wicket :( It's all Oracle adf, not bad either. But not as good as :) Ryan Sonnek wrote: That's a really good question. If you look at the source for my solution, it's a very lightweight wrapper around the ROME RSS library. I don't have any code that's setting response headers. If you have a solution, I'd be happy to incorporate it into the FeedPage. On 8/24/07, thijs [EMAIL PROTECTED] wrote: Hi Ryan, I've added this as a comment to your blog entry as wel, but is was marked as spam... Wow, cool is the right word for this. Does it also incorporate responses to http headers? For example: I had to modify the RssPage example to work with If-Modified-Since headers because some feed readers just keep updating their information (adding the same articles over and over). Also it helps keep traffic to the site low Thijs Ryan Sonnek wrote: http://www.jroller.com/wireframe/entry/wicket_and_rss_feeds Just wanted to post an announcement that there's a new wicket stuff project (wicketstuff-rome) to allow for creation of RSS (or Atom) feeds from within Wicket. I've been using it for the past several weeks and it's allowed me to integrate RSS feeds into my Wicket app *very* quickly. This new project is a definite step up from the existing wicket wiki article for Rss pages, but I'm not sure what to do about that info. Please let me know if anyone has suggestions or issues with the project. Now that it's on wicketstuff, feel free to tweak or add features! Ryan
Re: Wicket-Stuff Tinymce-Editor: No toolbars in IE6
He Benjamin,
I have the same problem. I have opened a JIRA issue for it:
http://wicketstuff.org/jira/browse/WCTINYMCE-2 But no response so far. I
can't help you any further but lets hoop the maintainer of the tinymce
project picks it up...
Thijs
Benjamin Ernst wrote:
Hi,
has nobody an idea? Any help would be great!
Thanks,
Benjamin
2007/8/16, Benjamin Ernst [EMAIL PROTECTED]:
Hi,
I have a problem with the wicket-stuff Tinymce-Editor in the
InternetExplorer:
the first time the page is loaded, there are no tool-icons, just the
text-area. And IE gives the following Error:
Error: 'tinyMCE is undefined'
It' s an Java-Script-Error and it might be, that the scripts are not
loaded the right way. But I don´t know how to fix this. Here are the scripts
from generated the HTML-Source:
script type=text/javascript id=import!--/*--![CDATA[/*!--*/
var script = document.createElement('script');
script.id='tinyMCEScript ';
script.src='resources/wicket.contrib.tinymce.TinyMCEPanel/tiny_mce/tiny_mce_src.js
';
script.type='text/javascript';
document.getElementsByTagName ('head')[0].appendChild(script);
/*--]]*//script
script type=text/javascript id=init!--/*--![CDATA[/*!--*/
tinyMCE.init({
mode : specific_textareas,
editor_selector : mceEditor,
theme : advanced,
language : en,
plugins : contextmenu, save, paste, searchreplace, insertdatetime,
preview, zoom, table, emotions, iespell, flash, print, directionality,
fullscreen, spellchecker,
theme_advanced_buttons1_add_before : save, newdocument, separator,
theme_advanced_buttons1_add : fontselect, fontsizeselect,
theme_advanced_buttons2_add_before: cut, copy, paste, pastetext,
pasteword, separator, search, replace, separator,
theme_advanced_buttons2_add : separator, inserttime, insertdate,
separator, preview, zoom, separator, forecolor, backcolor,
theme_advanced_buttons3_add_before : tablecontrols,
theme_advanced_buttons3_add : emotions, iespell, flash, separator,
print, separator, ltr, rtl, separator, fullscreen,
theme_advanced_buttons4 : spellchecker,
theme_advanced_toolbar_location : top,
theme_advanced_statusbar_location : bottom,
theme_advanced_toolbar_align : left,
theme_advanced_resizing : true,
theme_advanced_resize_horizontal : false,
plugin_insertdate_timeFormat : Time: %H:%M,
plugin_insertdate_dateFormat : Date: %m-%d-%Y,
fullpage_default_xml_pi : false,
spellchecker_languages : +English=en
});
/*--]]*//script
Sometimes when the page is loaded again, the tool-icons are there. In
FireFox it works fine, but unfortunately I have to use IE for this project.
Thanks in advance,
Benjamin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
full path/url to page using wicket.servlet
I'm migrating my app from 1.2.2 to 1.3 And the only real problem I have
is getting my rss feed up.
I'm adding the rss to the page head
link title=foo.com rel=alternate type=application/rss+xml...
I need the full path to the bookmarkable page to get this working (and
generate the all links inside the rss xml)
What I used to do was:
private String getFullUrl(
final String pageMapName,
final Class pageClass,
final PageParameters parameters)
{
HttpServletRequest
request=((ServletWebRequest)getRequest()).getHttpServletRequest();
final StringBuffer url = new StringBuffer();
url.append(getProtocolHeader(request.getProtocol()));
url.append(request.getServerName());
if(request.getServerPort()!=80)
{
url.append(:);
url.append(String.valueOf(request.getServerPort()));
}
url.append(urlFor(
pageClass,
parameters));
}
private String getProtocolHeader(String protocol)
{
if(protocol.equals(HTTP/1.1))
return http://;;
else
return ;
}
Basically what is described on the wiki page (search for rss)
But using the Filter instead of the Servlet I'm missing part of the url.
urlFor only returns the last bit of the bookmarkable part for example:
Rss.class is mounted as /rss
and urlFor(Rss.class, new PageParameters()); returns 'rss' instead of
'/servlet/app/rss' (what it used to do in 1.2.x)
What do I have to change to get this working again?
cheers
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: full path/url to page using wicket.servlet
Thnx Al I'll do what you suggest as a temp fix (maybe store them in a db for easy redeployment) Hope you fix this though :) Thijs Al Maw wrote: Thijs wrote: I need the full path to the bookmarkable page to get this working What do I have to change to get this working again? I need to fix WICKET-609 to make this easy for you. ;-) The reason this has become difficult in Wicket 1.3 is that we now generate relative URLs so sitting behind a mod_proxy Just Works(tm). However, that now means that Wicket doesn't really know or care about the servlet context path bit of your deployment, or the domain name it's all sitting on. This is a good thing, as relying on those when you're behind a mod_proxy breaks everything. The only way to make this work until I've fixed WICKET-609 is to use the urlFor() method and manually add the appropriate domain name and path on to the front of your URL. Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fwd: Wickest way to format a label before render
Why not use the onComponentTag? Francisco Diaz Trepat - gmail wrote: sorry sent to the wrong address. -- Forwarded message -- From: Francisco Diaz Trepat - gmail [EMAIL PROTECTED] Date: Aug 15, 2007 12:02 PM Subject: Wickest way to format a label before render To: [EMAIL PROTECTED] Hi, I have the dumbest request from our functional team. A label that holds the result of a calculation must invert the positive negative sign (- +), with that the color, and add a percentage symbol. So, basically I have to change the display model value and based on the model value itself. onBeforeRender? I had some difficulties, thanks, f(t) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fwd: Wickest way to format a label before render
Sorry
onComponentTagBody
protected void onComponentTagBody(final MarkupStream markupStream, final
ComponentTag openTag) {
replaceComponentTagBody(markupStream, openTag,
doYourStuffWithTheModel(getModelObject()));
}
And you can probably add a SimpleAttributeModifier to add a class
element to add a css property.
see
http://cwiki.apache.org/WICKET/how-to-modify-an-attribute-on-a-html-*tag*.html
http://cwiki.apache.org/WICKET/how-to-modify-an-attribute-on-a-html-tag.html
Put this al in a custom component and you have what you want...
Francisco Diaz Trepat - gmail wrote:
Sounds good. I thought about it too.
as the subject suggest, would that be the wickets way?
would that be the more nit way from a wicket perspective?
f(t)
On 8/15/07, Thijs [EMAIL PROTECTED] wrote:
Why not use the onComponentTag?
Francisco Diaz Trepat - gmail wrote:
sorry sent to the wrong address.
-- Forwarded message --
From: Francisco Diaz Trepat - gmail [EMAIL PROTECTED]
Date: Aug 15, 2007 12:02 PM
Subject: Wickest way to format a label before render
To: [EMAIL PROTECTED]
Hi, I have the dumbest request from our functional team.
A label that holds the result of a calculation must invert the positive
negative sign (- +), with that the color, and add a percentage symbol.
So, basically I have to change the display model value and based on the
model value itself.
onBeforeRender?
I had some difficulties,
thanks,
f(t)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
