<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.comp.java.wicket.devel">
    <title>gmane.comp.java.wicket.devel</title>
    <link>http://blog.gmane.org/gmane.comp.java.wicket.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23992"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23984"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23983"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23981"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23979"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23978"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23972"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23968"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23960"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23959"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23932"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23920"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23918"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23914"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23906"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23898"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23893"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23892"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23878"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.java.wicket.devel/23870"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23992">
    <title>WicketStuff owners - please review</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23992</link>
    <description>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.co</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-30T07:06:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23984">
    <title>TeamCity on wicketstuff.org</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23984</link>
    <description>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 re</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-29T13:59:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23983">
    <title>wicketstuff-core migration guide on wiki</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23983</link>
    <description>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
*&lt;http://wicketstuff.org/confluence/display/STUFFWIKI/NEW+-+WicketStuff+Core+-+Migration+Guide&gt;

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/continuu</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-28T19:52:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23981">
    <title>donate source : Wicket reaction game...?</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23981</link>
    <description>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/

</description>
    <dc:creator>Nino Saturnino Martinez Vazquez Wael</dc:creator>
    <dc:date>2008-11-27T23:37:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23979">
    <title>[VOTE] Consistent naming for Wicket Stuff projects</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23979</link>
    <description>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?

</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-27T21:54:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23978">
    <title>[VOTE] End of Life wicket-contrib-gmap?</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23978</link>
    <description>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
</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-27T21:49:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23972">
    <title>Igor - FileUploadField change in 1.4-rc1 - WHY?</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23972</link>
    <description>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&lt;FileUpload&gt;()) ??

Thanks!

</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-25T05:33:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23968">
    <title>[VOTE] Organizing Wicket Stuff / Regular Release Schedule?</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23968</link>
    <description>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 wi</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-24T18:13:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23960">
    <title>please make RequestLogger.log(RequestData, SessionData) protected</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23960</link>
    <description>Could we please make the method above protected (rather than private).  This
makes it very simple to do something like this:

    &lt; at &gt;Override
    protected IRequestLogger newRequestLogger() {
        return new RequestLogger() {
            &lt; at &gt;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 = r</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-19T23:31:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23959">
    <title>Update SCM in Wicket 1.3.x branch</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23959</link>
    <description>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:
&lt;scm&gt;
 &lt;connection&gt;scm:svn:http://svn.apache.org/repos/asf/wicket/trunk&lt;/connection&gt;

 &lt;developerConnection&gt;scm:svn:https://svn.apache.org/repos/asf/wicket/trunk&lt;/developerConnection&gt;

 &lt;url&gt;http://svn.apache.org/viewvc/wicket/trunk&lt;/url&gt;
&lt;/scm&gt;

to:
&lt;scm&gt;
 &lt;connection&gt;scm:svn:
http://svn.apache.org/repos/asf/wicket/branches/wicket-1.3.x/&lt;/connection&gt;
 &lt;developerConnection&gt;scm:svn:
https://svn.apache.org/repos/asf/wicket/branches/wicket-1.3.x/&lt;/developerConnection&gt;

 &lt;url&gt;http://svn.apache.org/viewvc/wicket/branches/wicket-1.3.x/&lt;/url&gt;
&lt;/scm&gt;

[1] - http://www.wickettraining.com/continuum/
Thanks!
</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-19T14:46:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23932">
    <title>Continuum Build Server Set Up</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23932</link>
    <description>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

</description>
    <dc:creator>Jeremy Thomerson</dc:creator>
    <dc:date>2008-11-18T16:21:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23920">
    <title>RES: Drop wicket:link</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23920</link>
    <description>What do you mean? Like recursively detect other pages?

    &lt;ul wicket:id="menus"&gt;
      &lt;li&gt;&lt;a href="ControlCenter.html"&gt;ControlCenter&lt;/a&gt; &lt;br/&gt;
  &lt;ul&gt;
          &lt;li&gt;&lt;a href="controlcenter/Users.html"&gt;Users&lt;/a&gt;&lt;/li&gt;
          &lt;li&gt;&lt;a href="controlcenter/Departments.html"&gt;Departments&lt;/a&gt;&lt;/li&gt;
        &lt;/ul&gt;
      &lt;/li&gt;
      &lt;li&gt;&lt;a href="Profile.html"&gt;Profile&lt;/a&gt;
      &lt;li&gt;&lt;a href="../Home.html"&gt;Home&lt;/a&gt;
    &lt;/ul&gt;

Something that could parse this template?

-----Mensagem original-----
De: Nino Saturnino Martinez Vazquez Wael
[mailto:nino.martinez-PgGV5VupRVRaa/9Udqfwiw&lt; at &gt;public.gmane.org]
Enviada em: segunda-feira, 17 de novembro de 2008 17:25
Para: dev-X1ioaoK8vgJd/SJB6HiN2Ni2O/JbrIOy&lt; at &gt;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:

</description>
    <dc:creator>Bruno Cesar Borges</dc:creator>
    <dc:date>2008-11-17T19:37:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23918">
    <title>RES: Drop wicket:link</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23918</link>
    <description>Maybe, but to migrate a codebase wouldn't be that harder. People will only have to replace &lt;wicket:link&gt; with &lt;span wicket:id="myid"&gt; 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 &lt;wicket:link&gt; 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 &lt;wicket:link&gt;

I say +1

[]'s
Bruno Borges

-----Mensagem original-----
De: James Carman [mailto:james-+RXjrjb0GfS5azolltMz9laTQe2KTcn/&lt; at &gt;public.gmane.org]
Enviada em: segunda-feira, 17 de novembro de 2008 17:07
Para: dev-X1ioaoK8vgJd/SJB6HiN2Ni2O/JbrIOy&lt; at &gt;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 &lt;brunoborges-UAukS</description>
    <dc:creator>Bruno Cesar Borges</dc:creator>
    <dc:date>2008-11-17T19:15:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23914">
    <title>Drop wicket:link</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23914</link>
    <description>This might sound crazy, but what about dropping the support for the tag &lt;wicket:link&gt; ? :-)

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
   &lt;ul wicket:id="menus"&gt;
     &lt;li&gt;&lt;a href="Users.html"&gt;Users&lt;/a&gt;&lt;/li&gt;
     &lt;li&gt;&lt;a href="Departments.html"&gt;Departments&lt;/a&gt;&lt;/li&gt;
   &lt;/ul&gt;

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 é p</description>
    <dc:creator>Bruno Cesar Borges</dc:creator>
    <dc:date>2008-11-17T19:03:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23906">
    <title>Client-Side Image Map...</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23906</link>
    <description>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 &lt;area&gt; elements within the &lt;map&gt;.  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).

