gmane.comp.java.wicket.devel

TeamCity wizard?

Jeremy Thomerson — 2008-12-04T02:38:21

First - wicketstuff.org (Confluence) seems to be down (TeamCity / Maven repo are both up). Okay - Can a wicketstuff.org admin take a look at the build results of the GMap2 project (as part of wicketstuff-core): http://www.wicketstuff.org/teamcity/viewLog.html?buildId=2479&buildTypeId=bt35&tab=buildResultsDiv Can we install those on a local repo on that machine so that it has access to them for the builds? Or is there another way? Thanks!

Wicketstuff-core pom?

Nino Saturnino Martinez Vazquez Wael — 2008-12-03T10:52:25

Hi guys I've just pulled my openlayers project from the wicketstuff-core on stuff svn. It does not build. Because it are unable to find the wicketstuff core pom... Where are it available from the ordinary wicketstuff repo? nino-martinez-vazquez-waels-computer-367:openlayers-parent nino$ mvn eclipse:eclipse [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. GroupId: org.wicketstuff ArtifactId: wicketstuff-core Version: 1.4-SNAPSHOT Reason: Unable to download the artifact from any repository org.wicketstuff:wicketstuff-core:pom:1.4-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.wicketstuff:wicketstuff-core for project: null:openlayers-parent:pom:null for project null:openlayers-parent:pom:null at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.wicketstuff:wicketstuff-core for project: null:openlayers-parent:pom:null for project null:openlayers-parent:pom:null at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.wicketstuff:wicketstuff-core' not found in repository: Unable to download the artifact from any repository org.wicketstuff:wicketstuff-core:pom:1.4-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.wicketstuff:wicketstuff-core at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:603) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1366) ... 17 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.wicketstuff:wicketstuff-core:pom:1.4-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:556) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:331) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200) ... 20 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Wed Dec 03 11:47:01 CET 2008 [INFO] Final Memory: 1M/2M [INFO] ------------------------------------------------------------------------

How about removing the timestamps from the snapshot builds?

Timo Rantalaiho — 2008-12-02T15:51:25

Hello, Would it be OK if the snapshots built by TeamCity would always just have SNAPSHOT as the version, without the timestamp that they currently have http://www.wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.4-SNAPSHOT/ I think that Buildr probably doesn't recognise the timestamped versions but just gets the ones without the timestamp in the version number, dating from 30 June. And probably the old snapshots aren't worth filling the disk with them either. And if this is OK, who could do it? Best wishes, Timo

Wait confirmation from ModalWindow

Eric Lemaitre — 2008-12-01T23:02:47

Hi all, I have a confirmation ModalWindow (I expect "yes" or "no") which opens above another ModalWindow which allows to update a TextArea and a List which feed a DropDownBox : final ConfirmationModel confirmationModel = new ConfirmationModel(this); final DialogWindow confirmPanel = new DialogWindow("confirmPanel", confirmationModel); add(confirmPanel); public class ConfirmationModel extends Observable implements Serializable ....... // Confirm to Add something AjaxLink add = new AjaxLink(ADD_COMMAND) { < at >Override public void onClick(AjaxRequestTarget target) { confirmPanel.setTitle(getString("confirm")); confirmPanel.setContent(new DialogPanel(confirmPanel, parmeters)); confirmationModel.setCommand(ADD_COMMAND); confirmPanel.show(target); // 1st OPTION: I WOULD LIKE TO BE KEPT WAITING HERE UNTIL CONFIRMATION OCCURS FROM confirmPanel // Here below Add command dynamically updates TextArea and List (session.getUserNotesList()) which feed a DropDownBox (notes) target.addComponent(notesForm.get("textArea")); // VITAL for the DropDownList to refresh its inner list when an item is removed target.addComponent(form.get("notes")); String id = myNotesChapter + "_" + (session.getUserNotesList().size() + 1); Note noteModel = (Note)form.getModelObject(); Note note = new Note(id, (Person)(session.getUser()), textArea.getContent()); session.getUserNotesList().add(note); dao.addNoteToUser(session.getUser().getLogin(), note); textArea.setModelValue(new String[1]); ................................................................ public void update(Observable observable, Object object) { String command = ((ConfirmationModel)observable).getCommand(); String result = object.toString(); AjaxRequestTarget target = new AjaxRequestTarget(getPage()); if(command.equals(ADD_COMMAND)) { // 2nd OPTION: REPORT THE DYNAMICAL UPDATES WITH AjaxRequestTarget HERE ........................... _______________________________________________________________________ So with 1st option I cannot block smartly the confirmation confirmPanel until I get "yes" or "no" just after line: confirmPanel.show(target); And with 2nd option where I try to deport dynamical updates inside the update() method of Observer/Observable all works fine BUT the elements don't refresh properly, I have to close then open again the ModalWindow with its DropDownList and TextArea to check updates happened. Is there either a way to block the confirmation ModalWindow until answer comes, or to make the refresh in deported update() work properly? TIA, best regards.

