+0
You will need to fix a lot of unit tests I figure.
Martijn
On 7/25/07, Al Maw <[EMAIL PROTECTED]> wrote:
Hi folks,
Although some people don't really care what their URLs look like, lots
of people do.
If you use UrlCompressingWebCodingStrategy you can get the actual
parameter values for i
On 7/25/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
On 7/24/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Therefore, the javadocs
> for 1.2 *most likely* don't belong on the Apache site.
but we could put them on sf.net and link to there from wicket.apache.org?
We are aware of the multiple site issue and working on it. There are
only so many hours in a day.
As for the 1.2 javadocs: we need to see if that is feasable: the code
is not from Apache, nor hosted. For instance we will not provide 1.2
releases using the Apache mirrors. These will remain and con
and for the casual reader: [1] means:
[1]
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310561&fixfor=12312533
On 7/24/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I
I monitor the issue list in JIRA and there are still about 27 issues
unresolved for beta3 [1].
I could build a release, but I want to spend our time effectively. The
book doesn't get written on its own, nor does money grow on the tree
in my backyard! (GOD I wish that were true on both accounts!)
I tried something that should throw an exception IMO.
public class Foo implements Serializable {}
public Index extends WebPage {
private Foo foo = null;
public Index() {
Form form = new Form("form");
form.add(new TextField("foo", new PropertyModel(this, "foo")));
}
}
I think that depending on the catch all for spring is probably the
best for Wicket. If you really want to depend on the individual
modules, it is merely a matter of adding excludes to your
wicket-spring dependency and including those you do want.
The reason being: most people (at least those that
I'm on the subject in the book, so I need an answer now. Are we or aren't we?
pro: better feedback
con: need to acquire new feedback resource bundles for all languages.
I'm 0 on the issue, but do need a decision quickly. The solution may
follow later.
I appreciate the argument that people don'
1. This type of questions belong on the user list, please repost there
if you have any remaining questions after this reply
2. Did you read http://incubator.apache.org/wicket/exampledropdownchoice.html ?
Martijn
On 7/20/07, saleh <[EMAIL PROTECTED]> wrote:
Hi Threre,
I am struggling to sort t
ehcache seems to be Apache licensed, so there is no immediate reason
to put it into wicketstuff.
Given that the extensions project is used to mature components and
features, I think it is a logical place for it to be in.
But given the limited usage: it is only used for the markup cache,
correct?
On 7/11/07, Gwyn Evans <[EMAIL PROTECTED]> wrote:
I did want to respond to Johan's comment, but it's /not/ a -1 vote,
especially in view of your reasons above - "0" if anything.
I didn't want to imply as such, but I would not hold a grudge if you
would -1 it. It is late in the game, so ...
Mar
On 7/11/07, Gwyn Evans <[EMAIL PROTECTED]> wrote:
I do - that's the reason that we /always/ slip releases, as there's
/always/ just one more "let's tidy this up" change.
It also means that committers don't feel any big urge to ship
releases, as they're still tweaking as they want, while normal
LongAndVerboseClassNameOfTheComponent), so
not having the parameter there makes the learning curve less.
Martijn
On 7/10/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
Sorry for not voting in this reply, but do you really consider the
constructor with type parameter confusing for noobs?
-Matej
On 7/10/07, M
Working on the Book I found a difference between 1.2 and 1.3:
In the following setup if you click on the 'link' a couple of times,
you see that the list in the session grows, and that it is reflected
in each page render.
Now, press the back button and continue clicking on the link. You will
see
Matej had the brilliant idea of auto discovery of the type parameter
for FormComponents when they use a PropertyModel or
CompoundPropertyModel. In order to remove confusion for noobs, and to
point out that there is a Better Way (tm) I propose the following
options:
For those wondering if it is st
If it doesn't have major API consequences, I don't mind getting it in.
How much extra memory are we talking about? Is the usecase for the
border to be used as much as the AttributeModifier? Or is it more used
once or twice on a page?
We had to optimize one of our pages to remove the AttributeMod
Killed long argument
Summary:
* disable it in development profile, but turn it on in
quickstart#init with comment
* provide link to switch it on on exception page
* add debug profile
* switch markup location to 'on' in development mode
* add Java based profiles, with non-deprecated web.xml init p
We still need to do something with the downloads page. Al, I think you
had some ideas for that?
Martijn
On 7/4/07, Al Maw <[EMAIL PROTECTED]> wrote:
Sean Sullivan wrote:
> The Wicket home page:
>
> http://incubator.apache.org/wicket/
>
> has a link to
>
>
http://people.apache.org/dist/incubato
Use the releases/wicket-1.3.0-beta2 branch instead
Martijn
On 7/2/07, Vincent Demay <[EMAIL PROTECTED]> wrote:
Hi all,
First of all, congrats for graduation and beta2 release.
I've just checked out the new beta2 tags from svn and I was surprised to
see 1.3.0-SNAPSHOT in all pom.xml instead of
Igor just committed a maven archetype to our svn and we still have a
quickstart and examples project that seem a bit out of place for our
main distribution.
trunk/
archetypes/
jdk-1.4/
wicket-quickstart
jdk-1.5/
wicket-examples/
testing/
README
NOTICE
LICENSE
4J here: http://slf4j.org
- Validating the release -
The release has been signed by Martijn Dashorst, 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.3.0-be
I have enough +1's from PMC members, so I have started the upload to
the mirroring system. I'll send a general announcement tomorrow with
download details and I hope that maven also has updated its
repository.
If that is done, and I still have energy I'll document the process for
what its worth (
+1
On 6/29/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
We are on 1.3.1 now but i see there is a 1.4.0
and i have to use it anyway in another project (thats also using wicket)
so i could also upgrade wicket to 1.4.0
johan
--
Wicket joins the Apache Software Foundation as Apache Wicket
Joi
Release can be found here:
http://people.apache.org/~dashorst/releases/apache-wicket-1.3.0-beta2
Martijn
On 6/28/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
The build now includes guice and ioc, and the release notes (list of
fixed JIRA issues)
[ ] I have checked the distribution
The build now includes guice and ioc, and the release notes (list of
fixed JIRA issues)
[ ] I have checked the distribution and +1 its release
[ ] I haven't checked the distribution and +0 its release
[ ] I have checked the distribution and -1 its release because...
I will try to upload this to
I found this one on the Apache site [1]:
If A Distribution Contains Code Under Several Licenses, Should It
Contain Several License Files?
No - all license information should be contained in the LICENSE file.
When a distribution contains code under several licenses, the LICENSE
file should conta
On 6/26/07, Frank Bille <[EMAIL PROTECTED]> wrote:
On 6/26/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Because it is 1.1 ... Apache doesn't ship 1.1 (prohibits it).
But what does this mean to us? If we are allowed to ship ASL2 code which
includes ASL1.1 code aRat shou
Because it is 1.1 ... Apache doesn't ship 1.1 (prohibits it).
Martijn
On 6/26/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
[X ] I checked the distribution, and I +1 the release of them
why doesn't RAT like the Diff package?
it is ASL (not 2.0 but 1.1)
johan
On 6/26/07,
and [1] is: http://issues.apache.org/jira/browse/INFRA-1278
/me reminds him not to [2]
Martijn
[2] work after 12am.
--
Wicket joins the Apache Software Foundation as Apache Wicket
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicke
The changes are:
- no mass migration of users
- added footer to lists with info on how to unsubscribe from the list
Martijn
On 6/26/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I filed (a slightly modified version) with the infra team [1].
Migration will be imminent soon.
M
I filed (a slightly modified version) with the infra team [1].
Migration will be imminent soon.
Martijn
--
Wicket joins the Apache Software Foundation as Apache Wicket
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http:/
Release notes:
Release Notes - Wicket - Version 1.3.0-beta2
** Bug
* [WICKET-4] - Page.onBeginRequest() [and consequently
.onAttach()] not called when form on page is submitted.
* [WICKET-40] - Parameters of nice URL's pages with 'sensitive' characters
* [WICKET-65] - Handle String ar
This is a vote to release the Apache Wicket 1.3.0-beta2 (note the
missing -incubating) distribution I just uploaded to my
people.apache.org account page.
I know we are anxious to get this one out the door, but I urge all of
us to go through the release and check if you find anything wrong with
it
I am going to cut the release now. Unit tests run
Martijn
--
BREAKING NEWS: Wicket joins the Apache Software Foundation as Apache Wicket
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
On 6/24/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] new, mass migration of subscribers from sf.net
[EMAIL PROTECTED] new, mass migration of subscribers from sf.net
It seems this won't be possible. Some states frown upon transferring
privacy sensitive inform
What are the side effects?
We have been down this road too many times and we keep forgetting them
(or ignoring until we can't bare them) I'd hate to not fix this one
once and for all.
Martijn
--
BREAKING NEWS: Wicket joins the Apache Software Foundation as Apache Wicket
Join the wicket communi
On 6/22/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
And there's lots of stuff we need to do as well.
Such as http://issues.apache.org/jira/browse/WICKET-691
Martijn
--
BREAKING NEWS: Wicket joins the Apache Software Foundation as Apache Wicket
Join the wicket c
On 6/24/07, Frank Bille <[EMAIL PROTECTED]> wrote:
> On 6/24/07, Frank Bille <[EMAIL PROTECTED]> wrote:
> > Does Infra need to involved in domain transfers?
I just sent a question regarding the DNS entries to infra@
Martijn
--
BREAKING NEWS: Wicket joins the Apache Software Foundation as Apac
On 6/24/07, Frank Bille <[EMAIL PROTECTED]> wrote:
Does Infra need to involved in domain transfers?
Yes, but that is another issue according to me. We can resolve that seperately.
Martijn
--
BREAKING NEWS: Wicket joins the Apache Software Foundation as Apache Wicket
Join the wicket community
On 6/24/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> I. Reply-To: Header [X] yes [ ] no
> NOTE: [EMAIL PROTECTED] -> [EMAIL PROTECTED]
> II. Message Trailer [ ] yes [X] no
Anyone wondering about what the message trailer is? Answer is here:
http://mail-archives.apach
I think everyone ran into it at one time... I know I did. Last time I
think Igor threw some issues with repeaters into the mix, and then the
discussion went dead.
Martijn
On 6/24/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Yep, you read that right. I just found out that if you explicitly
def
[1] is of course: http://issues.apache.org/jira/browse/INFRA-1260
Martijn
On 6/24/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
This is a proposal for the tasks infra needs to take to make us a TLP.
Please review if I have misspelled something, or if there is something
missing.
All,
This is a proposal for the tasks infra needs to take to make us a TLP.
Please review if I have misspelled something, or if there is something
missing. I took the draft from [1], and adjusted it to our specific
needs.
Martijn
The board has agreed to create the Wicket project.
To aid in th
The benefits of unix:
find jdk-1.4/wicket -name "*.js" | xargs grep -E "rag|rop"
delivers jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js
Martijn
On 6/22/07, Sean Sullivan <[EMAIL PROTECTED]> wrote:
Is there drag/drop code in svn.apache.org? Wh
On 6/21/07, Upayavira <[EMAIL PROTECTED]> wrote:
Martijn Dashorst wrote:
> Now that we are a top level project we need to transfer our project
> resources to our new home.
>
> This thread is used to make an inventory of things that need to be
> moved. I'll monitor the
On 6/21/07, Upayavira <[EMAIL PROTECTED]> wrote:
Seems like you've got most things. Which is reasonable seeing as likely
you nicked this all from your own graduation guide :-)
Having commit access to the incubator repository makes me feel like:
I've got the power hey yeah heh
I've got the powe
All,
I've updated the sf.net site with our news. Also tried to update any
old links, and published our beta1 release.
Martijn
--
BREAKING NEWS: Wicket joins the Apache Software Foundation as Apache Wicket
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very impor
Now that we are a top level project we need to transfer our project
resources to our new home.
This thread is used to make an inventory of things that need to be
moved. I'll monitor the thread using the following issue:
http://issues.apache.org/jira/browse/WICKET-675
Please see the graduation
coatl: this springs mod_python and related bits out of
the HTTPD project into its own TLP. Gregory Trubetskoy is its Chair.
* Apache Wicket: this is a light webapp framework for Java, graduating
from the Incubator into its own TLP. Martijn Dashorst is the new
AFAIK, the eclipse quickstart video still works (apart from some
package names, changed code and version numbers)
http://wicket.sourceforge.net/wicket-quickstart/demos/EclipseDemo.html
Martijn
On 6/20/07, tnjtn1 <[EMAIL PROTECTED]> wrote:
I followed that http://wicket.sourceforge.net/ file.
I'd rather not put it in a separate project. The number of sub
projects is growing again and if we can provide a way to maximize
reuse of project infrastructure, then I'm for that.
I tried looking in the archives for a discussion on moving them into
extensions, but didn't find it. I guess the re
On 6/19/07, Watter <[EMAIL PROTECTED]> wrote:
This is no big deal to add, but out of curiosity, is this something new? Our
builds have been running fine without this on all previous 1.3-SNAPSHOTs,
and if it's a dependency of Wicket now, why is it not indicated in the
Wicket pom? I assume it's bec
Yes,
You need to define your own logging implementation. For log4j this is:
org.slf4j
slf4j-log4j12
(add version yourself, best put in a dependencyManagement part).
Martijn
On 6/19/07, Watter <[EMAIL PROTECTED]>
.org/bamboo/
On 6/19/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>
> When running maven from the root:
>
> mvn clean test
>
> I get the following test failure:
>
> [surefire] Running
> org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactoryTest
>
When running maven from the root:
mvn clean test
I get the following test failure:
[surefire] Running
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactoryTest
[surefire] Tests run: 4, Failures: 1, Errors: 0, Time elapsed: 0.492
sec FAILURE !!
Anyone committed something
-1 on the streamline. I'm not going to go through and rewrite my
chapters of the book yet *again*.
Can we just agree to keep the API stable?
Martijn
On 6/18/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
because wicket is so flexible that you can do almost everything with just
one component!
On 6/18/07, Al Maw <[EMAIL PROTECTED]> wrote:
Just an idea, but when you go tagging, etc. a quick e-mail to
wicket-private saying what you're up to might be nice for avoidance of
doubt and toe-treading. :-)
Sure, I was in the process of building a release, but got side tracked
by a rather press
I didn't push the released button because I hadn't actually built it :)
I had forgotten that the release can also be 'unreleased', like I did
for the previous version.
I'll remove the tags and do those steps again, this one seems really
like one I want to have anyway :)
I'll document the steps
The top level should *not* be updated, only the wicket-examples one.
The top level (as is noted in that file) will be overwritten when we
release using the subproject NOTICE files (see release.sh)
Martijn
On 6/14/07, Al Maw <[EMAIL PROTECTED]> wrote:
Martijn Dashorst wrote:
> JHighlig
On 6/13/07, Oleg Taranenko <[EMAIL PROTECTED]> wrote:
Wednesday, June 13, 2007, 10:44:32 AM, you wrote:
> It is in fact the project you are trying to run that is at fault here.
> Wicket doesn't prescribe which logging framework one should use.
> Therefore the examples projects need to choose thei
It is in fact the project you are trying to run that is at fault here.
Wicket doesn't prescribe which logging framework one should use.
Therefore the examples projects need to choose their own logging
implementation. This holds for the wicket-examples from Apache as well
as for wicket stuff relate
Welcome! Enjoy your stay at Wicket Stuff!
Martijn
On 6/11/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
Dear developers,
Please welcome Grégory Maes among the WicketStuff developers.
Grégory has filed [1]several patches on WicketStuff Dojo, and has
shown a long-term interest in t
On 6/10/07, Al Maw <[EMAIL PROTECTED]> wrote:
Sure. We can't exclude commons-logging, as it's a genuine dependency for
their code, so to do so would be wrong. But we can fix their
non-optional compile-scoped dependencies on servlet-api, log4j, logkit
and avalon.
There is still one problem in ou
Can we fix the commons-logging thing too? I.E. in dependency
management force commons-logging 1.0.4, though not specify it? And
possibly excluding it from the spring dependency?
I don't like to fix the world, but this forces us to ship logkit,
avalon and other stuff I don't want to support.
Mart
Are we already an Apache project? So how are those pages outdated?
Martijn
On 6/10/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Matthew R Hanlon:
> I thought someone would like to know that there is a typo on the Wicket
> Ajax Counter example page,
> http://www.wicketframework.org/Exam
On 6/10/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
whats wrong with 2.4? it is java 1.4.
It's newer than 2.3. And I don't have the time to hunt for a jar with
a compatible license that is traceable (i.e. somewhere in the jar).
Geronimo seems like a good candidate:
http://repo1.maven.org/mave
But that is servlet api 2.4 or 2.5, not 2.3...
Martijn
On 6/10/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
afir, jetty has their own servlet api jar if that helps.
-igor
On 6/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>
> All,
>
> After Noel (rightfully) w
All,
After Noel (rightfully) wagged his finger for our beta 2 release, I
have been going through our notice and license files.
- spring was not in a notice file, but we do ship it in wicket-examples
- joda time was not in a notice file, but we do ship it
- wicket listed in the notice file a CC d
So for the tree and treetable nothing changes with respect to wicket
1.2? Both are in extensions, and a new tree replaces the old, pre ajax
tree?
Martijn
On 6/10/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
I think it is much better.
As for the TreeTable: The new TreeTable that I plan (without t
I did some soul searching and of course the servletapi jar seems a bit
out-of-the-blue. The license states it comes from the Jakarta Tomcat
effort, and after some digging it was found on the maven 1 repository:
http://repo1.maven.org/maven/servletapi/jars/
It seems to be ASL 1.1 licensed and
Given the concern raised by Noel and some other things I noticed, I'm
going to retract this distribution and start a new vote in a couple of
hours.
Martijn
On 6/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Nah,
It is in the distribution to prevent the nice event of depende
Nah,
It is in the distribution to prevent the nice event of dependency
hunting, and we always shipped log4j in our 1.2.x zips (including
commons-logging and the servlet api)
Martijn
On 6/10/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
wicket core shipping log4j? thats wrong anyway.
only exa
public boolean onCloseButtonClicked(AjaxRequestTarget target) {
return true;
}
});
form.add(new AjaxLink("showModalRD") {
public void onClick(AjaxRequestTarget target) {
modalRD.show(target);
}
});
--------
Without code, which wicket version you are using and other important
information particular to your problem (like: do you use a panel in
the modal window, how many times can you open the modal window before
this happens, etc), we can't help you!
Asking questions in a smart way:
- English version:
On 6/10/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
What's the deal with
http://svn.apache.org/viewvc/incubator/wicket/tags/wicket-1.3.0-incubating-b
eta-2/licenses/log4j-license.txt?revision=545721&view=markup ?
It is a left over from the good old days: 1.2.8 (the first log4j
version we inc
All,
I have prepared our beta 2 release and uploaded it to my
people.apache.org site [1]
You know the drill: vote if you think this release will is legally
sound and will be approved by the IPMC. I have run 'rat' on the
distribution, and you can see the report in the release directory.
[ ] Yes,
On 6/7/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Until we find a usecase for the creation of the stack elements at a
> later stage, I'm fine with killing the metadata for now. We have the
> ability for keeping it, so it is easily re-instated.
That sounds good to me. Do you want to impleme
On 6/7/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
The memory footprint is bothering me way more than the performance hit
is tbh. I would be ok with keeping this if we clear it after
rendering.
Another option might be to see if the stack trace could be compressed.
I now keep the string repre
Actually, the metadata could be removed at the end of the request, or
as part of the render check (at a cost of processing time), so the
memory footprint would not be noticable after the first render. The
effect on the performance is not mitigated with that.
The metadata currently is not cleared,
This is the proposal for our end game to a final release of Wicket 1.3.0
- build 1.3.0-beta 2 this weekend, release next week
- after the 20th start work on release candidates:
These will not be official releases, because I want to move quickly on
these builds. So at least once every week we (I?
I've scanned other models as well, and will apply this to
AbstractPropertyModel too.
I also included/created a unit test for this issue.
See http://issues.apache.org/jira/browse/WICKET-621
Martijn
On 6/6/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
I'm not sur
All,
I'm not sure the usecase is general, but in our application we have a
couple of classes that implement IDetachable, but not IModel, and
these are put into a CompoundPropertyModel
The thing is that the CompoundPropertyModel does an instanceof check
for IModel instead of the slightly more gen
On 6/4/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> i am getting a bit tired of all those threadlocals that have to be
> cleaned... I already discussed this with matej and i thing we should
> give the RequestCycle metadata... then we can store any thing we want
> and it is auto cleanup
Agree
I have queried a couple of times the status. It seems that we just don't know.
I suggest cutting a release, calling it beta 2 and let it go through
the hoops of the IPMC.
My biggest problem at the moment with a release is that it always is
the code of one week ago: that is the time it takes from
I've added you to the wicket-stuff-admin group.
The page you mentioned generates its contents, and does not have a
list of all projects. So I'm not sure what you want to change.
Martijn
On 6/2/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
I'd like to edit this page:
http://wicketstuff.o
tiste, Juergen
+1 non-binding: C. Bergstöm, Philip.
Thanks for voting!
Martijn
On 5/25/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
In the licensing mumbo jumbo, graduation proceedings and fixing bugs
for 1.3.0 we forgot to officially vote wicket-contrib-velocity in. So
with
These were specifically introduced by Al.
Martijn
On 6/1/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
Hi there,
I think there is a problem in JIRA as all issues resolved for
"1.3-beta1" are labelled as "trunk".
If you don't mind, I'd like to move all fixed issues from trunk to
1.3
Or
Aah... those old web 1.0 days...
Martijn
On 6/1/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Yeah, good idea. Too bad we can't use ;)
Eelco
On 5/31/07, Al Maw <[EMAIL PROTECTED]> wrote:
> Eelco Hillenius wrote:
> >> +1... But just to make sure: is the DEPLOYMENT configuration going t
For the component use check I specifically removed any
non-wicket-markup stack elements, otherwise the stack trace contains
too much information. Though I'm not sure if you are referring to
that.
Martijn
On 5/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
Which part do you mis then?
because
On 5/31/07, Sylvain Wallez <[EMAIL PROTECTED]> wrote:
For the real story behind John Banana Qwerty, see
http://bluxte.net/blog/2006-04/21-11-35.html :-D
Now, that is a good read :)
Martijn
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. D
On 5/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
and it will make the output more xhtml
Heh, the world is moving away from xhtml: html5 will be the next big
thing. Even the w3c seems to think so. That said, lower casing
attributes should not be a problem for html5 as well, iiuc.
Martijn
On 5/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
the problem that testing all these is not just very simple
Now it is just a hash lookup but then we need to iterate
over all the keys everytime and check for equals ignoring case.
Can't we put them in there always using lower case?
Martijn
Is already in place, but not everyone checks the logs, and apparently
you also didn't notice the message :)
INFO - Application- [QuickStartApplication] init:
Wicket extensions initializer
INFO - WebApplication - [QuickStartApplication] Started
Wicket version 1.3.0-in
On 5/30/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
JPQ is tha man!
Tha bananman! [1,2]
Martijn
[1] http://blog.caraldi.com/jbq/
[2] http://en.wikipedia.org/wiki/Bananaman
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicke
Close observers to our graduation proposal would already have noticed
our newest member to the Wicket PPMC, but it is always a good time to
celebrate happy events:
Please join me in welcoming Jean-Baptiste Quenot to the Wicket PPMC.
Congratulations Jean-Baptiste!
Martijn
--
Join the wicket com
http://issues.apache.org/jira/browse/WICKET-599
On 5/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> On 5/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > With the proposed 'powered by wicket' button on each page, shifting to
> > > deployment mode will be a big drive once you get to p
On 5/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> With the proposed 'powered by wicket' button on each page, shifting to
> deployment mode will be a big drive once you get to production. :D
Agreed. We keep on disagreeing on the best default, but if the being
in development is that visible
There is some real activity regarding Wicket in Japan. It is hard for
a westerner like myself to come to grips with it, but stories like
these:
http://translate.google.com/translate?u=http%3A%2F%2Fjapan.zdnet.com%2Foss%2Fstory%2F0%2C3800075264%2C20349166%2C00.htm&langpair=ja%7Cen&hl=en&ie=UTF8
a
As Eelco voiced his opinion on the matter, I feel obligated to voice
mine as well.
I think the default must remain development because it helps people
out-of-the-box for the 99% usecase. Before they ever reach production
they need to have a good and solid development experience. For new
comers th
On 5/29/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> And we have that component: the inspector bug... We moved it to
> wicket-examples because it was a security risk.
Sure. But if it would be part of the 'development dashboard' it
wouldn't be a security risk as we don't want people to run in
1 - 100 of 709 matches
Mail list logo
