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 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 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 before the exception is thrown. > > PS: Btw, when the stable wicket-1.3 version is planned to be released? > > Regards, > Alex. > > > Matej Knopp-2 wrote: > > > > 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]> wrote: > >> > >> 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 > >> wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:295)" > >> problem? > >> 2) How much pain involves the process of migration from wicket-1.2.6 to > >> wicket-1.3? > >> > >> Thank you! > >> > >> > >> > >> Matej Knopp-2 wrote: > >> > > >> > 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 > >> > > > > > > > -- > View this message in context: > http://www.nabble.com/Problem-with-concurren-ajax-requests-on-page-tf3667503.html#a10419990 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