WicketStuff owners - please review

Jeremy Thomerson — 2008-11-30T07:06:49

Hello everyone. I have completed the bulk of the work planned on the WicketStuff reorg discussed earlier this week. A status report is located at [1] below. If you own a WicketStuff project, PLEASE review [2] below - there are still quite a few things I need community input on to complete. A brief summary of input needed: - There are quite a few projects in trunk that are working with Wicket 1.3 and have had work in trunk since the 1.3 branch was created. Since trunk is technically for 1.4 development, I would suggest moving these to the Wicket 1.3 branch. - There are a couple of projects in trunk that are already on 1.4, but I have not heard from the project owner as to whether they want their project moved into wicketstuff-core. - Wicket-SECURITY - I have no idea what to do with this one since Maurice is no longer with us. Would anyone like to take ownership of it (and commit to keep the work up-to-date on it)? [1] - *http://tinyurl.com/647hjz* [2] - *http://tinyurl.com/64tdor* Quick summary of work done: - 21 projects migrated (including examples projects) - 32 removed from trunk - 73 svn commits :) - quite a few open questions - see above Thank you!

TeamCity on wicketstuff.org

Jeremy Thomerson — 2008-11-29T13:59:51

Who owns the wicketstuff.org server? Since TeamCity has been continually having problems building against SF repo, I set up Continuum on my server. It has been working fine. I'd like to see us get some permanent setup that allows built artifacts to be deployed to the wicketstuff.org maven repo since that's the repo everyone has in their POM for wicketstuff projects. This will be especially important now that so many wicketstuff projects will be able to be built together and released together. I see two options: 1 - We switch from TeamCity to Continuum on the wicketstuff.org site. This would require someone with shell access installing Continuum or giving me access to do so. It's a VERY simple setup. Also, if we switch to Continuum and then have problems we'll know instantly that there is a network issue between the wicketstuff.org server and SF (since my server has not had the problem and been running Continuum against SF for weeks). 2 - Someone gives me information so that my server can SCP to the repo on wicketstuff.org. My server could continue to run the builds and then SCP the artifacts to wicketstuff.org's repo. This would be fine with me as well. Whatever works best - I'd just like us to have some Continuous Integration actually running and deploying snapshots and release artifacts. The next step will be to get the central maven repo to mirror the wicketstuff.orgreleased artifacts to central. I don't mind working through this at some point.

wicketstuff-core migration guide on wiki

Jeremy Thomerson — 2008-11-28T19:52:30

I have created a guide to migrating your project under the new wicketstuff-core parent project. If you own a WS project, you should consider doing this as soon as possible so that your project will be included in the 1.4 release (and even earlier in the RC2 release) when Wicket releases the same - we will be releasing all projects under wicketstuff-core in sync with Wicket's release. * http://wicketstuff.org/confluence/display/STUFFWIKI/WicketStuff+Core+-+Migration+Guide * Let me know if you see any additions that need to be made. PS - One really nice thing about restructuring everything to follow conventions is that we will be able to utilize maven plugins such as the site plugin. Here's an example of a current site generated for all the wicketstuff-core projects: http://www.wickettraining.com/wicketstuff-core/ Here's a link for the build server building wicketstuff-core: http://www.wickettraining.com/continuum/projectGroupSummary.action?projectGroupId=12

