I compiled my own wicket.jar from the 1.2.x branch on 1/25/07 which
greatly reduced the frequency of the problem in my code that added css
to the header from java however I am still seeing javascript files
being left out on occasion (wicket-ajax.js). A few refreshes later and
the javascript will
any help for tracking it down will certainly help us fix it :)
-igor
On 2/1/07, Ryan [EMAIL PROTECTED] wrote:
I compiled my own wicket.jar from the 1.2.x branch on 1/25/07 which
greatly reduced the frequency of the problem in my code that added css
to the header from java however I am still
I got the same problem with 1.2.4
2006/11/11, Matej Knopp [EMAIL PROTECTED]:
That's weird. Which wicket version are you using? Seems that Wicket 1.x
has already become 1.3 and the latest revision is 473519.
Wicket 1.2 has it's own branch now.
Are you sure you're using the apache repository?
its fixed and will be included in the upcoming 1.2.5
-igor
On 1/31/07, smallufo [EMAIL PROTECTED] wrote:
I got the same problem with 1.2.4
2006/11/11, Matej Knopp [EMAIL PROTECTED]:
That's weird. Which wicket version are you using? Seems that Wicket 1.x
has already become 1.3 and the
Its not just pages, i have a panel that adds some javascript to the
header which suffers from this problem.
Matej, ill see if i can put something together.
Maurice
On 11/13/06, Matej Knopp [EMAIL PROTECTED] wrote:
I've tested this with current 1.3 and couldn't reproduce this. Can you
please
Ok
I just finished a simple quickstart showing the problem.
you can get it here https://issues.apache.org/jira/browse/WICKET-68.
Maurice
On 11/14/06, Maurice Marrink [EMAIL PROTECTED] wrote:
Its not just pages, i have a panel that adds some javascript to the
header which suffers from this
I am using wicket:1.3-incubating-20061113.111007-1 and also have this
problem with javascript not being rendered the second time.
I render a new page and all is rendered fine. i click on a link to
open a new page. there i click on a link that brings me back to the
previous page instance. The
My current workaround is to include the reference in the markup with
wicket:head tags around it.
I am sorry I did not yet have the time to create a quickstart/unit test
with the problem.
Erik.
Maurice Marrink schreef:
I am using wicket:1.3-incubating-20061113.111007-1 and also have
Unfortunately this is not an option for me as the javascript is
generated dynamically by the java code.
Maurice
On 11/13/06, Erik van Oosten [EMAIL PROTECTED] wrote:
My current workaround is to include the reference in the markup with
wicket:head tags around it.
I am sorry I did not yet have
I'm also experiencing this. I believe it only occurs for a Page
object. All of my components that add css don't pose this problem at
all. Here is the constructor of my page class:
public UserProfilePage() {
add(HeaderContributor.forCss(UserProfilePanel.class,
I've tested this with current 1.3 and couldn't reproduce this. Can you
please provide a quick-start project? I'd be more than happy to look
into it.
-Matej
Maurice Marrink wrote:
I am using wicket:1.3-incubating-20061113.111007-1 and also have this
problem with javascript not being rendered
Hello,
Something is going wrong with my header contributions. A css that was
added like this
add(HeaderContributor.forCss(MyPage.class, MyPage.css));
are only rendered once and then never again.
To be precise:
- I start jetty.
- I request the page (it is bookmarkable).
- I get redirected to
add a bug into jira preferrably with a quickstart-igorOn 11/10/06, Erik van Oosten [EMAIL PROTECTED]
wrote:Hello,Something is going wrong with my header contributions. A css that was
added like thisadd(HeaderContributor.forCss(MyPage.class, MyPage.css));are only rendered once and then never
On 11/10/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
add a bug into jira preferrably with a quickstart
Or maybe even better a unit test that proves this and that we can put in wicket.
Eelco
-
Using Tomcat but need to do
Ok, I'll try to extract the problem.
Erik.
Eelco Hillenius schreef:
On 11/10/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
add a bug into jira preferrably with a quickstart
Or maybe even better a unit test that proves this and that we can put in
wicket.
Eelco
--
Erik
15 matches
Mail list logo
