Re: IHeaderContributor of invisible Components
When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? It is not added to the page. There's no script-tag. Am 14.07.2011 14:15, schrieb Rodrigo Heffner: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de wrote: I have a problem with IHeaderContributor and invisible Components: A Panel MyPanel implements IHeaderContributor. The renderHead-Methods adds some JavaScript-References. When the page is rendered this panel is invisible. So these JavaScript-References are not loaded when the page is loaded. Later visibility is switched within an Ajax-Call and the MyPanel will be rendered. But than my JavaScript is not loaded. Strange: During the Ajax-Call the renderHead-Method of MyPanel is even called, but the call doesn't provoke anything concerning the output to the browser. Any suggestions? Benedikt - 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: IHeaderContributor of invisible Components
Check Ajax Debug panel for errors. On Fri, Jul 15, 2011 at 10:35 AM, Benedikt Rothe benedikt.ro...@qleo.de wrote: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? It is not added to the page. There's no script-tag. Am 14.07.2011 14:15, schrieb Rodrigo Heffner: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de wrote: I have a problem with IHeaderContributor and invisible Components: A Panel MyPanel implements IHeaderContributor. The renderHead-Methods adds some JavaScript-References. When the page is rendered this panel is invisible. So these JavaScript-References are not loaded when the page is loaded. Later visibility is switched within an Ajax-Call and the MyPanel will be rendered. But than my JavaScript is not loaded. Strange: During the Ajax-Call the renderHead-Method of MyPanel is even called, but the call doesn't provoke anything concerning the output to the browser. Any suggestions? Benedikt - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Generate ajax link
This JavaScript is generated by AbstractDefaultAjaxBehavior.
On Thu, Jul 14, 2011 at 11:26 PM, Lurtz Nazgul lu...@ymail.com wrote:
Thanks Martin; but it doesn't make sense to me, sorry.
Wicket generates below code for a simple counter increment example.
var wcall =
wicketAjaxGet('?wicket:interface=:2:panel1:okla::IBehaviorListener:0:',
The first parameter is the callback url to the ajax behavior.
This means: find the first behavior in component with id 'okla' which
is in component with id 'panel1' which is in page with id 2.
function() {
}.bind(this),
The first function is the onSuccess callback
function() {
}.bind(this),
The second is the onFailure callback
function() {
return Wicket.$('okla') != null;
}.bind(this));
The last is the precondition: execute the Ajax request only if there
is an HTMLElement with id 'okla' in the DOM.
return !wcall;
Just the callback url is mandatory parameter, all other can be null.
Any suggestions ?
Thanks.
From: Martin Grigorov mgrigo...@apache.org
To: users@wicket.apache.org
Sent: Thu, July 14, 2011 2:46:04 PM
Subject: Re: Generate ajax link
See how AjaxLink generates its markup.
On Thu, Jul 14, 2011 at 2:31 PM, Lurtz Nazgul lu...@ymail.com wrote:
I mean; generating ajax link format
Instead of
lia href='?thePanel=com.test.PanelOne'/a/li
I want to generate ajax link on the fly
Example :
a onclick=var
wcall=wicketAjaxGet('wicket/page?2-1.IBehaviorListener.0-c1--link',function()
{
}.bind(this),function() { }.bind(this), function() {return Wicket.$('idc') !=
null;}.bind(this));return !wcall; id=idc href=#increment/a
Any suggestions ?
Thanks.
From: Andrea Del Bene adelb...@ciseonweb.it
To: users@wicket.apache.org
Sent: Thu, July 14, 2011 2:00:32 PM
Subject: Re: Generate ajax link
Hi,
you can use Loop component to generate a dynamic number of links. For
example:
HTML code:
ol title=Menù class=main_menu
li style=list-style: none; wicket:id=itemList
a wicket:id=menuItem/a
/li
/ol
Java code:
ListAbstractLink linkList = ...
Loop loop = new Loop(itemList, linkList.size()) {
@Override
protected void populateItem(LoopItem item) {
AbstractLink curLink = linkList.get(item.getIndex());
item.add(curLink);
}
};
Hi all;
I can generate normal links in to my dynamic menu
lia href='?thePanel=com.test.PanelOne'/a/li
...
I wonder if i can generate those links in ajax link format ?
Thanks.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: getRelativePathPrefixToWicketHandler String index out of range
Hi On Thu, Jul 14, 2011 at 8:10 PM, Jonathan Gray jonathan.g...@f-i.com wrote: please excuse me if this is a dupe - i posted to the general apache forum and then MOVED it to the users forum i wasn't sure if the post would go to the mailing list if it was moved rather than originally posted there...anyway: i have seen this error reported several times and i have seen wicket devs come back and say that it is fixed. what i see is that all versions of wicket from 1.4.11 - 1.4.17 have this exact problem. i have a number of RESTful calls to an app that are rewritten w mod_rewrite. the rewritten requests are processed by a MultiActionController and which then uses RequestDispatcher.forward to pass the request on to my custom WebRequestCycle. Anything that is rewritten by mod_rewrite in 1.4.11 or greater throws the StringIndexOutOfBounds exception in the * getRelativePathPrefixToWicketHandler* method when it tries to do this: relativeUrl = filterPath == null ? relativeUrl : relativeUrl.substring(filterPath.length()); because the forwardUrl = '/rw' and the relativeUrl = What is 'forwardUrl' ? 'account/updates/14883'. can someone please offer a workaround for this? let me know if you need more information. upgrading to 1.5 is fine and all, but i would like to get this working in 1.4, too. This specific logic has been removed in Wicket 1.5 so the chance your app to work is much bigger. If it is broken then please create a tutorial how to setup Apache HTTPD and the Wicket application so we can debug it and fix it. There is similar issue https://issues.apache.org/jira/browse/WICKET-2836 - but it as I said this is improved in 1.5. i have seen several threads on this problem but nothing that definitively tells me what the solution is. thanks. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: IHeaderContributor of invisible Components
Check Ajax Debug panel for errors. I did check the Ajax-Debug-Panel. No error. Situation: A Component has JavaScript-header-Contributors but is invisible. Visibility is switched during an AjaxRequest. What is Wicket's *supposed* to do? a) JavaScript-header-Contributor shall be mentioned in the Page although the Component is Wicket-Invisible b) JavaScript-header-Contributor shall be mentioned in header-contribution-Section of the wicket-ajax-response c) Wicket doesn't want to deal with a situation like this. Am 15.07.2011 09:46, schrieb Martin Grigorov: Check Ajax Debug panel for errors. On Fri, Jul 15, 2011 at 10:35 AM, Benedikt Rothebenedikt.ro...@qleo.de wrote: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? It is not added to the page. There's no script-tag. Am 14.07.2011 14:15, schrieb Rodrigo Heffner: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.dewrote: I have a problem with IHeaderContributor and invisible Components: A Panel MyPanel implements IHeaderContributor. The renderHead-Methods adds some JavaScript-References. When the page is rendered this panel is invisible. So these JavaScript-References are not loaded when the page is loaded. Later visibility is switched within an Ajax-Call and the MyPanel will be rendered. But than my JavaScript is not loaded. Strange: During the Ajax-Call the renderHead-Method of MyPanel is even called, but the call doesn't provoke anything concerning the output to the browser. Any suggestions? Benedikt - 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: IHeaderContributor of invisible Components
Wicket calls renderHead() for each component added in the AjaxRequestTarget. Then for each call of IHeaderResponse.renderXYZ() Wicket checks whether this is static resource and whether it is already rendered. If it is not then it renders it. If it is non-static (e.g. renderOnDomReady or renderOnLoad) then it is contributed every time the component is re-rendered. Better create a quickstart and attach it to Jira. On Fri, Jul 15, 2011 at 11:39 AM, Benedikt Rothe benedikt.ro...@qleo.de wrote: Check Ajax Debug panel for errors. I did check the Ajax-Debug-Panel. No error. Situation: A Component has JavaScript-header-Contributors but is invisible. Visibility is switched during an AjaxRequest. What is Wicket's *supposed* to do? a) JavaScript-header-Contributor shall be mentioned in the Page although the Component is Wicket-Invisible b) JavaScript-header-Contributor shall be mentioned in header-contribution-Section of the wicket-ajax-response c) Wicket doesn't want to deal with a situation like this. Am 15.07.2011 09:46, schrieb Martin Grigorov: Check Ajax Debug panel for errors. On Fri, Jul 15, 2011 at 10:35 AM, Benedikt Rothebenedikt.ro...@qleo.de wrote: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? It is not added to the page. There's no script-tag. Am 14.07.2011 14:15, schrieb Rodrigo Heffner: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de wrote: I have a problem with IHeaderContributor and invisible Components: A Panel MyPanel implements IHeaderContributor. The renderHead-Methods adds some JavaScript-References. When the page is rendered this panel is invisible. So these JavaScript-References are not loaded when the page is loaded. Later visibility is switched within an Ajax-Call and the MyPanel will be rendered. But than my JavaScript is not loaded. Strange: During the Ajax-Call the renderHead-Method of MyPanel is even called, but the call doesn't provoke anything concerning the output to the browser. Any suggestions? Benedikt - 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 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: getRelativePathPrefixToWicketHandler String index out of range
you asked what is forwardUrl - it is the httprequest attribute javax.servlet.forward.servlet_path forwardUrl is just the variable name that this attribute is assigned to in the ServletWebRequest.getRelativePathPrefixToWicketHandler method. i will try to get 1.5 going. it seems strange to me, however, that mod_rewrite and wicket requestdispatcher + servletwebrequest don't play nice together seeing as how both mod_rewrite Wicket are popular somewhat mature apache technologies. re: tutorial. well, it's probably going to take too much back and forth to make it worth either of our time to do this. thanks. - j -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/getRelativePathPrefixToWicketHandler-String-index-out-of-range-tp3668486p3670029.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: getRelativePathPrefixToWicketHandler String index out of range
I know people in the mailing lists said that the combination mod_rewrite + Wicket works for them. Maybe you forgot some mod_rewrite setting, or you added one that breaks the things... Without a quickstart/tutorial I'm unable to help you. On Fri, Jul 15, 2011 at 5:09 PM, nojyarg jonathan.g...@f-i.com wrote: you asked what is forwardUrl - it is the httprequest attribute javax.servlet.forward.servlet_path forwardUrl is just the variable name that this attribute is assigned to in the ServletWebRequest.getRelativePathPrefixToWicketHandler method. i will try to get 1.5 going. it seems strange to me, however, that mod_rewrite and wicket requestdispatcher + servletwebrequest don't play nice together seeing as how both mod_rewrite Wicket are popular somewhat mature apache technologies. re: tutorial. well, it's probably going to take too much back and forth to make it worth either of our time to do this. thanks. - j -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/getRelativePathPrefixToWicketHandler-String-index-out-of-range-tp3668486p3670029.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: IHeaderContributor of invisible Components
Thank you for your good explanation. I will have to reflect about your explanation first. May be I'll come back :-) Am 15.07.2011 11:12, schrieb Martin Grigorov: Wicket calls renderHead() for each component added in the AjaxRequestTarget. Then for each call of IHeaderResponse.renderXYZ() Wicket checks whether this is static resource and whether it is already rendered. If it is not then it renders it. If it is non-static (e.g. renderOnDomReady or renderOnLoad) then it is contributed every time the component is re-rendered. Better create a quickstart and attach it to Jira. On Fri, Jul 15, 2011 at 11:39 AM, Benedikt Rothebenedikt.ro...@qleo.de wrote: Check Ajax Debug panel for errors. I did check the Ajax-Debug-Panel. No error. Situation: A Component has JavaScript-header-Contributors but is invisible. Visibility is switched during an AjaxRequest. What is Wicket's *supposed* to do? a) JavaScript-header-Contributor shall be mentioned in the Page although the Component is Wicket-Invisible b) JavaScript-header-Contributor shall be mentioned in header-contribution-Section of the wicket-ajax-response c) Wicket doesn't want to deal with a situation like this. Am 15.07.2011 09:46, schrieb Martin Grigorov: Check Ajax Debug panel for errors. On Fri, Jul 15, 2011 at 10:35 AM, Benedikt Rothebenedikt.ro...@qleo.de wrote: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? It is not added to the page. There's no script-tag. Am 14.07.2011 14:15, schrieb Rodrigo Heffner: When you say my javascript is not loaded, do you mean it's not added to the page or it's added but doesn't work? On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de wrote: I have a problem with IHeaderContributor and invisible Components: A Panel MyPanel implements IHeaderContributor. The renderHead-Methods adds some JavaScript-References. When the page is rendered this panel is invisible. So these JavaScript-References are not loaded when the page is loaded. Later visibility is switched within an Ajax-Call and the MyPanel will be rendered. But than my JavaScript is not loaded. Strange: During the Ajax-Call the renderHead-Method of MyPanel is even called, but the call doesn't provoke anything concerning the output to the browser. Any suggestions? Benedikt - 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: IHeaderContributor of invisible Components
I made some further investigations. I do think there is a bug in wicket
1.4.14.
My Ajax-Request add's *two* targets which shall be rerenderd:
class MyLink extends AjaxLinkVoid {
...
public void onClick(AjaxRequestTarget target) {
... do Something and change visibilities ...
target.addComponent(component1);
target.addComponent(component2);
}
}
If the JavaScript-Reference belongs to component2 the Reference will
not be rendered.
If I switch the order of the two targetAddComponet-Statements the
Reference will be rendered.
Code-Analysis: The Ajax-Requests uses one HeaderResponse-Instance.
For each of the components the Method
AjaxRequestTarget#onComponentTagBody will
be called. After the first call onComponentTagBody will close() the
HeaderResponse-Instance.
Therefore the HeaderResponse-Instance rejects further Header-Contributions.
Benedikt Rothe
Am 15.07.2011 16:50, schrieb Benedikt Rothe:
Thank you for your good explanation.
I will have to reflect about your explanation first. May be I'll come
back :-)
Am 15.07.2011 11:12, schrieb Martin Grigorov:
Wicket calls renderHead() for each component added in the
AjaxRequestTarget.
Then for each call of IHeaderResponse.renderXYZ() Wicket checks
whether this is static resource and whether it is already rendered. If
it is not then it renders it. If it is non-static (e.g.
renderOnDomReady or renderOnLoad) then it is contributed every time
the component is re-rendered.
Better create a quickstart and attach it to Jira.
On Fri, Jul 15, 2011 at 11:39 AM, Benedikt
Rothebenedikt.ro...@qleo.de wrote:
Check Ajax Debug panel for errors.
I did check the Ajax-Debug-Panel. No error.
Situation:
A Component has JavaScript-header-Contributors but is invisible.
Visibility is switched during an AjaxRequest.
What is Wicket's *supposed* to do?
a) JavaScript-header-Contributor shall be mentioned in the Page
although the
Component is Wicket-Invisible
b) JavaScript-header-Contributor shall be mentioned in
header-contribution-Section of the wicket-ajax-response
c) Wicket doesn't want to deal with a situation like this.
Am 15.07.2011 09:46, schrieb Martin Grigorov:
Check Ajax Debug panel for errors.
On Fri, Jul 15, 2011 at 10:35 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
It is not added to the page.
There's no script-tag.
Am 14.07.2011 14:15, schrieb Rodrigo Heffner:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
On 14 Jul 2011 12:21, Benedikt
Rothebenedikt.ro...@qleo.de wrote:
I have a problem with IHeaderContributor and invisible Components:
A Panel MyPanel implements IHeaderContributor.
The renderHead-Methods adds some JavaScript-References.
When the page is rendered this panel is invisible.
So these JavaScript-References are not loaded when the page is
loaded.
Later visibility is switched within an Ajax-Call and the MyPanel
will
be
rendered.
But than my JavaScript is not loaded.
Strange: During the Ajax-Call the renderHead-Method of MyPanel
is even
called, but
the call doesn't provoke anything concerning the output to the
browser.
Any suggestions?
Benedikt
-
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: IHeaderContributor of invisible Components
There is no AjaxRequestTarget#onComponentTagBody()
The bug with #close() has been fixed in later version of Wicket.
On Fri, Jul 15, 2011 at 6:25 PM, Benedikt Rothe benedikt.ro...@qleo.de wrote:
I made some further investigations. I do think there is a bug in wicket
1.4.14.
My Ajax-Request add's *two* targets which shall be rerenderd:
class MyLink extends AjaxLinkVoid {
...
public void onClick(AjaxRequestTarget target) {
... do Something and change visibilities ...
target.addComponent(component1);
target.addComponent(component2);
}
}
If the JavaScript-Reference belongs to component2 the Reference will not be
rendered.
If I switch the order of the two targetAddComponet-Statements the Reference
will be rendered.
Code-Analysis: The Ajax-Requests uses one HeaderResponse-Instance.
For each of the components the Method AjaxRequestTarget#onComponentTagBody
will
be called. After the first call onComponentTagBody will close() the
HeaderResponse-Instance.
Therefore the HeaderResponse-Instance rejects further Header-Contributions.
Benedikt Rothe
Am 15.07.2011 16:50, schrieb Benedikt Rothe:
Thank you for your good explanation.
I will have to reflect about your explanation first. May be I'll come back
:-)
Am 15.07.2011 11:12, schrieb Martin Grigorov:
Wicket calls renderHead() for each component added in the
AjaxRequestTarget.
Then for each call of IHeaderResponse.renderXYZ() Wicket checks
whether this is static resource and whether it is already rendered. If
it is not then it renders it. If it is non-static (e.g.
renderOnDomReady or renderOnLoad) then it is contributed every time
the component is re-rendered.
Better create a quickstart and attach it to Jira.
On Fri, Jul 15, 2011 at 11:39 AM, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
Check Ajax Debug panel for errors.
I did check the Ajax-Debug-Panel. No error.
Situation:
A Component has JavaScript-header-Contributors but is invisible.
Visibility is switched during an AjaxRequest.
What is Wicket's *supposed* to do?
a) JavaScript-header-Contributor shall be mentioned in the Page although
the
Component is Wicket-Invisible
b) JavaScript-header-Contributor shall be mentioned in
header-contribution-Section of the wicket-ajax-response
c) Wicket doesn't want to deal with a situation like this.
Am 15.07.2011 09:46, schrieb Martin Grigorov:
Check Ajax Debug panel for errors.
On Fri, Jul 15, 2011 at 10:35 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
It is not added to the page.
There's no script-tag.
Am 14.07.2011 14:15, schrieb Rodrigo Heffner:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
I have a problem with IHeaderContributor and invisible Components:
A Panel MyPanel implements IHeaderContributor.
The renderHead-Methods adds some JavaScript-References.
When the page is rendered this panel is invisible.
So these JavaScript-References are not loaded when the page is
loaded.
Later visibility is switched within an Ajax-Call and the MyPanel
will
be
rendered.
But than my JavaScript is not loaded.
Strange: During the Ajax-Call the renderHead-Method of MyPanel is
even
called, but
the call doesn't provoke anything concerning the output to the
browser.
Any suggestions?
Benedikt
-
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
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: IHeaderContributor of invisible Components
There is no AjaxRequestTarget#onComponentTagBody()
Sorry: AjaxRequestTarget#respondHeaderContribution closes the
HeaderResponse.
I'll try to switch to wicket 1.4.17.
Benedikt
Am 15.07.2011 17:32, schrieb Martin Grigorov:
There is no AjaxRequestTarget#onComponentTagBody()
The bug with #close() has been fixed in later version of Wicket.
On Fri, Jul 15, 2011 at 6:25 PM, Benedikt Rothebenedikt.ro...@qleo.de wrote:
I made some further investigations. I do think there is a bug in wicket
1.4.14.
My Ajax-Request add's *two* targets which shall be rerenderd:
class MyLink extends AjaxLinkVoid {
...
public void onClick(AjaxRequestTarget target) {
... do Something and change visibilities ...
target.addComponent(component1);
target.addComponent(component2);
}
}
If the JavaScript-Reference belongs to component2 the Reference will not be
rendered.
If I switch the order of the two targetAddComponet-Statements the Reference
will be rendered.
Code-Analysis: The Ajax-Requests uses one HeaderResponse-Instance.
For each of the components the Method AjaxRequestTarget#onComponentTagBody
will
be called. After the first call onComponentTagBody will close() the
HeaderResponse-Instance.
Therefore the HeaderResponse-Instance rejects further Header-Contributions.
Benedikt Rothe
Am 15.07.2011 16:50, schrieb Benedikt Rothe:
Thank you for your good explanation.
I will have to reflect about your explanation first. May be I'll come back
:-)
Am 15.07.2011 11:12, schrieb Martin Grigorov:
Wicket calls renderHead() for each component added in the
AjaxRequestTarget.
Then for each call of IHeaderResponse.renderXYZ() Wicket checks
whether this is static resource and whether it is already rendered. If
it is not then it renders it. If it is non-static (e.g.
renderOnDomReady or renderOnLoad) then it is contributed every time
the component is re-rendered.
Better create a quickstart and attach it to Jira.
On Fri, Jul 15, 2011 at 11:39 AM, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
Check Ajax Debug panel for errors.
I did check the Ajax-Debug-Panel. No error.
Situation:
A Component has JavaScript-header-Contributors but is invisible.
Visibility is switched during an AjaxRequest.
What is Wicket's *supposed* to do?
a) JavaScript-header-Contributor shall be mentioned in the Page although
the
Component is Wicket-Invisible
b) JavaScript-header-Contributor shall be mentioned in
header-contribution-Section of the wicket-ajax-response
c) Wicket doesn't want to deal with a situation like this.
Am 15.07.2011 09:46, schrieb Martin Grigorov:
Check Ajax Debug panel for errors.
On Fri, Jul 15, 2011 at 10:35 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
It is not added to the page.
There's no script-tag.
Am 14.07.2011 14:15, schrieb Rodrigo Heffner:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
I have a problem with IHeaderContributor and invisible Components:
A Panel MyPanel implements IHeaderContributor.
The renderHead-Methods adds some JavaScript-References.
When the page is rendered this panel is invisible.
So these JavaScript-References are not loaded when the page is
loaded.
Later visibility is switched within an Ajax-Call and the MyPanel
will
be
rendered.
But than my JavaScript is not loaded.
Strange: During the Ajax-Call the renderHead-Method of MyPanel is
even
called, but
the call doesn't provoke anything concerning the output to the
browser.
Any suggestions?
Benedikt
-
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: IHeaderContributor of invisible Components
The bug with #close() has been fixed in later version of Wicket.
wicket4.1.17 still has the bug.
Am 15.07.2011 17:32, schrieb Martin Grigorov:
There is no AjaxRequestTarget#onComponentTagBody()
The bug with #close() has been fixed in later version of Wicket.
On Fri, Jul 15, 2011 at 6:25 PM, Benedikt Rothebenedikt.ro...@qleo.de wrote:
I made some further investigations. I do think there is a bug in wicket
1.4.14.
My Ajax-Request add's *two* targets which shall be rerenderd:
class MyLink extends AjaxLinkVoid {
...
public void onClick(AjaxRequestTarget target) {
... do Something and change visibilities ...
target.addComponent(component1);
target.addComponent(component2);
}
}
If the JavaScript-Reference belongs to component2 the Reference will not be
rendered.
If I switch the order of the two targetAddComponet-Statements the Reference
will be rendered.
Code-Analysis: The Ajax-Requests uses one HeaderResponse-Instance.
For each of the components the Method AjaxRequestTarget#onComponentTagBody
will
be called. After the first call onComponentTagBody will close() the
HeaderResponse-Instance.
Therefore the HeaderResponse-Instance rejects further Header-Contributions.
Benedikt Rothe
Am 15.07.2011 16:50, schrieb Benedikt Rothe:
Thank you for your good explanation.
I will have to reflect about your explanation first. May be I'll come back
:-)
Am 15.07.2011 11:12, schrieb Martin Grigorov:
Wicket calls renderHead() for each component added in the
AjaxRequestTarget.
Then for each call of IHeaderResponse.renderXYZ() Wicket checks
whether this is static resource and whether it is already rendered. If
it is not then it renders it. If it is non-static (e.g.
renderOnDomReady or renderOnLoad) then it is contributed every time
the component is re-rendered.
Better create a quickstart and attach it to Jira.
On Fri, Jul 15, 2011 at 11:39 AM, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
Check Ajax Debug panel for errors.
I did check the Ajax-Debug-Panel. No error.
Situation:
A Component has JavaScript-header-Contributors but is invisible.
Visibility is switched during an AjaxRequest.
What is Wicket's *supposed* to do?
a) JavaScript-header-Contributor shall be mentioned in the Page although
the
Component is Wicket-Invisible
b) JavaScript-header-Contributor shall be mentioned in
header-contribution-Section of the wicket-ajax-response
c) Wicket doesn't want to deal with a situation like this.
Am 15.07.2011 09:46, schrieb Martin Grigorov:
Check Ajax Debug panel for errors.
On Fri, Jul 15, 2011 at 10:35 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
It is not added to the page.
There's no script-tag.
Am 14.07.2011 14:15, schrieb Rodrigo Heffner:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
I have a problem with IHeaderContributor and invisible Components:
A Panel MyPanel implements IHeaderContributor.
The renderHead-Methods adds some JavaScript-References.
When the page is rendered this panel is invisible.
So these JavaScript-References are not loaded when the page is
loaded.
Later visibility is switched within an Ajax-Call and the MyPanel
will
be
rendered.
But than my JavaScript is not loaded.
Strange: During the Ajax-Call the renderHead-Method of MyPanel is
even
called, but
the call doesn't provoke anything concerning the output to the
browser.
Any suggestions?
Benedikt
-
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
How to combine two wicket maven archetypes
I am having a maven project for wicket hibernate integration and wicket jasper-reports integration now i want to combine it to have both features in my application can anyone tell how to do that or any other better solution like create applications without combining the maven projects -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/How-to-combine-two-wicket-maven-archetypes-tp3670354p3670354.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: IHeaderContributor of invisible Components
ticket + quickstart
On Fri, Jul 15, 2011 at 7:05 PM, Benedikt Rothe benedikt.ro...@qleo.de wrote:
The bug with #close() has been fixed in later version of Wicket.
wicket4.1.17 still has the bug.
Am 15.07.2011 17:32, schrieb Martin Grigorov:
There is no AjaxRequestTarget#onComponentTagBody()
The bug with #close() has been fixed in later version of Wicket.
On Fri, Jul 15, 2011 at 6:25 PM, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
I made some further investigations. I do think there is a bug in wicket
1.4.14.
My Ajax-Request add's *two* targets which shall be rerenderd:
class MyLink extends AjaxLinkVoid {
...
public void onClick(AjaxRequestTarget target) {
... do Something and change visibilities ...
target.addComponent(component1);
target.addComponent(component2);
}
}
If the JavaScript-Reference belongs to component2 the Reference will not
be
rendered.
If I switch the order of the two targetAddComponet-Statements the
Reference
will be rendered.
Code-Analysis: The Ajax-Requests uses one HeaderResponse-Instance.
For each of the components the Method
AjaxRequestTarget#onComponentTagBody
will
be called. After the first call onComponentTagBody will close() the
HeaderResponse-Instance.
Therefore the HeaderResponse-Instance rejects further
Header-Contributions.
Benedikt Rothe
Am 15.07.2011 16:50, schrieb Benedikt Rothe:
Thank you for your good explanation.
I will have to reflect about your explanation first. May be I'll come
back
:-)
Am 15.07.2011 11:12, schrieb Martin Grigorov:
Wicket calls renderHead() for each component added in the
AjaxRequestTarget.
Then for each call of IHeaderResponse.renderXYZ() Wicket checks
whether this is static resource and whether it is already rendered. If
it is not then it renders it. If it is non-static (e.g.
renderOnDomReady or renderOnLoad) then it is contributed every time
the component is re-rendered.
Better create a quickstart and attach it to Jira.
On Fri, Jul 15, 2011 at 11:39 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
Check Ajax Debug panel for errors.
I did check the Ajax-Debug-Panel. No error.
Situation:
A Component has JavaScript-header-Contributors but is invisible.
Visibility is switched during an AjaxRequest.
What is Wicket's *supposed* to do?
a) JavaScript-header-Contributor shall be mentioned in the Page
although
the
Component is Wicket-Invisible
b) JavaScript-header-Contributor shall be mentioned in
header-contribution-Section of the wicket-ajax-response
c) Wicket doesn't want to deal with a situation like this.
Am 15.07.2011 09:46, schrieb Martin Grigorov:
Check Ajax Debug panel for errors.
On Fri, Jul 15, 2011 at 10:35 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
It is not added to the page.
There's no script-tag.
Am 14.07.2011 14:15, schrieb Rodrigo Heffner:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
I have a problem with IHeaderContributor and invisible Components:
A Panel MyPanel implements IHeaderContributor.
The renderHead-Methods adds some JavaScript-References.
When the page is rendered this panel is invisible.
So these JavaScript-References are not loaded when the page is
loaded.
Later visibility is switched within an Ajax-Call and the MyPanel
will
be
rendered.
But than my JavaScript is not loaded.
Strange: During the Ajax-Call the renderHead-Method of MyPanel is
even
called, but
the call doesn't provoke anything concerning the output to the
browser.
Any suggestions?
Benedikt
-
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
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail:
Controlling head element order with renderHead(IHeaderResponse)
I am adding script and css references on the fly using renderHead(IHeaderResponse). However this adds the head elements after the Wicket scripts and that interferes with how my scripts and css work. When I hardcode my elements before the Wicket elements everything works as we need. How can I add my head elements on the fly so they are located before the Wicket elements? Thanks, Scott - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Controlling head element order with renderHead(IHeaderResponse)
You'll need to setup custom response decorator. See http://www.wicket-library.com/wicket-examples/resourceaggregation On Fri, Jul 15, 2011 at 9:01 PM, Scott Reed sr...@avacoda.com wrote: I am adding script and css references on the fly using renderHead(IHeaderResponse). However this adds the head elements after the Wicket scripts and that interferes with how my scripts and css work. When I hardcode my elements before the Wicket elements everything works as we need. How can I add my head elements on the fly so they are located before the Wicket elements? Thanks, Scott - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Controlling head element order with renderHead(IHeaderResponse)
Thanks, Martin. That example is about the Wicket header. Will that also work somehow for the HTML head? If so, how? Scott On 7/15/2011 2:07 PM, Martin Grigorov wrote: You'll need to setup custom response decorator. See http://www.wicket-library.com/wicket-examples/resourceaggregation On Fri, Jul 15, 2011 at 9:01 PM, Scott Reedsr...@avacoda.com wrote: I am adding script and css references on the fly using renderHead(IHeaderResponse). However this adds the head elements after the Wicket scripts and that interferes with how my scripts and css work. When I hardcode my elements before the Wicket elements everything works as we need. How can I add my head elements on the fly so they are located before the Wicket elements? Thanks, Scott - 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: Controlling head element order with renderHead(IHeaderResponse)
Looking at that code some more I realize I have no idea what it's doing and I'm finding the javadocs and comments pretty opaque. Is there anything you can refer me to that will give me the background to understand this? I have both Wicket in Action and the Cookbook. On 7/15/2011 2:07 PM, Martin Grigorov wrote: You'll need to setup custom response decorator. See http://www.wicket-library.com/wicket-examples/resourceaggregation On Fri, Jul 15, 2011 at 9:01 PM, Scott Reedsr...@avacoda.com wrote: I am adding script and css references on the fly using renderHead(IHeaderResponse). However this adds the head elements after the Wicket scripts and that interferes with how my scripts and css work. When I hardcode my elements before the Wicket elements everything works as we need. How can I add my head elements on the fly so they are located before the Wicket elements? Thanks, Scott - 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: IHeaderContributor of invisible Components
Martin,
I stated, that the bug with close() still occurs in Wicket 1.4.17.
I had a closer look. This was a mistake.
The bug is in Wicket 1.4.14 but *not* in Wicket 1.4.17.
Thanks and sorry
Benedikt
Am 15.07.2011 18:41, schrieb Martin Grigorov:
ticket + quickstart
On Fri, Jul 15, 2011 at 7:05 PM, Benedikt Rothebenedikt.ro...@qleo.de wrote:
The bug with #close() has been fixed in later version of Wicket.
wicket4.1.17 still has the bug.
Am 15.07.2011 17:32, schrieb Martin Grigorov:
There is no AjaxRequestTarget#onComponentTagBody()
The bug with #close() has been fixed in later version of Wicket.
On Fri, Jul 15, 2011 at 6:25 PM, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
I made some further investigations. I do think there is a bug in wicket
1.4.14.
My Ajax-Request add's *two* targets which shall be rerenderd:
class MyLink extends AjaxLinkVoid{
...
public void onClick(AjaxRequestTarget target) {
... do Something and change visibilities ...
target.addComponent(component1);
target.addComponent(component2);
}
}
If the JavaScript-Reference belongs to component2 the Reference will not
be
rendered.
If I switch the order of the two targetAddComponet-Statements the
Reference
will be rendered.
Code-Analysis: The Ajax-Requests uses one HeaderResponse-Instance.
For each of the components the Method
AjaxRequestTarget#onComponentTagBody
will
be called. After the first call onComponentTagBody will close() the
HeaderResponse-Instance.
Therefore the HeaderResponse-Instance rejects further
Header-Contributions.
Benedikt Rothe
Am 15.07.2011 16:50, schrieb Benedikt Rothe:
Thank you for your good explanation.
I will have to reflect about your explanation first. May be I'll come
back
:-)
Am 15.07.2011 11:12, schrieb Martin Grigorov:
Wicket calls renderHead() for each component added in the
AjaxRequestTarget.
Then for each call of IHeaderResponse.renderXYZ() Wicket checks
whether this is static resource and whether it is already rendered. If
it is not then it renders it. If it is non-static (e.g.
renderOnDomReady or renderOnLoad) then it is contributed every time
the component is re-rendered.
Better create a quickstart and attach it to Jira.
On Fri, Jul 15, 2011 at 11:39 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
Check Ajax Debug panel for errors.
I did check the Ajax-Debug-Panel. No error.
Situation:
A Component has JavaScript-header-Contributors but is invisible.
Visibility is switched during an AjaxRequest.
What is Wicket's *supposed* to do?
a) JavaScript-header-Contributor shall be mentioned in the Page
although
the
Component is Wicket-Invisible
b) JavaScript-header-Contributor shall be mentioned in
header-contribution-Section of the wicket-ajax-response
c) Wicket doesn't want to deal with a situation like this.
Am 15.07.2011 09:46, schrieb Martin Grigorov:
Check Ajax Debug panel for errors.
On Fri, Jul 15, 2011 at 10:35 AM, Benedikt
Rothebenedikt.ro...@qleo.de
wrote:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
It is not added to the page.
There's no script-tag.
Am 14.07.2011 14:15, schrieb Rodrigo Heffner:
When you say my javascript is not loaded, do you mean it's not
added
to
the page or it's added but doesn't work?
On 14 Jul 2011 12:21, Benedikt Rothebenedikt.ro...@qleo.de
wrote:
I have a problem with IHeaderContributor and invisible Components:
A Panel MyPanel implements IHeaderContributor.
The renderHead-Methods adds some JavaScript-References.
When the page is rendered this panel is invisible.
So these JavaScript-References are not loaded when the page is
loaded.
Later visibility is switched within an Ajax-Call and the MyPanel
will
be
rendered.
But than my JavaScript is not loaded.
Strange: During the Ajax-Call the renderHead-Method of MyPanel is
even
called, but
the call doesn't provoke anything concerning the output to the
browser.
Any suggestions?
Benedikt
-
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
