Re: Spring secury + auth-roles authentication and authorization: access denied
Hello Andrew, that was the solution! You saved my day! Thank you a lot! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Spring-secury-auth-roles-authentication-and-authorization-access-denied-tp4004013p4019263.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: Validating HTML 4
Le 08/11/2011 16:43, Martin Grigorov a écrit : Hi, Hello, thanks very much for your quick answer ! The problem is that there are several specifications and all of them expect different output. We try to stick to HTML5 because this is the future. You mean, HTML 5 in Wicket 1.5 ? I tryed to find what was really done to get more HTML 5 compliant in that new Wicket version but can't find many more details that what is writen on https://cwiki.apache.org/WICKET/wicket-wish-list.html#WicketWishList-Supportofhtml5 : it talks only of new components ? Can't find anything about the way tags are closed, and in HTML 5 it's as of any previous html version right ? - When using ResourceReference the link tags are closed in the xhtml way : link ... /. Should belink ... in HTML. It seems to be hard coded in HeaderResponse#renderCSSReference() You can use org.apache.wicket.Application.setHeaderResponseDecorator(IHeaderResponseDecorator) to setup custom HeaderResponse and modify this. - In Form components Wicket adds hidden inputs. They are also closed in the xhtml way. Seems to be hard coded in Form#onComponentTagBody() and Form#appendDefaultButtonField(). none of these is final. you can override them This is a lot of code to duplicate !! To put in a balance, of course I'd prefer sticking with those validation errors than to override wicket core components code, and get in trouble when upgrading to the next wicket version (we'll sure do it in a few weeks, and maybe to the 1.5 branch ? At least to the last 1.4.* !). May Wicket offers something to specify which tag closing maner to adopt ? In the application IMarkupSettings for exemple ? And if Wicket team goal is HTML5, it should be by defaut the html way ? - DataTable : a SPAN is always added in the TD and TH. Override DataTable component and provide your own MyDataTable.html. The .java code will just call super constructors. As said before, I don't feel very confident in duplicating wicket code and change a very little detail in it. Is there a way to change those span to div in future versions of Wicket ? - DataTable : the TFOOT node is always sent to the client, even if it's empty. In that last case, the html code is invalid in html. I think this is improved in 1.5.x Good news :) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Validating HTML 4
Hi, On Wed, Nov 9, 2011 at 12:12 PM, pgoiffon.wic...@free.fr wrote: Le 08/11/2011 16:43, Martin Grigorov a écrit : Hi, Hello, thanks very much for your quick answer ! The problem is that there are several specifications and all of them expect different output. We try to stick to HTML5 because this is the future. You mean, HTML 5 in Wicket 1.5 ? I tryed to find what was really done to get more HTML 5 compliant in that new Wicket version but can't find many more details that what is writen on https://cwiki.apache.org/WICKET/wicket-wish-list.html#WicketWishList-Supportofhtml5 : it talks only of new components ? Can't find anything about the way tags are closed, and in HTML 5 it's as of any previous html version right ? Yes, in Wicket 1.5. Wicket 1.4.x branch receives only bug fixes and only major ones. I say that in Wicket.current we try to follow HTML5 recomendations. There is no sense to start supporting all the versions of HTML 4 standards (strict, loose, ...) when even the browser vendors agreed that this doesn't work and they have to maintain just one specification. - When using ResourceReference the link tags are closed in the xhtml way : link ... /. Should belink ... in HTML. It seems to be hard coded in HeaderResponse#renderCSSReference() You can use org.apache.wicket.Application.setHeaderResponseDecorator(IHeaderResponseDecorator) to setup custom HeaderResponse and modify this. - In Form components Wicket adds hidden inputs. They are also closed in the xhtml way. Seems to be hard coded in Form#onComponentTagBody() and Form#appendDefaultButtonField(). none of these is final. you can override them This is a lot of code to duplicate !! To put in a balance, of course I'd prefer sticking with those validation errors than to override wicket core components code, and get in trouble when upgrading to the next wicket version (we'll sure do it in a few weeks, and maybe to the 1.5 branch ? At least to the last 1.4.* !). 1.4.x is close to its end of life. Soon we will stop porting fixes and only security fixes will be committed in this branch. May Wicket offers something to specify which tag closing maner to adopt ? In the application IMarkupSettings for exemple ? And if Wicket team goal is HTML5, it should be by defaut the html way ? This would be too much work for no big gain. See my opinion above. - DataTable : a SPAN is always added in the TD and TH. Override DataTable component and provide your own MyDataTable.html. The .java code will just call super constructors. As said before, I don't feel very confident in duplicating wicket code and change a very little detail in it. Is there a way to change those span to div in future versions of Wicket ? Sure. File a ticket in Jira. We cannot change it in 1.5.x because it may break silently apps in production. So it will have to wait Wicket.next. - DataTable : the TFOOT node is always sent to the client, even if it's empty. In that last case, the html code is invalid in html. I think this is improved in 1.5.x Good news :) - 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: Modal Window with Ajax in Firefox
Hi, I uploaded quickstart that reproduces error to github at https://github.com/iref/modaltest . 2011/11/2 Andrea Del Bene adelb...@ciseonweb.it Hi, can you reproduce your problem in a separate project and upload it somewhere? It would help much to understand if this problem is a bug and to find a solution. --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Jan Ferko, julyl...@gmail.com
Re: Advice wanted about polished component set with Wicket
That sounds encouraging. I am very interested in how you went about integrating Dojo into Wicket. On 9/11/2011 2:51 PM, Martin Grigorov wrote: Hi David, I'm interested in your work. Another guy also did something at https://github.com/vijaykiran/wicketstuff-dojo On Tue, Nov 8, 2011 at 8:36 PM, David Berkmandavid.berk...@glu.com wrote: I've had excellent success wrapping most of Dojo with Wicket, and it would not be hard to complete the rest. There's a wicket-dojo project out there, but it didn't seem to be active, so I just started in on my own. Dojo is a comprehensive, well laid out project (always had a good concept of namespace and packaging, unlike most other javascript frameworks), with decent documentation. Browsers have a tendency to fire events in different orders, and when you start adding your own 'onxxx' functions, you can get unexpected behavior. My first guess would be that this is the cause of your problems in IE, as it seems to be particularly random in this regard. Dojo has its own, extensive, event framework, that corrects for these issues. If you want to look at my code, let me know and I'll send it your way. David -Original Message- From: James Stewart [mailto:james.stewart...@gmail.com] Sent: Tuesday, November 08, 2011 4:58 AM To: users@wicket.apache.org Subject: Advice wanted about polished component set with Wicket Hi all, We have been using Wicket for some time now with our home grown html some wicket components. However, there are some complaints that our components and pages look a bit bland. This has prompted us to look around at various alternatives. We tried using plain jQuery with wicket and found some odd behaviour here and there on Internet Explorer when using Ajax, which we never got to the bottom of. If I remember correctly it was the calendar appearing on first render which then disappeared and it would never reappear again. This has lead us to reassess our component situation. Having looked at the wiQuery demo site it doesn't fill me with confidence. Perhaps it is just the demo site that does not work well and is not an indication of the underlying library. The next library we are considering is Visural Wicket. It looks promising but it only seem to have one developer working on it. Otherwise we would probably look to something like YUI of which I have some experience but not with Wicket. It would take some investigating though to establish if it would have similar problems that we encountered with JQuery. Any advice or real world experience will be appreciated. Thanks, James. - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Advice wanted about polished component set with Wicket
Hi Martin, Have you got a typical example of a destroy + create new in the wicket-ajax.onBeforeRender? This may make life easier with JQuery. Thanks, James. On 8/11/2011 9:26 PM, Martin Makundi wrote: Hi! When you render jquery components via ajax you often need to recreate them (destroy old + create new) with wicket-ajax.onBeforeRender It might seem bit tricky at start but simply make it part of onBeforeRender or similar in either a behavior or component itself. ** Martin 2011/11/8 James Stewartjames.stewart...@gmail.com: Hi all, We have been using Wicket for some time now with our home grown html some wicket components. However, there are some complaints that our components and pages look a bit bland. This has prompted us to look around at various alternatives. We tried using plain jQuery with wicket and found some odd behaviour here and there on Internet Explorer when using Ajax, which we never got to the bottom of. If I remember correctly it was the calendar appearing on first render which then disappeared and it would never reappear again. This has lead us to reassess our component situation. Having looked at the wiQuery demo site it doesn't fill me with confidence. Perhaps it is just the demo site that does not work well and is not an indication of the underlying library. The next library we are considering is Visural Wicket. It looks promising but it only seem to have one developer working on it. Otherwise we would probably look to something like YUI of which I have some experience but not with Wicket. It would take some investigating though to establish if it would have similar problems that we encountered with JQuery. Any advice or real world experience will be appreciated. Thanks, James. - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Migrating a ResourceStreamRequestTarget to a ResourceStreamRequestHandler (2)
I managed to pinpoint my issue. I'm starting a new topic in order to exclude
information I
now think isn't relevant anymore.
I don't think it's a caching problem any longer, but that is has to do with
a hanging
thread or something that's not closed properly, that is, when using Firefox
and Chrome.
In IE8: no problems, works as it did in 1.4.18 with the Wicket
ResourceStreamRequestTarget.
My code again:
LinkString downloadInstallationmanualButton = new
LinkString(downloadinstallationmanual, new ModelString()) {
@Override
public void onClick() {
if (user didn't supply any data) {
info(Please supply this and that);
return;
}
//create an subclass of AbstractResourceStream called
InstallationManualResourceStream
InstallationManualResourceStream theInstallationManualResourceStream
= new InstallationManualResourceStream();
if (theInstallationManualResourceStream.manualNotfound) {
info(No manual found for your input);
return;
}
ResourceStreamRequestTarget resourceStreamRequestTarget = new
ResourceStreamRequestTarget(
theInstallationManualResourceStream,
theFileName);
RequestCycle.get().setRequestTarget(resourceStreamRequestTarget);
}
(The underlying InputStream is closed properly, even in Firefox.)
The problem is in the last statement:
/RequestCycle.get().setRequestTarget(resourceStreamRequestTarget);/
This statement causes something to hang, so that in a new RequestCycle, the
onclick() isn't
fired anymore (and never again). When I omit this statement, the onClick()
fires each time.
I don't think I'm doing something wrong, certainly not after I discovered
that it works in IE8.
Maybe this is relevant: the underlying InputStream is part of a
ZipInputstream. Bij 'newing' my
InstallationManualResourceStream, the ZipInputStream is read until an
installation manual is found (hence
the /theInstallationManualResourceStream.manualNotfound()/ and it's info
message),
and then 'handed over' to the Wicket AbstractResourceStream.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Migrating-a-ResourceStreamRequestTarget-to-a-ResourceStreamRequestHandler-2-tp4019661p4019661.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: unit testing cookies after redirect
so if this is the last line in my code those two approaches are pretty the same pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski@gmail.com __ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migrating a ResourceStreamRequestTarget to a ResourceStreamRequestHandler (2)
Made a quick start, but couldn't reproduce the issue, it worked in FireFox... Be it on a Jetty-server, and I have to cope with WebSphere... Well, I'll strip my application down to the essentials that I have in the quick start, and then build up one by one, I guess. Many thanks, so far! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-a-ResourceStreamRequestTarget-to-a-ResourceStreamRequestHandler-2-tp4019661p4020304.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: Validating HTML 4
Martin Grigorov mgrigo...@apache.org a écrit : The problem is that there are several specifications and all of them expect different output. We try to stick to HTML5 because this is the future. You mean, HTML 5 in Wicket 1.5 ? Yes, in Wicket 1.5. Wicket 1.4.x branch receives only bug fixes and only major ones. I say that in Wicket.current we try to follow HTML5 recomendations. There is no sense to start supporting all the versions of HTML 4 standards (strict, loose, ...) when even the browser vendors agreed that this doesn't work and they have to maintain just one specification. I'm confused with this statement : what do you mean by supporting all the version of HTML 4 standards ? Wicket lets you put whatever doctype you want, and send to the user agents any tag you may want to use. The only problem I had with wicket considering html validation is the way some tags in certain components are closed : valid in xhtml but invalid in both transitionnal or strict html 4. I was convinced that HTML5 is still HTML, so auto-closed tags are invalid. I checked the html 5 draft recommandation this morning before answering and can't find anywhere that auto closed tags are valid. But I've just use the validator with this markup : !DOCTYPE HTML html head titleTesting tag closing/title /head body pA paragraph with a auto-closed brbr / Done !/p /body /html And it's stated as valid html 5 ! So if it is right and not just a validator bug (seems unlikely), I suppose you meant, as your idea is to do html 5 with Wicket 1.5 and plus, that auto closed tags will always be sent by Wicket ? Am I right ? If so, for what I know now on, if it's too hard to add a mean for the developpers to pick the way he wants the tag to be closed, then I would recommend Wicket to close tags in the HTML way and forgive about XHTML auto-closed tags. Thus Wicket will be compatible with all HTML versions, up to 5 included. I don't think so much web site / app use XHTML nowdays ? 1.4.x is close to its end of life. Soon we will stop porting fixes and only security fixes will be committed in this branch. We didn't get in that migration yet, we're finishing some of our products major versions. It will certainly be the first step after those products shipping :) Though with just a quick view as we add, there seems to be a great amount of efforts to produce to get existing apps to the 1.5 version ? We'll see when the moment comes. - DataTable : a SPAN is always added in the TD and TH. Is there a way to change those span to div in future versions of Wicket ? Sure. File a ticket in Jira. We cannot change it in 1.5.x because it may break silently apps in production. So it will have to wait Wicket.next. Will do :) But I'm a bit sad about the perspective of resolution which seems quite fareway. If the correction is just to change span to div, all the possible troubles for existing apps I see are about css selectors that wouldn't be right anymore (in css but eventually other areas - see $() in jQuery). - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Advice wanted about polished component set with Wicket
David, I would be extremely interested in your work. I have been trying to integrate JqUery plugins with wicket and not have had much success. The answers from this post will surely be helpful -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Advice-wanted-about-polished-component-set-with-Wicket-tp4015908p4020360.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: Advice wanted about polished component set with Wicket
May I ask which plugins you tried to integrate? I have integrated a few of them and for most of them integration was not that hard. Regards, Ernesto On Wed, Nov 9, 2011 at 5:29 PM, anantasthana anant.a...@gmail.com wrote: David, I would be extremely interested in your work. I have been trying to integrate JqUery plugins with wicket and not have had much success. The answers from this post will surely be helpful -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Advice-wanted-about-polished-component-set-with-Wicket-tp4015908p4020360.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: DI in wicket
Hi,
I have done the configuration in web.xml.
When I print the DAO reference, it is printing like
org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler@f2164f
But the error has been thrown like
org.apache.wicket.WicketRuntimeException: Can't instantiate page using
constructor 'public com.wicket.pages.IndexPage()'. Might be it doesn't
exist, may be it is not visible (public).
Kindly find the Page class, which throws the exception
public class IndexPage extends WebPage
{
@SpringBean(name=userDao)
private UserDao userDao;
public IndexPage()
{
System.out.println(userDao);
add(new Label(sampleLabel, This is a text which is also a
model.));
userDao.test();
}
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/DI-in-wicket-tp3824880p4020478.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: Advice wanted about polished component set with Wicket
I tried to integrate the JCaurosel and Ajax Vertical slider which is basically a lazy load scroll bar. I am still new to wicket and still learning new things every day so ther are alot of things I am still learning. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Advice-wanted-about-polished-component-set-with-Wicket-tp4015908p4020538.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: Modal Window with Ajax in Firefox
Hi,
I think the best solution would be replace modal window's content
instead of closing it and opening a new one. Considering your example
you should completely remove notifierWindow. The new code for HomePage
would be like this:
public HomePage(final PageParameters parameters) {
final ModalWindow homeWindow = new ModalWindow(modal);
final FeedbackPanel notifier = new
FeedbackPanel(homeWindow.getContentId());
notifier.setOutputMarkupId(true);
final HomePanel homePanel = new
HomePanel(homeWindow.getContentId()) {
@Override
public void performAction(AjaxRequestTarget target) {
replaceWith(notifier);
target.addComponent(notifier);
//homeWindow.close(new AjaxRequestTarget(getPage()));
// notifierWindow.show(target);
}
};
//the same code
Hope this could help you.
Hi,
I uploaded quickstart that reproduces error to github at
https://github.com/iref/modaltest .
2011/11/2 Andrea Del Beneadelb...@ciseonweb.it
Hi,
can you reproduce your problem in a separate project and upload it
somewhere? It would help much to understand if this problem is a bug and to
find a solution.
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.orgusers-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: Validating HTML 4
pgoiffon.wic...@free.fr a écrit : I was convinced that HTML5 is still HTML, so auto-closed tags are invalid. I checked the html 5 draft recommandation this morning before answering and can't find anywhere that auto closed tags are valid. Found it ! http://www.w3.org/TR/html5/syntax.html#syntax-start-tag - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DI in wicket
Please provide the complete stacktrace
Hi,
I have done the configuration in web.xml.
When I print the DAO reference, it is printing like
org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler@f2164f
But the error has been thrown like
org.apache.wicket.WicketRuntimeException: Can't instantiate page using
constructor 'public com.wicket.pages.IndexPage()'. Might be it doesn't
exist, may be it is not visible (public).
Kindly find the Page class, which throws the exception
public class IndexPage extends WebPage
{
@SpringBean(name=userDao)
private UserDao userDao;
public IndexPage()
{
System.out.println(userDao);
add(new Label(sampleLabel, This is a text which is also a
model.));
userDao.test();
}
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/DI-in-wicket-tp3824880p4020478.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: Advice wanted about polished component set with Wicket
Hi, There are at least two projects out there that already do some integration with jquery... So, it might be a good idea to take a look at them:-) On Wed, Nov 9, 2011 at 6:15 PM, anantasthana anant.a...@gmail.com wrote: I tried to integrate the JCaurosel and Ajax Vertical slider which is basically a lazy load scroll bar. We have integrated a vertical slider on [1]. I have also integrated a component similar to jCarousel in one of my applications, if you want I can share the code with you. You can see the component at work in [2]... This is just a prototype... So be kind with the design and so for... Just click on the magnifying glass icon and go to the images tab. Regards, Ernesto References, 1-http://wiquery-plugins-demo.appspot.com/demo/?wicket:bookmarkablePage=:com.wiquery.plugins.demo.SlideDeckPage 2-http://infomar.javaprovider.net/infomaresme/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Advice wanted about polished component set with Wicket
Yeah I have tried learning from some stuff in wicketstuff and Wiquery so someday I will be ready to contribute. -Original Message- From: Ernesto Reinaldo Barreiro reier...@gmail.com Date: Wed, 9 Nov 2011 18:48:17 To: users@wicket.apache.org Reply-To: users@wicket.apache.org Subject: Re: Advice wanted about polished component set with Wicket Hi, There are at least two projects out there that already do some integration with jquery... So, it might be a good idea to take a look at them:-) On Wed, Nov 9, 2011 at 6:15 PM, anantasthana anant.a...@gmail.com wrote: I tried to integrate the JCaurosel and Ajax Vertical slider which is basically a lazy load scroll bar. We have integrated a vertical slider on [1]. I have also integrated a component similar to jCarousel in one of my applications, if you want I can share the code with you. You can see the component at work in [2]... This is just a prototype... So be kind with the design and so for... Just click on the magnifying glass icon and go to the images tab. Regards, Ernesto References, 1-http://wiquery-plugins-demo.appspot.com/demo/?wicket:bookmarkablePage=:com.wiquery.plugins.demo.SlideDeckPage 2-http://infomar.javaprovider.net/infomaresme/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicket-dojo wrappers
I've had a number of requests, so I'll upload this bit of code here so people can have a look. I know there's room for improvement in the code that exists, and a ton that needs to be done. There's a wicket-dojo project on GitHub https://github.com/vijaykiran/wicketstuff-dojo that's much cleaner, with many more advanced integrations. However, that project lacked implemented wrappers for Dojo Dijits, which is what I wanted most. The code there also seemed a bit daunting, so I began a project to make wrappers I could understand, and extend, and learn both Wicket and Dojo in the process. This is the results so far. The few advantages it has over the GitHub code I've linked to are... 1) A bunch of useful Dijits wrapped in a way I hope is fairly clear and extensible (it's getting better). 2) All the wrappers use fluent APIs 3) You can generally set a field, or your own model, interchangeably. For instance, if you want to set a Title, you can usually setTitle(String title) or setTitleModel(IModelString titleModel). Being able to control the model is extremely useful. 4) You can generally set attributes in your HTML and these values will initialize the fields/models in the wrappers on a non-Ajax render. Values can then be dynamically altered from there via Ajax (as with user interaction). 5) Using setIntermediateChanges(true) will generally update the wrappers' fields/models upon user interactions with the Dijit, via Ajax (you can also add DojoAjaxUpdatingBehaviors to get your own callbacks). This extends to things like stack container updating its models for selected child index and id. There's still much to do. It's not the cleanest code yet. It doesn't handle animations or fx or anything but presenting widgets. It's part of a larger project so I haven't presented a real build, just the code. If people are interested, I can cleave this off and provide a true maven build. David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Modal Window with Ajax in Firefox
Hi,
thanks for help. I ended with very similar solution.
2011/11/9 Andrea Del Bene adelb...@ciseonweb.it
Hi,
I think the best solution would be replace modal window's content instead
of closing it and opening a new one. Considering your example you should
completely remove notifierWindow. The new code for HomePage would be like
this:
public HomePage(final PageParameters parameters) {
final ModalWindow homeWindow = new ModalWindow(modal);
final FeedbackPanel notifier = new FeedbackPanel(homeWindow.**
getContentId());
notifier.setOutputMarkupId(**true);
final HomePanel homePanel = new HomePanel(homeWindow.**getContentId())
{
@Override
public void performAction(**AjaxRequestTarget target) {
replaceWith(notifier);
target.addComponent(notifier);
//homeWindow.close(new AjaxRequestTarget(getPage()));
// notifierWindow.show(target);
}
};
//the same code
Hope this could help you.
Hi,
I uploaded quickstart that reproduces error to github at
https://github.com/iref/**modaltest https://github.com/iref/modaltest .
2011/11/2 Andrea Del Beneadelb...@ciseonweb.it
Hi,
can you reproduce your problem in a separate project and upload it
somewhere? It would help much to understand if this problem is a bug and
to
find a solution.
--**
--**-
To unsubscribe, e-mail:
users-unsubscribe@wicket.**apa**che.orghttp://apache.org
users-unsubscribe@**wicket.apache.orgusers-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@wicket.**apache.orgusers-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Jan Ferko,
julyl...@gmail.com
wicket-dojo wrappers (correction)
Sorry for the repost, but this list doesn't take attachments I guess, so I've upload the code at https://github.com/zenbones/WicketDojo I've had a number of requests, so I'll upload this bit of code here so people can have a look. I know there's room for improvement in the code that exists, and a ton that needs to be done. There's a wicket-dojo project on GitHub https://github.com/vijaykiran/wicketstuff-dojo that's much cleaner, with many more advanced integrations. However, that project lacked implemented wrappers for Dojo Dijits, which is what I wanted most. The code there also seemed a bit daunting, so I began a project to make wrappers I could understand, and extend, and learn both Wicket and Dojo in the process. This is the results so far. The few advantages it has over the GitHub code I've linked to are... 1) A bunch of useful Dijits wrapped in a way I hope is fairly clear and extensible (it's getting better). 2) All the wrappers use fluent APIs 3) You can generally set a field, or your own model, interchangeably. For instance, if you want to set a Title, you can usually setTitle(String title) or setTitleModel(IModelString titleModel). Being able to control the model is extremely useful. 4) You can generally set attributes in your HTML and these values will initialize the fields/models in the wrappers on a non-Ajax render. Values can then be dynamically altered from there via Ajax (as with user interaction). 5) Using setIntermediateChanges(true) will generally update the wrappers' fields/models upon user interactions with the Dijit, via Ajax (you can also add DojoAjaxUpdatingBehaviors to get your own callbacks). This extends to things like stack container updating its models for selected child index and id. There's still much to do. It's not the cleanest code yet. It doesn't handle animations or fx or anything but presenting widgets. It's part of a larger project so I haven't presented a real build, just the code. If people are interested, I can cleave this off and provide a true maven build. David
Wicket 1.4, IBM WebSphere Portal 6.1 and AJAX issue and solution
Hi!, Recently, when we were developing an application for IBM WebSphere Portal 6.1 (JSR286 Portlet) using Wicket 1.4.18, we had problems with forms that use AjaxButton component for submitting. After some investigations, we realized that the problem was on the javascript side (wicket-ajax.js). The url encoded by IBM WebSphere Portal 6.1 has the following pattern: /wps/myportal/!ut/p/c5/_very_very_long_string_ended_with_a_slash/ and when wicket-ajax.js do the submit, builds the following url /wps/myportal/!ut/p/c5/_very_very_long_string_ended_with_a_slash/wicket:ajax=true As you can see, this is an invalid URL: after the / must be an ? not an Fortunately, the solutions is easy. Here are the patch: Index: wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js === --- wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js (revision 1176907) +++ wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js (working copy) @@ -1192,7 +1192,7 @@ // reconfigure the form form.target=iframe.name; - form.action=this.request.url + wicket:ajax=true; + form.action=this.request.url + (this.request.url.indexOf(?)-1 ? : ?) + wicket:ajax=true; form.method=post; form.enctype=multipart/form-data; form.encoding=multipart/form-data; do you think this solution is fine? If it is, can this fix be included in the next release of wicket 1.4.x? Best regards, José Antonio Matute keen*soft *email: matu...@keensoft.es web: http://www.keensoft.es CONFIDENCIALIDAD: La presente comunicación y, en su caso, los ficheros que lleve adjuntos, pertenecen exclusivamente a las personas a las que va dirigido y puede contener información confidencial. Si usted no es el destinatario de este mensaje (o la persona responsable de su entrega), considérese advertido de que lo ha recibido por error y que cualquier uso, difusión, reenvío o copia están prohibidos legalmente. Si ha recibido este mensaje por error, por favor notifíquelo al remitente y proceda a destruirlo inmediatamente. This message and the attached documents may contain privileged/confidential information and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient (or responsible for delivery of the message to such a person) be advised that you have received this message in error and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this message in error please notify it to the sender and destroy it immediately
Design patterns for panel navigation
Hi, Panels are great to encapsulate functionality in reusable units. In order to reuse some panels in different contexts, I need to make the navigation elements they contain configurable. For example, consider a form whose post-submit navigation and cancel link destination need to be configurable. Are there any recommended best-practices for this? Which patterns do you use to accomplish this? My first method was to make the form panel abstract with getPageClass() and getPageParameters() as abstract methods to provide navigation configuration. This proved too limitative as it forced the navigation destination to be bookmarkable pages. My current method is form the form to receive a strategy implementation responsible for setting the response page on form submit and constructing a cancel link. This allows to use bookmarkable pages, page references, ect. as navigation destinations. Do you have any better alternatives to suggest? Regards, Bertrand - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-dojo wrappers
I think your attachment didn't make it to the mailing list. Maarten On Wed, Nov 9, 2011 at 7:52 PM, David Berkman david.berk...@glu.com wrote: I've had a number of requests, so I'll upload this bit of code here so people can have a look. I know there's room for improvement in the code that exists, and a ton that needs to be done. There's a wicket-dojo project on GitHub https://github.com/vijaykiran/wicketstuff-dojo that's much cleaner, with many more advanced integrations. However, that project lacked implemented wrappers for Dojo Dijits, which is what I wanted most. The code there also seemed a bit daunting, so I began a project to make wrappers I could understand, and extend, and learn both Wicket and Dojo in the process. This is the results so far. The few advantages it has over the GitHub code I've linked to are... 1) A bunch of useful Dijits wrapped in a way I hope is fairly clear and extensible (it's getting better). 2) All the wrappers use fluent APIs 3) You can generally set a field, or your own model, interchangeably. For instance, if you want to set a Title, you can usually setTitle(String title) or setTitleModel(IModelString titleModel). Being able to control the model is extremely useful. 4) You can generally set attributes in your HTML and these values will initialize the fields/models in the wrappers on a non-Ajax render. Values can then be dynamically altered from there via Ajax (as with user interaction). 5) Using setIntermediateChanges(true) will generally update the wrappers' fields/models upon user interactions with the Dijit, via Ajax (you can also add DojoAjaxUpdatingBehaviors to get your own callbacks). This extends to things like stack container updating its models for selected child index and id. There's still much to do. It's not the cleanest code yet. It doesn't handle animations or fx or anything but presenting widgets. It's part of a larger project so I haven't presented a real build, just the code. If people are interested, I can cleave this off and provide a true maven build. David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-dojo wrappers
OK, hadn't seen your last message On Thu, Nov 10, 2011 at 5:42 AM, Maarten Bosteels mbosteels@gmail.comwrote: I think your attachment didn't make it to the mailing list. Maarten On Wed, Nov 9, 2011 at 7:52 PM, David Berkman david.berk...@glu.comwrote: I've had a number of requests, so I'll upload this bit of code here so people can have a look. I know there's room for improvement in the code that exists, and a ton that needs to be done. There's a wicket-dojo project on GitHub https://github.com/vijaykiran/wicketstuff-dojo that's much cleaner, with many more advanced integrations. However, that project lacked implemented wrappers for Dojo Dijits, which is what I wanted most. The code there also seemed a bit daunting, so I began a project to make wrappers I could understand, and extend, and learn both Wicket and Dojo in the process. This is the results so far. The few advantages it has over the GitHub code I've linked to are... 1) A bunch of useful Dijits wrapped in a way I hope is fairly clear and extensible (it's getting better). 2) All the wrappers use fluent APIs 3) You can generally set a field, or your own model, interchangeably. For instance, if you want to set a Title, you can usually setTitle(String title) or setTitleModel(IModelString titleModel). Being able to control the model is extremely useful. 4) You can generally set attributes in your HTML and these values will initialize the fields/models in the wrappers on a non-Ajax render. Values can then be dynamically altered from there via Ajax (as with user interaction). 5) Using setIntermediateChanges(true) will generally update the wrappers' fields/models upon user interactions with the Dijit, via Ajax (you can also add DojoAjaxUpdatingBehaviors to get your own callbacks). This extends to things like stack container updating its models for selected child index and id. There's still much to do. It's not the cleanest code yet. It doesn't handle animations or fx or anything but presenting widgets. It's part of a larger project so I haven't presented a real build, just the code. If people are interested, I can cleave this off and provide a true maven build. David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: What is the difference between wicket panel and webmarkupcontainer?
A Panel has its own markup while WebMarkupContainer reuses the markup of its parent. On 11/10/2011 06:50 AM, raju.ch wrote: Hi, could some please tell me the difference between wicket panel and webmarkupcontainer? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/What-is-the-difference-between-wicket-panel-and-webmarkupcontainer-tp4022541p4022541.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
AW: What is the difference between wicket panel and webmarkupcontainer?
See RecursivePanel in wicket-examples: It *is* a panel (having its own markup in RecursivePanel.html) and utilizes a WebMarkupContainer for its rows. Sven -Ursprüngliche Nachricht- Von: raju.ch [mailto:raju.challagun...@gmail.com] Gesendet: Donnerstag, 10. November 2011 07:44 An: users@wicket.apache.org Betreff: Re: What is the difference between wicket panel and webmarkupcontainer? Thank you for your reply..Can you elaborate with an example or do send me the link if you have it.? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/What-is-the-difference-between-wi cket-panel-and-webmarkupcontainer-tp4022541p4022609.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
