File a ticket please.
On Thu, Mar 10, 2011 at 3:01 AM, Matt Brictson wrote:
> Hi,
>
> CompressedResourceReference in trunk is basically empty and has the comment
> "TODO NG". A quick search through the source leads me to believe that
> IResourceSettings#getDisableGZipCompression() is also unused
On 10 Mar 2011, at 04:25, Henrique Boregio wrote:
>
> Hi, I have a RestartResponseAtInterceptPageException working correctly in
> one case and not so in another.
>
> I have a Login page with a LoginForm. In this form's onSubmit method, right
> after the user validation takes place, I have:
>
> i
Hi, I have a RestartResponseAtInterceptPageException working correctly in
one case and not so in another.
I have a Login page with a LoginForm. In this form's onSubmit method, right
after the user validation takes place, I have:
if(!continueToOriginalDestination()) {
setResponsePage(Dashboard
Hi,
CompressedResourceReference in trunk is basically empty and has the comment
"TODO NG". A quick search through the source leads me to believe that
IResourceSettings#getDisableGZipCompression() is also unused.
In other words, gzipping of resources is not implemented in Wicket 1.5.
Are there
On 09 Mar 2011, at 22:36, Brown, Berlin [GCG-PFS] wrote:
>> On 09 Mar 2011, at 22:01, Chris Colman wrote:
>>>
>>> Sorry, CompoundPropertyModel is not deprecated in 1.5, it's
>>> BoundCompoundPropertyModel that is.
>>
>> Too bad :-)
>>
>> Really, you use normal models and LDMs, or BindGen
>> (h
On 09 Mar 2011, at 23:31, Chris Colman wrote:
>
>
> Surely there must be a way to support both styles of 'construction' (I
> use that term loosely) within the one framework.
My proposed [3] and [4] already does that without an external configuration
option that would confuse things about as muc
Just a thought:
Surely there must be a way to support both styles of 'construction' (I
use that term loosely) within the one framework.
Perhaps a runtime switch in the properties could dictate the
'construction' mode.
You could leave the default as 'traditional wicket' mode but in 'two
phase' co
What is wrong with compoundpropertymodel (pre 1.5)?
-Original Message-
From: Maarten Billemont [mailto:lhun...@gmail.com]
Sent: Wednesday, March 09, 2011 4:30 PM
To: users@wicket.apache.org
Subject: Re: CompoundPropertyModel deprecated in 1.5 - what is the
replacement?
On 09 Mar 2011, a
On 09 Mar 2011, at 22:01, Chris Colman wrote:
>
> Sorry, CompoundPropertyModel is not deprecated in 1.5, it's
> BoundCompoundPropertyModel that is.
Too bad :-)
Really, you use normal models and LDMs, or BindGen
(http://code.google.com/p/bindgen-wicket/) and make your code type-safe.
---
On 09 Mar 2011, at 21:42, Igor Vaynberg wrote:
> oninitialize() is an atomic callback that notifies components when the
> page becomes available. the page is special because since a page is
> always available to itself it doesnt need such a callback. how is that
> for a rationalization... :)
Only,
I didn't realize that so I found this line on that page a bit confusing:
"The IModel interface was simplified in Wicket 2.0"
Maybe it should say:
"The IModel interface was simplified in Wicket 1.4"
now that 2.0 doesn't exist and the change was actually made in 1.4.
>-Original Message-
Hi,
I think you've forgotten adding code
Hi, I am calling second page onsubmit method of the first page as:
setResponsePage(PGSecond.class);
and on the second page label is added as:
Thanx.
-
To unsubscribe, e-mail: users-un
My bad! I was had done s search on CompoundPropertyModel and
BoundCompoundPropertyModel showed up in the deprecated list but I just
saw the highlighted "CompountPropertyModel" part... =]
Sorry, CompoundPropertyModel is not deprecated in 1.5, it's
BoundCompoundPropertyModel that is.
--
On Wed, Mar 9, 2011 at 11:54 AM, Maarten Billemont wrote:
> On 09 Mar 2011, at 18:56, Igor Vaynberg wrote:
>>
>> On Wed, Mar 9, 2011 at 1:15 AM, Maarten Billemont wrote:
yep, calling overridable methods from constructors is bad - you just
made the case for making page.oninitialize() fin
On 09 Mar 2011, at 18:56, Igor Vaynberg wrote:
>
> On Wed, Mar 9, 2011 at 1:15 AM, Maarten Billemont wrote:
>>> yep, calling overridable methods from constructors is bad - you just
>>> made the case for making page.oninitialize() final...
>>
>> No, I've made the case for this issue. Either add(
On 09 Mar 2011, at 19:15, Gary Thomas wrote:
>
> On 3/9/11 2:18 AM, Maarten Billemont wrote:
>> On 09 Mar 2011, at 10:44, Gary Thomas wrote:
>>>
>>> While a minority use-case, this allows for very elegant Wicket code when
>>> using Scala:
>>>
>>> add(new Form[Person]("form", model) {
>>>add
Wicket 2 has been discontinued.
Most of the features in it has been merged to 1.4/1.5.
Some of them was considered unsuccessful and dropped.
On Wed, Mar 9, 2011 at 9:46 AM, Coleman, Chris <
chris.cole...@thalesgroup.com.au> wrote:
> At the bottom of this page:
>
> https://cwiki.apache.org/WICKET/
On Wed, Mar 9, 2011 at 9:56 AM, Coleman, Chris <
chris.cole...@thalesgroup.com.au> wrote:
> I noticed that CompoundPropertyModel is deprecated in 1.5 but I can't find
> anything relating to this on the "Migration to Wicket 1.5" page.
>
> What is meant to be used instead of this class?
>
It is not
wicket 1.4.9
When a wicket behavior tries to load a javascript resource from the response, I
want to create some error handler (a javascript alert) that runs if the
javascript package resource is not found.
I set an IAjaxCallDecorator which spits out a javascript string on failure, but
the fail
On Tue, Mar 8, 2011 at 3:34 PM, Frank van Lankvelt
wrote:
> On Tue, Mar 8, 2011 at 1:21 PM, Antoine van Wel
> wrote:
>>
>> Since "you can't always have what you want"..
>>
>> Is there any PHP framework out there which comes even close to Wicket;
>> component based, strict separation between HTML
Hi everyone,
In a quite complex wizard Wicket based application, I have filled a
WizardModel with many steps.
Each of those steps required some mandatories inputs, which are validated
against Wicket IValidator mechanism.
The "overview" component of the Wizard is implemented with a custom
WizardN
On 3/9/11 2:18 AM, Maarten Billemont wrote:
On 09 Mar 2011, at 10:44, Gary Thomas wrote:
While a minority use-case, this allows for very elegant Wicket code when using
Scala:
add(new Form[Person]("form", model) {
add (new TextArea[String]("text", (getModel -> "text")) {
override
> I have a c++ background and this kind of problem is even more dangerous in
> c++ (virtual calls don't work as normal in constructors). In Java also, I
> think making "this" known to the outside world before it is fully
> constructed is unsafe, as illustrated above.
It's a potential problem we've
On Wed, Mar 9, 2011 at 1:15 AM, Maarten Billemont wrote:
>> yep, calling overridable methods from constructors is bad - you just
>> made the case for making page.oninitialize() final...
>
> No, I've made the case for this issue. Either add() should be disallowed
> from the constructor (meaning o
Hi, I am calling second page onsubmit method of the first page as:
setResponsePage(PGSecond.class);
and on the second page label is added as:
Thanx.
-
Developer
Wicket
Java
JSP
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Using-jQuery-with-Wicket-tp3343275p3344
Hi,
how do you add this label to your page? can you show initialization code
of second page?
any idea? I am really stuck with that.
I will be thankful if you share your idea with me.
-
Developer
Wicket
Java
JSP
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Us
On Wed, Mar 9, 2011 at 12:25 PM, Hiren Patel <
hiren_pa...@kaleconsultants.com> wrote:
> Hi,
>
> I have done the following to disabled the text field.
>
> field.setDisabled(isDisabled);
>
There is no method setDisabled() in Wicket.
>
> now when I inspect the html code in the browser the *value* a
any idea? I am really stuck with that.
I will be thankful if you share your idea with me.
-
Developer
Wicket
Java
JSP
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Using-jQuery-with-Wicket-tp3343275p3344002.html
Sent from the Users forum mailing list archive at N
Josh thank you for response.I will do that.
Also I have another question:
I have a page extending from basepage and i have i second page also
extending from base page.
When I click on submit button on first page it will redirect me to second
page but it gives an error like that:
WicketMessage: Pro
Hi,
Another way is to have a service manage the list. We have a reference
data list (list of streets) in our application that has >100k elements
that is stored in memory and we have a service hold one instance that is
shared between all accessors (typically the autocomplete search fields)
of
Should work, though perhaps going to the datastore for each
back/forward button press might be overkill. Retrieving it from a
cache, like ehcache, allows you to set an expiry on the data, keep it
thread safe and even memory safe (i.e. let ehcache throw away the
objects when memory is tight, or let
Hi!
Is a good idea to have appropriate build script that does the changes
/ assert checklist for you.
For example,
Hello. I am getting close to deploying my first wicket web
application. It's not huge but it does have lots of classes,
components, database stuff, search features, etc.
I was wondering if anyone had some kind of checklist on what things to
definitely check before deploying a wicket application in
Martijn,
Wouldn't this be a safe way to cache a list at the expense of memory (using
transient)? In a lot of my projects I have to do some aggregation of the
results from multiple data stores that are slow even with the caching layer.
private class SomeDataProvider extends SortableDataProvide
on the first Select , and an ajax form compenent behavior for 'onchange' ,
On the implementation , remove the item from the first select's model, add
it to the other select component's model then add both select components to
the target.
Also use LoadableDetachableModels for your select compone
can you point me to a good wicket + ehcache tutorial?
On 9 March 2011 13:13, Martijn Dashorst wrote:
> On Wed, Mar 9, 2011 at 1:00 PM, Jan Juno wrote:
> > I have One Array-list(with over 1 objects in it) what is the best
> > practice for caching it so I don't have to load it over and over a
On Wed, Mar 9, 2011 at 1:00 PM, Jan Juno wrote:
> I have One Array-list(with over 1 objects in it) what is the best
> practice for caching it so I don't have to load it over and over again in
> each request?
Usually at our company we expect our ORM mapper (hibernate) to take
care of caching,
I have One Array-list(with over 1 objects in it) what is the best
practice for caching it so I don't have to load it over and over again in
each request?
Jan
Thank you for your response.
Actually this is not meet with my requirements.
Any other suggestion?
-
Developer
Wicket
Java
JSP
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Using-jQuery-with-Wicket-tp3343275p3343437.html
Sent from the Users forum mailing list arc
Hi tech7,
could Palette component be helpfull for you?
http://wicketstuff.org/wicket14/compref/?wicket:bookmarkablePage=:org.apache.wicket.examples.compref.PalettePage
I have some html pages including some jquery functionaliy.
For example: select a choice from a select box then click a butto
Both very helpful answers
@Mike ManderThe wicket-stuff thing is very cool indeed.
However, I'd like to mounting to be controlled by some
strategy/configuration in most cases which wont help if i have the
Annotation within the WebPage (but yes very very cool to know it exists).
@Attila Király : Ya
Am 09.03.2011 11:28, schrieb Arjun Dhar:
Hi,
I wanted to externalize the Page Mounts using Spring.
Earlier in my "Application" class the code was like:
mount(new QueryStringUrlCodingStrategy("login", loginPage.class));
So What I did was:
...
//Scan for All IMountLoaders in
Dear All
I have a list of user names, I populated listView using it, with each
username I created three radion buttons (present,absent, leave), please see
appended source code
I want when I click save button then status of each username printed or
saved, how to do it.
*
ListView* listView = *
I have some html pages including some jquery functionaliy.
For example: select a choice from a select box then click a button moves
this choice to the other select box but what i need to do is also update the
select box (list)content also.
How can I do that? Any suggestions?
With my best regards.
Your xml config tries to instantiate the page. Try this:
Attila
2011/3/9 Arjun Dhar
> Hi,
> I wanted to externalize the Page Mounts using Spring.
>
> Earlier in my "Application" class the code was like:
>
> mount(new QueryStringUrlCodingStrategy("login", loginPage.class));
>
>
> So What I di
Hi,
I wanted to externalize the Page Mounts using Spring.
Earlier in my "Application" class the code was like:
mount(new QueryStringUrlCodingStrategy("login", loginPage.class));
So What I did was:
...
//Scan for All IMountLoaders in the context and get the
Mount points from th
Hi,
I have done the following to disabled the text field.
field.setDisabled(isDisabled);
now when I inspect the html code in the browser the *value* attribute is
missing.
Can you suggest me a solution for this.
_Hiren
http://kaleusermeet-march-2011.doattend.com/";>
http://email.kalecon
On 09 Mar 2011, at 10:44, Gary Thomas wrote:
>
> While a minority use-case, this allows for very elegant Wicket code when
> using Scala:
>
> add(new Form[Person]("form", model) {
>add (new TextArea[String]("text", (getModel -> "text")) {
>override def isVisible: Boolean = false
>
On 3/8/11 12:33 PM, Martijn Dashorst wrote:
On Tue, Mar 8, 2011 at 6:03 PM, GOODWIN, MATTHEW (ATTCORP)
wrote:
+1 for clear documentation/Javadoc explaining proper use of
onInitialize.
Does this exist somewhere? As someone new to Wicket I'm trying to learn
as fast as I can and a lot of example
> yep, calling overridable methods from constructors is bad - you just
> made the case for making page.oninitialize() final...
No, I've made the case for this issue. Either add() should be disallowed from
the constructor (meaning onInitialize won't get called from it), onInitialize
should be ma
On Wed, Mar 9, 2011 at 12:22 AM, Coleman, Chris
wrote:
>> yep, calling overridable methods from constructors is bad -
>
> Yes I agree...
>
>> you just made the case for making page.oninitialize() final...
>
> But isn't that the very thing that the whole overridable onInitialize method
> was inten
> yep, calling overridable methods from constructors is bad -
Yes I agree...
> you just made the case for making page.oninitialize() final...
But isn't that the very thing that the whole overridable onInitialize method
was intended to avoid as it gets called after construction by the framework
On Tue, Mar 8, 2011 at 11:22 PM, Maarten Billemont wrote:
Just like EJBs, you should be careful about how much interaction you do
beyond your object's scope within the constructor. Your component doesn't
have a hierarchy, getPage() cannot be accessed, none of your subclass
53 matches
Mail list logo