</description>
    <dc:creator>James Carman</dc:creator>
    <dc:date>2008-11-15T14:43:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23898">
    <title>Wicket, url rewriting and shared resources browser caching</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23898</link>
    <description>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:

&lt;script type="text/javascript"
src="resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js;jsess</description>
    <dc:creator>Dominik Drzewiecki</dc:creator>
    <dc:date>2008-11-14T21:20:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23893">
    <title>[ANNOUNCE] Apache Wicket 1.4 release candidate 1</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23893</link>
    <description>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</description>
    <dc:creator>Frank Bille</dc:creator>
    <dc:date>2008-11-13T14:06:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23892">
    <title>Problem closing a ModalWindow... (JIRA: Wicket-1120) not in 1.3.5??</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23892</link>
    <description>Why this isn't in Wicket 1.3.5 as it was supposed to?

Problem with frames and ModalWindow combination is a showstopper for us. To make our situation
even more difficult, our application is going to production in only two weeks. This was kind of unexpected,
because we have never before encountered web site or application that does not work with frames.
So adding them to application was not regarded as something that could cause any errors in the project.
Any idea when this fix will really be in release version?

Regards,
  Mikko Pukki
</description>
    <dc:creator>Mikko Pukki</dc:creator>
    <dc:date>2008-11-13T14:05:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23878">
    <title>Provide an easy switch for TextField's browser autocomplete</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23878</link>
    <description>I'm finding myself coding the same code over and over, on different  
projects (for different customers), having to provide a subclass of  
TextField with an option to setAutocomplete(boolean) where it will add(or  
not) the 'autocomplete' tag for &lt;input type="text"&gt; during the componentTag  
method - saving from creating an instance of AttributeModifier

What about adding that to TextField?

Regards,
Bruno
</description>
    <dc:creator>bruno.borges-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-11-12T13:08:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23870">
    <title>Class Cast Exception on WebSession</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23870</link>
    <description>I'm brand new to wicket and going through the book "Wicket in Action".  I've
ran into a problem that I can't seem to get around, maybe I am over thinking
it.  I have a class I wrote that extends
org.apache.protocol.http.WebSession, and I am getting a ClassCastException
when I try to return my session.  This is the cheese store example from the
book if anyone is familiar with it.  Here is the code in question:

*From my class that extends WebPage:
*
public CheeseStoreSession getCheeseStoreSession()
    {
        return (CheeseStoreSession) getSession(); *//exception occurs right
here*
    }

I've confirmed that the getSession method is returning an object of type
WebSession.
*
My custom session class looks like this:*


package com.manning.example;

import org.apache.wicket.Request;
import org.apache.wicket.Response;
import org.apache.wicket.Session;
import org.apache.wicket.protocol.http.WebSession;


public class CheeseStoreSession extends WebSession
{
    private Cart cart = new Cart();


    protected Che</description>
    <dc:creator>Brad Gardner</dc:creator>
    <dc:date>2008-11-08T18:44:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.java.wicket.devel/23869">
    <title>Move WICKET-1902 to version 1.3.6</title>
    <link>http://comments.gmane.org/gmane.comp.java.wicket.devel/23869</link>
    <description>Just a remind to update issue WICKET-1902 to be fixed in version 1.3.6

regards,
Bruno Borges
blog.brunoborges.com.br
+55 21 76727099

"The glory of great men should always be
measured by the means they have used to
acquire it."
- Francois de La Rochefoucauld
</description>
    <dc:creator>Bruno Borges</dc:creator>
    <dc:date>2008-11-07T18:45:57</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.java.wicket.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.java.wicket.devel</link>
  </textinput>
</rdf:RDF>