donate source : Wicket reaction game...?

Nino Saturnino Martinez Vazquez Wael — 2008-11-27T23:37:28

Hi guys I'd like to donate the source for the wicket reaction game to the wicket examples or somewhere... What do you say to that? You can see a demo here : http://wicketgames.ninosbox.thruhere.net/

[VOTE] Consistent naming for Wicket Stuff projects

Jeremy Thomerson — 2008-11-27T21:54:28

I am beginning the WS reorg as noted in previous emails. You can monitor progress here: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/ As we move projects into the wicketstuff-core, I would like to see us rename them consistently, getting rid of the prepended "wicket-contrib-" or "wicketstuff-". This would mean that when we release WicketStuff 1.4 (when Wicket 1.4 is released) that if you are using that project, you would need to update your POM to the new name. Please vote: [ ] - YES - I would like consistent naming [ ] - NO (convincing reason) PS - I feel like I'm starting a lot of vote threads - should I not be? Any suggestions? I would like to efficiently get this reorg done, but I am leery of just moving other people's projects around and making changes without permission. Feelings / thoughts?

[VOTE] End of Life wicket-contrib-gmap?

Jeremy Thomerson — 2008-11-27T21:49:24

I am starting to work on the WicketStuff reorg as the community voted to do. In doing so, I noticed that wicket-contrib-gmap is still set up to compile against 1.3.0-incubating-snapshot. Also, we know that Iulian has said he is no longer maintaining it. In light of this, I propose the following vote: [ ] - YES, please create a branch in the Wicket Stuff repo just for abandoned projects and move wicket-contrib-gmap into that branch. [ ] - NO (please provide convincing reason). For those who say "I'm still using it" - you'll still be able to - from the abandoned branch, you can build your own release, just like you must be doing now. But it helps new users not be as confused with the multiple projects, and trying to use one that's dead. PS - I will probably be sending more votes along like this as I go through the repo trying to organize it. If you have suggestions, please let us know. Thanks, Jeremy Thomerson http://www.wickettraining.com

Igor - FileUploadField change in 1.4-rc1 - WHY?

Jeremy Thomerson — 2008-11-25T05:33:14

Igor, It has come up a couple of times on the user list, but in 1.4rc1 there was a change to FileUploadField to make it always use a model. Now, the new FileUploadField("id") constructor is practically useless, and I would venture to say that tons of apps out there (like mine do in numerous places), have always just used the ID constructor since nothing else was needed. Why the change? At the very least, could we make the ID-only constructor call super(id, new Model()) ?? Thanks!

[VOTE] Organizing Wicket Stuff / Regular Release Schedule?

Jeremy Thomerson — 2008-11-24T18:13:13

Hello everyone, I would like to get your opinion on an idea regarding the Wicket Stuff project(s). As you are familiar with, Wicket Stuff is where anyone can create anything related to Wicket, small or large. One problem that new users of Wicket (and us "old" users) come across is that there is a lot of stuff in there, and not all of it is well maintained, and there aren't specific releases of many of the projects. So, you have to build it yourself and figure out which version matches which Wicket version, etc... What I would like to know is if everyone thinks it would be good to have a subset of WS projects that are structured in a way that they are always in sync with the Wicket versions. IOW, there would be two branches - 1.3.X and 1.4 (trunk), just like Wicket has. There would be a parent module and all of the modules that wanted to participate would be structured under it. They would all release in sync with Wicket. For instance, when Wicket releases 1.4-RC2, we would cut a release of this wicket-stuff-structured (bad name) and all of the projects under it at 1.4-RC2. I haven't yet figured out how interim releases would work (new features are added to a WS project and it wants to cut a release between wicket releases) or if that matters. This would not have to effect all WS projects - someone could continue to add projects to WS just like they do today. This would simply create a sub-tree of projects that are in the structured / scheduled release area. For those that don't want to be part of that structure, they could continue operating as they do today. So, here's the vote: [ ] - NO! We should leave Wicket Stuff like it is - a free-for-all with no structure [ ] - YES - I would like to see at least the most used Wicket Stuff projects structured so that they mirror Wicket, and a release is produced for each Wicket release. [ ] - Maybe - I have a better idea (perfect!) Also - please add the following: 1 - Would you be interested in helping to maintain such a thing. (If we had two or three of the owners of the larger projects on board, I don't think it would be too hard to keep the codebase of this in sync with Wicket core.) 2 - What projects do you own (and by your vote we'll see if you want those projects to be included in this restructuring).

