Hi guys,
Can someone of the committers please implement the fix to Wicket-2150 in
the trunk. It was postponed from 1.4 to 1.5 and I really need this, but
it is not yet in the 1.5 codebase (as far as I can see). The code that
needs to be changed is the delegateSubmit-method in the Form and it
How the fix in 1.5-SNAPSHOT will help you ?
Currently 1.5-SNAPSHOT is not even buildable (at least the tests), so it
is not quite ready for use.
On Fri, 2010-01-15 at 09:07 +0100, Dave Schoorl wrote:
Hi guys,
Can someone of the committers please implement the fix to Wicket-2150 in
the
I don't know about the tests, but in the snapshot repository there are
1.5-SNAPSHOT binaries. My application is not yet in production, so I
(think I) can manage the rough edges of working with a development
release. On top of that, I want to make sure it is in 1.5.
What would be a reason not
Sorry ,a little late ..
push is a great project,thanks for your efforts.
i am a little confused,
1)does the time out only happens after a remove event is published or apart
from this, there is another
timeout which happens when server is finished pushing into the client?
2)i see some problems
Sorry for jumping into this issue again, but I am still a bit confused. I
need a definitive answer for this as I have to document it in my diploma
thesis.
In my app I have a requirement that a new page has to be opened in a popup
window, which is pretty easy with wicket using the popupsettings
Nino,
When I add the link to a Panel (see below) and run the application, I get an
erro:
org.apache.wicket.markup.MarkupNotFoundException: Markup of type 'html' for
component 'org.apache.wicket.markup.html.panel.Panel' not found. Enable
debug messages for org.apache.wicket.util.resource to get a
Johan,
The Markup is defined by the panel. Just copy the first class a sent you and
the HTML snippet
html xmlns:wicket=org.apache.
wicket
body
wicket:panel
a wicket:id=link title=Title class=button
span wicket:id=text[text goes here]/span
/a
Looks good, sure will save time of new explorers. Are you going to add
more archetypes in future (what's next)?
I saw hibernate there, maybe ibatis or cayenne would be fine, although
they are not that hard to figure out. I will try the wicket-guice myself.
Good luck,
Marek
On 01/15/2010
Hi all,
I have the following code which generates a URL to a page with some parameters:
String url = urlFor(MyMessageView.class, new PageParameters(thread= +
ad9697d2-8328-43b4-be28-ee677a88bc9a)).toString();
This generates a URL like so:
On Fri, 2010-01-15 at 22:29 +1100, Steve Swinsburg wrote:
Hi all,
I have the following code which generates a URL to a page with some
parameters:
String url = urlFor(MyMessageView.class, new PageParameters(thread=
+ ad9697d2-8328-43b4-be28-ee677a88bc9a)).toString();
This generates a
This is great !
2010/1/15 Cemal Bayramoglu jweekend_for...@cabouge.com
Marek, Jeremy,
Thanks.
Yes, we do plan to gradually add more configurations. We have already
had offers to contribute Wicket/Scala templates and a few others we
will consider. Wicket/WiQuery will be popular too, once
Hi all,
i have a litte problem.
I have implemented an own AuthorizationStrategy where I check I a user
is allowed to render/enable a component/page.
Each page has a navigation. If I restrict enable for a page, then the
navigation gets also disabled.
I tried overwriting isEnabled() for the whole
Why you're disabling whole page in first place?
2010/1/15 Giambalvo, Christian christian.giamba...@excelsisnet.com:
Hi all,
i have a litte problem.
I have implemented an own AuthorizationStrategy where I check I a user
is allowed to render/enable a component/page.
Each page has a
Well, i have implemented a different authorization model and don't use the
annotation based.
All restrictions are written in one onfig file to have them all in place.
I there is a viewonly user I don't want to disable each panel/textfield ... one
by one, so that’s why I disable the whole page.
Hi everyone,
I would like to know if someone can share their experience with
graphical templates under wicket. It's easy to provide markup code for
designers, they just need to preserve hierarchy of wicket elements,
right? But how do you cope with things like attribute modifier inside
so you are giving designers markup from a wicket app? why not just let
them run the app, that way they can go in and do things themselves?
in my company out developers checkout the code and run mvn jetty to
get the app up and running with markup reloading, then they go in with
textmate or coda
That's what we are doing as well.
The big gotcha is when you end up doing something in code, it throws them off.
I.E. SimpleAttributeModifier,
D/
On Jan 15, 2010, at 10:14 AM, Jonathan Locke wrote:
we did almost exactly the same thing at thoof. although occasionally you'll
get a
thats what html comments are for.
-igor
On Fri, Jan 15, 2010 at 9:55 AM, Douglas Ferguson
doug...@douglasferguson.us wrote:
That's what we are doing as well.
The big gotcha is when you end up doing something in code, it throws them off.
I.E. SimpleAttributeModifier,
D/
On Jan 15, 2010,
Yep, thank you all for sharing your insights, anyway, most of the time I
work with single ui projects. I was just curious how you guys do it so I
would have PreparedStatement for pointy haired bosses :)
On 01/15/2010 06:55 PM, Douglas Ferguson wrote:
That's what we are doing as well.
The big
looks like a bug. open a ticket in jira. attach a quickstart if you can.
-igor
On Fri, Jan 15, 2010 at 10:29 AM, Tony Wu e90t...@gmail.com wrote:
Not sure if this is a bug or something I overlooked, but I get a strange cast
exception (org.apache.wicket.markup.RawMarkup cannot be cast to
A while back I added basic WicketTester rendering tests for each of my
pages. They have been great for discovering problems, but not so great for
telling me what those problems are. My tests are of the most basic kind:
tester.startPage(MyPage.*class*);
the exception is spit out into the log
-igor
On Fri, Jan 15, 2010 at 2:17 PM, Dane Laverty danelave...@gmail.com wrote:
A while back I added basic WicketTester rendering tests for each of my
pages. They have been great for discovering problems, but not so great for
telling me what those
Dear fellow wicketers!
I am now new to wicket and would like to say: wow + thanks for this
great framework!
I never see such a good separation of view and code. and making a small
solr+wicket example working was really fun (like in good old desktop eras).
Now I have the following questions:
Gone because creating the page(s) during the rendering of another page is a
bad idea. It should be done in the onClick handler. See the comment in the
deprecation note (of the method, not just the class).
See inline answers.
Hope this helps.
--
Jeremy Thomerson
http://www.wickettraining.com
On Fri, Jan 15, 2010 at 4:49 PM, Peter Karich peat...@yahoo.de wrote:
Dear fellow wicketers!
I am now new to wicket and would like to say: wow + thanks for this great
framework!
I never see such a
25 matches
Mail list logo
