Hello,
I've just done some debugging work for Ingo Renner. His project is somehow
similar to the brix cms and the way of manipulating the components within the
markup stream resolution. This worked in 6.x and 7.0-7.2, but was broken in
7.3+ with commit:
https://github.com/apache/wicket/commi
Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Oct 3, 2016 at 1:50 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
>> Hello,
>>
>> I've just done some debugging work for Ingo Renner. His project is somehow
>> similar to t
Hi,
while I'm not one of the commiters I still like to respond to this. I'm fine
with changing from 1.x to 3.x as IE 10 and lower really has no relevance
anymore IMHO.
However, the real question that came into my mind:
Why not just use plain js / vanilla js?
When it was decided to go to jQu
tJavaScriptLibrarySettings().setWicketAjaxReference(...) !
>
>
>>
>> On Mon, Mar 20, 2017 at 11:33 AM, Korbinian Bachl <
>> korbinian.ba...@whiskyworld.de> wrote:
>>
>> > Hi,
>> >
>> > while I'm not one of the commiters I still
Hi,
is it planned to have a 8-m5 anytime soon? I ask because quite much changed
(e.g.: BookmarkableListenerRequestHandler, other JSON) and I really had some
time keeping up the current snapshot builds with my project.
Also, any idea when can wicket-8.0 be expected?
Best,
Korbinian
Hi,
in https://issues.apache.org/jira/browse/WICKET-6348 the way how to react on
onSelectionChanged(Object object) got changed to now a usage of
// Wicket 7.x
new CheckBox("id", model) {
protected boolean wantOnSelectionChangedNotifications() {
return true;
}
protected
Hi,
according to jira
(https://issues.apache.org/jira/projects/WICKET/versions/12340604) only 1 open
issue before wicket8-m7 (WICKET-6406).
So I ask myself, humble wicket devs, how the current plan for the release might
be. With JAVA 9 out soon (83 days) wouldnt it be time to move wicket8 at l
Hello,
http://examples8x.wicket.apache.org/ is giving me a 503 for several days now.
Can you please tell me who is in charge of it?
Best,
Korbinian
Hi,
is it intended that any wicket:enclosure breaks if it is depending on a
component that is not added in the constructor but in "onBeforeRender"?
e.g:
Bezeichnung:
value
with java:
public HomePage(final PageParameters parameters) {
super(pa
Would a wicket 8.0.0 release be possible soon?
(I know I'm nagging :) )
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> An: dev@wicket.apache.org
> Gesendet: Mittwoch, 12. Juli 2017 11:40:57
> Betreff: Re: [VOTE] Release Apache Wicket 7.8.0
> This vote passes with 4 binding votes.
t;Maxim Solodovnik"
> An: dev@wicket.apache.org
> Gesendet: Mittwoch, 12. Juli 2017 12:47:27
> Betreff: Re: [VOTE] Release Apache Wicket 7.8.0
> WICKET-6419 <https://issues.apache.org/jira/browse/WICKET-6419> might be
> blocker for 8.0.0 release ...
>
>
Hi,
our dev system is running 8 snapshot now for about 2 weeks without any problem.
I would like to push 8 into production, but not before M7 is here as I dont
want a production to depend on a snapshot - any chance M7 will get out the next
days?
Best,
KB
- Ursprüngliche Mail -
> Vo
Please a thousand +1 (non-binding)
:)
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> An: dev@wicket.apache.org
> Gesendet: Freitag, 4. August 2017 17:12:43
> Betreff: Re: Wicket 8 (M7) release
> Hi,
>
> I think we are ready to promote Wicket 8 to GA but I would wait for
> September
gt;>> Hello All,
>> >>>>
>> >>>> I would like to update version on libraries being used by wicket to
>> the
>> >>>> most recent versions is it OK?
>> >>>>
>> >>>>
>> >>
Hello Andrea,
currently the jira shows M7 as unreleased with 1 item toDo, see
https://issues.apache.org/jira/projects/WICKET/versions/12340604
Best,
KB
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> An: dev@wicket.apache.org
> Gesendet: Samstag, 12. August 2017 17:02:58
> Betreff:
Hi,
after deploying our app with wicket 8, I've seen that the javacript files of
AJAX are not really optimised.
Issues are:
- 2 Files - instead of putting out 1 file of JS for wicket, we get 2 (3 if we
count jQuery); I dont see this as good especially since 1 of those files is
quite small...
Hi,
>
>>
>> - JS Code is not compressed/ optimized for production; so far only
>> comments are stripped out but no real optimization in terms of newline
>> (nearly 3k!) and whitespaces are done
>>
>
> Not true!
> At
> https://github.com/apache/wicket/tree/master/wicket-core/src/main/java/org/apa
Please also wicket 8 - this one is a real problem
- Ursprüngliche Mail -
> Von: "Emond Papegaaij"
> An: dev@wicket.apache.org
> CC: "Martijn Dashorst"
> Gesendet: Mittwoch, 30. August 2017 13:10:27
> Betreff: Re: Major page store issue found in 7.8.0, release a 7.8.1?
> I've applie
Hi,
due to the problematic bugs in wicket8 up to m7 (2 x pagestore and
filesystemresource-leak), would it be possible to release wicket8-m8 anytime
soon?
Best,
Korbinian
Hi,
currently wicket renders all its jQuery and Ajax stuff right into the head, and
I wonder why.
Current best practice seems to defer all javascript till the end of the page
just right before the closing tag to let the browser meanwhile get the
DOM and do some work and not get blocked by lo
upports the attribute since
> https://issues.apache.org/jira/browse/WICKET-5715
>
> Have fun
> Sven
>
>
> Am 07.10.2017 um 19:49 schrieb Korbinian Bachl:
>> Hi,
>>
>> currently wicket renders all its jQuery and Ajax stuff right into the head,
>> an
and if you make it
Integer.MAX_VALUE - 1
as default? :)
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> An: dev@wicket.apache.org
> Gesendet: Dienstag, 17. Oktober 2017 12:11:06
> Betreff: Re: WICKET-6481
> On Tue, Oct 17, 2017 at 9:32 AM, Martin Grigorov
> wrote:
>
>> Hi,
>>
>> M
Hi,
after WICKET-6492 seems to take care of the bug of minification and even
uniting of the Javascript files of wicket, I wonder if wicket cant even get
better in the js part. Currently each page having ajax somehow ends up with
following in the head:
(1)
(2)
(3)
(4 - inline var and not reall
Hello,
wouldn't option 2 put the Jjqery.js into it?
Best,
KB
- Ursprüngliche Mail -
> Von: "Maxim Solodovnik"
> An: dev@wicket.apache.org
> Gesendet: Mittwoch, 22. November 2017 07:21:22
> Betreff: Question regarding WICKET-6497 unify javascript files
> Hello,
>
> I'm currently inve
I'd like some comment on WICKET-6498, as that wicket-JS impl. currently is just
not good IMHO as its blocking the DOM with JS;
Best,
KB
- Ursprüngliche Mail -
> Von: "Maxim Solodovnik"
> An: dev@wicket.apache.org
> Gesendet: Mittwoch, 29. November 2017 03:32:48
> Betreff: 8.0.0 block
Yes, you are right - it has to be optional at least, something even the current
jQuery reference isn't yet (you only can provide an empty one js file - still a
request);
>From my experience this all is worse than at the time before jQuery was
>introduced to wicket as this really slows down the
inified and optimized JS file from webdesigner" jquery
> version as the main one for wicket .
>
> On Wed, Nov 29, 2017 at 3:57 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
>> Yes, you are right - it has to be optional at least, something even t
icket.apache.org
> Gesendet: Mittwoch, 29. November 2017 10:08:15
> Betreff: Re: 8.0.0 blockers
> I love to help here
> But I don't see clear solution .
>
>
> On Wed, Nov 29, 2017 at 4:06 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
>> N
May I also mention WICKET-6498?
https://issues.apache.org/jira/browse/WICKET-6498
- Ursprüngliche Mail -
> Von: "Sven Meier"
> An: dev@wicket.apache.org
> Gesendet: Freitag, 29. Dezember 2017 16:22:47
> Betreff: Re: 8.0.0 blockers
> Not strictly necessary, but I would like to merge W
rote:
>>
>>> I’m working on restyling the QuickStart to look like the new
>>examples. Not
>>> a blocker but would be awesome to include. Will work on it 2nd Jan
>>>
>>> Martijn
>>>
>>>
>>>
>>> Op vr 29 dec. 2017 om 20:2
gt; before the 8.0.0 release) is not the right moment for it.
>>
>> Regards
>> Sven
>>
>>
>>
>> Am 02.01.2018 um 11:34 schrieb Martin Makundi:
>>
>>> If configuration option is final solution then yes, otherwise it opens a
>>> new
Im really sorry Sven but I broke your defer patch :/
see comment here:
https://issues.apache.org/jira/browse/WICKET-6498
A solution to it is provided :)
- Ursprüngliche Mail -
> Von: "Sven Meier"
> An: dev@wicket.apache.org
> Gesendet: Donnerstag, 1. Februar 2018 14:15:11
> Betreff: Re
>>>>>
>>>>> I have question regarding site generation.
>>>>>
>>>>> I have added following file: 2018/_posts/2018-02-12-wicket-
>>>>> 8.0.0-released.md
>>>>> But news for 2018 are not being generated
>>
+1 to release for M9
IMHO a warning should be added with regards to WICKET-6498 as it is not yet
working in a reliable way but may break depending on client specifics;
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> An: dev@wicket.apache.org
> Gesendet: Sonntag, 11. Februar 2018 17:34
red experimental.
>
> IMHO this is warning enough.
>
> Sven
>
>
> Am 11.02.2018 um 20:03 schrieb Andrea Del Bene:
>> Good point. We should also underline that WICKET-6498 breaks custom
>> response decoration that might be used to place JavaScript inside body
>>
: Re: [VOTE] Release Apache Wicket 8.0.0-M9
> Hi,
>
> I need your help. what's exactly the caveat about WICKET-6498? It uses
> javascript events that might not be supported buy browser?
>
> On Sun, Feb 11, 2018 at 6:16 PM, Korbinian Bachl <
> korbinian.ba...@whisky
IMHO: its 2018 and any browser sniffing has to be dropped at all, as it has no
use anyway and its not working reliable... what for do we need this at all?
even in 2009 it was considered bad:
https://www.sitepoint.com/why-browser-sniffing-stinks/
and in case that is not enough, read what the guy
- Ursprüngliche Mail -
>> even in 2009 it was considered bad: https://www.sitepoint.com/why-
>> browser-sniffing-stinks/
>> and in case that is not enough, read what the guy that invented modernizr
>> has to say:
>> http://farukat.es/journal/2011/02/499-lest-we-forget-or-
>> how-i-learned
+1 to release
- Ursprüngliche Mail -
> Von: "Maxim Solodovnik"
> An: dev@wicket.apache.org
> Gesendet: Dienstag, 3. April 2018 16:36:35
> Betreff: [DISCUSSION] Wicket 8 Release
> Hello All,
>
> I believe it is time to release :)
> Do we have any blockers?
>
> Some non-technical block
Maybe stupid question but: why not align with Java EE?
-> Java EE8 relies on JDK8, not JDK 9 - and wicket 8 relies on JDK 8
-> Java EE9 (or whatever naming scheme comes) might rely on Java 11 lts -> so
align wicket 9 (or whatever EE naming scheme) with JDK 11?
In the end the Java version itself
with the latest LTS JDK whatever it is at the moment.
> The version of EE4J / Servlet specs are also not relevant to Wicket's
> version.
>
> On Mon, Apr 16, 2018 at 4:03 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
>> Maybe stupid question bu
+1
- Ursprüngliche Mail -
> Von: "Emond Papegaaij"
> An: dev@wicket.apache.org
> Gesendet: Freitag, 18. Mai 2018 11:58:43
> Betreff: Re: [VOTE] Release Apache Wicket 8.0.0
> +1
>
> Tested our application with the complete test suite
> Checked signatures and hashes
>
> I did notice som
Hi,
under https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+8.0
I get various errors in the document like
"Unable to locate Jira server for this macro. It may be due to Application Link
configuration."
and
"Fehler beim Ausführen des Makros 'jira'
Unable to locate Jira
Option 3:
1) wait for MS to apply the switch to the chromium engine (ditching the current
edge engine completely - see:
https://www.computerworld.com/article/3325333/web-browsers/with-move-to-rebuild-edge-atop-googles-chromium-microsoft-raises-white-flag-in-browser-war.html
)
2) relax while doin
Hi,
we dont use queueing but we use enclosures in quite a few places. Getting rid
of it would mean we have to switch to markup containers holding the content and
add additonal layer of complexity and boilerplatecode for us.
Beside that: can wicket 10 finally get rid of jQuery? Since IE is now
Apologies for hijacking this, but can we assume now the following?
wicket 8: java 8 + java apis + servlet 3.1 + jQuery
wicket 9: java 11 + java apis + servlet 3.1 + JQery
wicket 10: java 17 + jakarta apis + servlet 5.x + no jQuery
??
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> A
cket 10 based on jakarta.** APIs ?
> On Fri, Sep 3, 2021, 12:08 Korbinian Bachl
> wrote:
>
>> Apologies for hijacking this, but can we assume now the following?
>>
>> wicket 8: java 8 + java apis + servlet 3.1 + jQuery
>> wicket 9: java 11 + java apis + servlet 3.
itag, 3. September 2021 14:12:15
> Betreff: Re: Wicket 10 based on jakarta.** APIs ?
> On Fri, Sep 3, 2021 at 3:08 PM Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
>> Oh, ok.
>> Why hold on it?
>> IE is dead and ECMAScript 2015 (ES6) is here in a
Hi,
I've read the article about rails 7 and the way of its javascript multiple
times - yet I'm not 100% sure I understood everything - but for me it sounds
somehow awesome. You'll seem to end up getting a choice:
3 choices to be exact.
A, use rails as an api backend, meaning you can have your
Hi Martin,
thanks for the details, please see below.
- Ursprüngliche Mail -
>
> From what I've understood you know just some parts of Wicket and this makes
> you think some things are hard or even imposible.
> Have you considered using Wicket's mounted resource ? it is something
> simila
- Ursprüngliche Mail -
>> >
>> Could you make a quickstart example use case and we could maybe brainstorm
>> about it together, what would actually be the leanest solution?
>>
>
> http://wicketinaction.com/2014/07/build-resources-with-node.js/
> https://github.com/davidB/livereload-jvm
>>
>> I'm a bit short on time currently but what I meant with the fewer
>> redeploys is not anywhere near this livereload jvm. Why? well, I dont think
>> wicket is used that much in "small" projects but in rather larger ones.
>> (I know DHL uses it for the GK-Portal - the solution any smaller custo
Hi,
I deployed our app on 9.9.0 this morning and after initializing a crawl of the
page I ended up getting a low quote of 503s.
The 503s are always the same:
2022-03-31 09:35:05,031 ERROR [org.apache.wicket.DefaultExceptionMapper]
Unexpected error occurred
org.apache.wicket.markup.MarkupExce
lodovnik"
> An: "dev"
> Gesendet: Donnerstag, 31. März 2022 10:06:34
> Betreff: Re: wicket 9.9.0 - MarkupExceptions after upgrade - any idea why I
> get this?
> " tags are only allowed before , ,
> etc. tag"
> sounds reasonable :)
>
> On
s where the singleton strategy
>>> doesn't work.
>>>
>>> Can you reproduce this issue in a test-case?
>>>
>>> Thomas
>>>
>>> On Thu, Mar 31, 2022 at 10:06 AM Maxim Solodovnik
>>> wrote:
>>>
>>>> "
e:
>> > >>
>> > >>> This is probably caused by my change in
>> > >>> https://issues.apache.org/jira/browse/WICKET-6963
>> > >>>
>> > >>> I have been using this code in production for a couple of weeks now
>> > &
PS: with "rendering" I mean the kind of page composition from changed HTML
source, not the rerendering in terms of changed on page content due to Java
code...
I think I have expressed myself not clear and good here. Sorry :(
- Ursprüngliche Mail -
> Von: "Korbinian
I wouldn't drop any of the wicket-x.x branches as these were the releases and
imagine you had to use wicket 1.4 in an old app and need a fix asap?
- Ursprüngliche Mail -
> Von: "Maxim Solodovnik"
> An: "dev"
> Gesendet: Donnerstag, 28. April 2022 09:01:09
> Betreff: Re: [DISCUSSION] Sh
Hi,
we use wicket for many years now and so far it is a great framework to use. One
thing that however seems still a bit of a problem is the way wicket handles
(runtime) errors.
If you look at a page then the content is often composed of 100's of panels and
components.
As long as every single
t.com)
> kirjoitti:
>
>> Yes. You can override runtime handling yourself @
>> RequestCycle.onRuntimeException (at least used to be with such name)
>>
>> In production it is recommended to do so as you best see fit.
>>
>> **
>> Martin
>>
>> ma 10. lokak. 2022 klo 9.45 K
>
> It is your application so you must know/design how to recover from the
> error. You either re-render the same page or redirect the user to a
> suitable error page.
>
> **
> Martin
>
Thats exactly the misunderstanding. If one of 100s of components fails - not
even necessarily "made" by my
> ti 11. lokak. 2022 klo 11.12 Korbinian Bachl (korbinian.ba...@whiskyworld.de)
> kirjoitti:
>
>>
>> >
>> > It is your application so you must know/design how to recover from the
>> > error. You either re-render the same page or redir
- Ursprüngliche Mail -
>
> If you are ok with a 80% failing page, I cannot help you, because in that
> case you can simply come up with another fallback which works 80%. You know
> this leads/creeps to exponential growth of failures and work, yes?
>
> The right way to handle it is to i
When looking at
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+10.0
I wondered what Jakarta version is required?
Is Jakarta 9.0 enough? Because, it says Java 17 needed - this is even above
Jakarta 9.1 abd 10 that both have a JDK 11 baseline?
Oh and also what does this
Hi,
just a short question. Since wicket 10 removed ModalWindow and insists now on
using ModalDialog even so many features of ModalWindow aren't in ModalDialog
existing
(for example closeCallback, resize, move, header, closebutton, init of width,
height etc.etc).
Would it maybe possible if the
o wicket-stuff, but
> apparently I forgot to do it actually.
>
> For explanation: the old ModalWindow is riddled with JS and dynamically
> generated HTML markup which we didn't want to maintain any more.
>
> Sven
>
>
> On 20.10.23 11:22, Korbinian Bachl wrote:
&g
cket 10
> Hi,
>
> I thought we already moved the old implementation to wicket-stuff, but
> apparently I forgot to do it actually.
>
> For explanation: the old ModalWindow is riddled with JS and dynamically
> generated HTML markup which we didn't want to maintain any more.
Hi,
is there any reason wicket has static
9.19.0-SNAPSHOT
everywhere, even in modules
org.apache.wicket
wicket-parent
9.19.0-SNAPSHOT
../pom.xml
instead of a single defined properties in Wicket Parent:
${revision}${changelist}
...
9.19.0
-SNAPSHOT
...
and in submodules
twoch, 19. Juni 2024 11:48:52
> Betreff: Re: wicket version definition in maven poms
> Hum... I have the vague idea that I asked the same questions long long time
> ago and someone pointed me to some maven plugin bug
>
> On Wed, Jun 19, 2024 at 2:33 AM Korbinian Bachl
> wrote:
>
Hi,
I've stumbled over a not so old blog post describing the problem when many
components with AJAX are used:
https://www.coderdreams.com/tracking-down-a-bug-in-production-wicket-application/
Can this problem still happen?
After watching
https://github.com/apache/wicket/blob/master/wicket-core
How can it be published there on 19th of January?
That's two (2) days before even the vote was closed!
--
Korbinian
- Ursprüngliche Mail -
> Von: "Guillaume Smet"
> An: dev@wicket.apache.org
> Gesendet: Mittwoch, 23. Januar 2013 01:28:29
> Betreff: Re: [VOTE] Release Apache Wicket 6.5.0
Hi,
i downloaded wicket-jmx and put it into the classpath of a new
wicket-skeleton app - I then deployed it to GF V5 b50g and logged into
the management console, but no MBeans were displayed... do I need to
register it anywhere or did I miss sth? - Beside Eelcos post
(chillenious blog 2006) t
Hi,
did have a look at it, but thats quite useless there, as im on an
appserver while the pure start is only for situations where you dont
have any server at all - this is, because the MBeansever etc. is already
existant and no container is required.
(in fact, as wicket-jmx has its own initi
Hi,
i've noticed that in 1.3.0 you get repeatedly
13864 [ModificationWatcher Task] ERROR
org.apache.wicket.util.resource.UrlResourceStream 's
wich really pollutes the logfiles. Im using the 1.3.0 Snapshot Daily
from 19th August, and get every second at leas one of these errors in
the logs..
Hi Gerolf,
short follow up question:
after playing for some hours with JMX im really lovin it... who needs
xml-resources when you jut can have a MBean with a default value and
edit it during runtime! the only thing that now comes to me if there is
any management console existant that can be e
tried now the build from 23.08.2007 - same problem here :( - should I
file a bug in JIRA ?
Igor Vaynberg schrieb:
try the latest trunk
-igor
On 8/23/07, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
Hi,
i've noticed that in 1.3.0 you get repeatedly
13864 [ModificationWatcher
done:
https://issues.apache.org/jira/browse/WICKET-883
Igor Vaynberg schrieb:
yes please
-igor
On 8/23/07, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
tried now the build from 23.08.2007 - same problem here :( - should I
file a bug in JIRA ?
Igor Vaynberg schrieb:
try the latest
in my log:
[8/24/07 12:21:05:226 EDT] 702c702c SystemOut O DEBUG <2007-08-24
12:21:05,226> [ModificationWatcher Task] - Run the job:
[EMAIL PROTECTED]
Is this similar to what you reported here?
Thanks!
Korbinian Bachl wrote:
Hi,
i've noticed that in 1.3.0 you get repeat
Hi,
in my init() i used the addComponentInstantiationListener for loading
the wicket-contrib-javaee ejb3 bridge, but this is now broken, as
@Override
protected void init()
{
addComponentInstantiationListener(new
JavaEEComponentInjector(this));
.
is not valid anymore - i
Hi,
after creating yet another WebMarkupContainer to allow a ajaxified
resultset, i wondered why we are forced to this? - I mean, im not a JS
guru, but why do we have to create abstract containers to let some
content change? I know that we need a hook (namely an tag with id) but
couldnt this
, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
Hi,
after creating yet another WebMarkupContainer to allow a ajaxified
resultset, i wondered why we are forced to this? - I mean, im not a JS
guru, but why do we have to create abstract containers to let some
content change? I know that we need a hook (
re replacing. Since listview itself has no body, you need a
> container above it.
this is something I understand for RepeatingView, but not for ListView -
where you have an enclosing tag which is put around all repeated content?
Thanks for your time to answer these questions,
Korbinian
", new ArrayList()) {
public void onPopulateItem(ListItem item) {}
});
it gives output:
if i have a list with 1 item it gives
item
so why isnt the UL then a valid hook?
Best,
Korbinian
Matej Knopp schrieb:
On 10/31/07, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
Hi Mat
i find this idea nice, too
Regards,
Korbinian
PS: if the cost of the domain is an issue, then dump me an email and ill
pay these bucks - 10 euro / year is not an issue regarding a great piece
of software IMHO...
Bruno Borges schrieb:
I'd like to suggest to turn wicketframework.org into a
Hi,
i added following items to it:
(http://cwiki.apache.org/confluence/display/WICKET/Wicket+1.4+Wish+List)
Add Rapid Prototyping Forms
The Idea of Alistair Maw and Jonathan Locke (ROR? No. Wicket on Wheels.)
should be included in next Wicket. A set of nice looking
Defaultformcomponents and a
Hi Eelco,
Eelco Hillenius schrieb:
Add Rapid Prototyping Forms
The Idea of Alistair Maw and Jonathan Locke (ROR? No. Wicket on Wheels.)
should be included in next Wicket. A set of nice looking
Defaultformcomponents and a Beanresolver to automatically let create
forms from just the plain bean bu
Hi,
i get
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
named 'foo' is defined
when defining a Bean like this:
@Component("foo")
public class someDAO {...
and in XML:
while if defining that way:
public class someDAO {...
XML:
works.
Wicket Java is:
public
Here you are:
Compilation of sources using maven install in /src (did a complete local
maven repo clean before).
result:
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
happy new year,
Korbinian
Timo Rantalaiho schrieb:
On Mon, 17 Dec 2007, Korbinian Bachl wrote:
Did I do something wrong here or can it be that SpringBean doesnt work
with annotation configured spring beans?
It does, there must be some other Spring configuration error.
You're better
Hello Ahmed,
Drupal is a CMS similar to Typo3 & co while wicket is a Java Web
Framework, similar in term to what Zend Framework is to PHP. So they
share nothing real in common - or did I get you wrong?
there has been a CMS called Kronos based on wicket but I dont know what
happened to it.
My wish list:
1. Java 6
2. JEE6 where possible like e.g. CDI;
3. Modularization using OSGI
4. AJAX overhaul: currently Ajax is a pain in case it gets more
complicated as one
-> needs to add components to target AND page hierarchy;
-> needs to do .setOutputId(true) all over
-> can't touch
Well, I think there is consent that we can say current wicket ajax is
quite broken and a big pain in everyday usage.
The current ajax means loads of code in java for even trivial things.
Triple-checking that a component knows its ajax and so on. So even *if*
it will break api in future, I don'
tetsu, ever tried to:
- get an AjaxRequestTarget in a component that was not designed by ajax
in mind?
- tried to ajaxify a table-row in a dataTable component?
- tried ajax with repeaters?
- tried to interact with a modal window from inside in case you have a
pure non-ajax page within it?
Hi Martin,
Am 20.09.11 09:59, schrieb Martin Grigorov:
...
Well, I think there is consent that we can say current wicket ajax is quite
broken and a big pain in everyday usage.
Really? Is that broken ?
Neither mailing lists questions nor tickets prove that statement.
The current ajax means loa
Heya,
Am 20.09.11 11:37, schrieb Martin Grigorov:
...
Ok, well, wicket consists of components. So basically it is making a page
full of a tree with components. Wicket now could scan the component if it
has any Ajax on it - then auto add what it needs like the setOuput... - so
we got rid of thi
Am 20.09.11 12:30, schrieb Martin Grigorov:
On Tue, Sep 20, 2011 at 1:11 PM, Korbinian Bachl - privat
wrote:
...
Wrong approach IMHO. The question is: Do we need outprinted Id's to find an
element in DOM?
Answer is: No, we don't as long as we know the path (!). Funnywise this p
Am 20.09.11 13:11, schrieb Pointbreak:
I'm completely agreeing with Martin on this one. The things you are
suggesting imho have the following consequences:
- Wicket implementation becomes way more complicated, because Wicket has
to translate between component hierarchy and browser DOM-tree, whic
Hello,
is it possible in wicket 6.0 to programatically switch to SSL mode? -
I've read that according to the wiki:
"HttpsMapper has been refactored to make subclassing easier" - but
couldnt find the jira for it?
Reason why I'm asking is that I'm trying to get Brix CMS working with
wicket 5 o
Hello,
I've noticed that a Form inside a ModalWindow can't be submitted using
the onSubmit function (and dislikes a standard submit button) but
instead requires an AjaxButton to call the action - why is this so? It
makes my life currently somehow hard as I need 2 nearly identical forms
- one
I think it would be even better to wrap the panel nino is talking
about in a new page for your modal window.
Maurice
On Tue, Apr 8, 2008 at 2:59 PM, Nino Saturnino Martinez Vazquez Wael
<[EMAIL PROTECTED]> wrote:
Korbinian Bachl - privat wrote:
Hello,
I've noticed t
1 - 100 of 139 matches
Mail list logo
