that method has javadoc...
-igor
On Sat, Mar 15, 2008 at 9:41 PM, Warren [EMAIL PROTECTED] wrote:
What is cleanupFeedbackMessages() used for ?
-Original Message-
From: Warren [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 15, 2008 9:37 PM
To: users@wicket.apache.org
Hi,
I was actually trying to use getPageParameters() as well, and it was
returning null too...
The reason I want to use it is, I have a base page which adds a context
panel fragment in the page, which it gets by an abstract method
getContextPanel(). Now in the sub page I wanted to use the
Is there any way to ask a component what its preferred tag type is?
For instance, TextField would return input and DropDownChoice would
return select. This would be useful if one were to want to
dynamically generate a form (using Velocity) based on a list of
Components (property editors).
If
+1 for moving to java 5
On Sun, Mar 16, 2008 at 12:45 AM, Gabor Szokoli [EMAIL PROTECTED] wrote:
Hi,
Your conclusion covers our case, but I'd debate your reasoning:
We use java 5, deploy to GlassFish.
No nostalgic attachments to pre-generics Java :-)
But we believe these (including
On 3/16/08, Maarten Bosteels [EMAIL PROTECTED] wrote:
+1 for moving to java 5
+1 for moving to Java 5 *quickly* :)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
java 5 now definitely
On Sun, Mar 16, 2008 at 7:48 PM, James Carman [EMAIL PROTECTED]
wrote:
On 3/16/08, Maarten Bosteels [EMAIL PROTECTED] wrote:
+1 for moving to java 5
+1 for moving to Java 5 *quickly* :)
-
To
+1 to java 5
atul singh wrote:
java 5 now definitely
On Sun, Mar 16, 2008 at 7:48 PM, James Carman [EMAIL PROTECTED]
wrote:
On 3/16/08, Maarten Bosteels [EMAIL PROTECTED] wrote:
+1 for moving to java 5
+1 for moving to Java 5 *quickly* :)
Hi,
strange problem: when changing language in my app which is a Form done
with Wicket 1.3.0-RC1, the Models loose their values when the browser
is IE6/7. With Firefox everything is ok.
Component streetaddress = get(customerInfo+:contactInfo+:streetaddress);
String modelAsString =
Update first, ask questions later. There are roughly 300 issues solved
between your version and 1.3.2.
Martijn
On 3/16/08, Marcus Mattila [EMAIL PROTECTED] wrote:
Hi,
strange problem: when changing language in my app which is a Form done
with Wicket 1.3.0-RC1, the Models loose their values
Thanks!
This works. Just need some adjustments in the css :)
--
View this message in context:
http://www.nabble.com/css-menu-and-wicket-tp16062124p16079941.html
Sent from the Wicket - User mailing list archive at Nabble.com.
Another YES for 1.5
Phil
On Sun, Mar 16, 2008 at 10:12 AM, Maurice Marrink [EMAIL PROTECTED] wrote:
+1 (non binding) for a quick x-m1 with only generics release
Maurice
On Sun, Mar 16, 2008 at 3:32 PM, Thijs [EMAIL PROTECTED] wrote:
+1 to java 5
atul singh wrote:
java 5 now
Suppose I have a package structure like this...
com.mycompany.myproject
--- module1
--- page
- Page1.html
--- module2
--- page
- Page2.html
If I want to autolink from Page1.html to Page2.html, it would look like:
wicket:link
a href=../../module2/page/Page2.htmlClick
On Mar 16, 2008, at 16:58 , Phil Grimm wrote:
Another YES for 1.5
Phil
+1
--
Fabrizio Giudici, Ph.D. - Java Architect, Project Manager
Tidalwave s.a.s. - We make Java work. Everywhere.
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
[EMAIL PROTECTED] - mobile: +39 348.150.6941
That's funny, I was about to post regarding the numerous issues with
wicket:link...
And one suggestion I was going to give was to add support for
../packge/Page.html.
I don't think it currently supports this, at least I couldn't see it from a
code examination.
Your only option, I believe, is to
On 3/16/08, Phil Grimm [EMAIL PROTECTED] wrote:
That's funny, I was about to post regarding the numerous issues with
wicket:link...
And one suggestion I was going to give was to add support for
../packge/Page.html.
I don't think it currently supports this, at least I couldn't see it from
I think a JIRA request is appropriate.
Perhaps we'll hear a confirmation from the Wicket developers.
I'd add the following to the request...
1. Add support for ../ relative path resolution
2. Add support for searching the classpath (if absolute and relative search
fails)
-- I think this is
On 3/16/08, Phil Grimm [EMAIL PROTECTED] wrote:
I think a JIRA request is appropriate.
Perhaps we'll hear a confirmation from the Wicket developers.
I'd add the following to the request...
1. Add support for ../ relative path resolution
+1 - This is essential and shouldn't be very
no there isnt such a thing. usually the beanstuff we have done uses
some metadata to generate both markup and components...there is
wicket-stuff-crud project that generates crud views based on a
bean...maybe look into that for inspiration
-igor
On Sun, Mar 16, 2008 at 7:02 AM, James Carman
its binding now...
-igor
On Sun, Mar 16, 2008 at 8:12 AM, Maurice Marrink [EMAIL PROTECTED] wrote:
+1 (non binding) for a quick x-m1 with only generics release
Maurice
On Sun, Mar 16, 2008 at 3:32 PM, Thijs [EMAIL PROTECTED] wrote:
+1 to java 5
atul singh wrote:
In our application we have three basic pages:
- search page
- results page
- details page
Search page has a form with all of the search criteria. On submit,
the search is saved to the database and response page is set to the
results page, with the ID of the search as a page parameter.
The
you guys do both realize that wicket:link is nothing more then
convinience. it isnt really meant to support all these complex
usecases. it is nice when you need to quickly include an image or link
to a near by page, but nothing more then that.
-igor
On Sun, Mar 16, 2008 at 10:24 AM, James
On 3/16/08, Igor Vaynberg [EMAIL PROTECTED] wrote:
you guys do both realize that wicket:link is nothing more then
convinience. it isnt really meant to support all these complex
usecases. it is nice when you need to quickly include an image or link
to a near by page, but nothing more then
Yeah, as a new user to Wicket, I just see it as another feature of Wicket.
There's no issues with it, if all your pages are in the same package.
Is that what most Wicket developers do?
I agree that searching the classpath could be problematic and more involved
to implement. But, the ../ support
On 3/16/08, James Carman [EMAIL PROTECTED] wrote:
On 3/16/08, Igor Vaynberg [EMAIL PROTECTED] wrote:
you guys do both realize that wicket:link is nothing more then
convinience. it isnt really meant to support all these complex
usecases. it is nice when you need to quickly include an
On 3/16/08, James Carman [EMAIL PROTECTED] wrote:
In fact, I believe I already have a patch that fixes it. I'll create
a JIRA and attach the patch. You folks can discuss whether it is
worthy or not to make it into core.
For future reference, I've created:
../ syntax is just as prone to refactoring errors as the absolute
path, so i dont buy that argument
-igor
On Sun, Mar 16, 2008 at 11:51 AM, Phil Grimm [EMAIL PROTECTED] wrote:
Yeah, as a new user to Wicket, I just see it as another feature of Wicket.
There's no issues with it, if all your
Hi,
I'm developing an application in which I'm using the TreeTable component.
My table contains the table (nodes) and 7 other columns which are
TextField's in
which users may enter data. OnBlur on the TextFields updates the model:
public EditablePanel(MarkupContainer parent, String id,
+1 for Java 5 Generics
On Sun, Mar 16, 2008 at 11:03 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
its binding now...
-igor
On Sun, Mar 16, 2008 at 8:12 AM, Maurice Marrink [EMAIL PROTECTED] wrote:
+1 (non binding) for a quick x-m1 with only generics release
Maurice
Hi everyone,
How to implement a model driven visibility? Are there any best
practices? Should I use the AttributeModifier to set a style
visibility attribute or there is a better way?
Vitaly
-
To unsubscribe, e-mail:
Martijn, you're right. Probably not so thankful to fix bugs if people
then uses old versions and complain :). Ok, I tried in 1.3.2 and get
the same problem with IE. Problem seems to be Ajax. Before changing
language
in my app, everything works fine and inputting data to a field
generates the
@override boolean isVisible() {
return ((MyClass)getModelObject()).isSomeValueSet();
}
On 3/16/08, Vitaly Tsaplin [EMAIL PROTECTED] wrote:
Hi everyone,
How to implement a model driven visibility? Are there any best
practices? Should I use the AttributeModifier to set a style
Well, ../ path it's slightly more tolerant to refactoring.
You can change anything that comes before the ../ without needing to touch
HTML files.
So Igor, do you always use absolute paths?
I'm thinking that's what I'll use, since the limited relative path support
only works when the current page
On Sun, Mar 16, 2008 at 2:48 PM, Phil Grimm [EMAIL PROTECTED] wrote:
So Igor, do you always use absolute paths?
i only use wicket:link for trivial cases. for example, if one of my
components needs to display an image or include a js file that lives
next to it
-igor
+1 for Java 5 Generics
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I have been surprised that we have not had a single person say that they still
require 1.4. Although I was originally against dropping 1.3 if we did a quick
1.4 (because I assumed there'd be many who still needed Java 1.4), perhaps we
should open this up on the users list and get a more
Those people who do are still in struts 1.x mode. And thats what ... ? 85%
of the commercial java world ? ... i hear lots of those are moving to JSF
... **sigh** =(
On Sun, Mar 16, 2008 at 6:16 PM, Jeremy Thomerson
[EMAIL PROTECTED] wrote:
I have been surprised that we have not had a single
it was already on the user list
On Sun, Mar 16, 2008 at 11:16 PM, Jeremy Thomerson
[EMAIL PROTECTED] wrote:
I have been surprised that we have not had a single person say that they
still require 1.4. Although I was originally against dropping 1.3 if we
did a quick 1.4 (because I assumed
DOH! Pitfall of keeping up with the dev and users lists on my phone - sometimes
I miss something - I was thinking this discussion was on the dev list
(should've scrolled up and double-checked).
Either way, that actually lends more probability to us being able to do a quick
1.4 and drop 1.3.
Personally all my projects are on java 1.5 at least, so I would love
to have a quick 1.4 release and drop 1.3. But that's just me.
-igor
On 3/16/08, Jeremy Thomerson [EMAIL PROTECTED] wrote:
DOH! Pitfall of keeping up with the dev and users lists on my phone -
sometimes I miss something - I
FWIW +1 to java5 and 1.3.
Generics == joy, especially with the model stuff wicket uses :)
igor.vaynberg wrote:
Personally all my projects are on java 1.5 at least, so I would love
to have a quick 1.4 release and drop 1.3. But that's just me.
-igor
--
View this message in context:
Can anybody suggest how I can try to resolve my
StreamCorruptedException?
I have an autocomplete text field. When I hit the back button and modify
the text, I get the said Exception.
I've tried stepping through the code, but the error is not obvious at
all.
The error only happens with the
On Sun, Mar 16, 2008 at 9:32 PM, Ned Collyer [EMAIL PROTECTED] wrote:
FWIW +1 to java5 and 1.3.
Generics == joy, especially with the model stuff wicket uses :)
Same here; would like to see generics.
Enrique
-
To
So far, no one has said they need Java 1.4. So, how do we request that a
vote is started for this?
Option A - Generics go in 1.4-M1, we still support 1.3, and 1.4 will be the
next big-feature release, many months from now
Option B - Generics *are *1.4, we drop support for 1.3 (and Java 1.4), and
43 matches
Mail list logo
