Hi, I'm requesting commit access to wicket stuff, to send an mbean view
component
my SourceForge user: pedrosans
-- Forwarded message --
From: Pedro Santos pedros...@gmail.com
Date: Fri, Sep 4, 2009 at 3:17 PM
Subject: Re: Wicketstuff really needs some updates
To: us
Hi people,
I realize that I have sent to the wicket stuff, an project that depends on
some 1.6 java api. So I comment it on wicket-stuff-core pom, to let the
project compile...
But I really want to share the this project ( table ), so I wondering if
there are any chance of we have another agent,
Hi, I'm trying to visit parents components with an special interface like:
component.visitParents(IFeedback.class, new IVisitorComponent)
and the methods signature is blocking me:
Component class code:
public final C extends Component Object visitParents(final ClassC c,
final
The Wicket Stuff core project has wicket 1.4.1 as dependence. Is it
deliberately?
--
Pedro Henrique Oliveira dos Santos
Hi, I have an similar case were I have done it. At the time I had an
textfield to receive an code that is case sensitive. So I create an
decorated model for the form component. In the case of a user write an code
were only characters are correct, the setObject method of component model
fix the
2 - here I have an simple consideration: framework should respect my
component design.
My view is different: we should respect the framework design. Don't fight
your tools, learn how to use them properly.
I agree. Let me say it in a different way:
framework should allow an simple component
I know it is an minor thing, but the creation act that the new keyword
exposes, the 'of' method don't has. IMO the simple fact of an method name
does not contain an verb is an anti-pattern.
On Tue, Nov 17, 2009 at 2:50 PM, nino martinez wael
nino.martinez.w...@gmail.com wrote:
im +1, unless
Hi, Wicket has the style session attribute. Why the resources reference has
this attribute too?
Currently I can need code like:
resourceReference.setStyle(Session.get().getStyle());
response.renderReference(resourceReference);
I see it as unnecessary. IMO ResourceReference can lose this
Why do Wicket call abort method on XMLHttpRequest after process it?
(wicket-ajax.js line 1001) It doesn't cause any damage, just the response
get the error flag set to true.
http://www.w3.org/TR/XMLHttpRequest/#the-abort-method
--
Pedro Henrique Oliveira dos Santos
The actual wicket ajax implementation use a pool of XmlHttpRequest objects.
So, after an request is made, wicket call his abort method to get his
readyState back to 0, and use this object again. Other frameworks like
jQuery have an pluggable factory method to create XmlHttpRequest objects.
The
, Pedro Santos pedros...@gmail.com wrote:
The actual wicket ajax implementation use a pool of XmlHttpRequest objects.
So, after an request is made, wicket call his abort method to get his
readyState back to 0, and use this object again. Other frameworks like
jQuery have an pluggable factory method
at 12:53 PM, Pedro Santos pedros...@gmail.com
wrote:
Actually everything in javascript is pluggable, just the call to abort
method from XmlHttpRequest you can't avoid.
Ex.:
Wicket.Ajax.getTransport = function(){
var t = Wicket.Ajax.createTransport();
t.abort = function(){console.log
I'm geting the mesagem: Resource interpreted as image but transferred with
MIME type text/plain.
on google chrome when Wicket returns with the state not modified for
requests to resources with 'If-Modified-Since' parameter.
There is any need to wicket filter - the guy who is creating the response
Why do onClick method from Link is public? Who would want or need to call it
from outside?
--
Pedro Henrique Oliveira dos Santos
From an instance of what class, other than Link and it subclasses?
On Fri, Feb 5, 2010 at 1:20 PM, Erik van Oosten e.vanoos...@grons.nlwrote:
Perhaps the Wicket framework needs some way to call it ;)
Regards,
Erik.
Pedro Santos wrote:
Why do onClick method from Link is public? Who
Hi Martin, thanks for the reply!
Hi, the form component clearInput method that clean this state is called
on
the valid method. I'm trying to guess why the form component keep his raw
input after an form processing with errors. I can't figure out why don't
clear the raw input in this
IMO the form processing can be:
1. validate
2. detect error
3. keep rawinput
4. re-render error components with red border AND rawinput
4.1. throw away the raw input in some detach method
5. user retry form submit
6. all form components get they raw input again since they get rendered
, 2010 at 5:55 PM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
Hi!
What's the difference whether it's thrown away or not if the next step
is re-submit with new values?
**
Martin
2010/2/22 Pedro Santos pedros...@gmail.com:
IMO the form processing can be:
1. validate
2
be any invalid input for
it anymore.
valid();
}
public final void valid()
{
clearInput();
onValid();
}
**
Martin
2010/2/23 Pedro Santos pedros...@gmail.com:
Hi Martin, call get or set defaultModel
Hi Johan, actually it is 2 overridable protected methods that can execute an
rule already implemented by some custom component.
I attached an test to via Jira site showing the possible problem.
https://issues.apache.org/jira/browse/WICKET-2960
On Fri, Jul 23, 2010 at 5:38 AM, Johan Compagner
use the package org.apache.wicket!!!
But that is something i definitely dont see as a problem because you
shouldnt do that.
org.apache.wicket is the package of wicket itself (just like java.lang
is of java itself)
johan
On Fri, Jul 23, 2010 at 14:02, Pedro Santos pedros...@gmail.com wrote
Hi Jeremy, I think it would be interesting close the
https://issues.apache.org/jira/browse/WICKET-2969 before push the release
1.4.10
On Thu, Aug 5, 2010 at 5:11 PM, Jeremy Thomerson
jer...@wickettraining.comwrote:
Does everyone have everything they want in for 1.4.10? I think we should
push
-1, comments on the ticket
On Fri, Oct 29, 2010 at 10:12 AM, nino martinez wael
nino.martinez.w...@gmail.com wrote:
I want change my vote to -1 until this is fixed :
https://issues.apache.org/jira/browse/WICKET-3142
2010/10/29 Martin Grigorov mgrigo...@apache.org
+1
On Fri, Oct 29,
I'm just concerned about the side effects. A bug on the component data index
can cause URL issues. For instance an URL generated for one behavior
invoking another behavior on the same component. Then we will have
developers evaluating the milestone and returning different problems than
the one
wrote:
On Fri, Oct 29, 2010 at 11:41 AM, Pedro Santos pedros...@gmail.com
wrote:
I'm just concerned about the side effects. A bug on the component data
index
can cause URL issues. For instance an URL generated for one behavior
invoking another behavior on the same component. Then we
Hi Jean, you can add an IComponentInstantiationListener to do that on your
app.
On Fri, Nov 19, 2010 at 8:27 AM, Jean-Francois Larouche (JIRA)
j...@apache.org wrote:
Default Component Behaviors
---
Key: WICKET-3179
URL:
Thomerson jer...@wickettraining.com wrote:
I'd just like to pass this on to everyone on the list. Pedro Santos
has been added as a committer and PMC member for Apache Wicket. Pedro
Congratulations!
Carl-Eric
www.wicketbuch.de
--
Pedro Henrique Oliveira dos Santos
Why don't simple change the AbstractBehavior default isEnabled
implementation to respect the component state, like:
public boolean isEnabled(Component component)
{
return component.isEnabled();
}
It would solve the problem at the ticket. IMO the proposed interface is
prolix
24, 2010 at 17:21, Pedro Santos pedros...@gmail.com wrote:
Why don't simple change the AbstractBehavior default isEnabled
implementation to respect the component state, like:
public boolean isEnabled(Component component)
{
return component.isEnabled();
}
It would
);
}
}
}
On Tue, Nov 30, 2010 at 2:16 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
so how is it different if they can still override something that needs
to be checked all the time?
-igor
On Tue, Nov 30, 2010 at 8:02 AM, Pedro Santos pedros...@gmail.com wrote:
I understand the concern
?
isVisible() will work as expected when the criteria for visibility does
not change during render
Am 30.11.2010 um 17:02 schrieb Pedro Santos:
I understand the concern about possible isVisible implementations like
isVisible(return currentlyTime 10:00:00;) //imagine this component
being
. for example
before we invoke a listener on the component we should check again to
make sure that visibility hasnt changed. eg if visibility depends on
some property of the user clicking the link that changed between
render and clicking the link.
-igor
On Tue, Nov 30, 2010 at 8:30 AM, Pedro
invoke configure before the render. this would mean
we would have to invoke it before processing a listener, clearing the
cache, and then invoking it again before render. i wonder if that is
enough places to invoke it
-igor
On Tue, Nov 30, 2010 at 9:15 AM, Pedro Santos pedros...@gmail.com
- this should
fail, but wont if we are using last-rendered state.
-igor
On Tue, Nov 30, 2010 at 11:18 AM, Pedro Santos pedros...@gmail.com
wrote:
I need to look better on which core components are relying on an updated
visibility/enabled state at the process event time, and why the last
rendered
www.wicketbuch.de
On Wed, 1 Dec 2010 20:31:35 -0200
Pedro Santos pedros...@gmail.com wrote:
Hi Carl, you are mixing two different initializations strategies,
that is why you are finding it weird. If you are using an overwritten
onInitialize to initialize your component, do all your initialization
Page will always be the root node at the components tree, we don't need an
useless hotspot on the framework, that is why I think the page should have
an final onInitialize.
On Thu, Dec 2, 2010 at 4:53 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
No. the contract is that the parent is
yes, delaying onInitialize until the constructor ends for pages isn't the
goal.
On Thu, Dec 2, 2010 at 5:03 PM, Pedro Santos pedros...@gmail.com wrote:
Page will always be the root node at the components tree, we don't need an
useless hotspot on the framework, that is why I think the page
at 11:44 AM, Pedro Santos pedros...@gmail.com
wrote:
I have a different point of view, the HTTP imposes us some
limitations,
we
will hardly have an good synchronization between the component state
on
browser and server using only HTTP conversation. So it is mandatory
the
service
The Wicket.Event.handle function at wicket-event.js calls the Wicket.$ one
defined at wicket-ajax.js. But it is not safe call Wicket.$ because the page
can be not using AJAX. Is interest separate utility methods at an
wicket-util.js file?
--
Pedro Henrique Oliveira dos Santos
complains about that in the mailing lists, but if
you
want you can play with it.
On Thu, Dec 9, 2010 at 8:51 PM, Pedro Santos pedros...@gmail.com
wrote:
The Wicket.Event.handle function at wicket-event.js calls the Wicket.$
one
defined at wicket-ajax.js. But it is not safe call Wicket
.
On Sat, Dec 18, 2010 at 8:07 PM, zkybar...@gmail.com
zkybar...@gmail.comwrote:
Pedro,
Thanks for reply. Yeah i have workaround for this - i just reset submit
parameters from last request to current request.
On Sat, Dec 18, 2010 at 6:30 PM, Pedro Santos pedros...@gmail.comwrote:
Hi
of
course you reset parameters from previous request to current). So, my
question is, what should I do with the issue I have, do you want me to
create jira task? Is it bug at all?
On Tue, Dec 21, 2010 at 4:31 PM, Pedro Santos pedros...@gmail.com wrote:
Hi Zilvinas, thank u for the test
this method in the 1.5.
On Tue, Dec 21, 2010 at 1:40 PM, Pedro Santos pedros...@gmail.com wrote:
IMO it is not a bug, rather an improvement: set the form components value
as parameter in form submit request.
the scenario is:
- a new form is created
- a form components receive a new value
Not simplifing (not complicating also), but making clear that an specific
parameter is optional, it can prevent some runtime NPE by exposing in a very
clear way at development time that some parameter may be null.
On Wed, Jan 5, 2011 at 3:53 PM, Martin Makundi
martin.maku...@koodaripalvelut.com
Often Wicket Ajax Debug Window has a lot of lines like:
INFO: focus removed from
INFO: focus set on
INFO: focus removed from
INFO: focus set on
INFO: focus removed from
INFO: focus set on
and you have to navigate some to find AJAX processing info messages that is
the majority of devs use cases.
At the linked thread Matej wrote about serialize the parent form of the
modal inner form on its submit. I think it would end up sending unnecessary
data back to server, since it is quite safe assume that user did not change
anything outside the modal window.
The FormComponent#inputChanged method
Linking the thread with the existing ticket:
https://issues.apache.org/jira/browse/WICKET-1826
https://issues.apache.org/jira/browse/WICKET-1826I attached the described
patch in it.
On Mon, Jan 24, 2011 at 5:30 PM, Pedro Santos pedros...@gmail.com wrote:
At the linked thread Matej wrote about
Spring distribution hasn't the spring.jar anymore:
https://fisheye.springsource.org/browse/spring-framework/trunk/build-spring-framework/resources/readme.txt?r=2858r=2854r=2940r=3872
On Tue, Jan 25, 2011 at 10:27 AM, tetsuo ronald.tet...@gmail.com wrote:
When you don't use maven.
For example,
Currently the serializable checker is only triggered when
an NotSerializableException was thrown. Means that @WicketDontSerialize
annotated beams will not get detected only by changing
the SerializableChecker.
Perhaps an IObjectStreamFactory that return an ObjectInputStream doing the
check? Would
onInitialize is only there to provide an place on the component code where
you can rely on a path to the page from the component. It is useless inside
an page.
On Tue, Feb 1, 2011 at 9:25 AM, tetsuo ronald.tet...@gmail.com wrote:
Overriding onInitialize() on Pages certainly may cause some
useful
methods on it that configure it further.
-igor
On Tue, Feb 1, 2011 at 3:35 AM, Pedro Santos pedros...@gmail.com wrote:
onInitialize is only there to provide an place on the component code
where
you can rely on a path to the page from the component. It is useless
inside
an page
There is one: https://issues.apache.org/jira/browse/WICKET-3438
It was fixed, but I don't know if it was the right fix, why Wicket 1.4 is
cloning the request parameters to bookmarkable targets in
RequestCycle#urlFor(Component,RequestListenerInterface,ValueMap)
If it just use those on params
My mistake, RequestCycle is cloning the page parameters, not in every case
it will be those in request.
On Wed, Feb 9, 2011 at 2:59 PM, Pedro Santos pedros...@gmail.com wrote:
There is one: https://issues.apache.org/jira/browse/WICKET-3438
It was fixed, but I don't know if it was the right
I think the Form or even the Component needs another property to make
visible the hierarchy mismatch between Wicket components and its HTML. The
problem is that the modal window components has its markup on top of the
markup hierarchy, but the same is not true for the component hierarchy.
Some
fine by me also, can hudson integration messages be disabled also?
On Tue, Feb 8, 2011 at 8:58 AM, Martijn Dashorst martijn.dasho...@gmail.com
wrote:
It appears that we can reduce the amount of spam JIRA sends to our
commits list by telling it not to send notifications when the fix-in
+1
On Tue, Feb 22, 2011 at 1:30 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
+1
-igor
On Sun, Feb 20, 2011 at 8:33 PM, Igor Vaynberg igor.vaynb...@gmail.com
wrote:
This vote is to release wicket 1.4.16. This is a bugfix release on the
1.4.x (stable) branch.
Branch:
+1
On Tue, Feb 22, 2011 at 1:35 PM, Jeremy Thomerson jer...@wickettraining.com
wrote:
+1 release
On Tue, Feb 22, 2011 at 10:31 AM, Igor Vaynberg igor.vaynb...@gmail.com
wrote:
+1
-igor
On Sun, Feb 20, 2011 at 8:34 PM, Igor Vaynberg igor.vaynb...@gmail.com
wrote:
This vote is
PersistentPageManager$SessionEntry is the serializable piece of Wicket
inside the servlet session, IMO it should serialize/deserialize regardless
of the Wicket lifecycle. Can the DefaultPageStore be changed to be a
singleton an not a per application instance?
On Fri, Mar 18, 2011 at 12:42 PM,
+1 just compiled the branch, played on wicket-examples, it is all fine.
As a side note, I played a bit at wicket-examples on wicket stuff also and
some repeater examples are not working. e.g. OrderedRepeatingView example
at http://wicketstuff.org/wicket14/repeater/ After the 1.4.17 being released
+1
On Tue, Mar 29, 2011 at 5:27 AM, Andrea Del Bene adelb...@ciseonweb.itwrote:
+1 to release
works just fine for me.
On behalf of Igor Vaynberg:
This vote is to release wicket 1.5-RC3
Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.5-RC3/
Artifacts:
Component#visitParents expects Component as the type to be visited, IMO
should expect the same type of the first parameter.
On Tue, Mar 29, 2011 at 5:22 AM, nino martinez wael
nino.martinez.w...@gmail.com wrote:
why is this not valid?
Hi, I want to contribute to minis project with a new request handler
responsible to respond some table component as a XLS file.
I already forked the project and sent 2 examples[1], next I will to write
some doc in the wiki also.
[1]
He Petr, by add the prolog in the html files those pages are not correctly
rendered in IE8, IMO opinion the best option we have now is to move the
Apache header in those files to inside the html tag plus restore the prolog
[1].
Devs, I don't know if we can freely move the Apache header to outside
+1
On Tue, May 10, 2011 at 11:38 AM, Andrea Del Bene adelb...@ciseonweb.it wrote:
+1 for me.
This vote is to release wicket 1.5-RC4.2.
Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.5-RC4.2/
Artifacts: http://people.apache.org/~ivaynberg/wicket-1.5-RC4.2/dist/
Maven repo:
+1
On Thu, Jun 16, 2011 at 8:34 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
This vote is to release wicket 1.5-RC5
Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.5-RC5/
Artifacts: http://people.apache.org/~ivaynberg/wicket-1.5-RC5/dist/
Maven repo:
Welcome!
On Wed, Jun 29, 2011 at 5:19 AM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
The Wicket PMC is proud to have Sven Meier join our team. Sven has
been active with Wicket since 2007, helping out on the mailing lists
and has provided numerous patches.
Welcome Sven!
Martijn
+1 to copy the compatibility score logic from BufferedResponseMapper to PIM
2011/8/29 Martin Grigorov mgrigo...@apache.org
Hi,
Currently the compatibility score of PIM and BM is 0 so that users'
mappers have priority. I think this is a bit wrong because mounting
more pages in YourApp#init()
Helps a bit because it will be tested first in the list of MapperWithScore
in CompoundRequestMapper
2011/8/29 Igor Vaynberg igor.vaynb...@gmail.com
you can do this once in SystemMapper. if url starts with the namespace
give it a high value.
however, this wont solve the problem where you have
+1 I'm already using successfully 1.5-RC7 in production apps.
2011/8/29 Igor Vaynberg igor.vaynb...@gmail.com
+1
-igor
On Mon, Aug 29, 2011 at 1:39 PM, Igor Vaynberg igor.vaynb...@gmail.com
wrote:
this vote is to promote 1.5-RC7 to 1.5.0.
current bug fixes already made to trunk will
+1
2011/9/4 jcgarciam jcgarc...@gmail.com
+1
On Sun, Sep 4, 2011 at 6:01 AM, Peter Ertl-3 [via Apache Wicket]
ml-node+3788932-1962192371-65...@n4.nabble.com wrote:
+1
Am 03.09.2011 um 22:49 schrieb Bruno Borges:
+ 1
On Sep 3, 2011 1:11 PM, Ron Smits [hidden email]
+1
Pedro Henrique Oliveira dos Santos
2011/11/11 Andrea Del Bene adelb...@ciseonweb.it:
+1
This vote is to release wicket 1.5.3
Branch
http://svn.apache.org/repos/asf/wicket/branches/wicket-1.5.3
Artifacts
http://people.apache.org/~ivaynberg/wicket-1.5.3/dist/
Maven repo
Welcome Emond!
Pedro Henrique Oliveira dos Santos
2011/12/30 Peter Ertl pe...@gmx.org
Welcome aboard, Emond ! :-)
Am 30.12.2011 um 20:42 schrieb Sven Meier:
Welcome :)
Sven
On 12/30/2011 04:26 PM, Emond Papegaaij wrote:
Thank you all for the confidence you have in my work! I'm
value your input on the matter.
Cheers,
Pedro Santos
2012/5/29 Martin Grigorov mgrigo...@apache.org
On Tue, May 29, 2012 at 3:40 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
On Tue, May 29, 2012 at 2:24 PM, Martin Grigorov mgrigo...@apache.org
wrote:
- [...] should we provide
Hi Daniel,
if you want to call back a AJAX behaviour, you can also check the method
AbstractDefaultAjaxBehavior#getCallbackScript()
cheers,
Pedro Santos
2012/6/20 Martin Dilger martin.dil...@googlemail.com
Check the wiki to see what changed
https://cwiki.apache.org/confluence/display
+1
Pedro Santos
On Fri, Aug 24, 2012 at 11:44 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
+1
-igor
On Thu, Aug 23, 2012 at 2:13 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
No fuzz, no separate RC releases. This is the real deal.
Please vote for releasing
+1
Pedro Santos
On Fri, Oct 19, 2012 at 5:51 PM, Bruno Borges bruno.bor...@gmail.comwrote:
+1
*Bruno Borges*
(11) 99564-9058
*www.brunoborges.com*
On Fri, Oct 19, 2012 at 5:42 PM, Igor Vaynberg igor.vaynb...@gmail.com
wrote:
+1
-igor
On Fri, Oct 19, 2012 at 1:10 PM
a functionality. I think that a more consistent way of to honor such
flag is by improving AbstractBookmarkableMapper itself and not only one of
its extension (MountedMapper).
Let me know what you think so we can improve bookmarkable mapper.
Cheers,
Pedro Santos
/1ec0b8b3637feb19da4f87b485e96bfc7ce4e992
2 -
https://github.com/apache/wicket/commit/fba8bddd98da943ea74c9c04d90f17c75417c2fe
Cheers,
Pedro Santos
On Wed, Jan 9, 2013 at 6:35 PM, Martin Grigorov mgrigo...@apache.orgwrote:
I've commented in the commit thread.
On Wed, Jan 9, 2013 at 9:53 PM, Pedro Santos pedros...@gmail.com
.
Pedro Santos
On Thu, Jan 10, 2013 at 7:29 AM, Martin Grigorov mgrigo...@apache.orgwrote:
On Thu, Jan 10, 2013 at 12:58 AM, pe...@apache.org wrote:
Updated Branches:
refs/heads/sandbox/bookmarkable-callback-url fba8bddd9 - 1ec0b8b36
WICKET-4932: testing if the page is bookmarkable
Not sure, they are closely related to its outer class and their code next
to each other exposes their fundamental difference giving it readability.
It's your call.
Pedro Santos
On Fri, Jan 11, 2013 at 6:28 AM, Martin Grigorov mgrigo...@apache.orgwrote:
On Thu, Jan 10, 2013 at 7:39 PM, Pedro
finish and merge the work
during the week.
1 - http://wicket-dev.markmail.org/thread/unwdqpxulw7tcd5l
Pedro Santos
On Thu, Jan 12, 2017 at 9:08 PM, Martin Grigorov <mgrigo...@apache.org> wrote:
> Hi,
>
> @Sven: have you started migrating your app ?
>
> @Pedro: any idea wh
my personal view that Wicket 8 is the right place for
proposed improvements.
Pedro Santos
On Tue, Jan 31, 2017 at 1:58 PM, Martin Grigorov <mgrigo...@apache.org> wrote:
> Hi Pedro,
>
> On Tue, Jan 31, 2017 at 3:14 PM, Pedro Santos <pedros...@gmail.com> wrote:
>
>>
it pluggable in a better place and
the default resolver to be a simpler syntax closer to the standard
JSR-341.
1 - http://wicket-dev.markmail.org/thread/unwdqpxulw7tcd5l
Pedro Santos
On Tue, Jan 31, 2017 at 7:59 PM, Sven Meier <s...@meiers.net> wrote:
> Hi Pedro,
>
> Propert
org/thread/unwdqpxulw7tcd5l
2 - http://markmail.org/message/yc2pwmbmasx5rzim
On Tue, Jan 31, 2017 at 10:13 AM, Martin Grigorov <mgrigo...@apache.org> wrote:
> Hi Pedro,
>
> On Tue, Jan 31, 2017 at 10:25 AM, Pedro Santos <pedros...@gmail.com> wrote:
>
>> Hi Martin,
>
t.
Cheers
Pedro Santos
1 - https://issues.apache.org/jira/browse/WICKET-4201
2 - https://github.com/apache/wicket/tree/WICKET-4201-improved-page-provider
Sure, working on it. Created WICKET-6318 to track the configurable
property resolver implementation.
Pedro Santos
On Tue, Feb 7, 2017 at 8:16 PM, Martin Grigorov <mgrigo...@apache.org> wrote:
> Hi Pedro,
>
> Please create Pull Requests for your proposed changes!
> Thanks!
&
meone help to fix the 6.x
build?
Cheers
1 -
https://ci.apache.org/builders/wicket-branch-6.x/builds/206/steps/compile/logs/stdio
2 -
https://ci.apache.org/builders/wicket-branch-6.x/builds/207/steps/compile/logs/stdio
Pedro Santos
On Fri, Feb 3, 2017 at 1:23 AM, <build...@apache.org> wrote
+1 to release.
Built the branch locally and runned wicket-examples. Only I think your
public key used to sign the release is missing on Wicket's keys file
at http://archive.apache.org/dist/wicket/KEYS
Cheers
Pedro Santos
On Sun, Feb 5, 2017 at 12:35 PM, Andrea Del Bene <an.delb...@gmail.
it at the branch
"WICKET-6318-configurable-property-expression-resolver" and I add more
detailed description of the changes at the ticket WICKET-6318
Cheers
Pedro Santos
1 -
https://github.com/apache/wicket/tree/WICKET-6318-configurable-property-expression-resolver
2 - https://issues.apach
+1
Pedro Santos
On Thu, Aug 18, 2016 at 7:56 AM, Andrea Del Bene <an.delb...@gmail.com>
wrote:
> +1 for me too
>
>
>
> On 18/08/2016 00:47, Martijn Dashorst wrote:
>
>> Sounds good to me
>>
>> Martijn
>>
>> On Wednesday, 17 August 2016, Mar
dea and to get your thoughts while
resolving WICKET-6219 in wicket-7.x branch.
cheers,
Pedro Santos
1 - https://github.com/apache/wicket/tree/WICKET-6219-no-fragment-resolver
Hi Martin,
Indeed, thx. Just removed the duplicated dependencies. I noticed that we
have a few more redundant scopes across 6.x, 7.x and master branches; will
run a larger cleanup later so we can have a meaningful setup inside
.
Pedro Santos
On Tue, Sep 6, 2016 at 5:02 AM, Martin Grigorov
Hi Martin, thx!
In this case I need to make sure of to set a default locale before
instantiate the tester. But actually I can add this in a @BeforeAll and
still extend from WicketTestCase. Will improve the test next.
Pedro Santos
On Tue, Sep 13, 2016 at 4:19 AM, Martin Grigorov <mgr
-api-improvement
Pedro Santos
On Wed, Sep 7, 2016 at 4:09 AM, Pedro Santos <pedros...@gmail.com> wrote:
> Hi Sven,
>
> I think you meant the bug fix shouldn't be backported given this change is
> both a bug fix and a consistency improvement, and that the consistency
> i
Looking through wicket examples in Wicket 7 branch, it looks like the ajax
debug bar is missing. I would hold up the release.
Pedro Santos
On Fri, Sep 23, 2016 at 11:12 AM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:
> Are there any holdups for issuing new
My bad, missed to import wicket-devutils in my workspace. No hold ups from
me.
Thanks Martijn!
Pedro Santos
On Fri, Sep 23, 2016 at 9:43 PM, Pedro Santos <pedros...@gmail.com> wrote:
> Looking through wicket examples in Wicket 7 branch, it looks like the ajax
> debug bar is miss
Hi Sven, thx. Sending the response inline.
Cheers
Pedro Santos
On Wed, Sep 28, 2016 at 3:08 AM, Sven Meier <s...@meiers.net> wrote:
> Hi Pedro,
>
> very interesting work, thank you very much.
>
> I have a little nitpick though:
>
> The expressio
on resolution inside PropertyResolver, not by the parser.
Pedro Santos
On Thu, Sep 22, 2016 at 4:25 PM, Martin Grigorov <mgrigo...@apache.org>
wrote:
> Hi Pedro,
>
> There were no complains about the current parser, but that doesn't mean we
> should not improve!
>
> Two questions
mmons-ognl/language-guide.html
cheers
Pedro Santos
change log looks enough to me.
Any dev using Wicket to parse and iterate a markup would have ran in the
same problem. As WICKET-6165 is the first ticket I see on this matter, it
looks like this steam API, even being public, wasn't being used outside
Wicket core.
cheers
Pedro Santos
On Wed, Sep 7
1 - 100 of 134 matches
Mail list logo
