Did something change in 1.3?
http://wicketstuff.org/wicket13/compref/?wicket:bookmarkablePage=%3Aorg.apache.wicket.examples.compref.FormPage
This simple example doesn't work for me either. I get a
1. [MarkupContainer [Component id = feedback, page =
ca.arcticpenguin.mff.NewListingPage, path =
There is no example application (that i know of) showing what you want.
Let me recap what i think you want:
You have an application (probably with a basic set of roles)
You want to add plugins (probably containing several pages each
requiring there own special permissions to do stuff)
The extra
http://www.jroller.com/wireframe/entry/wicket_client_side_validation
I've spent the past couple weeks investigating Wicket's support for
client side validation. IMO, using Ajax for validation in Wicket is
really amazing. Lots of folks are touting javascript validation
right now, but I think
I have a peculiar problem that I hope can be solved by the experts!
I have on my application pages a panel that is updated using an
AbstractAjaxTimerBehavior to update the style attribute making it
visible or not.
This works just fine on the current page. If, however, I press the
back
that looks like a database pool, where connections are in and after a while
a specific connection isn't used for a long time and oracle terminates or
makes in invalid.
configure your database pool that way that you test the connection before it
gives you the connection
johan
On Jan 26, 2008
out of curiosity, would there be any interest in shipping Wicket with
Ajax form validation turned on *by default* instead of developers
manually adding the AjaxFormValidatingBehavior? Are there any
drawbacks to having this be the default behavior?
On Jan 27, 2008 9:00 AM, Ryan Sonnek [EMAIL
-1. There are enough companies and projects that can't use or aren't allowed
to use JavaScript, which also precludes the default enabling of such
functionality.
Martijn
On 1/27/08, Ryan Sonnek [EMAIL PROTECTED] wrote:
out of curiosity, would there be any interest in shipping Wicket with
Ajax
Seriously? there are companies that mandate you can't use javascript?
Even if it's done for you and just works?
Wow...that's sad, but I hardly think that's the norm and such extremes
should not mandate system defaults.
Any other arguments against such a default? The reason I'm bringing
this
The Wicket training courses in London, with http://herebebeasties.com/ Al
Maw , are bookable using http://www.jweekend.com/dev/BookingPage/ our
simple but effective Ajax cart (built on Wicket) with payments handled by
Google Checkout.
Since Google Checkout will globally start charging vendors
also -1. it is trivial to do it yourself automatically like you said
in your blog. there are plenty of usecases that wont work out of the
box. take a common usecase where the label turns red if the field is
in error, how do you do that out of the box?
-igor
On Jan 27, 2008 8:39 AM, Ryan Sonnek
On Jan 27, 2008 11:39 AM, Martijn Dashorst [EMAIL PROTECTED] wrote:
Almost any government site/application must comply with accessibility rules
which often prohibit the use of JavaScript.
section 508 compliance does *not* prohibit javascript or Ajax. You
just have to be careful how you use
True, I guess you could create your own form superclass that does the
default behavior you want.
On 1/27/08, Igor Vaynberg [EMAIL PROTECTED] wrote:
also -1. it is trivial to do it yourself automatically like you said
in your blog. there are plenty of usecases that wont work out of the
box.
On Jan 27, 2008 12:07 PM, James Carman [EMAIL PROTECTED] wrote:
True, I guess you could create your own form superclass that does the
default behavior you want.
Yuk...I'd hate to go through my *entire* application and replace
org.apache.wicket.Form with com.mysite.MySpecialForm. very messy.
On Jan 27, 2008 12:04 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
also -1. it is trivial to do it yourself automatically like you said
in your blog. there are plenty of usecases that wont work out of the
box. take a common usecase where the label turns red if the field is
in error, how do you
So, create an IComponentInstantiationListener that looks for Forms and
adds the behavior to them.
On 1/27/08, Ryan Sonnek [EMAIL PROTECTED] wrote:
On Jan 27, 2008 12:07 PM, James Carman [EMAIL PROTECTED] wrote:
True, I guess you could create your own form superclass that does the
default
On Jan 27, 2008 12:15 PM, James Carman [EMAIL PROTECTED] wrote:
So, create an IComponentInstantiationListener that looks for Forms and
adds the behavior to them.
Yep. That's what I posted on my blog.
I'm just asking if there's any interest in making this the *default*
behavior. When people
but then my app wont work. i add my own ajax behavior that knows how
to do all this... so i would have to override some method on the form
and tell it not to do its default thing? let me quote someone
Yuk...I'd hate to go through my *entire* application and replace
org.apache.wicket.Form with
Great, that handles my security question, thanks. Now if my two users have
access to different reports, the only way to present this is through a
DropDownChoice (with each report as an item) as opposed to rows of anchor
tags?
Could you suggest an alternative display strategy?
With thanks,
-Matt
What if the Ajax stuff could be turned on globally using the web
application itself? Then, it could be customized on a per-project
basis.
public class HelloWorldApplication extends WebApplication
{
public boolean isAjaxFormValidationEnabled()
{
return true;
}
Almost any government site/application must comply with accessibility rules
which often prohibit the use of JavaScript.
And no, we're not going to fall for the Foo did it ploy :)
Martijn
On 1/27/08, Ryan Sonnek [EMAIL PROTECTED] wrote:
Seriously? there are companies that mandate you can't use
why does it work for everyone else and not you? could you paste the
entire stack trace?
-igor
On Jan 27, 2008 5:31 AM, Andy Czerwonka [EMAIL PROTECTED] wrote:
Did something change in 1.3?
I'm guessing you want an alternative to display those reports because
of the problems hiding an item?
Why not put some logic in your model and have it decide which items to
pass to your dropdownchoice, or adjust your query that fills the
model.
Maurice
On Jan 27, 2008 6:30 PM, mgiedt [EMAIL
On Jan 27, 2008 12:20 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
but then my app wont work. i add my own ajax behavior that knows how
to do all this... so i would have to override some method on the form
and tell it not to do its default thing? let me quote someone
Yuk...I'd hate to go through
On Jan 27, 2008 10:35 AM, Ryan Sonnek [EMAIL PROTECTED] wrote:
On Jan 27, 2008 12:20 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
but then my app wont work. i add my own ajax behavior that knows how
to do all this... so i would have to override some method on the form
and tell it not to do
how would specific components opt out? if i have a textarea i am going
to add tinymce behavior to, i dont want it to be validated via ajax.
i often have validators that hit the database to check for uniquness,
etc. since every time i press a key the entire form is reprocessed, it
will add quiet a
Okay everyone,
after re-reading my posts on this thread, I need to take a minute and
apologize for my previous comments. They came off very argumentative
and that's not what I intended.
I was *so* excited to share this idea and I was kind of expecting
everyone's response to be more like WOW,
Hi
Just a thought about client side validation.
I have looked at simple validation like maxlength, min length stuff like
that. The jQuery
validation plugin solves that easily.
My idea was to inherit from the corresponding wicket-validator and implement
IBehavoir.
Then I would be able to
Igor Vaynberg [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
why does it work for everyone else and not you? could you paste the
entire stack trace?
-igor
Because I'm an idiot. Sorry group - my Eclipse environment was messed up
and it wasn't building properly.
mixing validators and behaviors has been on our todo list for a while,
but we couldnt do it cleanly in 1.3 because it would mean an api
break.
we will do it for 1.4
as far as getting the name of formcomponent, that is already possible
through ibehavior.bind(component)
-igor
On Jan 27, 2008
Guess i misunderstood you the first time.
For a layout as you described here i recommend the following:
Hard code the top level menu items and either use swarm to hide the
items or use the isVisible technique i told you about.
use swarm to hide tabs (http://wicketstuff.org/wicketsecurity/tabs/)
or
Hi!
I have a design question for wicket.
In my Article page the user can filter the articles in many ways, by
category, brand, price, department, gender etc. I wan't to Use the same
wicketpage for the Article list. What is the best approach with wicket?
make New ArticlePage().setDepartment(
Yes, this is an improperly configured connection pool. In Tomcat you
would look at these settings such as the following:
timeBetweenEvictionRunsMillis
numTestsPerEvictionRun
minEvictableIdleTimeMillis
- Scott
On Jan 27, 2008 7:08 AM, Johan Compagner [EMAIL PROTECTED] wrote:
that looks like a
Depending on the component you use to display the list there are a few
differences in putting it all together but generally you should create
a bean containing all your filter options. you can then pass the bean
to your query and adjust it accordingly.
If you use a ListView or DataView you have to
Use stylesheets:
select.yourCssClass option {
background-color: pink;
color: green;
}
Frank
On Jan 26, 2008 1:47 AM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote:
Is there anyway to control the rendering of a dropdownchoice?
I don't mean implementing IChoiceRenderer but to set style
I don't quit follow what you mean since I'm a newbie. Can you please explain
in a little more detail or give me some pointers.
--
View this message in context:
http://www.nabble.com/Filter-data-with-wicket-tp15124809p15126484.html
Sent from the Wicket - User mailing list archive at Nabble.com.
You can only controll the select and not a single option using this. At least
not all browsers
--
View this message in context:
http://www.nabble.com/Controlling-render-for-DropDownChoice-tp15100129p15126445.html
Sent from the Wicket - User mailing list archive at Nabble.com.
see Select, SelectOption, SelectOptions in wicket-extensions. that
should give you complete control over the markup.
-igor
On Jan 25, 2008 4:47 PM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote:
Is there anyway to control the rendering of a dropdownchoice?
I don't mean implementing
Hello Igor Vaynberg,
I have check the code from wicket stuff's svn
(https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/ )
both the example and source of YUI TinyMCE!
but there are too many error, most is missing the jar.
How to get the correlation jar?
I have no clue at all!
suppose you have a single text keyword box:
class searchpage extends webpage {
private String keywords;
public searchpage() {
Form form=new Form(form);
form.add(new TextBox(keywords, new PropertyModel(this, keywords)));
add(new DataView(results, new MyDataProvider()) {
after you check out the source run mvn install - that will fetch the
necessary jars.
-igor
On Jan 27, 2008 5:44 PM, Mead [EMAIL PROTECTED] wrote:
Hello Igor Vaynberg,
I have check the code from wicket stuff's svn
(https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/ )
Hello Igor Vaynberg,
The YUI-example get a Exception:
org.apache.wicket.WicketRuntimeException:Application class
org.wicketstuff.yui.example.pages.YuiApplication must be a subclass of
WebApplication
Well, I have run the cmd mvn install, and everything is run ok.
Than, I copy the *.war to
Hi,
I have encountered a DragNDrop problem using wicketStuff-scriptaculous
in IE6/IE7. The DragNDrop only work for the first time, but
subsequently, the draggable object is no longer draggable. FYI, this
problem doesn't exist in Firefox and it can be reproduced in
Thanks for the info Igor.
On Jan 27, 2008 9:33 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
mixing validators and behaviors has been on our todo list for a while,
but we couldnt do it cleanly in 1.3 because it would mean an api
break.
we will do it for 1.4
as far as getting the name of
That doesn't work.
Sometimes you want to add multiple behaviors to the same event. Wicket
doesn't support that.
Erik.
James Carman wrote:
So, create an IComponentInstantiationListener that looks for Forms and
adds the behavior to them.
44 matches
Mail list logo
