Is there any progress on this issue ?
I search JIRA but there is no related issue...
On 5/11/07, Alex Objelean [EMAIL PROTECTED] wrote:
I'll add a quickstart as soon as possible... (tomorrow by noon)
Thank you!
Matej Knopp-2 wrote:
Okay. Can you please create a quickstart that can be
Well, it wasn't wicket fault... It was mine. Actually, I used YUI for layout
management and this didn't work very well for my fully ajaxified application
by causing this kind of errors. Therefore I gave up using it...
The problem appears when the component is not in the sync with its model.
I managed to migrate my application to wicket-1.3 ... but the same problem
still persist...:( - this time it is complaining that he is unable to find
the componentRelativePath of the component which is supposed to be added to
the target. :(
The problem with NPE in
Okay. Can you please create a quickstart that can be used to reproduce
this and add attach it to a jira bug entry?
Thanks
-Matej
On 5/10/07, Alex Objelean [EMAIL PROTECTED] wrote:
I managed to migrate my application to wicket-1.3 ... but the same problem
still persist...:( - this time it is
I'll add a quickstart as soon as possible... (tomorrow by noon)
Thank you!
Matej Knopp-2 wrote:
Okay. Can you please create a quickstart that can be used to reproduce
this and add attach it to a jira bug entry?
Thanks
-Matej
On 5/10/07, Alex Objelean [EMAIL PROTECTED] wrote:
I
I have the same issue and I am using wicket 1.2.6..
I am also developing an ajax application (desktop like)... Is it a known
issue or bug in my code?
Thank you!
Regards,
Alex.
Matej Knopp-2 wrote:
You seem to be using 1.2, is that right?
-Matej
On 4/30/07, RedFury [EMAIL PROTECTED]
If you are developing ajax-heavy web application I'd certainly suggest
you migrating to 1.3. There are issues in 1.2 with AJAX that are
unfixable, because they would require API breaks, which is something
we can't do.
-Matej
On 5/9/07, Alex Objelean [EMAIL PROTECTED] wrote:
I have the same
Well, it's a bad-bad news for me :(
As far as I know, the wicket-1.3 does not have yet stable release, is it
correct? If so, when approximately it will be available?
And another two questions:
1) Does the wicket-1.3 solve the
java.lang.NullPointerException
at
Well, there is no DefaultRequestTargetResolverStrategy in 1.3, as
there was a refactoring done. But even if you have problem with the
NPE, we can fix much easier than in 1.2.
As for the migration, it depends on how complex your application is.
-Matej
On 5/9/07, Alex Objelean [EMAIL PROTECTED]
The problem with NPE in DefaultRequestTargetResolverStrategy:295 seems to be
the way wicket retrieves the component using its relative component path...
[code]
page.get(pageRelativeComponentPath);
[code]
The component which cause the problem was removed and then added back by the
AjaxTabbedPanel
You seem to be using 1.2, is that right?
-Matej
On 4/30/07, RedFury [EMAIL PROTECTED] wrote:
Hi all, just want to say that I've relatively new to Wicket but am loving
every minute of it! In just a few weeks of learning and programming I have
been able to create a robust, javascripted,
Though I'm not sure, maybe you'll get a hint from this :
JAVASCRIPT : httpRequest.open('GET', 'http://www.example.org/some.file',
true);
* The third parameter sets whether the request is asynchronous. If TRUE,
the execution of the JavaScript function will continue while the response of
which version of wicket do you use?
can you reproduce this in a quickstart example?
johan
On 4/30/07, RedFury [EMAIL PROTECTED] wrote:
Hi all, just want to say that I've relatively new to Wicket but am loving
every minute of it! In just a few weeks of learning and programming I
have
been
Hi all, just want to say that I've relatively new to Wicket but am loving
every minute of it! In just a few weeks of learning and programming I have
been able to create a robust, javascripted, ajaxified app for our company.
Great work to the devs!
However, I have one problem which I'm a
14 matches
Mail list logo
