People,
We could use everyone's help. I just came across some stale
documentation, particularly RequestCycle, which stated in large
caption that it is not meant for being subclassed (which is nonsense
of course). I'm a bit afraid that the API docs may be stale in more
places.
If you (including u
On 6/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
As we only link to the file, and I don't want to go around trying to
find a new, correctly licensed file with good antecedents, I am going
to disable the explicit inclusion of our dependencies. Only the
wicket-examples WAR archive will keep
I submitted an issue to add a fallback version of AjaxSubmitButton. It has
attached to it the completed implementation of the class.
https://issues.apache.org/jira/browse/WICKET-634
Couldn't find where it had been discussed before whether it was needed or
not, but since I needed it and implemen
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
Martijn Dashorst wrote:
> 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 s
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
Martijn Dashorst wrote:
> Any one have other/better/alternative ideas?
I don't think we should call something a release candidate if it has
issues in JIRA that we intend to fix before the final release. A release
candidate should be just that - we only push it out when we're fairly
sure things are
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
* 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/ExampleAjaxCounter.html. Under the first
> heading ("Ajax Counter") second paragraph: oblibatory; should be
> obligatory. Not being snotty, j
Well, if I remember correctly the outcome of the discussion was
DataView into core, DataTable stays in extensions.
Yeah, it was. But not because I wanted that :)
Although I wouldn't mind DataTable in core.
I think a Tree (the new one :) ) belongs to the core. But the
TreeTable really can live
Done.
Eelco Hillenius wrote:
> Yeah, that sounds right.
>
> Eelco
>
> On 6/5/07, Al Maw <[EMAIL PROTECTED]> wrote:
>> Hi folks,
>>
>> I'm pretty sure our slf4j dependencies are very wrong.
>>
>> I see the root pom.xml in trunk has a dependencies section that doesn't
>> actually include slf4j-api
On 6/10/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>a) remove the old (kinda unsupported) tree from extensions (is
> anyone even use it?)
+1
Cool.
>b) move the current Tree and TreeTable* from core to extensions
> (sight, i know we moved it into core just recently)
Don't know yet
Is the obvious too much so? Ask Craig about the provanance.
--- Noel
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
243 left. Sorry for the spam, I changed the fix version of all
issues assigned to me. I looked at the Subversion commit revision
and if it was before 531508 I set beta1, otherwise beta2.
See http://svn.apache.org/viewvc?view=rev&revision=531508
--
Jean-Baptiste Quenot
aka John Banana Qw
whats wrong with 2.4? it is java 1.4.
-igor
On 6/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
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/
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) wagged his finger for our be
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) 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
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
> the servletapi jar seems a bit out-of-the-blue.
And it evolves, too, e.g., the newest listeners.
--- Noel
a) remove the old (kinda unsupported) tree from extensions (is
anyone even use it?)
+1
b) move the current Tree and TreeTable* from core to extensions
(sight, i know we moved it into core just recently)
Don't know yet.
c) move the new Tree into core.
So the 'new new' tree is inc
Is there any feature set available for the "new" treetable?
/Regards Mats
On 6/10/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
Yes, exactly. That's what I want.
-Matej
On 6/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> So for the tree and treetable nothing changes with respect to wicket
Yes, exactly. That's what I want.
-Matej
On 6/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
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]
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 think it is much better.
As for the TreeTable: The new TreeTable that I plan (without those
neat lines but also without layout problems) is not alive yet. And the
one that we already have should be moved back to extensions. I don't
think we need (nor should have) TreeTable in core.
-Matej
On
if it is really better then do it now before we put out rcs. also what
happens to treetable? that should prob also move to extensions?
-igor
On 6/10/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
Hi folks,
I hope this e-mail won't upset anyone too much.
Let me summarize our tree components situ
And. The new tree is not really compatible with old one, because there
is not much the old one does (in the terms of extendability). But in
case anyone needs the old (ajax) one, it will still be in extensions.
-Matej
On 6/10/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Matej Knopp:
>
>
* Al Maw:
> Jean-Baptiste Quenot 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-beta1. However there are some issues (like WICKET-608) t
Err. Sorry for not-explaining it right. This is not a vote. What I
suggest are all those three options.
-Matej
On 6/10/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Matej Knopp:
>
> I hope this e-mail won't upset anyone too much.
>
> Let me summarize our tree components situation first.
* Matej Knopp:
>
> I hope this e-mail won't upset anyone too much.
>
> Let me summarize our tree components situation first.
>
> We have Tree and TreeTable components in core, and another Tree
> component in extensions.
[...]
>
> a) remove the old (kinda unsupported) tree from extensions (i
Hi folks,
I hope this e-mail won't upset anyone too much.
Let me summarize our tree components situation first.
We have Tree and TreeTable components in core, and another Tree
component in extensions.
The Tree from extensions is the oldest one, without Ajax support.
The Tree in core (as well a
Thanks .
But I have specified different pagemap name.
Example:
> modalRD.setPageMapName("modalRD");
> modalRD.setCookieName("modalRD");
after using setMaxPageMaps() to increase total number of pagemap, problem is
still existing.
2007/6/10, Matej Knopp <[EMAIL PROTECTED]>:
I think your
I think your problem is that the pages are evicted from pagemap.
You'll need to specify different pagemap name for each modal window
component (ModalWindow.setPageMapName). Also you might need to
increase total number of pagemap
(Application.getSessionSettings().setMaxPageMaps()).
-Matej
On 6/10
fix it! :)
On 6/10/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* [EMAIL PROTECTED]:
> Author: jcompagner
> Date: Thu Jun 7 14:39:55 2007
> New Revision: 545324
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=545324
> Log:
> api cleanup and a refactor of some getCallbackScript metho
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
* [EMAIL PROTECTED]:
> Author: jcompagner
> Date: Thu Jun 7 14:39:55 2007
> New Revision: 545324
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=545324
> Log:
> api cleanup and a refactor of some getCallbackScript methods.
> its now much more obvious what to call and what to override when you
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 dependency
hunting, an
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
wicket core shipping log4j? thats wrong anyway.
only examples could include it.
johan
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&vie
A panel is not needed, but an option. As you use a normal page inside
the modal window, I think you run into the limit of versioning.
Increase your versions or disable versioning for your pages using
ajax. The latter is probably the best for your usecase, popups don't
typically work well with the
I didn't use a panel in modal window.
There are more than 6 kinds of modal windows(content is different) in my
site.
Opening&closing these modal window(certainly in different pages) in turn,
when I close the 6th modal window,
session timeout happens.
If don't see it yet, please tell me.
netfo
Thanks for your answer.
I am using 1.2.6.
A panel in the modal window is needed?
My modal window is a general WebPage.
Maybe when open 6th modal window, session timeout happens.
My calling modal window's code :
---
Thanks for your answer.
I am using 1.2.6.
A panel in the modal window is needed?
My modal window is a general WebPage.
Maybe when open 6th modal window, session timeout happens.
My calling modal window's code :
-
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:
My site uses many many ModalWindow.
Now, find a serious problem.
After I log on the site, I open/close some ModalWindow.
At first, it's all right.
But after I open/close some ModalWindow many times, session timeout
happened.
As a result, please watch screenshots.
Please help me. Thanks.
http://ww
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
On 6/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
[1]
http://people.apache.org/~dashorst/releases/apache-wicket-1.3.0-incubating-beta-2
That is of cause:
http://people.apache.org/~dashorst/releases/apache-wicket-1.3.0-incubating-beta2
Frank
ps. my comments later today if any. But Noe
47 matches
Mail list logo