please make RequestLogger.log(RequestData, SessionData) protected

Jeremy Thomerson — 2008-11-19T23:31:54

Could we please make the method above protected (rather than private). This makes it very simple to do something like this: < at >Override protected IRequestLogger newRequestLogger() { return new RequestLogger() { < at >Override protected void log(RequestData rd, SessionData sd) { // do my custom logging HERE } }; } ALSO - it would be real nice if at the same time you extract that creation of the AppendingStringBuffer to a method, so that the log method now looks like: protected void log(RequestData rd, SessionData sd) { if (log.isInfoEnabled()) { log.info(createStringBuffer(rd, sd, true); } } protected final void createStringBuffer(RequestData rd, SessionData sd, boolean includeRuntimeInfo) { ... all of the stuff that was taken out of log that creates the ASB if (includeRuntimeInfo) { Runtime runtime = Runtime.getRuntime(); long max = runtime.maxMemory() / 1000000; long total = runtime.totalMemory() / 1000000; long used = total - runtime.freeMemory() / 1000000; asb.append(",maxmem="); asb.append(max); asb.append("M,total="); asb.append(total); asb.append("M,used="); asb.append(used); asb.append("M"); } return asb; }

Update SCM in Wicket 1.3.x branch

Jeremy Thomerson — 2008-11-19T14:46:09

I'm adding the Wicket 1.3.x branch to the Continuum build server [1], and it won't build because the SCM tag is incorrect after the branch. Could a committer please change the SCM tag in the parent pom to reflect the correct location? Here's the code: Change: scm:svn:http://svn.apache.org/repos/asf/wicket/trunk scm:svn:https://svn.apache.org/repos/asf/wicket/trunk http://svn.apache.org/viewvc/wicket/trunk to: scm:svn: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.3.x/ scm:svn: https://svn.apache.org/repos/asf/wicket/branches/wicket-1.3.x/ http://svn.apache.org/viewvc/wicket/branches/wicket-1.3.x/ [1] - http://www.wickettraining.com/continuum/ Thanks!

Continuum Build Server Set Up

Jeremy Thomerson — 2008-11-18T16:21:08

Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum

RES: Drop wicket:link

Bruno Cesar Borges — 2008-11-17T19:37:46

What do you mean? Like recursively detect other pages?

Something that could parse this template? -----Mensagem original----- De: Nino Saturnino Martinez Vazquez Wael [mailto:nino.martinez-PgGV5VupRVRaa/9Udqfwiw< at >public.gmane.org] Enviada em: segunda-feira, 17 de novembro de 2008 17:25 Para: dev-X1ioaoK8vgJd/SJB6HiN2Ni2O/JbrIOy< at >public.gmane.org Assunto: Re: Drop wicket:link And another thing it could make autolink parser able to look in other packages aswell for pages... Currently theres no support for autolinking to pages not in the same package.. Nino Saturnino Martinez Vazquez Wael wrote:

RES: Drop wicket:link

Bruno Cesar Borges — 2008-11-17T19:15:36

Maybe, but to migrate a codebase wouldn't be that harder. People will only have to replace with and add the Java component. And if the codebase has a good test coverage, Wicket will point out automatically places where the component should be added. Another solution to do a smooth migration, is to simply continue to interpret during the first release of (temporary name) AutoLinkMarkupContainer, but still requiring to add the component. This way, only Java code would need to sufer from changes. Then, on a future release, definitely drop the support of I say +1 []'s Bruno Borges -----Mensagem original----- De: James Carman [mailto:james-+RXjrjb0GfS5azolltMz9laTQe2KTcn/< at >public.gmane.org] Enviada em: segunda-feira, 17 de novembro de 2008 17:07 Para: dev-X1ioaoK8vgJd/SJB6HiN2Ni2O/JbrIOy< at >public.gmane.org Assunto: Re: Drop wicket:link I'd say -1. This would be a nightmare on existing codebases. 2008/11/17 Bruno Cesar Borges public.gmane.org>: *************************************************************************************************** "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas." "Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel." ***************************************************************************************************

Drop wicket:link

Bruno Cesar Borges — 2008-11-17T19:03:59

This might sound crazy, but what about dropping the support for the tag ? :-) People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that. Example: # Java AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer("menus"); # HTML

What do you guys think? Cheers, Bruno *************************************************************************************************** "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas." "Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel." ***************************************************************************************************

Client-Side Image Map...

James Carman — 2008-11-15T14:43:18

I've created a JIRA with an attached implementation of a new client-side image map. https://issues.apache.org/jira/browse/WICKET-1936 Basically what it does is it borrows some ideas from the VelocityPanel class, in that it generates its own markup. So, it's able to "attach" the AbstractLink objects to elements within the . I think this is a good replacement for ImageMap, since it's not so limiting (works with existing Images and allows any AbstractLink, not just Links). My patch also deprecates ImageMap, so that we can remove it in 1.5 (provided it makes it into 1.4; we could also back port it to 1.3.x).

Wicket, url rewriting and shared resources browser caching

Dominik Drzewiecki — 2008-11-14T21:20:47

I have recently started optimizing our wicket based application in terms of reducing the number of requests sent by the browser. This can be easily achieved by assuring the resources (js, css, gif, png and so on) get proper headers and get cached by the browser so that only a mere HTTP 304 response gets sent by the server or, even better, no request from the browser is sent at all. I noticed that when the session tracking is based on url rewriting, resources attached programmatically (as opposed to the resources "inlined" in the html templates) which urls are rendered by the o.a.w.markup.html.internal.HeaderResponse render(ResourceReference) and further by a.o.w.RequestCycle encodeUrlFor(IRequestTarget), get their respective session id appended to the returned url. Adding a simple AjaxFallbackLink to the page results in the following contibutions to the head section of the rendered page: The same applies to the images inserted using autolinking or manually as ResourceReference: The result, in terms of client-side caching, is that the resources are cached only within the scope of the current session (a they are keyed in the client-cache by the url containing sessionid). All of those resources are easily referrable outside of the session and accessing them without the jsessionid suffix results in an appropriate resource returned as well no additional session allocated on the server (based on jconsole & wicket-jmx observations). My suggestion is that the resource links should be generated without jsessionid (although I realize that when the cookie based session tracking is enabled they are referred to within the scope of the session as the request sent for such a resource contais a cookie with a session id...). Maybe all of the shared resources should be treated uniformly - as if they were accessed without a session. Cheers, Dominik Drzewiecki

[ANNOUNCE] Apache Wicket 1.4 release candidate 1

Frank Bille — 2008-11-13T14:06:51

The Apache Wicket team is proud to present the first release candidate of Apache Wicket 1.4. This is the first Wicket version with java 1.5 as minimum requirement. Eager people click here to download the distribution, others can read further: * http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1 We thank you for your patience and support. The Wicket Team - Apache Wicket Apache Wicket is a component oriented Java web application framework. With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Apache Wicket makes developing web-apps simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written with plain Java and HTML. You can find out more about Apache Wicket on our website: * http://wicket.apache.org - This release The Apache Wicket team is proud to announce the availability of the third milestone release of our first java 1.5 Wicket version: Apache Wicket 1.4-m3. This is the first release with java 1.5 as a minimum. Almost everything has been converted to java 1.5. If you find something missing, please help us and send a message to the dev< at > or user< at > list. - Migrating from 1.3 If you are coming from Wicket 1.3, you really want to read our migration guide, found on the wiki: * http://cwiki.apache.org/WICKET/migrate-14.html h3. Downloading the release You can download the release from the official Apache mirror system, and you can find it through the following link: * http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1/ For the Maven and Ivy fans out there: update your pom's to the following, and everything will be downloaded automatically: org.apache.wicket wicket 1.4-rc1 Substitute the artifact ID with the projects of your liking to get the other projects. Please note that we don't prescribe a Logging implementation for SLF4J. You need to specify yourself which one you prefer. Read more about SLF4J here: http://slf4j.org - Validating the release The release has been signed by Frank Bille, your release manager for today. The public key can be found in the KEYS file in the download area. Download the KEYS file only from the Apache website. * http://www.apache.org/dist/wicket/1.4-rc1/KEYS Instructions on how to validate the release can be found here: * http://www.apache.org/dev/release-signing.html#check-integrity - Reporting bugs In case you do encounter a bug, we would appreciate a report in our JIRA: * http://issues.apache.org/jira/browse/WICKET - The distribution In the distribution you will find a README. The README contains instructions on how to build from source yourself. You also find a CHANEGELOG-1.4 which contains a list of all things that have been fixed, added and/or removed since the first release in the 1.4 branch. - Release Notes - Wicket - Version 1.4-RC1 ** Sub-task * [WICKET-1624] - ServletWebRequest.getRelativePathPrefixToContextRoot() double decodes servlet path * [WICKET-1805] - Allow to change charset in StringRequestTarget: change CharSet used by the OutStream as well ** Bug * [WICKET-550] - Use WebRequestEncoder everywhere a query string is constructed * [WICKET-861] - NumberFormatException with UrlCompressingWebRequestProcessor in WicketTester * [WICKET-1120] - Problem closing a ModalWindow when used through an IFrame * [WICKET-1180] - Converters : final vs non final * [WICKET-1220] - Component.visitParents visits the calling component as well * [WICKET-1311] - Improper HTML escaping for most wicket components and extensions * [WICKET-1376] - Using AbstractAjaxTimerBehavior and mounting that page gives exception * [WICKET-1425] - appendToInit() method is not called in class DatePicker * [WICKET-1436] - Unable to use properties file when generating XML files * [WICKET-1496] - DataTable.html does not validate (HTML 4.01/XHTML-Strict) * [WICKET-1535] - ExternalLink JavaScript not working in FF 3 * [WICKET-1565] - AbstractTransformerBehavior can't be added to a page * [WICKET-1582] - WicketTester executeAjaxEvent onclick generating non-AJAX response * [WICKET-1583] - NPE in EnclosureResolver * [WICKET-1627] - AbstractRequestTargetUrlCodingStrategy improper user of URLEncoder.encode * [WICKET-1634] - ClassName needs conversion from Path to dotted notation in AutoLinkResolver * [WICKET-1648] - AbstractRequestTargetUrlCodingStrategy(line 174) throws confusing exception. It would be better redirect to 404-page in this case. * [WICKET-1652] - Hard-coded quotes in xml prologue * [WICKET-1704] - ResourceStreamRequestTarget.configure set wrong ContentLength for non-ascii characters * [WICKET-1719] - StringResourceModel may fail to format numbers using MessageFormat * [WICKET-1728] - remove obsolete check from LocalizedImageResource * [WICKET-1730] - RfcCompliantEmailAddressValidator accepts whitespace and tab * [WICKET-1731] - When used in inherited markup, tries to load a class with an illegal name * [WICKET-1736] - Allow Access to AutoCompleteTextField AutoCompleteBehavior * [WICKET-1737] - wicketTester does not find HTML mark-up if custom location is used. * [WICKET-1740] - RequestCycle.urlFor modifies page parameters * [WICKET-1745] - Get rid of raw Model usage * [WICKET-1746] - gecko: ajax javascript reference rendering problem * [WICKET-1754] - form action URLs in non-Wicket forms not rewritten * [WICKET-1755] - In html Include component isAbsolute method returns false for an absolute path in unix-like systems * [WICKET-1756] - Generify PropertyColumn * [WICKET-1759] - Typo in method name: AttributeModifier#replaceAttibuteValue * [WICKET-1765] - Extending from org.apache.wicket.Page causes StackOverflowError * [WICKET-1776] - Quickstart's archetype misses maven compiler configuration * [WICKET-1777] - Overflow when setting Expires header in WebResource * [WICKET-1780] - NPE in feedback panel * [WICKET-1787] - AjaxSubmitLink in Internet Explorer does not work with Wicket's automatically genreated id's * [WICKET-1788] - "Invalid procedure call or argument" on AJAX call with IE7 * [WICKET-1789] - Border fails to render if its contents are not visible by default * [WICKET-1796] - When markup type is XML, getLocalizer().getString( "xyz", (WebPage) ) throws Exception * [WICKET-1797] - Bug with default RadioChoice "for" attribute on label generation. * [WICKET-1799] - wicket-extensions has unused reference to commons-collections.jar * [WICKET-1809] - wicket does not compile for 1.3.x because of method usage > jdk 1.4 * [WICKET-1816] - Wicket 1.3.4 violates servlet standard, Glassfish spews warnings * [WICKET-1818] - wicket:id attribute with a value containing spaces generates invalid markup * [WICKET-1820] - Embedded forms do not support multipart * [WICKET-1829] - MarkupComponentBorder skips first tag in MarkupStream * [WICKET-1834] - Invalid Cookie Names for persistence used according to RFC (doesn't work in tomcat 6.x) * [WICKET-1836] - RequestUtils.toAbsolutePath() should handle dot paths in the url * [WICKET-1839] - IAjaxIndicatorAware/WicketAjaxIndicatorAppender with AutoCompleteTextField doesn't work * [WICKET-1843] - Disabling RadioGroup via authorization strategy does not disable contained Radio buttons * [WICKET-1846] - Dutch text message for NumberValidator incorrect * [WICKET-1857] - Unfound markup information is not entirely cached even in deployment mode * [WICKET-1870] - MinimumLengthValidator throws NullPointerException * [WICKET-1901] - Spelling error in fonts list in CaptchaImageResource * [WICKET-1903] - RadioChoice disable certain choice bug * [WICKET-1904] - CheckBox incorrectly converts its model value when a custom Boolean converter is installed - again ** Improvement * [WICKET-1055] - Add ability to have Radio and RadioGroup not related via component hierarchy * [WICKET-1103] - Support validator and package level resource bundles * [WICKET-1115] - DownloadLink fix that encodes non-ASCII file names properly * [WICKET-1138] - Better warning of design errors during development * [WICKET-1692] - on Java 6+ DatePicker.localize should use DateFormatSymbols.getInstance(Locale) instead of new DateFormatSymbols(Locale) to support DateFormatSymbolsProviders * [WICKET-1696] - CaptchaImageResource - should take an IModel instead of String for captcha-text * [WICKET-1744] - RadioChoice , MultiListChoice, DropDownChoice, ListChoice - model handlers should take a Collection instead of the more specific List * [WICKET-1748] - 304 Last Modified responses should include an Expires header * [WICKET-1749] - Want to add SignInPanel_ja.html * [WICKET-1753] - Allow WicketFilter to be configured to skip certain paths * [WICKET-1767] - Protection against Session Fixation * [WICKET-1770] - PagingNavigation's javadoc contains malformed html snippet * [WICKET-1782] - Protection against CSRF (cross-site request forgery) attacks * [WICKET-1801] - Make AbstractDefaultAjaxBehavior.findIndicatorId() protected * [WICKET-1802] - Propertyresolver could be more informative * [WICKET-1810] - StringRequestTarget is bloated and needs some care * [WICKET-1824] - AbstractDecimalConverter * [WICKET-1830] - Include Component Path in Generated Markup * [WICKET-1833] - Ungenerifying IConverter, because overriding Component.getConverter() generated warnings in user code * [WICKET-1844] - Wizard button implementations should not be final * [WICKET-1853] - Wicket should allow non-formcomponents to plug into form's FormComponent#updateModel event * [WICKET-1854] - What's the point of requiring IConverters to be superclasses of the objects they convert? * [WICKET-1891] - AjaxLazyLoadPanel shouldn't call getLoadingComponent(String) in constructor * [WICKET-1895] - AjaxButton should have a constructor to set the label ** New Feature * [WICKET-1720] - Add clearLocalizerCache to Application JMX bean * [WICKET-1877] - Provide Option to Specify XML Attribute Name in getDebugSettings().setOutputComponentPath(true); ** Wish * [WICKET-1758] - Make DiskPageStore#getSessionFolder protected (rather than private)