Hi Martin
Theres still some trouble with sourceforge svn. But it should be
somewhat okay, you just cant count on what youve just comitted will be
compiled within the normal 60s timeframe, but this has been the case all
the time..
Martin Grigorov wrote:
I've updated and build locally all
Ahh yeah, me and my memory..
I thought that this were related, but it's not as it's jasperreports:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-jasperreports
But thanks for posting.
jwray wrote:
I looked around wicket stuff and didn't see anything
Hello S D,
This might interest you:
http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html
Note there are still some limitations. Your milage may vary.
Regards,
Erik.
S D wrote:
Hi,
I was browsing through examples, it looks very impressive but there's a thing
while this might work for your usecase this will pretty much break
things. the version number is in the url for a reason.
1) it completely kills the backbutton for that page. since the url
remains the same the browser wont record your actions in the history.
based on what you are trying to do
Hi,
Francisco and I here where discussing whether we could figure a way of
having some form of static/compile time checking on our
(Compound)PropertyModels, as I'm a bit concerned long term about some nasty
runtime bugs that might slip through the testing coverage. Francisco found
this thread -
Thanks for clarifying limitation no 2, I had not though of this. Indeed
in my usecase this is not a problem.
'Limitation' no 1 is quite intentional.
If you don't mind, I've also added this comment to the article.
Regards,
Erik.
Igor Vaynberg wrote:
while this might work for your usecase
I cannot comment on the stabiliy, but for the javadoc you'll need to
download the source and generate the javadoc (use maven for the quickest) as
I don;t beleive its online anywhere
On Tue, Oct 28, 2008 at 5:53 PM, miro [EMAIL PROTECTED] wrote:
I am new to wicket and no guru to help me answer
Hi,
Thanks for help but the problem with your solution is that it doesnt work in
IE (when I have multiple columns with such links only links in first column
'fills' entire cells) in Firefox that works.
Jeremy Thomerson-5 wrote:
If that's your problem, I'd suggest using CSS, something like:
Hi Igor,
igor.vaynberg wrote:
yes it sucks. i agree. personally i prefer code written against wicket
1.3. even in 1.3 i hardly had to cast anything and even with those
casts i do not remember getting any class cast exceptions.
It is nice to know that somebody thinks similar to me :)
Because I havent found better solution then adding 'onclick' handler to
cellItem I have to do it your way.
I looked at urlFor methods in Component class and didnt found the one with
Component attribute.
How should I generate url for Link component, AjaxLink or AjaxFallbackLink ?
Do I have to add
Hi Igor,
yes it sucks. i agree. personally i prefer code written against wicket
1.3. even in 1.3 i hardly had to cast anything and even with those
casts i do not remember getting any class cast exceptions.
hehe - just as I was saying months ago. *g*
anyways, we will see how it goes. until
Hi.
I have application which consists of questions to user provided in
some order. Each question is reachable on the same address, let's say
http://myApp/Question. Application engine knows which question to show
from database record. Each question page has 'Previous Question' and
'Next Question'
Yeah, I must say im looking forward to getting Wicket-1327 a reality too..
Wayne Pope wrote:
Hi,
Francisco and I here where discussing whether we could figure a way of
having some form of static/compile time checking on our
(Compound)PropertyModels, as I'm a bit concerned long term about some
You could download it from Maven repos as any other artefact:
http://repo1.maven.org/maven2/org/apache/wicket/wicket/1.4-m3/wicket-1.4-m3-javadoc.jar
Since 1.4 is actually 1.3 + generics (and very few other changes) you
could start with 1.4 and downgrade to 1.3 any time if you are concerned
that
Hi,
does the objectautocomplete libs require wicket 1.4 or is it possible to use
it with 1.3.x? Is it compatible with the AutoCompleteTextField of wicket
extensions? Can I use a AutoCompleteTextField of wicket extensions and an
ObjectAutoCompleteField in one form?
Thanks in advance,
Kai
How do I change the session timeout page? I want my application to
display the actual home page on session timout instead of the default
Return to homepage-link page.
//Swanthe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Hi
See here for all kinds of different error pages you can easily adjust:
http://cwiki.apache.org/WICKET/error-pages-and-feedback-messages.html
Matt
Swanthe Lindgren wrote:
How do I change the session timeout page? I want my application to
display the actual home page on session timout
Hi Kai
Im not sure if the authors are around.. But the one Objectautocomplet in
trunk of stuff are not backwards compatible, that goes for every contrib
which depends on wicket 1.4. But there should be a branch with the old
version I think, Igor did that a while back the 1.3 branch I mean..
On Wed, Oct 29, 2008 at 8:35 AM, Wayne Pope [EMAIL PROTECTED] wrote:
Hi,
Francisco and I here where discussing whether we could figure a way of
having some form of static/compile time checking on our
(Compound)PropertyModels, as I'm a bit concerned long term about some nasty
runtime bugs
Hmm, this requires a bit low level Java understanding (Wicket doesn't
have anything to do with it.
The underlying mechanism is the same as doing this:
public void foo2bar(String a) {
a = bar;
}
String b = foo;
System.out.println(b is now: + b);
foo2bar(b);
System.out.println(b is now: +
Hi Maarten
interesting idea thanks. I think the major issue is the null pointer
checking.
for your:
public class Customer implements Serializable {
public final IModelString firstName = new ModelString();
public final IModelString lastName = new ModelString();
}
do you wrap this around you
Hi Johan,
we're now maigrating to 1.4 M3 - do you have any idea roughly when the
release proper of 1.4 would be?
thanks
Wayne
On Wed, Oct 29, 2008 at 10:34 AM, Johan Compagner [EMAIL PROTECTED]wrote:
wicket 1.5
first 1.4 has to be released
On Wed, Oct 29, 2008 at 8:35 AM, Wayne Pope [EMAIL
Nino Saturnino Martinez Vazquez Wael wrote:
Hi Kai
Im not sure if the authors are around.. But the one Objectautocomplet
in trunk of stuff are not backwards compatible, that goes for every
contrib which depends on wicket 1.4. But there should be a branch
with the old version I think, Igor
hi,
One problem I see with this approach is when you need null-checking
for nested properties:
eg: new TextFieldString(city, customer.address.getObject().city );
exactly, that is *the* problem
otherwise we could have
new AlternativeCompoundPropertyModel(customer.getAddress().getCity());
Hi Tomasz,
Recently I integrated a JavaScript library with Wicket that could help
you with this particular application.
Take a look at the code and examples:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-jquery/src/main/java/org/wicketstuff/jquery/ajaxbackbutton
Hi Kai
No it seems Objectautocomplete were added after the branching.. So seems
you are a bit out of luck, however backporting should not be too hard..
Kai Mütz wrote:
Nino Saturnino Martinez Vazquez Wael wrote:
Hi Kai
Im not sure if the authors are around.. But the one
On Wed, Oct 29, 2008 at 10:54 AM, Wayne Pope
[EMAIL PROTECTED] wrote:
Hi Maarten
interesting idea thanks. I think the major issue is the null pointer
checking.
for your:
public class Customer implements Serializable {
public final IModelString firstName = new ModelString();
public
Is this session expiration or page expiration ?
I know it is a bit misleading but Wicket throws PageExpiredException
when it doesn't find a particular version of the requested page in the
page store.
There could be different reasons why the page is not found but in my
experience the most often
hi maarten
About the null checking, I will see if I can avoid having nested null values
in my proof-of-concept project.
thing is the object chain is going to be resolved before it gets
passed in - there's nothing you can do about it inside your class :(
an eventual null pointer exception would
hmm, it depends.
if you upgrade to 1.4 and parameterize models and components, it could
be really tough to go back to 1.3. depending of course on the size of
your app.
francisco
On Wed, Oct 29, 2008 at 9:50 AM, Martin Grigorov [EMAIL PROTECTED] wrote:
You could download it from Maven repos as
On Wed, Oct 29, 2008 at 11:47 AM, francisco treacy
[EMAIL PROTECTED] wrote:
hi maarten
About the null checking, I will see if I can avoid having nested null
values
in my proof-of-concept project.
thing is the object chain is going to be resolved before it gets
passed in - there's
Swanthe Lindgren mailto:[EMAIL PROTECTED] wrote:
How do I change the session timeout page? I want my application to
display the actual home page on session timout instead of the default
Return to homepage-link page.
Try
getApplicationSettings().setPageExpiredErrorPage(HomePage.class);
in the
Hi,
does the objectautocomplete libs require wicket 1.4 or is it possible to use
it with 1.3.x? Is it compatible with the AutoCompleteTextField of wicket
extensions? Can I use a AutoCompleteTextField of wicket extensions and an
ObjectAutoCompleteField in one form?
Thanks in advance,
Kai
afiar the proxy based model is null safe.
Martijn
On Wed, Oct 29, 2008 at 11:47 AM, francisco treacy
[EMAIL PROTECTED] wrote:
hi maarten
About the null checking, I will see if I can avoid having nested null values
in my proof-of-concept project.
thing is the object chain is going to be
I think a better solution is to make the browser's back/forward buttons have
the same effect as clicking on the 'Previous Question'/'Next Question'
buttons. If you put effort into making that work instead of putting your
effort into trying to disable the browser's back/forward buttons, then you
or you can go with this solution:
http://cwiki.apache.org/WICKET/autocomplete-using-a-wicket-model.html
-Original Message-
From: Nino Saturnino Martinez Vazquez Wael [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 6:15 AM
To: users@wicket.apache.org
Subject: Re:
On Wed, Oct 29, 2008 at 12:03 PM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
afiar the proxy based model is null safe.
Hello Martijn,
But IIUC it's not refactor-friendly (and no navigation and code completion),
right ?
I really hope they add first-class properties (that is, not string-based)
On Wed, Oct 29, 2008 at 12:02 PM, Maarten Bosteels
[EMAIL PROTECTED]wrote:
On Wed, Oct 29, 2008 at 11:47 AM, francisco treacy
[EMAIL PROTECTED] wrote:
hi maarten
About the null checking, I will see if I can avoid having nested null
values
in my proof-of-concept project.
thing is the
My colegue point out that for Ajax requests AjaxEventBehavior can be used,
and it works fine. so now I need only solution for normal (non Ajax)
requests.
dlipski wrote:
Because I havent found better solution then adding 'onclick' handler to
cellItem I have to do it your way.
I looked at
And any hint how to do this? :)
I thought about two possible ways to solve my problem:
1. on clicking Next/Prev Question button remove current page from
PageMap (although no idea how to do this yet ;) ) and then redirect
further, so when user use back button he will see session-expired-like
page
it is refactor friendly and you also have code completion
(it works with generics)
johan
On Wed, Oct 29, 2008 at 12:12 PM, Maarten Bosteels
[EMAIL PROTECTED]wrote:
On Wed, Oct 29, 2008 at 12:03 PM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
afiar the proxy based model is null safe.
You shouldn't muddy up your domain with view-specific logic (the
IModel interface).
On Wed, Oct 29, 2008 at 5:42 AM, Maarten Bosteels
[EMAIL PROTECTED] wrote:
On Wed, Oct 29, 2008 at 8:35 AM, Wayne Pope [EMAIL PROTECTED] wrote:
Hi,
Francisco and I here where discussing whether we could
or you can use:
https://svn.apache.org/repos/asf/wicket/trunk/wicket-velocity/ in which
case you could have a separate js/vm file that can inject the values for
you:
myscript.vm
script language=JavaScript
function removeBlur(checked) {
if(checked) {
Hoover, William mailto:[EMAIL PROTECTED] wrote:
or you can go with this solution:
http://cwiki.apache.org/WICKET/autocomplete-using-a-wicket-model.html
Hi William,
I have tried it but not successfully. I can select a choice from the
choicelist. But if I want to save it I get a
The CHOICE is your domain model object (there was an error in the WIKI). You
should be able to use any object in your domain. Can you post your code example?
-Original Message-
From: Kai Mütz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 8:57 AM
To: users@wicket.apache.org
To make this work in Firefox with window.open, it seems I need Sjax
(synchronous) to call window.open just inside the onclick handler. Is it
possible in Wicket, in any way?
Adriano
Adriano dos Santos Fernandes escreveu:
In a non-Wicket application, I had a page for report parameters
i agree - that's why i think it would be difficult to avoid an
eventual NPE in something like
customer.getAddress().getCity().getBlabla() in that case
On Wed, Oct 29, 2008 at 1:09 PM, James Carman
[EMAIL PROTECTED] wrote:
You shouldn't muddy up your domain with view-specific logic (the
IModel
// optional, but probably needed
final AjaxFormComponentUpdatingBehavior afcub = new
AjaxFormComponentUpdatingBehavior(onchange) {
protected final void onUpdate(final AjaxRequestTarget target) {
// TODO : do something
}
};
// optional
final
It can be done, but the expression languages that I've used don't do
it out of the box, so that would be an issue with using the proxy
approach. You'd have to roll your own
On Wed, Oct 29, 2008 at 9:14 AM, francisco treacy
[EMAIL PROTECTED] wrote:
i agree - that's why i think it would be
On Wed, Oct 29, 2008 at 1:09 PM, James Carman [EMAIL PROTECTED]wrote:
You shouldn't muddy up your domain with view-specific logic (the
IModel interface).
In my example I just used IModelT instead of PropertyT because everybody
knows IModel.
Have a look at
On Wed, Oct 29, 2008 at 2:24 PM, James Carman [EMAIL PROTECTED]wrote:
The IModel interface, if you're talking about the one from Wicket, is
a view-specific interface (it comes with a view layer library).
James,
Have you actually read what I wrote ?
Maarten
On Wed, Oct 29, 2008 at 9:20
Sorry, but I am on many mailing lists as part of my open source
involvement. I apologize if I breezed over some of what you wrote. I
see now where you said you could use the Property API from that other
project, which is what I would suggest as opposed to IModel from the
Wicket library if you're
The IModel interface, if you're talking about the one from Wicket, is
a view-specific interface (it comes with a view layer library).
On Wed, Oct 29, 2008 at 9:20 AM, Maarten Bosteels
[EMAIL PROTECTED] wrote:
On Wed, Oct 29, 2008 at 1:09 PM, James Carman [EMAIL PROTECTED]wrote:
You shouldn't
it is too bad that there are no deployed examples of wicketstuff-jquery
project to see it in action.
What I've done is exactly this.
With HistoryAjaxBehavior you could listen for clicks on back/forward
button.
On Wed, 2008-10-29 at 07:10 -0400, Richard Allen wrote:
I think a better solution
I wrote a simple resource-based implementation:
http://svn.carmanconsulting.com/public/wicket-advanced/trunk/src/main/java/com/carmanconsulting/wicket/advanced/web/common/resource/ChartImageResource.java
and an example of using it:
I am extending the upload component and have a problem with the maximum file
size detection. The mechanism seems to be working fine except for that it
has an user unfriendliness to it: An exception is thrown, an error message
is set and the onError event called, but the message only arrives AFTER
On Tue, 28 Oct 2008, dlipski wrote:
Textfields do recive onchange event, even AutocompleteTextField has modified
version off onchange event handler.
Whats more new AjaxFormComponentUpdatingBehavior(onchange){..}; works well
in this scenario but
OnChangeAjaxBehavior not.
I looked at
Hi,
I've got the above problem which I have boiled down to the following basic
example.
MyPage references PanelA and PanelB which it swaps about depending on the
current state - both are created when the page is created but PanelA is
added to MyPage as the default display panel.
PanelB
Sorry I meant can we add a page to a modal window
张伟-4 wrote:
try page not panel
2008/10/29 sureshram [EMAIL PROTECTED]
Hello,
I am trying to add auto validation in the modal window but I don't see
any
error messages. I added a feedback panel on a modal window which has a
of course i dont mind.
-igor
On Wed, Oct 29, 2008 at 12:39 AM, Erik van Oosten [EMAIL PROTECTED] wrote:
Thanks for clarifying limitation no 2, I had not though of this. Indeed in
my usecase this is not a problem.
'Limitation' no 1 is quite intentional.
If you don't mind, I've also added
I would like to confirm to folks here that you can use a page that has
a wicket:child element in it directly. You do not have to subclass
it! I found that to be quite weird, but it was very helpful in our
situation!
On Thu, Oct 23, 2008 at 10:42 PM, Richard Paul [EMAIL PROTECTED] wrote:
From
I would like to make it so that whenever Wicket throws a
WicketRuntimeException, it also prints out getSession().getUser(). I'm
not especially clear on the flow for RuntimeExceptions, so any
suggestions on where I would add the code to do this will be greatly
appreciated.
Dane Laverty
On Wed, Oct 29, 2008 at 1:13 AM, Artur W. [EMAIL PROTECTED] wrote:
Hi Igor,
igor.vaynberg wrote:
yes it sucks. i agree. personally i prefer code written against wicket
1.3. even in 1.3 i hardly had to cast anything and even with those
casts i do not remember getting any class cast
you are against generics completely. but they are going to happen. the
way they are now is not perfect, in 1.5 we will try to move them to a
better place, but like it or not they are here to stay.
-igor
On Wed, Oct 29, 2008 at 1:28 AM, Jan Kriesten
[EMAIL PROTECTED] wrote:
Hi Igor,
yes it
look in the project pom
-igor
On Wed, Oct 29, 2008 at 2:14 AM, Kai Mütz [EMAIL PROTECTED] wrote:
Hi,
does the objectautocomplete libs require wicket 1.4 or is it possible to use
it with 1.3.x? Is it compatible with the AutoCompleteTextField of wicket
extensions? Can I use a
Should be possible to catch WicketRuntimeException with a servlet filter ...
On Wed, Oct 29, 2008 at 4:27 PM, Dane Laverty [EMAIL PROTECTED]wrote:
I would like to make it so that whenever Wicket throws a
WicketRuntimeException, it also prints out getSession().getUser(). I'm
not especially
Create your own RequestCycle and in the onRuntimeException(Page page,
RuntimeException e) do this.
Ryan Gravener
http://ryangravener.com/flex | http://twitter.com/ryangravener
On Wed, Oct 29, 2008 at 11:27 AM, Dane Laverty [EMAIL PROTECTED]wrote:
I would like to make it so that whenever
abstract class clickableitem extends item implements ilinklistener {
protected oncomponenttag(tag) {
super
tag.put(onclick,window.location='+urlfor(ilinklistenerinterface.interface)+';);
}
}
thats about all it takes
-igor
On Wed, Oct 29, 2008 at 4:20 AM, dlipski [EMAIL PROTECTED]
what you pasted looks ok, but its incomplete. go ahead and create a
quickstart and a jira issue and i will take a look.
-igor
On Wed, Oct 29, 2008 at 2:07 AM, eyalbenamram [EMAIL PROTECTED] wrote:
OK. I used the IHeader contributor and the problem still exist!
The error:
http-6789-2 ERROR
the fact remains that there are components that are sometimes used
with a model and sometimes without one. as it is we only generify
components that we *think* are most likely to be used with a model,
this is why we spent many an hour backing out generics from Component.
it is too bad that java
Hi Igor,
you are against generics completely. but they are going to happen. the
way they are now is not perfect, in 1.5 we will try to move them to a
better place, but like it or not they are here to stay.
huh - hell, no, I'm not against generics at all. Where do you get that from? I'm
you will need to reshuffle your code so that it opens the window and
all processing happens inside that window rather then in the ajax
behavior. that way you can just add window.open piece to the onclick
of whatever and pass all the necessary attributes on the url.
-igor
On Wed, Oct 29, 2008 at
its not just compound
we have 2 special cases for this:
IComponentAssignedModel and IComponentInheritedModel
which will be both pretty tricky to do if the users must make a field for
the model them selfs.
but we will see.
johan
On Tue, Oct 28, 2008 at 5:22 PM, Igor Vaynberg [EMAIL
James, slow down (and read the thread) :)
The guy actually asked for a place to commit some integration stuff..
Unless you want him to put it in your svn? :)
James Carman wrote:
I wrote a simple resource-based implementation:
I wasn't giving a place to put stuff. I was just offering up an
alternative solution to the problem.
I don't let anyone put stuff in my SVN! :)
On Wed, Oct 29, 2008 at 12:07 PM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
James, slow down (and read the thread) :)
The guy
That was the solution I was looking for.
I havent know that it is possible to do thinks that way !
I supose that I have to override newCellItem and newRowItem method in
DataTable class and return ClickableItem instead of Item.
Good to know that it is possible to do this in standard Wicket way
yes, the inherited will have to most likely go away - but that is
there only for the CPM.
the icomponentassignedmodel is already broken if a component has more
then one model because you have to manually call wrap() on those
anyways...lately ive been writing a lot of components that take more
this is how posts work. we do not get control until the browser has
processed the entire request. at least afaik.
if you want to fix it you will have to write a custom servlet that
processes uploads, and not use the standard POST mechanism.
-igor
On Wed, Oct 29, 2008 at 7:40 AM, lodewijkdans
just dont write those!
On Wed, Oct 29, 2008 at 5:18 PM, Igor Vaynberg [EMAIL PROTECTED]wrote:
yes, the inherited will have to most likely go away - but that is
there only for the CPM.
the icomponentassignedmodel is already broken if a component has more
then one model because you have to
jira, patch, etc... the mailing list is not a good place to report bugs.
-igor
On Wed, Oct 29, 2008 at 7:40 AM, Shailesh Verma [EMAIL PROTECTED] wrote:
I am using wicket-extensions v 1.3.5 and see the javascript Type Mismatch
error on Line 287 of wicket-autocomplete.js. This error comes on
Those are definitely sticking points. I guess we'll just have to
evaluate what is better for the framework. These two features are
definitely convenient.
On Wed, Oct 29, 2008 at 11:59 AM, Johan Compagner [EMAIL PROTECTED] wrote:
its not just compound
we have 2 special cases for this:
Its probably not fool-proof, but it has worked fine up till now
public class MyLDMT extends MyDomainModelIF extends
LoadableDetachableModel{
private MyServiceIFT modelLoaderService;
private Long id;
/**
* Constructor.
*
* @param
that looks fine. is the myservice serializable? do you see any
serialization errors in the log.
if load() is not called then detach() is not called, that means you
are removing the model or the component that contains it after
getobject() has been called but before detach() was and you are
Maybe I have found another solution using the standard AutoCompleteTextField
and a custom converter by overwriting getConverter():
public IConverter getConverter(final Class type) {
return new MyAutoCompleteConverter();
}
private class MyAutoCompleteConverter implements IConverter {
I tried with a modal window and page, still no luck, I do see validation
happening in the server but I don't see that response coming back to the
client
12:20:12,263 DEBUG [ComponentStringResourceLoader] Found resource from:
org/apache/wicket/Application.properties; key: R
equired
12:20:12,263
Ok found the solution myself, The problem was In the AjaxFallBackButton I had
not overriden the onError() method, here's the solution added,
onError(AjaxTarget target, Form form) {
target.addComponent(feedbackPanel);
}
sureshramakrishnaiah wrote:
I tried with a modal window and page,
Theres no problem.. The guy just implemented a clickable chart, and
wanted to share..
James Carman wrote:
I wasn't giving a place to put stuff. I was just offering up an
alternative solution to the problem.
I don't let anyone put stuff in my SVN! :)
On Wed, Oct 29, 2008 at 12:07 PM, Nino
Yeah I for one would defiantly hate for compound model to go away..:(
But I guess one could come along away with propertymodel and when we get
the proxybase model aproach in it could be okay.
[1] https://issues.apache.org/jira/browse/WICKET-1327
James Carman wrote:
Those are definitely
I dont find it a bit wierd.. It just means that you've prepped the class
for inheritance (by telling wicket that markup should be inserted where
wicket:child are), so that if someone comes along latter and extends
your component they are allowed todo so:)
I actually think this is a very nice
In my mind, I think of wicket:child like an abstract method in an
abstract superclass. That's why I find it a bit weird.
On Wed, Oct 29, 2008 at 3:31 PM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
I dont find it a bit wierd.. It just means that you've prepped the class for
I have a ModalWindow containing a class extending Panel. On the Panel I have
a class extending Form.
The Form contains a custom AjaxButton which overrides protected void
onSubmit(AjaxRequestTarget target, Form? form).
When I click this button it retrieves text from a PasswordField and
validates
FYI, I did try some of the suggestions in here but to no avail:
http://www.nabble.com/Form-Enter-Key-Problem-td14408121.html
Also I have investigated using some custom JavaScript manipulate IE, but I
would like to avoid a messy solution like that if possible.
--
View this message in context:
Greetings,
I have spent a couple days trying to fix this issue, any help would be
appreciated:
Action sequence:
1. User of my application loads a wicket/html form page
2. User clicks a link and goes to another page
3. User clicks the browser's BACK button
4. User edits form's content and clicks
easiest thing is to simply disable the enter key on the textfield by
override onkeydown
-igor
On Wed, Oct 29, 2008 at 1:04 PM, mallet [EMAIL PROTECTED] wrote:
I have a ModalWindow containing a class extending Panel. On the Panel I have
a class extending Form.
The Form contains a custom
wicket can clone your model objects for versioning or serialize the
entire page to disk. it is not a good idea to hold direct references
to object's whose lifecycle is independent of wicket components, for
that you should use loadabledetachablemodel or something like it.
-igor
On Wed, Oct 29,
Ahh, and in my mind
It just goes hand in hand with classes which are not final:)
I guess different mindsets.. So my idea is that if you can extend
something you place in wicket:child. and if not you leave it out.
James Carman wrote:
In my mind, I think of wicket:child like an abstract
Ah, I get It. I thought we could count on direct object references to the
application level for at least the duration of the user session, but now i
see it's not a good idea, especially if you want proper back-button
functionality serialization. LoadableDetachableModel sounds good, thanks.
Err, sort of confused about the last few messages.
I submitted the component as I thought it would be useful for other people,
and from the emails I've got I guess it was.
When I had the need to implement a clickable chart a few weeks ago I looked
around for an existing solution, and found
I have some reused panels that have a custom built CollapsiblePanelHeader
component in them. I would like to save the boolean value of whether it is
collapsed or not within the Session object. I had it working for a while by
using a Map in the Session with the panel's classname as the key and the
Igor,
Thanks for your reply. Here's what I did:
PasswordTextField passwordTextField = new
PasswordTextField(password, new ModelString());
passwordTextField.add(new
AjaxFormComponentUpdatingBehavior(onkeydown) {
@Override
public void
1 - 100 of 108 matches
Mail list logo
