[jira] [Updated] (WICKET-6666) Rewrite ModalWindow

[ https://issues.apache.org/jira/browse/WICKET-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-: -- Component/s: ModalDialog > Rewrite ModalWindow > --- > >

[jira] [Updated] (WICKET-6666) Rewrite ModalWindow

[ https://issues.apache.org/jira/browse/WICKET-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-: -- Affects Version/s: 9 > Rewrite ModalWindow > --- > >

[jira] [Created] (WICKET-6666) Rewrite ModalWindow

Igor Vaynberg created WICKET-: - Summary: Rewrite ModalWindow Key: WICKET- URL: https://issues.apache.org/jira/browse/WICKET- Project: Wicket Issue Type: New Feature

[jira] [Updated] (WICKET-6626) Introduce application-wide Component#onComponentTag listeners

[ https://issues.apache.org/jira/browse/WICKET-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-6626: -- Description: Such a listener will be useful for implementing application-wide styling

[jira] [Resolved] (WICKET-6626) Introduce application-wide Component#onComponentTag listeners

[ https://issues.apache.org/jira/browse/WICKET-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-6626. --- Resolution: Fixed > Introduce application-wide Component#onComponentTag listen

[jira] [Created] (WICKET-6626) Introduce application-wide Component#onComponentTag listeners

Igor Vaynberg created WICKET-6626: - Summary: Introduce application-wide Component#onComponentTag listeners Key: WICKET-6626 URL: https://issues.apache.org/jira/browse/WICKET-6626 Project: Wicket

[jira] [Updated] (WICKET-6626) Introduce application-wide Component#onComponentTag listeners

[ https://issues.apache.org/jira/browse/WICKET-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-6626: -- Fix Version/s: 7.12.0 9.0.0 8.3.0 > Introd

[jira] [Resolved] (WICKET-6623) Consecutive Temporary Behaviors are not properly removed

[ https://issues.apache.org/jira/browse/WICKET-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-6623. --- Resolution: Fixed Fix Version/s: 9.0.0 8.3.0

[jira] [Created] (WICKET-6623) Consecutive Temporary Behaviors are not properly removed

Igor Vaynberg created WICKET-6623: - Summary: Consecutive Temporary Behaviors are not properly removed Key: WICKET-6623 URL: https://issues.apache.org/jira/browse/WICKET-6623 Project: Wicket

[jira] [Commented] (WICKET-6604) Ajax repaint is not correctly handled when component being repainted has an enclosure associated with it and is not a child of the enclosure

[ https://issues.apache.org/jira/browse/WICKET-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668883#comment-16668883 ] Igor Vaynberg commented on WICKET-6604: --- forgot, its there now. > Ajax repaint is not correc

[jira] [Resolved] (WICKET-6604) Ajax repaint is not correctly handled when component being repainted has an enclosure associated with it and is not a child of the enclosure

[ https://issues.apache.org/jira/browse/WICKET-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-6604. --- Resolution: Fixed > Ajax repaint is not correctly handled when component being repain

[jira] [Resolved] (WICKET-6604) Ajax repaint is not correctly handled when component being repainted has an enclosure associated with it and is not a child of the enclosure

[ https://issues.apache.org/jira/browse/WICKET-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-6604. --- Resolution: Fixed > Ajax repaint is not correctly handled when component being repain

[jira] [Created] (WICKET-6604) Ajax repaint is not correctly handled when component being repainted has an enclosure associated with it and is not a child of the enclosure

Igor Vaynberg created WICKET-6604: - Summary: Ajax repaint is not correctly handled when component being repainted has an enclosure associated with it and is not a child of the enclosure Key: WICKET-6604 URL

Re: Repeaters, dynamic data & detaching models

> On Aug 27, 2018, at 6:00 AM, Tobias Gierke > wrote: > > Hi, > > A collegue of mine just came across a rather interesting bug in our Wicket > application. > > 1. We have a simple page with a repeater (ListView) that displays a table and > on each row, some buttons to perform actions on

Wicket Job Opportunity

Hi, My company is looking to fill a 100% telecommuting (must reside within two time zones of US/Central time GMT-0600) senior software engineer position. We use Wicket/Weld/Hibernate stack. If you are interested you can read more about the position here:

Re: Proposal: Improve syntax for inline anonymous class instantiations

he end of the day I think > this is quite reasonable, don't you? Yes, indeed. Thanks Alexander. I don't know why I didnt think of that myself. It is a little soupy since it adds an extra line and four extra keywords, but at least it allows this style of code. Thanks again, -Igor > > Che

Re: Proposal: Improve syntax for inline anonymous class instantiations

> On Jan 6, 2017, at 7:04 PM, Allen Wirfs-Brock wrote: > > (new class extends foo(bar) {…}) > is already valid syntax that means use the value return from calling foo with > argument bar as the superclass of the class that is being instantiated. What > you propose would

Proposal: Improve syntax for inline anonymous class instantiations

Given a simple class with an abstract method "populateItem" class ArrayView extends Container { constructor(id, model) { super(id); this.model = model; } // methods referencing "populateItem" omitted for clarity } the current anonymous instantiation syntax looks like

Re: proposal: behavior bundles

On Thu, Jul 17, 2014 at 9:08 AM, Garret Wilson gar...@globalmentor.com wrote: On 7/17/2014 8:25 AM, Martin Grigorov wrote: ... For some reason this feature doesn't seem that usable to me... Could you be more specific about why you don't find this feature doesn't seem useful? None of your

Re: [VOTE] Release Apache Wicket 6.16.0

+1 to release -igor On Thu, Jun 12, 2014 at 1:18 AM, Martin Grigorov mgrigo...@apache.org wrote: [X] Yes, release Apache Wicket 6.16.0 tested our main app, random wicket examples, local build Martin Grigorov Wicket Training and Consulting On Tue, Jun 10, 2014 at 3:37 PM, Sven Meier

[jira] [Commented] (WICKET-5566) Catch-All FencedFeedbackPanel has lost message in case of message-level filter in nested FencedFeedbackPanel

[ https://issues.apache.org/jira/browse/WICKET-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13976945#comment-13976945 ] Igor Vaynberg commented on WICKET-5566: --- indeed, this is as designed. messages do

Re: [VOTE] Release Apache Wicket 6.15.0

+1 to release -igor On Wed, Apr 16, 2014 at 3:56 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: This is a vote to release Apache Wicket 6.15.0 Please download the source distributions found in our staging area linked below. I have included the signatures for both the source

Re: [VOTE] Release Apache Wicket 7.0.0-M1

+1 to release -igor On Sun, Apr 20, 2014 at 1:44 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: WOW. This is the first of many votes to come for our first Wicket 7 release train. It took some work, but I managed to manipulate our projects, Maven and its release plugin to generate the

Re: Wicket 7: IChoiceRenderer restore or keep out?

On Wed, Mar 19, 2014 at 2:58 AM, Sven Meier s...@meiers.net wrote: Hi Martin, I'm +1 on releasing 7.x soon. ListMultipleChoice#getModelValue() and AbstractSingleSelectChoice#getModelValue() are still problematic though: Both call getChoices().indexOf(object), thus any non-primitive option

Re: Future of org.apache.wicket.util.iterator.ComponentHierarchyIterator

i think the visitors are a simpler solution. -igor On Mon, Mar 17, 2014 at 3:09 AM, Martin Grigorov mgrigo...@apache.org wrote: Hi, Juergen has introduced component hierarchy iterators with https://issues.apache.org/jira/browse/WICKET-3789 to simplify the hierarchy traversal via IVisitor.

Re: Best practice for updating JPA object without persisting changes

have a look here: https://www.42lines.net/2011/12/01/simplifying-non-trivial-user-workflows-with-conversations/ -igor On Wed, Mar 5, 2014 at 3:47 AM, Chris Snyder chris.sny...@biologos.org wrote: I'm dealing with an issue that I'm sure has been solved by many people on this list, but I'm

Re: Best practice for updating JPA object without persisting changes

- perhaps I should embrace a hard dependency on JPA and simplify everything. JPA is itself an abstraction layer, after all... Thanks, Chris On Wed, Mar 5, 2014 at 11:44 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote: have a look here: https://www.42lines.net/2011/12/01/simplifying-non-trivial

Re: Show textfield as plaintext when disabled?

class MyTextField extends TextField { onComponentTag(tag) { super.onComponentTag(tag); if (!enabledInHierarchy()) { tag.setName(label); tag.removeAttribute(type); tag.removeAttribute(value); tag.setType(TagType.OPEN); } } void

[jira] [Resolved] (WICKET-3335) Component Queuing (extract hierarchy information from markup)

[ https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-3335. --- Resolution: Fixed Fix Version/s: 7.0.0 Component Queuing (extract hierarchy

[jira] [Updated] (WICKET-3335) Component Queueing (extract hierarchy information from markup)

[ https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-3335: -- Summary: Component Queueing (extract hierarchy information from markup) (was: Component

[jira] [Commented] (WICKET-3335) Component Queueing (extract hierarchy information from markup)

[ https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915347#comment-13915347 ] Igor Vaynberg commented on WICKET-3335: --- user description of the implementation

Component Queueing is here (master), aka Free Wicket From Hierarchy Hell, aka Markup Driven Component Tree

in the past couple of weeks i finally had some time to finish up the component queueing feature. it is meant to greatly decrease common maintenance headaches associated with markup tweaks and moving components around. see the intro here:

Re: Wicket 7: IChoiceRenderer restore or keep out?

On Wed, Feb 26, 2014 at 8:00 AM, Sven Meier s...@meiers.net wrote: To add another point to the discussion: IMHO (I)ChoiceRenderer in 7.x is broken anyway. As long as the user has to implement #equals() in his model objects *or* override #getModelValue(), the choice renderer API is not yet

Re: [1/2] git commit: WICKET-3335 fragment and wicket:container support

Branch: refs/heads/master Commit: 61b01295d0d52929178d058d48456cae4acbc3e7 Parents: a79ed51 Author: Igor Vaynberg igor.vaynb...@gmail.com Authored: Mon Feb 24 11:09:12 2014 -0800 Committer: Igor Vaynberg igor.vaynb...@gmail.com Committed: Mon Feb 24 11:09:12 2014 -0800

Re: Markup driven component tree

tests fixed, merged into master. -igor On Tue, Feb 18, 2014 at 5:29 AM, Martin Grigorov mgrigo...@apache.org wrote: On Mon, Feb 17, 2014 at 5:48 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote: i think the implementation is good enough to be merged into master now. it supports: I am still

Re: git commit: WICKET-3335 test fixes

: 1fd9d57c0954f393e7cf6b6391d2f69c2815674d Parents: 63d15c5 Author: Igor Vaynberg igor.vaynb...@gmail.com Authored: Thu Feb 20 23:09:43 2014 -0800 Committer: Igor Vaynberg igor.vaynb...@gmail.com Committed: Thu Feb 20 23:18:25 2014 -0800

Re: ajax child component and enclosures visibility doesn't seem to work properly

that only works on inline enclosure - enclosures that do not use wicket:enclosure tags. -igor On Fri, Feb 21, 2014 at 5:37 AM, Simon B simon.bott...@gmail.com wrote: Hi, I'm using wicket 6.13. I've got an ajax link that I want to toggle the visibility of two components, each component is

Re: ajax child component and enclosures visibility doesn't seem to work properly

yes, thats what i mean. the markup you posted did not come through to the mailing list... -igor On Fri, Feb 21, 2014 at 7:48 AM, Simon B simon.bott...@gmail.com wrote: Hi Igor, Thanks for the reply. I'm a bit confused, the markup that I'm using (and that I posted originally) does have

Re: [2/2] git commit: WICKET-3335 nested borders working. everything should be working. needs more cleanup and javadoc

: 384d748c150031fa584aa44fce2f0a7e05e98531 Parents: 14797ed Author: Igor Vaynberg igor.vaynb...@gmail.com Authored: Sat Feb 15 00:40:48 2014 -0800 Committer: Igor Vaynberg igor.vaynb...@gmail.com Committed: Sat Feb 15 00:40:48 2014 -0800 -- .../java/org

Re: setting visibility of a component decocorated with a behavior

see IAjaxRegionMarkupIdProvider -igor On Mon, Feb 17, 2014 at 7:37 AM, Simon B simon.bott...@gmail.com wrote: Hi, I have a behavior that decorates the component that it is added to by using beforeRender(Component) and afterRender(Component). So a simplified version of my behavior would be

Re: setting visibility of a component decocorated with a behavior

cheers -igor On Mon, Feb 17, 2014 at 1:53 PM, Simon B simon.bott...@gmail.com wrote: Igor, Incidentally the javadoc on that interface is awesome, thanks for taking the time to make it so easily readable and understandable. Cheers Simon -- View this message in context:

Re: Markup driven component tree

structures maybe, but i dont think its needed... todo: * fragments - should be trivial, possibly as trivial as letting it implement IQueueRegion * check markup inheritance works on pages, panels, fragments. * examples * update to the guide -igor On Fri, Feb 14, 2014 at 8:36 AM, Igor Vaynberg

Re: Jetty, Wicket and getting live JavaScript changes?

Make sure wicket is running in development mode. It will scan resources for changes. A refresh in the browser will load the latest version. -igor On Feb 14, 2014 3:59 PM, tertioptus benpaige...@hotmail.com wrote: I use Jetty, maven and Eclipse. *What's the best way for me to have Jetty pick

Re: Jetty, Wicket and getting live JavaScript changes?

Yes. Because they have shared classpath. -igor On Feb 15, 2014 7:58 AM, tertioptus benpaige...@hotmail.com wrote: Even if the resource files are in another project? Which is my particular issue. /For instance: Module 1 - jar ---some-wicket-component.java ---some-javascript-file.js

Re: Markup driven component tree

i am reworking the implementation a bit to properly support borders and repeaters by delegating to components...will check it in when i have it working... -igor On Fri, Feb 14, 2014 at 7:26 AM, Martin Grigorov mgrigo...@apache.org wrote: On Mon, Feb 10, 2014 at 6:01 PM, Igor Vaynberg

Re: [VOTE] Release Apache Wicket 6.14.0 - second try

+1 -igor On Fri, Feb 14, 2014 at 7:45 AM, Jonas barney...@gmail.com wrote: [X] Yes, release Apache Wicket 6.14.0 (try 2) (non binding) Tested our main webapp, plus verified the jira tracks I've filed (WICKET-5469, WICKET-5493) cheers, Jonas On Fri, Feb 14, 2014 at 4:01 PM, Martijn

[jira] [Commented] (WICKET-3335) Component Queuing (extract hierarchy information from markup)

[ https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896310#comment-13896310 ] Igor Vaynberg commented on WICKET-3335: --- new implementation in sandbox/component

[jira] [Commented] (WICKET-3335) Component Queuing (extract hierarchy information from markup)

[ https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896324#comment-13896324 ] Igor Vaynberg commented on WICKET-3335: --- http://markmail.org/message

Re: Markup driven component tree

stuff. On Thu, Jan 23, 2014 at 6:09 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: what about components added in onInitialize() or on onConfigure()? this will also lead to a higher memory/serialization space usage since by default you need a field to store the component

Re: Markup driven component tree

On Mon, Feb 10, 2014 at 6:26 AM, Martin Grigorov mgrigo...@apache.org wrote: On Mon, Feb 10, 2014 at 9:43 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote: i just pushed my new idea into sandbox/component-queueing-2 the way this works now is instead of doing it in onInitialize

Re: [VOTE] Release Apache Wicket 1.4.22

+1 -igor On Thu, Jan 30, 2014 at 5:00 AM, Martin Grigorov mgrigo...@apache.orgwrote: This vote is to release Apache Wicket 1.4.22 Git repo http://git-wip-us.apache.org/repos/asf/wicket.git Branch name build/wicket-1.4.22 Archived and signed Git repo

Re: Eclipse formatting, was: Martin's wicket pull request

lines selected in the configuration? Regards Sven On 01/28/2014 09:52 AM, Igor Vaynberg wrote: apparently eclipse formatter setup in master is incorrect. i am working on a new queuing implementation idea and keep getting crap like this all over the code, any ideas? after running code

Re: [Vote] Release Apache Wicket 1.5.11

+1 -igor On Thu, Jan 23, 2014 at 1:00 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: +1 On Mon, Jan 20, 2014 at 5:09 PM, Martin Grigorov mgrigo...@apache.orgwrote: This vote is to release Apache Wicket 1.5.11 Git repo http://git-wip-us.apache.org/repos/asf/wicket.git Branch

Re: Markup driven component tree

what about components added in onInitialize() or on onConfigure()? this will also lead to a higher memory/serialization space usage since by default you need a field to store the component ref. not sure its worth doing it this way... -igor On Wed, Jan 22, 2014 at 12:12 PM, Martin Grigorov

Re: Markup driven component tree

for the reflection stuff. On Thu, Jan 23, 2014 at 6:09 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote: what about components added in onInitialize() or on onConfigure()? this will also lead to a higher memory/serialization space usage since by default you need a field to store the component ref

Re: Markup driven component tree

On Thu, Jan 23, 2014 at 8:53 AM, Martin Grigorov mgrigo...@apache.org wrote: On Thu, Jan 23, 2014 at 6:36 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote: On Thu, Jan 23, 2014 at 8:20 AM, Martin Grigorov mgrigo...@apache.org wrote: Once the markup driven construction is done (just before

[jira] [Resolved] (WICKET-4062) Introduce wicket:link attribute in addition to wicket:link tag

[ https://issues.apache.org/jira/browse/WICKET-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-4062. --- Resolution: Won't Fix Introduce wicket:link attribute in addition to wicket:link tag

[jira] [Commented] (WICKET-3491) Introduce IComponentConfigurationListener

[ https://issues.apache.org/jira/browse/WICKET-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13873530#comment-13873530 ] Igor Vaynberg commented on WICKET-3491: --- no, i did not have any strong opinions

Re: Why is getDisplayValue in getDisplayValue final?

that there is no reason to override that method directly as its functionality can be completely replaced by overriding postprocess()... so why override the original? -igor Martin Grigorov Wicket Training and Consulting On Thu, Jan 9, 2014 at 1:12 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote

Re: Why is getDisplayValue in getDisplayValue final?

the method is final because overriding it means you will most likely break the contract of the resourceKey and postprocess methods which are meant to be used by you to customze the behavior of getDisplayValue(). so lets say you create subclass MyEnumChoiceRenderer with an overridden

[jira] [Updated] (WICKET-5462) Ajax form-component-label repainting fails when setResponsePage() is used to navigate away from the page that has previously failed form validaiton

[ https://issues.apache.org/jira/browse/WICKET-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5462: -- Summary: Ajax form-component-label repainting fails when setResponsePage() is used

[jira] [Created] (WICKET-5462) Automatic form-component-label repainting fails when setResponsePage() is used to navigate away from the page that has previously failed form validaiton

Igor Vaynberg created WICKET-5462: - Summary: Automatic form-component-label repainting fails when setResponsePage() is used to navigate away from the page that has previously failed form validaiton Key: WICKET-5462

[jira] [Resolved] (WICKET-5462) Ajax form-component-label repainting fails when setResponsePage() is used to navigate away from the page that has previously failed form validaiton

[ https://issues.apache.org/jira/browse/WICKET-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-5462. --- Resolution: Fixed Fix Version/s: 7.0.0 6.13.0 Ajax form

[jira] [Updated] (WICKET-5462) Ajax form-component-label repainting fails when setResponsePage() is used to navigate away from the page that has previously failed form validaiton

[ https://issues.apache.org/jira/browse/WICKET-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5462: -- Fix Version/s: (was: 6.13.0) 6.14.0 Ajax form-component-label

Re: [jira] [Resolved] (WICKET-5462) Ajax form-component-label repainting fails when setResponsePage() is used to navigate away from the page that has previously failed form validaiton

indeed, 6.13 hasnt been marked as released in jira yet... On Mon, Jan 6, 2014 at 11:47 AM, Sven Meier s...@meiers.net wrote: Fix Version/s: 7.0.0 6.13.0 That should be 6.14.0, no? Sven On 01/06/2014 07:27 PM, Igor Vaynberg (JIRA) wrote: [ https

Re: The state of Wicket 6.13

+1 to rebase On Sun, Jan 5, 2014 at 8:39 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: All, Since a long time I have tried to coerce the Maven release plugin to actually build a release. It appears that newer versions of git have altered the output format on which the m-r-p depends

Re: Passing Component or Class to IAuthorizationStrategy#isInstantiationAuthorized()

this is a security check, so the whole idea is that it is ran before any of the user's code in the constructor which may have side-effects. eg a constructor marking a record as ready to be deleted because a delete panel was instantiated. the class itself should be enough. even if you get an

Re: Passing Component or Class to IAuthorizationStrategy#isInstantiationAuthorized()

the page instance for anything Martin Grigorov Wicket Training and Consulting On Fri, Dec 20, 2013 at 6:14 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote: this is a security check, so the whole idea is that it is ran before any of the user's code in the constructor which may have side-effects

[jira] [Commented] (WICKET-663) enhance ichoicerenderer with id-choice object lookup

[ https://issues.apache.org/jira/browse/WICKET-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13853007#comment-13853007 ] Igor Vaynberg commented on WICKET-663: -- looks good. the only other thing i would

Re: wicket-el - is this a safe way to hook into wicket?

On Wed, Dec 18, 2013 at 9:40 PM, Steve Coughlan shadders@gmail.com wrote: A few weeks back I made a post about the first version of universal expression language for wicket. Since then it's come quite a way. The initial version hooked into by implementing IMarkupResourceStreamProvider

[jira] [Commented] (WICKET-663) enhance ichoicerenderer with id-choice object lookup

[ https://issues.apache.org/jira/browse/WICKET-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851877#comment-13851877 ] Igor Vaynberg commented on WICKET-663: -- something to look into in wicket 7 enhance

[jira] [Commented] (WICKET-663) enhance ichoicerenderer with id-choice object lookup

[ https://issues.apache.org/jira/browse/WICKET-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852122#comment-13852122 ] Igor Vaynberg commented on WICKET-663: -- the way this works currently is: lets say i

[jira] [Commented] (WICKET-5224) ModalWindow is not visible in Safari when opened from a link at the bottom of a large page

[ https://issues.apache.org/jira/browse/WICKET-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13844409#comment-13844409 ] Igor Vaynberg commented on WICKET-5224: --- looks like this issue is back

[jira] [Reopened] (WICKET-5224) ModalWindow is not visible in Safari when opened from a link at the bottom of a large page

[ https://issues.apache.org/jira/browse/WICKET-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg reopened WICKET-5224: --- ModalWindow is not visible in Safari when opened from a link at the bottom of a large page

[jira] [Updated] (WICKET-5224) ModalWindow is not visible in Safari when opened from a link at the bottom of a large page

[ https://issues.apache.org/jira/browse/WICKET-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5224: -- Fix Version/s: (was: 6.10.0) 6.13.0 ModalWindow is not visible

[jira] [Commented] (WICKET-5224) ModalWindow is not visible in Safari when opened from a link at the bottom of a large page

[ https://issues.apache.org/jira/browse/WICKET-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13844420#comment-13844420 ] Igor Vaynberg commented on WICKET-5224: --- reverted the revert, seems to have fixed

[jira] [Resolved] (WICKET-5224) ModalWindow is not visible in Safari when opened from a link at the bottom of a large page

[ https://issues.apache.org/jira/browse/WICKET-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-5224. --- Resolution: Fixed ModalWindow is not visible in Safari when opened from a link

[jira] [Resolved] (WICKET-5411) Improve AutoLabels by updating their CSS classes automatically during Ajax requests

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-5411. --- Resolution: Fixed Improve AutoLabels by updating their CSS classes automatically during

Re: Enfocing INPUT field names to respect hCard formats

override getInputName() and return the string you want. -igor On Sun, Nov 17, 2013 at 5:21 AM, Arjun Dhar dhar...@yahoo.com wrote: http://microformats.org/wiki/hcard-input-examples#person_billing_shipping_input To ensure browsers can Auto fill Input form fields for E-Commerce forms and

[jira] [Commented] (WICKET-5417) this.replaceWith is broken when called from onInitialize

[ https://issues.apache.org/jira/browse/WICKET-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13823752#comment-13823752 ] Igor Vaynberg commented on WICKET-5417: --- whats the usecase for component replacing

[jira] [Reopened] (WICKET-5418) PropertyValidator ignoring groups with the @NotNull annotation only

[ https://issues.apache.org/jira/browse/WICKET-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg reopened WICKET-5418: --- PropertyValidator ignoring groups with the @NotNull annotation only

[jira] [Resolved] (WICKET-5418) PropertyValidator ignoring groups with the @NotNull annotation only

[ https://issues.apache.org/jira/browse/WICKET-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-5418. --- Resolution: Fixed Fix Version/s: 7.0.0 6.13.0 PropertyValidator

Re: Future of wicket-cdi

i agree we should restart with the original implementation and incrementally introduce the new features - thats what i proposed in the original pull request. i am not a big fan of having the application instance managed. what is the value of this? it can be injected using noncontextual just like

Re: Future of wicket-cdi

the application and configured it got called before internalInit(). either create a subcpass with @PostConstruct that configures the application - which wont work - people dont like using subclasses - or create a provider. -igor On Wed, Nov 13, 2013 at 4:31 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote

Re: Future of wicket-cdi

On Wed, Nov 13, 2013 at 2:42 PM, John Sarman johnsar...@gmail.com wrote: snip further you are assuming i am running inside a container that has its filter's managed by cdi, this is not always the case so using your cdi filter would fail. one would have to fall back on wicket-filter and I

Re: Future of wicket-cdi

(this); // after the line above the application is injected and resource is now available. by default injectApplication bit in CdiConfiguration is set to true and it passes the instance through NonContextual. resource.doSomething(); } } -igor On Wed, Nov 13, 2013 at 6:40 PM, Igor

Re: weld conversation propagation page

this is the desired behavior. see conversation propagation settings. by default conversations are only propagated to non-bookmarkable pages. -igor On Wed, Nov 13, 2013 at 4:36 AM, brazz alexander.li...@man.eu wrote: Hi, after spending a hard time debugging i found this problem: i have to

[jira] [Commented] (WICKET-5411) Improve AutoLabels by updating their CSS classes automatically during Ajax requests

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820226#comment-13820226 ] Igor Vaynberg commented on WICKET-5411: --- i wasnt going to close it until i tested

[jira] [Resolved] (WICKET-5411) Improve AutoLabels by updating their CSS classes automatically during Ajax requests

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg resolved WICKET-5411. --- Resolution: Fixed Improve AutoLabels by updating their CSS classes automatically during

Re: Eclipse formatting, was: Martin's wicket pull request

, Nov 10, 2013 at 12:45 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote: yes, making it a workspace default messes up other projects... this way every time i import a project into the eclipse workspace i have to go and manually set the formatter on every module, which as you can imagine

Re: remove recently merged cdi 1.1 from 6.x

the point on INonContextualManager was to internalize NonContextual - in case cdi implementation provides a better way to perform non-contextual injection. now that NonContextualManager is @ApplicationScoped and CdiConfiguration does not have a setter for it this functionality is lost. and even

Re: git commit: WICKET-5411 auto label auto update during ajax

-us.apache.org/repos/asf/wicket/tree/a73209be Diff: http://git-wip-us.apache.org/repos/asf/wicket/diff/a73209be Branch: refs/heads/wicket-6.x Commit: a73209beab8814a06f2e085384ad87bdf1fda212 Parents: 4e9a83f Author: Igor Vaynberg igor.vaynb...@gmail.com Authored: Fri Nov 8 22:48:22 2013 -0800 Committer

Re: Eclipse formatting, was: Martin's wicket pull request

...@apache.org wrote: But you have to import the xml just once, right ? It is not a big deal. Or the problem is that the xml messes up the other projects in your workspace ? On Sat, Nov 9, 2013 at 7:24 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote: it is really frustrating that i have to do

[jira] [Created] (WICKET-5410) Remove setting interfaces

Igor Vaynberg created WICKET-5410: - Summary: Remove setting interfaces Key: WICKET-5410 URL: https://issues.apache.org/jira/browse/WICKET-5410 Project: Wicket Issue Type: Improvement

[jira] [Created] (WICKET-5411) Improve AutoLabels to update their CSS dynamically

Igor Vaynberg created WICKET-5411: - Summary: Improve AutoLabels to update their CSS dynamically Key: WICKET-5411 URL: https://issues.apache.org/jira/browse/WICKET-5411 Project: Wicket Issue

[jira] [Updated] (WICKET-5411) Improve AutoLabels to update their CSS dynamically

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5411: -- Fix Version/s: 6.13.0 Improve AutoLabels to update their CSS dynamically

[jira] [Updated] (WICKET-5411) Improve AutoLabels to update their CSS dynamically

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5411: -- Description: The problem with auto labels is that once they are rendered the only way

[jira] [Updated] (WICKET-5411) Improve AutoLabels by updating their CSS classes automatically during Ajax requests

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5411: -- Summary: Improve AutoLabels by updating their CSS classes automatically during Ajax requests

[jira] [Updated] (WICKET-5411) Improve AutoLabels to update their CSS dynamically

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5411: -- Description: The problem with auto labels is that once they are rendered the only way

[jira] [Updated] (WICKET-5411) Improve AutoLabels by updating their CSS classes automatically during Ajax requests

[ https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-5411: -- Description: The problem with auto labels is that once they are rendered the only way

  1   2   3   4   5   6   7   8   9   10   >