TextField custom inmplementation of fieldError
Hello I am currently using some textFields that have some sort of validation , witch works just fineThe moment one field is not valid the border of the text field turns red (default behaviour.) . Now i want to create a custom component that extends textField that will implement a custom behaviour for this situation (ex: show an error sign next to the field). Can you please give me some hints how can this be done? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/TextField-custom-inmplementation-of-fieldError-tp4651453.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: How to use wicket:fragment?
Hi Balaji,
I am not sure if this helps but I have used fragments in wicket 1.5.7 and from
what I see in your code, it should work. Here is a simple snippet that shows
how I used it:
In my page class, here is what I have to different and show a scrolling
fragment or ordered list of items fragment:
Fragment filterViewFragment;
if (isScrollingFragment(catList)) {
filterViewFragment = new Fragment("filterViewFragment",
"scrollingFragment", this);
// some other components or fields
} else {
filterViewFragment = new Fragment("filterViewFragment",
"regularFragment", this);
// some other components or fields
}
In my page html, here is what I have:
// somethig here
// something here
Thanks
Rama
-Original Message-
From: bala ji [mailto:balaji@gmail.com]
Sent: Wednesday, August 22, 2012 5:46 AM
To: users@wicket.apache.org
Subject: How to use wicket:fragment?
I've added a scenario where i need to use wicket:fragments.
Following is my parent html.
Now i'm giving child html which will replace of my parent
html
...
Example input (will be removed)
...
panel 1
panel 2
The above situation is working fine in case of wicket 1.4, but now in
wicket 1.5.3 its giving me an error of No Markup found.
--
Balaji.N
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax onUpdate (DropDown) Invoked In One Place, But Not The Other
Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-onUpdate-DropDown-Invoked-In-One-Place-But-Not-The-Other-tp4651438p4651442.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: WebApplication.getComponentPreOnBeforeRenderListeners not fount
Don't know what caused the duplicate jars, but you where right. Many thanks! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/WebApplication-getComponentPreOnBeforeRenderListeners-not-fount-tp4651434p4651441.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax onUpdate (DropDown) Invoked In One Place, But Not The Other
Yes, this is the problem.
Only one of the two updates will be performed:
https://issues.apache.org/jira/browse/WICKET-214
Sven
On 08/22/2012 06:51 PM, eugenebalt wrote:
Looking further in our code, I see that the 2nd form (which has the problem)
defines an additional Ajax "onchange" on its own, it finds the dropdown and
adds this extra Ajax code:
final DropDownChoice myDropDown =
(DropDownChoice)((Panel)get("myPanel")).get("myDropDown");
myDropDown.add(new AjaxFormComponentUpdatingBehavior("onchange") {
protected void onUpdate(AjaxRequestTarget target)
...
}
});
Is this an issue? Is there a problem getting *both* Ajax updates to kick in,
both the Form2-specific one and the general Panel one? Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-onUpdate-DropDown-Invoked-In-One-Place-But-Not-The-Other-tp4651438p4651439.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax onUpdate (DropDown) Invoked In One Place, But Not The Other
Looking further in our code, I see that the 2nd form (which has the problem)
defines an additional Ajax "onchange" on its own, it finds the dropdown and
adds this extra Ajax code:
final DropDownChoice myDropDown =
(DropDownChoice)((Panel)get("myPanel")).get("myDropDown");
myDropDown.add(new AjaxFormComponentUpdatingBehavior("onchange") {
protected void onUpdate(AjaxRequestTarget target)
...
}
});
Is this an issue? Is there a problem getting *both* Ajax updates to kick in,
both the Form2-specific one and the general Panel one? Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-onUpdate-DropDown-Invoked-In-One-Place-But-Not-The-Other-tp4651438p4651439.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Ajax onUpdate (DropDown) Invoked In One Place, But Not The Other
I have a reusable Panel which contains a DropDownChoice.
The DropDownChoice has an Ajax onChange action defined on it,
protected void onUpdate(AjaxRequestTarget target) {
...
}
When I add the Panel to one of my forms, the Ajax action gets invoked
correctly on the DropDown change, but when I add it to a different form, the
Ajax action never gets invoked. It's the same reusable Panel. The Ajax
action works in one place, but not the other (I verified that nothing
happens by adding debug statements to onUpdate).
Can anyone suggest any theories on what the problem might be with the 2nd
form that uses this panel? Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-onUpdate-DropDown-Invoked-In-One-Place-But-Not-The-Other-tp4651438.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: [6.0] wicket-atmosphere
Good afternoon,
Is there any way to have Comet channels using the wicket-atmosphere
API? For instance, with the Broadcaster API, you could use a
MetaBroadcaster which used to have a broadcasterID parameter.
I can't figure out how to integrate that in my wicket-atmosphere code
and the JavaDoc from EventBus#post() reads:
"Post an event to *all* pages that have a suspended connection".
Any help will be much appreciated!
Regards,
Pierre Goupil
On Thu, Aug 9, 2012 at 10:17 AM, Pierre Goupil wrote:
>
> Thanks!!! I'll have a close look at your ticket. And yes, I use Tomcat
> (7.0.29). I know it's all beta code, so no worries.
>
> Regards,
>
> Pierre
>
>
>
>
> On Thu, Aug 9, 2012 at 10:02 AM, Emond Papegaaij
> wrote:
>>
>> We've noticed this problem as well. It only happens on Tomcat. I'm not sure
>> what is going on, but it all starts with Tomcat loosing query parameters on
>> the ws-request ("url/?0-1.IBehaviorListener.0-" is changed to "url"). This
>> makes it impossible for wicket to recognize the call to a behavior, causing a
>> redirect to a new page on the ws-request, which is not allowed.
>>
>> The question is, is this a bug in Tomcat, Atmosphere or wicket-atmosphere. I
>> would say it's a bug in Atmosphere. I've created a ticket for this:
>> https://github.com/Atmosphere/atmosphere/issues/553
>>
>> For now, using jetty is a work around.
>>
>> Best regards,
>> Emond
>>
>> On Wednesday 08 August 2012 20:59:10 Pierre Goupil wrote:
>> > Hello,
>> >
>> > It looks like a problem with the WebSockets. I've tried to provide a
>> > Locale, but no way:
>> >
>> > class MySession extends WebSession
>> > {
>> > private static final long serialVersionUID = 1L;
>> >
>> > public MySession(final Request req)
>> > {
>> > super(req);
>> > }
>> >
>> > @Override
>> > public void setLocale(final Locale locale)
>> > {
>> > super.setLocale(new Locale("en", "GB"));
>> > }
>> > }
>> >
>> > and in my WicketApplication:
>> >
>> > @Override
>> > public Session newSession( final Request req, final Response res ) {
>> > return new MySession(req);
>> > }
>> >
>> > It all gives me the same error.
>> >
>> > BUT if I deactivate the WebSockets, it works:
>> >
>> >
>> > org.atmosphere.useWebSocket
>> > FALSE
>> >
>> >
>> > in my web.xml.
>> >
>> > Regards,
>> >
>> > Pierre
>> >
>> > On Wed, Aug 8, 2012 at 5:43 PM, Pierre Goupil
>> > wrote:
>> > > Good afternoon,
>> > >
>> > > I'm currently trying and have wicket-atmosphere work. I've looked at the
>> > > examples and I'm unable to post a message because of this exception:
>> > >
>> > >
>> > > INFO - EventBus - registering component for page 0 for
>> > > session 971E81ED0E61970FA35A1B03E5B218F8:
>> > > ERROR - DefaultExceptionMapper - Unexpected error occurred
>> > > java.lang.IllegalStateException: Request#getLocale() cannot return null,
>> > > request has to have a locale set on it
>> > >
>> > > at org.apache.wicket.Session.(Session.java:211)
>> > > at
>> > >
>> > > org.apache.wicket.protocol.http.WebSession.(WebSession.java:92)
>> > >
>> > > at
>> > >
>> > > org.apache.wicket.protocol.http.WebApplication.newSession(WebApplication.j
>> > > ava:536)>
>> > > at
>> > >
>> > > org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:15
>> > > 57)>
>> > > at org.apache.wicket.Session.get(Session.java:152)
>> > > at
>> > >
>> > > org.apache.wicket.RestartResponseAtInterceptPageException$InterceptData.ge
>> > > t(RestartResponseAtInterceptPageException.java:146)>
>> > > at
>> > >
>> > > org.apache.wicket.RestartResponseAtInterceptPageException$1.matchedData(Re
>> > > startResponseAtInterceptPageException.java:211)>
>> > > at
>> > >
>> > > org.apache.wicket.RestartResponseAtInterceptPageException$1.getCompatibili
>> > > tyScore(RestartResponseAtInterceptPageException.java:179)>
>> > > at
>> > >
>> > > org.apache.wicket.request.mapper.CompoundRequestMapper.mapRequest(Compound
>> > > RequestMapper.java:134)>
>> > > at
>> > >
>> > > org.apache.wicket.request.cycle.RequestCycle.resolveRequestHandler(Request
>> > > Cycle.java:182)>
>> > > at
>> > >
>> > > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.j
>> > > ava:207)>
>> > > at
>> > >
>> > > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(Reque
>> > > stCycle.java:281)>
>> > > at
>> > >
>> > > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.j
>> > > ava:188)>
>> > > at
>> > >
>> > > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:24
>> > > 5)>
>> > > at
>> > >
>> > > org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.j
>> > > ava:154)>
>> > > at
>> > >
>> > > org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilt
>> > > erChain.java:131)>
>> > > at
>> > >
>> > > org.atmosphere.handler.
Re: WebApplication.getComponentPreOnBeforeRenderListeners not fount
Check for duplicated Wicket jars in the classpath On Wed, Aug 22, 2012 at 5:49 PM, Delange wrote: > After a day of changing a lot I got this message when starting wicket from > mvn jetty:run > > I reinstalled older sources but still get this message > 1.5.7 > > Who can help on this? > > 2012-08-22 16:39:53.120::WARN: Error starting handlers > > Java.lang.NoSuchMethodError: > org.apache.wicket.protocol.http.WebApplication.getComponentPreOnBeforeRenderListeners()Lorg > apache/wicket/application/ComponentOnBeforeRenderListenerCollection; >at > com.vdr.logistiek.MasterApplication.init(MasterApplication.java:40) > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/WebApplication-getComponentPreOnBeforeRenderListeners-not-fount-tp4651434.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
WebApplication.getComponentPreOnBeforeRenderListeners not fount
After a day of changing a lot I got this message when starting wicket from mvn jetty:run I reinstalled older sources but still get this message 1.5.7 Who can help on this? 2012-08-22 16:39:53.120::WARN: Error starting handlers Java.lang.NoSuchMethodError: org.apache.wicket.protocol.http.WebApplication.getComponentPreOnBeforeRenderListeners()Lorg apache/wicket/application/ComponentOnBeforeRenderListenerCollection; at com.vdr.logistiek.MasterApplication.init(MasterApplication.java:40) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/WebApplication-getComponentPreOnBeforeRenderListeners-not-fount-tp4651434.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Which RENDER_STRATEGY is best for clustered setup?
Yes it is. Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Which-RENDER-STRATEGY-is-best-for-clustered-setup-tp4651420p4651433.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
How to use wicket:fragment?
I've added a scenario where i need to use wicket:fragments. Following is my parent html. Now i'm giving child html which will replace of my parent html ... Example input (will be removed) ... panel 1 panel 2 The above situation is working fine in case of wicket 1.4, but now in wicket 1.5.3 its giving me an error of No Markup found. -- Balaji.N
Re: Which RENDER_STRATEGY is best for clustered setup?
No, this is not related. I just improved its javadoc: https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=43878fc8c470044923f3b599953a1c4ff2aef63b Is it cleaner now ? On Wed, Aug 22, 2012 at 2:15 PM, sudeivas wrote: > Thanks Martin for the response. Could you please answer the below question as > well? > > What is the use of the below API? > getRequestCycleSettings().setBufferResponse(false); > > Does it make any difference to the render strategy? I guess it makes some > difference to 'REDIRECT_TO_BUFFER'. > > Thanks, > Suresh > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Which-RENDER-STRATEGY-is-best-for-clustered-setup-tp4651420p4651429.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Which RENDER_STRATEGY is best for clustered setup?
Thanks Martin for the response. Could you please answer the below question as well? What is the use of the below API? getRequestCycleSettings().setBufferResponse(false); Does it make any difference to the render strategy? I guess it makes some difference to 'REDIRECT_TO_BUFFER'. Thanks, Suresh -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Which-RENDER-STRATEGY-is-best-for-clustered-setup-tp4651420p4651429.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: stack traces in serialization caches
I think I have found the problem. Should be better with the fix in https://issues.apache.org/jira/browse/WICKET-4722 On Fri, Aug 10, 2012 at 2:53 PM, Martin Grigorov wrote: > No, these are no errors. > These are kept only in case of error. > We can improve though by removing them in Component#detach(). I see no > reason to keep them around after the first render of the page. > Please file a ticket. > > On Fri, Aug 10, 2012 at 2:45 PM, Andrew Geery wrote: >> I'm using Wicket 1.5.7. I understand how to turn the stacktraces on and >> off (in development more I have both those settings turned on). My >> question is more: the files look like they are indicating an error is >> happening, but I don't get a stacktrace at run-time. For example, if I >> have a mismatch between the Java class and the HTML I get a stacktrace at >> run-time in development mode. I'm running in development mode and I'm not >> getting any stacktraces. However, when I look at the wicket-filestore >> files I am seeing stacktraces. My questions are: >> >> (1) Do the stacktraces in the wicket-filestore files indicate that there is >> an error? The app seems to work fine, but a stacktrace would indicate an >> error to me... >> (2) If these are indeed errors, why are the errors on the wicket-filestore >> files not being thrown at run-time when running in dev mode? >> >> To make this more concrete, one place I'm seeing the errors is around >> ModalWindow components. Is the stacktrace simply saying that the >> ModalWindow is not rendered on the page (which would be true, it is not yet >> shown), but that it is present in the page's hierarchy? >> >> Thanks >> Andrew >> >> On Fri, Aug 10, 2012 at 3:12 AM, Martin Grigorov wrote: >> >>> Hi, >>> >>> Which version of Wicket do you use ? >>> >>> See >>> org.apache.wicket.settings.IDebugSettings#setLinePreciseReportingOnAddComponentEnabled >>> and >>> org.apache.wicket.settings.IDebugSettings#setLinePreciseReportingOnNewComponentEnabled. >>> When set to true these create an exception and saves its stacktrace as >>> String in the Component's meta data. This stacktrace is used to find >>> when and where the problem happened. >>> >>> These stacktraces are printed only if >>> org.apache.wicket.settings.IDebugSettings#getComponentUseCheck() >>> returns true. >>> >>> >>> On Fri, Aug 10, 2012 at 4:16 AM, Andrew Geery >>> wrote: >>> > I have a question about why I am seeing stack traces in my >>> wicket-filestore >>> > files. This question has been asked before ( >>> > >>> http://apache-wicket.1842946.n4.nabble.com/Strange-content-serialized-td1933194.html >>> ), >>> > but I don't understand the answer. When I run the app, I don't get any >>> > errors -- all of the components render fine. However, in the files I see >>> > errors like this: >>> > >>> > The webmarkupcontainer with id 'content' that failed to render was added >>> > >>> > In the previous thread, the answer was that the error was there because >>> > there was a discrepancy between the Java hierarchy and the HTML file. >>> > However, if there was an error, wouldn't I get a run-time error (since I >>> > am running the app in development mode)? Why, when there isn't >>> > a discrepancy, is there a stack trace in the cache? >>> > >>> > Thanks >>> > Andrew >>> >>> >>> >>> -- >>> Martin Grigorov >>> jWeekend >>> Training, Consulting, Development >>> http://jWeekend.com >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: page version and forms
Are you using wicket-tree or the new components in Wicket 6?
Please be more specific what information you're looking for. I'll gladly
provide more info in javadoc or in the wiki.
Sven
Alex Shubert schrieb:
>Sven while you are here:
>why no documentation for Tree? Nothing at all? Right now I face a
>problem - tree do not persist it's state (Bookmarcable links, copied
>from example) and I have no clue where to see.
>
>
>On 21 August 2012 21:38, Sven Meier wrote:
>> And the winner is ... Martin!
>>
>> On AppEngine I still have Wicket 1.4.x running.
>>
>> Sven
>>
>>
>> On 08/21/2012 02:59 PM, Martin Grigorov wrote:
>>>
>>> The Google Code repo contains 1.5 but the deployed app is using pre-1.5
>>> version.
>>> I can bet on this.
>>>
>>> On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert
>>> wrote:
Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
>>>
>>> Is there a reason why you don't trust me ? :-)
>>> wicket:interface is no more used in 1.5+, unless the application adds
>>> it explicitly. Wicket (the framework) doesn't use it anymore.
>>>
a look at event listener implementation.
About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
>>>
>>> Most of them are actually still valid.
>>> There are new pages labeled with "wicket15" and "wicket6" which refer
>>> to the new features in 1.5 and 6.0 respect.
>>>
If someone wonder how to determine why his page is stateful here is
the solution:
>>>
>>> There is StatelessChecker in wicket-devutils for this task.
>>>
if (!isPageStateless()) {
visitChildren(Component.class, new IVisitor>>> Component>() {
@Override
public void component(Component component,
IVisit iVisit) {
if (!component.isStateless()) {
LOGGER.info("Stateful component found [ "
+ component.getClass().getName() + " : "
+ component.getMarkupId() + " ]");
// iVisit.stop(component);
}
}
});
}
If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.
On 21 August 2012 15:47, Martin Grigorov wrote:
>
> Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
> url means that this is Wicket pre-1.5 ;-)
>
> I guess Sven will join this conversation later today and explain in
> more details.
>
> On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert
> wrote:
>>
>> Martin
>> with all my respect but their build script uses
>>
>>
>> org.apache.wicket
>> wicket-core
>> ${wicket.version}
>>
>>
>> ${wicket.version} derived from parent pom where
>> 1.5.0
>>
>> So,
>> 1. no stateless form
>> 2. it is 1.5
>> 3. it's pretty easy to ensure yourself just by looking into code
>> http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
>> can't be compiled under 1.4
>>
>> Anyway: what does your answer has to do with my question? One more
>> time: how that example manage not to increase page version shown in
>> url on every tree node selection?
>> thanks
>>
>>
>> On 21 August 2012 14:39, Martin Grigorov wrote:
>>>
>>> The deployed examples use Wicket 1.4.
>>>
>>> http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
>>>
>>> On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert
>>> wrote:
They are using
Form form = new Form("form");
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states
that
must be the case.
On 21 August 2012 14:20, Martin Grigorov
wrote:
>
> Use StatelessForm instead.
>
> On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert
> wrote:
>>
>> Hello
>>
>> Recently I found wicket tree control
>>
>> http://wicket-tree.appspot.com/nested
>>
>> and one there is a thing I can't understand: while the page
>> contains
>> Form it
Re: page version and forms
Hi,
These components have been merged in Wicket 6.
You can see the demo at
http://www.wicket-library.com/wicket-examples-6.0.x/tree
and the code in org.apache.wicket.extensions.markup.html.repeater.tree
package in wicket-extensions module.
The javadocs are also improved.
On Wed, Aug 22, 2012 at 10:10 AM, Alex Shubert wrote:
> Sven while you are here:
> why no documentation for Tree? Nothing at all? Right now I face a
> problem - tree do not persist it's state (Bookmarcable links, copied
> from example) and I have no clue where to see.
>
>
> On 21 August 2012 21:38, Sven Meier wrote:
>> And the winner is ... Martin!
>>
>> On AppEngine I still have Wicket 1.4.x running.
>>
>> Sven
>>
>>
>> On 08/21/2012 02:59 PM, Martin Grigorov wrote:
>>>
>>> The Google Code repo contains 1.5 but the deployed app is using pre-1.5
>>> version.
>>> I can bet on this.
>>>
>>> On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert
>>> wrote:
Martin,
http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
Again, no 1.4 at all. Not in one place. Moreover,
'?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
>>>
>>> Is there a reason why you don't trust me ? :-)
>>> wicket:interface is no more used in 1.5+, unless the application adds
>>> it explicitly. Wicket (the framework) doesn't use it anymore.
>>>
a look at event listener implementation.
About the problem: the page I gave link for is really stateless but it
is not meant to be, it just happened. If user choose any other tree
renders version number eager to appear.
The most Wicket problem right now is it's occult state. Wiki is
hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
>>>
>>> Most of them are actually still valid.
>>> There are new pages labeled with "wicket15" and "wicket6" which refer
>>> to the new features in 1.5 and 6.0 respect.
>>>
If someone wonder how to determine why his page is stateful here is
the solution:
>>>
>>> There is StatelessChecker in wicket-devutils for this task.
>>>
if (!isPageStateless()) {
visitChildren(Component.class, new IVisitor>>> Component>() {
@Override
public void component(Component component,
IVisit iVisit) {
if (!component.isStateless()) {
LOGGER.info("Stateful component found [ "
+ component.getClass().getName() + " : "
+ component.getMarkupId() + " ]");
// iVisit.stop(component);
}
}
});
}
If in need of test detection, extract visitor to separate class and
instantiate pages with WicketTester.
On 21 August 2012 15:47, Martin Grigorov wrote:
>
> Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
> url means that this is Wicket pre-1.5 ;-)
>
> I guess Sven will join this conversation later today and explain in
> more details.
>
> On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert
> wrote:
>>
>> Martin
>> with all my respect but their build script uses
>>
>>
>> org.apache.wicket
>> wicket-core
>> ${wicket.version}
>>
>>
>> ${wicket.version} derived from parent pom where
>> 1.5.0
>>
>> So,
>> 1. no stateless form
>> 2. it is 1.5
>> 3. it's pretty easy to ensure yourself just by looking into code
>> http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
>> can't be compiled under 1.4
>>
>> Anyway: what does your answer has to do with my question? One more
>> time: how that example manage not to increase page version shown in
>> url on every tree node selection?
>> thanks
>>
>>
>> On 21 August 2012 14:39, Martin Grigorov wrote:
>>>
>>> The deployed examples use Wicket 1.4.
>>>
>>> http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
>>>
>>> On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert
>>> wrote:
They are using
Form form = new Form("form");
and still no version in url on round-trips. Also, FilterForm from
Wicket API doesn't extends StatelessForm while your answer states
that
must be the case.
On 21 August 2012 14:20, Martin Grigorov
wrote:
>
> Use StatelessForm instead.
>
> On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert
> wrote:
>>
>> Hello
>>
>> Recently I found wicket tree control
>>
>> http://wicket-tree.appspot.com/nested
Re: page version and forms
Sven while you are here:
why no documentation for Tree? Nothing at all? Right now I face a
problem - tree do not persist it's state (Bookmarcable links, copied
from example) and I have no clue where to see.
On 21 August 2012 21:38, Sven Meier wrote:
> And the winner is ... Martin!
>
> On AppEngine I still have Wicket 1.4.x running.
>
> Sven
>
>
> On 08/21/2012 02:59 PM, Martin Grigorov wrote:
>>
>> The Google Code repo contains 1.5 but the deployed app is using pre-1.5
>> version.
>> I can bet on this.
>>
>> On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert
>> wrote:
>>>
>>> Martin,
>>>
>>> http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom
>>> Again, no 1.4 at all. Not in one place. Moreover,
>>> '?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take
>>
>> Is there a reason why you don't trust me ? :-)
>> wicket:interface is no more used in 1.5+, unless the application adds
>> it explicitly. Wicket (the framework) doesn't use it anymore.
>>
>>> a look at event listener implementation.
>>>
>>> About the problem: the page I gave link for is really stateless but it
>>> is not meant to be, it just happened. If user choose any other tree
>>> renders version number eager to appear.
>>> The most Wicket problem right now is it's occult state. Wiki is
>>> hopelessly outdated, most of the examples refer to 1.2.-1.3 version...
>>
>> Most of them are actually still valid.
>> There are new pages labeled with "wicket15" and "wicket6" which refer
>> to the new features in 1.5 and 6.0 respect.
>>
>>>
>>> If someone wonder how to determine why his page is stateful here is
>>> the solution:
>>
>> There is StatelessChecker in wicket-devutils for this task.
>>
>>> if (!isPageStateless()) {
>>> visitChildren(Component.class, new IVisitor>> Component>() {
>>> @Override
>>> public void component(Component component,
>>> IVisit iVisit) {
>>> if (!component.isStateless()) {
>>> LOGGER.info("Stateful component found [ "
>>> + component.getClass().getName() + " : "
>>> + component.getMarkupId() + " ]");
>>>
>>> // iVisit.stop(component);
>>> }
>>> }
>>> });
>>> }
>>>
>>> If in need of test detection, extract visitor to separate class and
>>> instantiate pages with WicketTester.
>>>
>>>
>>> On 21 August 2012 15:47, Martin Grigorov wrote:
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the
url means that this is Wicket pre-1.5 ;-)
I guess Sven will join this conversation later today and explain in
more details.
On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert
wrote:
>
> Martin
> with all my respect but their build script uses
>
>
> org.apache.wicket
> wicket-core
> ${wicket.version}
>
>
> ${wicket.version} derived from parent pom where
> 1.5.0
>
> So,
> 1. no stateless form
> 2. it is 1.5
> 3. it's pretty easy to ensure yourself just by looking into code
> http://code.google.com/p/wicket-tree/wiki/RunningExamples It even
> can't be compiled under 1.4
>
> Anyway: what does your answer has to do with my question? One more
> time: how that example manage not to increase page version shown in
> url on every tree node selection?
> thanks
>
>
> On 21 August 2012 14:39, Martin Grigorov wrote:
>>
>> The deployed examples use Wicket 1.4.
>>
>> http://wicket-tree.appspot.com/?wicket:interface=:0:1:::
>>
>> On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert
>> wrote:
>>>
>>> They are using
>>> Form form = new Form("form");
>>>
>>> and still no version in url on round-trips. Also, FilterForm from
>>> Wicket API doesn't extends StatelessForm while your answer states
>>> that
>>> must be the case.
>>>
>>>
>>> On 21 August 2012 14:20, Martin Grigorov
>>> wrote:
Use StatelessForm instead.
On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert
wrote:
>
> Hello
>
> Recently I found wicket tree control
>
> http://wicket-tree.appspot.com/nested
>
> and one there is a thing I can't understand: while the page
> contains
> Form it looks like not versioned. I mean there are no version
> number
> in a url.
> How does it work then? Is there any clear way to build pages
> containing Form without explicit version number in url except some
> black magic involved ( modified MountedMapper )
>
>
>
>
> --
