Re: page load timer
Milliseconds according to WIA Cheers, Adrian On 6/13/09, Igor Vaynberg igor.vaynb...@gmail.com wrote: dont remember offhand, look in the source. -igor On Fri, Jun 12, 2009 at 9:29 AM, Steve Swinsburgs.swinsb...@lancaster.ac.uk wrote: Thats the one I was after. A question though, what units are the measurements displayed in? time/totaltime in milliseconds, session size in bytes? thanks, Steve - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Fwd: [ANN] Maven Eclipse Plugin 2.7 Released
The Maven Eclipse plugin version 2.7 has been released, fixing the regression in functionality of 2.6 where Wicket resources (*.html, *.js, *.properties, etc) were not copied to the classpath. This release fixes that, and we can now all relax ;) Thanks to Barrie and other Maven devs for investing their precious time into fixing this problem. Martijn -- Forwarded message -- From: Barrie Treloar baerr...@apache.org Date: Sun, Jun 14, 2009 at 12:44 AM Subject: [ANN] Maven Eclipse Plugin 2.7 Released To: annou...@maven.apache.org, us...@maven.apache.org Cc: d...@maven.apache.org The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.7 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.7/version /plugin Release Notes - Maven 2.x Eclipse Plugin - Version 2.7 ** Bug * [MECLIPSE-434] - WTP 2.0 Documentation * [MECLIPSE-451] - EJB projects are not correctly referenced in .component * [MECLIPSE-455] - Invalid dependent module archive name for EJB artifact * [MECLIPSE-538] - Ajdt support needs to include*.aj on the classpath. * [MECLIPSE-546] - Aspectj libraries are included if using the aspectj jars from the springsource bundle repository * [MECLIPSE-551] - [regression] Resources are excluded if resource dir equals source dir * [MECLIPSE-553] - Maven Eciipse Plugin 2.6 excludes *.aj files from src/main/java ** Improvement * [MECLIPSE-327] - Improve documentation for options * [MECLIPSE-545] - Site documentation needs to be added to show how to use ajdt. * [MECLIPSE-547] - Maven Eclipse plugin 2.6 with AJDT changes are not backwards compatible. ** New Feature * [MECLIPSE-104] - Add the ability to specify source inclusions/exclusions Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
DOJO Menu Items and AJAX-Target-Components
Hi, i use dojo menues in my application and mostly it works fine. but when an other ajax-call refreshed menu's target component the menu will not be displayed. it seams, that the markup-id of wicket-component changed after ajax-refresh and so the dojo-js cannot find the menu item for this wicket-component. had anybody the same problem? when not what could be the problem? thanks alex - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
AW: DOJO Menu Items and AJAX-Target-Components
Yes! the markup-id of wicket-component changed after ajax-refresh as you wrote. I' looking for a solution for another javaxript library. Any hints from the Wicket gurus? -Ursprüngliche Nachricht- Von: news [mailto:n...@ger.gmane.org] Im Auftrag von Alexander Elsholz Gesendet: Sonntag, 14. Juni 2009 13:44 An: users@wicket.apache.org Betreff: DOJO Menu Items and AJAX-Target-Components Hi, i use dojo menues in my application and mostly it works fine. but when an other ajax-call refreshed menu's target component the menu will not be displayed. it seams, that the markup-id of wicket-component changed after ajax-refresh and so the dojo-js cannot find the menu item for this wicket-component. had anybody the same problem? when not what could be the problem? thanks alex - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DOJO Menu Items and AJAX-Target-Components
new markup id means you created new component instances. wicket does its best to try to preserver markup id - eg when you use replace or replacewith wicket will transfer new markupid of the component being replaced into the component it is being replaced with. if you need stable ids call setmarkupid() and propagate it to whatever hieararchy changes you are making. although for a menu it may help to use a non-volatile hierarchy since menus are usually static. -igor On Sun, Jun 14, 2009 at 7:09 AM, Stefan Lindnerlind...@visionet.de wrote: Yes! the markup-id of wicket-component changed after ajax-refresh as you wrote. I' looking for a solution for another javaxript library. Any hints from the Wicket gurus? -Ursprüngliche Nachricht- Von: news [mailto:n...@ger.gmane.org] Im Auftrag von Alexander Elsholz Gesendet: Sonntag, 14. Juni 2009 13:44 An: users@wicket.apache.org Betreff: DOJO Menu Items and AJAX-Target-Components Hi, i use dojo menues in my application and mostly it works fine. but when an other ajax-call refreshed menu's target component the menu will not be displayed. it seams, that the markup-id of wicket-component changed after ajax-refresh and so the dojo-js cannot find the menu item for this wicket-component. had anybody the same problem? when not what could be the problem? thanks alex - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicket:message on an attribute
Is there a way to use wicket:message on markup attributes? Pseudo something like this? li title='wicket:message key=category/' Thanks, -Luther
Re: wicket:message on an attribute
http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html#Wicket%27sXHTMLtags-Attributewicket:message *wicket:message=attribute:resource_identifier* - Used on any tag that we want Wicket to provide an attribute with a value that's the result of a resource lookup. Maarten On Sun, Jun 14, 2009 at 5:04 PM, Luther Baker lutherba...@gmail.com wrote: Is there a way to use wicket:message on markup attributes? Pseudo something like this? li title='wicket:message key=category/' Thanks, -Luther
Re: wicket:message on an attribute
That did it - thank you, -Luther On Sun, Jun 14, 2009 at 10:14 AM, Maarten Bosteels mbosteels@gmail.comwrote: http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html#Wicket%27sXHTMLtags-Attributewicket:message *wicket:message=attribute:resource_identifier* - Used on any tag that we want Wicket to provide an attribute with a value that's the result of a resource lookup. Maarten On Sun, Jun 14, 2009 at 5:04 PM, Luther Baker lutherba...@gmail.com wrote: Is there a way to use wicket:message on markup attributes? Pseudo something like this? li title='wicket:message key=category/' Thanks, -Luther
RE: DOJO Menu Items and AJAX-Target-Components
Just playing around with current wicket 1.4 trunk.
Having a a page with HTML like
div wicket:id=someContainer.../div
a wicket:id=triggerTest/a
and java like
final WebMarkupContainer container = new WebMarkupContainer(someContainer
);
container.addMarkupID true;
add(container);
add(new AjaxLinkVoid( trigger ) {
@Override
public void onClick(AjaxRequestTarget target) {
container.testAjaxRefresh(target);
}
});
Now deploying this in an application with AjaxDebugging set to true shows that
the markup id does NOT change when the link is clicked.
BUT
Having a custom AjaxBehavior added to container depending on some free
javscript libraries (e.g. Dojo, jQuery), the triggers get lost after the
original HTML contet was replaced in DOM. In other words: the Ajax response
replaces the original element and the functionality gets lost.
If the custom AjaxBehavior coud re-act in seponse tot he Ajax call and
reinstall the behavior, the custom AjaxBehavior could take care of this. But I
can't see where this can bedone.
This happens when the behavior is configured in the head section by calling
somthing like this (jquery)
jQuery(function(){jquery('#markupID').doSomnething();});
which means after DOM has built, bind 'doSomething()' to Wicket Component
'markupID').
If the behavior is configured in the body with a script section following the
Wicket Component, this script eection is re-rendered in response to to the
AjaxCall (in the on onComponentRendered() method) and the custom behavior is
re-activated.
Conclusion:
If a javascript action is bound to some component and some trigger, a DOM
replacement of this component (e.g. through an Ajax call with ing wicket via
AjaxRequestTarget.addComponent()) diables the action and needs to be
re-activated in the Ajax response.
I don't know if this is the case in DOJO menu items (I think so when I'm
looking at the old DOJO 0.4 implementation of drag and drop) but I see that I
need to modify my impelmantation of jQuery integration into wicket (currently
working on this, testet a seolution and proved it working).
-Ursprüngliche Nachricht-
Von: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Gesendet: Sonntag, 14. Juni 2009 16:43
An: users@wicket.apache.org
Betreff: Re: DOJO Menu Items and AJAX-Target-Components
new markup id means you created new component instances. wicket does
its best to try to preserver markup id - eg when you use replace or
replacewith wicket will transfer new markupid of the component being
replaced into the component it is being replaced with.
if you need stable ids call setmarkupid() and propagate it to whatever
hieararchy changes you are making. although for a menu it may help to
use a non-volatile hierarchy since menus are usually static.
-igor
On Sun, Jun 14, 2009 at 7:09 AM, Stefan Lindnerlind...@visionet.de wrote:
Yes! the markup-id of wicket-component changed after ajax-refresh as you
wrote.
I' looking for a solution for another javaxript library. Any hints from the
Wicket gurus?
-Ursprüngliche Nachricht-
Von: news [mailto:n...@ger.gmane.org] Im Auftrag von Alexander Elsholz
Gesendet: Sonntag, 14. Juni 2009 13:44
An: users@wicket.apache.org
Betreff: DOJO Menu Items and AJAX-Target-Components
Hi,
i use dojo menues in my application and mostly it works fine. but when an
other
ajax-call refreshed menu's target component the menu will not be displayed. it
seams, that the markup-id of wicket-component changed after ajax-refresh and
so
the dojo-js cannot find the menu item for this wicket-component.
had anybody the same problem?
when not what could be the problem?
thanks alex
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: DOJO Menu Items and AJAX-Target-Components
hi, i don't remove/add the components. the hierarchy is constant. its a very simple app: - add an ajaxlink and change the attributemodifier of a panel - add a menu item to the same panel after rerendering the panel (after link clicked) the menu will no more be displayed. i've the same problem in my table when using ajax and dojo menues i tried to set the markup-id manually, but no effect. the associated javascript uses the static markupid i set in code, but after rerendering the panel asynchron it does'nt work. alex - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DOJO Menu Items and AJAX-Target-Components
well if the id doesnt change - eg you called setmarkupid and you do not replace the component then i do not see what else wicket can do. perhaps dojo keeps a direct reference to a dom node instead of just the id - repainting the component will replace the dom node itself which i guess may break the script. -igor On Sun, Jun 14, 2009 at 8:51 AM, Alexander Elsholzalexander.elsh...@widas.de wrote: hi, i don't remove/add the components. the hierarchy is constant. its a very simple app: - add an ajaxlink and change the attributemodifier of a panel - add a menu item to the same panel after rerendering the panel (after link clicked) the menu will no more be displayed. i've the same problem in my table when using ajax and dojo menues i tried to set the markup-id manually, but no effect. the associated javascript uses the static markupid i set in code, but after rerendering the panel asynchron it does'nt work. alex - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DOJO Menu Items and AJAX-Target-Components
your custom ajaxbehavior can implement iheadercontributor where you
can do response.appendjavascript to output a script that will be
processed in both regular requests and ajax requests alike.
-igor
On Sun, Jun 14, 2009 at 8:44 AM, Stefan Lindnerlind...@visionet.de wrote:
Just playing around with current wicket 1.4 trunk.
Having a a page with HTML like
div wicket:id=someContainer.../div
a wicket:id=triggerTest/a
and java like
final WebMarkupContainer container = new
WebMarkupContainer(someContainer );
container.addMarkupID true;
add(container);
add(new AjaxLinkVoid( trigger ) {
�...@override
public void onClick(AjaxRequestTarget target) {
container.testAjaxRefresh(target);
}
});
Now deploying this in an application with AjaxDebugging set to true shows
that the markup id does NOT change when the link is clicked.
BUT
Having a custom AjaxBehavior added to container depending on some free
javscript libraries (e.g. Dojo, jQuery), the triggers get lost after the
original HTML contet was replaced in DOM. In other words: the Ajax response
replaces the original element and the functionality gets lost.
If the custom AjaxBehavior coud re-act in seponse tot he Ajax call and
reinstall the behavior, the custom AjaxBehavior could take care of this. But
I can't see where this can bedone.
This happens when the behavior is configured in the head section by calling
somthing like this (jquery)
jQuery(function(){jquery('#markupID').doSomnething();});
which means after DOM has built, bind 'doSomething()' to Wicket Component
'markupID').
If the behavior is configured in the body with a script section following
the Wicket Component, this script eection is re-rendered in response to to
the AjaxCall (in the on onComponentRendered() method) and the custom behavior
is re-activated.
Conclusion:
If a javascript action is bound to some component and some trigger, a DOM
replacement of this component (e.g. through an Ajax call with ing wicket via
AjaxRequestTarget.addComponent()) diables the action and needs to be
re-activated in the Ajax response.
I don't know if this is the case in DOJO menu items (I think so when I'm
looking at the old DOJO 0.4 implementation of drag and drop) but I see that I
need to modify my impelmantation of jQuery integration into wicket (currently
working on this, testet a seolution and proved it working).
-Ursprüngliche Nachricht-
Von: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Gesendet: Sonntag, 14. Juni 2009 16:43
An: users@wicket.apache.org
Betreff: Re: DOJO Menu Items and AJAX-Target-Components
new markup id means you created new component instances. wicket does
its best to try to preserver markup id - eg when you use replace or
replacewith wicket will transfer new markupid of the component being
replaced into the component it is being replaced with.
if you need stable ids call setmarkupid() and propagate it to whatever
hieararchy changes you are making. although for a menu it may help to
use a non-volatile hierarchy since menus are usually static.
-igor
On Sun, Jun 14, 2009 at 7:09 AM, Stefan Lindnerlind...@visionet.de wrote:
Yes! the markup-id of wicket-component changed after ajax-refresh as you
wrote.
I' looking for a solution for another javaxript library. Any hints from the
Wicket gurus?
-Ursprüngliche Nachricht-
Von: news [mailto:n...@ger.gmane.org] Im Auftrag von Alexander Elsholz
Gesendet: Sonntag, 14. Juni 2009 13:44
An: users@wicket.apache.org
Betreff: DOJO Menu Items and AJAX-Target-Components
Hi,
i use dojo menues in my application and mostly it works fine. but when an
other
ajax-call refreshed menu's target component the menu will not be displayed.
it
seams, that the markup-id of wicket-component changed after ajax-refresh and
so
the dojo-js cannot find the menu item for this wicket-component.
had anybody the same problem?
when not what could be the problem?
thanks alex
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For
RE: Re: DOJO Menu Items and AJAX-Target-Components
Yes, that's what I wrote. The ID does not change but the response of the Ajax
call replaces the original Wicket Component in THE DOM with a new Component
WITH THE SAME ID but fresh on... events. So the original event behavior (e.g.
menu display) gets lost. It needs tob e re-established in the Ajax resonse. For
wicket events (bound to onclick e.g.) this is done when the comonent is written
as a stream tot je Ajax response. Such an Ajax resonse looks like
component id=id1 encoding=wicket1 ![CDATA[a
class=draggableComponent
href=wicket:interface=:0:draggable1:draggableLink::ILinkListener::
style=display:block; height:80px; width:200px; id=id1 onclick=var
wcall=wicketAjaxGet('?wicket:interface=:0:draggable1:draggableLink::IBehaviorListener:0:-1',null,null,
function() {return Wicket.$('id1') != null;}.bind(this));return !wcall;
I am draggable.br/
span style=font-size:110%; font-weight:bold; id=id8Drag
me!/span
br/
span style=font-size:80%(Or click me and see what
happens...)/span
/ascript type=text/javascript !--/*--![CDATA[/*!--*/
-Ursprüngliche Nachricht-
Von: news [mailto:n...@ger.gmane.org] Im Auftrag von Alexander Elsholz
Gesendet: Sonntag, 14. Juni 2009 17:51
An: users@wicket.apache.org
Betreff: Re: DOJO Menu Items and AJAX-Target-Components
hi,
i don't remove/add the components. the hierarchy is constant. its a
very simple app:
- add an ajaxlink and change the attributemodifier of a panel
- add a menu item to the same panel
after rerendering the panel (after link clicked) the menu will no
more be displayed.
i've the same problem in my table when using ajax and dojo menues
i tried to set the markup-id manually, but no effect.
the associated javascript uses the static markupid i set in code,
but after rerendering the panel asynchron it does'nt work.
alex
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: DOJO Menu Items and AJAX-Target-Components
Yes Igor, we do this. But this seems not tob e sufficient for some java
libraries. The first time (after the initial page load) everything works. But
after an Ajax call (where the head section is present in the Ajax response)
the behavior is broken. Wat seems to work is to put the javascript stuff into
the body tag using the onComponentRendered() method like
JavascriptUtils.writeJavascript(RequestCycle.get().getResponse(), my
javascript);
-Ursprüngliche Nachricht-
Von: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Gesendet: Sonntag, 14. Juni 2009 18:42
An: users@wicket.apache.org
Betreff: Re: DOJO Menu Items and AJAX-Target-Components
your custom ajaxbehavior can implement iheadercontributor where you
can do response.appendjavascript to output a script that will be
processed in both regular requests and ajax requests alike.
-igor
On Sun, Jun 14, 2009 at 8:44 AM, Stefan Lindnerlind...@visionet.de wrote:
Just playing around with current wicket 1.4 trunk.
Having a a page with HTML like
div wicket:id=someContainer.../div
a wicket:id=triggerTest/a
and java like
final WebMarkupContainer container = new
WebMarkupContainer(someContainer );
container.addMarkupID true;
add(container);
add(new AjaxLinkVoid( trigger ) {
�...@override
public void onClick(AjaxRequestTarget target) {
container.testAjaxRefresh(target);
}
});
Now deploying this in an application with AjaxDebugging set to true shows
that the markup id does NOT change when the link is clicked.
BUT
Having a custom AjaxBehavior added to container depending on some free
javscript libraries (e.g. Dojo, jQuery), the triggers get lost after the
original HTML contet was replaced in DOM. In other words: the Ajax response
replaces the original element and the functionality gets lost.
If the custom AjaxBehavior coud re-act in seponse tot he Ajax call and
reinstall the behavior, the custom AjaxBehavior could take care of this. But
I can't see where this can bedone.
This happens when the behavior is configured in the head section by calling
somthing like this (jquery)
jQuery(function(){jquery('#markupID').doSomnething();});
which means after DOM has built, bind 'doSomething()' to Wicket Component
'markupID').
If the behavior is configured in the body with a script section following
the Wicket Component, this script eection is re-rendered in response to to
the AjaxCall (in the on onComponentRendered() method) and the custom behavior
is re-activated.
Conclusion:
If a javascript action is bound to some component and some trigger, a DOM
replacement of this component (e.g. through an Ajax call with ing wicket via
AjaxRequestTarget.addComponent()) diables the action and needs to be
re-activated in the Ajax response.
I don't know if this is the case in DOJO menu items (I think so when I'm
looking at the old DOJO 0.4 implementation of drag and drop) but I see that I
need to modify my impelmantation of jQuery integration into wicket (currently
working on this, testet a seolution and proved it working).
-Ursprüngliche Nachricht-
Von: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Gesendet: Sonntag, 14. Juni 2009 16:43
An: users@wicket.apache.org
Betreff: Re: DOJO Menu Items and AJAX-Target-Components
new markup id means you created new component instances. wicket does
its best to try to preserver markup id - eg when you use replace or
replacewith wicket will transfer new markupid of the component being
replaced into the component it is being replaced with.
if you need stable ids call setmarkupid() and propagate it to whatever
hieararchy changes you are making. although for a menu it may help to
use a non-volatile hierarchy since menus are usually static.
-igor
On Sun, Jun 14, 2009 at 7:09 AM, Stefan Lindnerlind...@visionet.de wrote:
Yes! the markup-id of wicket-component changed after ajax-refresh as you
wrote.
I' looking for a solution for another javaxript library. Any hints from the
Wicket gurus?
-Ursprüngliche Nachricht-
Von: news [mailto:n...@ger.gmane.org] Im Auftrag von Alexander Elsholz
Gesendet: Sonntag, 14. Juni 2009 13:44
An: users@wicket.apache.org
Betreff: DOJO Menu Items and AJAX-Target-Components
Hi,
i use dojo menues in my application and mostly it works fine. but when an
other
ajax-call refreshed menu's target component the menu will not be displayed.
it
seams, that the markup-id of wicket-component changed after ajax-refresh and
so
the dojo-js cannot find the menu item for this wicket-component.
had anybody the same problem?
when not what could be the problem?
thanks alex
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: changing choices component in Palette
any 1
?
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't print this e-mail unless it's really necessary
On Fri, Jun 12, 2009 at 7:13 AM, Eyal Golan egola...@gmail.com wrote:
BTW,
we use Wicket 1.3.6
I will try to rephrase my original question:
why are getChoicesComponent and getSelectionComponent() private?
Can I add a Wish in Jira to make them public?
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't print this e-mail unless it's really necessary
On Thu, Jun 11, 2009 at 5:30 PM, Eyal Golan egola...@gmail.com wrote:
Hi,
I have a situation that I want to change possible choices in a palette
according to a DropDown.
I added to the DropDown the Ajax Updating
add(new AjaxFormComponentUpdatingBehavior(onchange) {...}
I have this palette:
final CustomPalette palette = new CustomPalette(palette, new
PropertyModel(rolesCoverage, comparedConfigurations),
allConfigurationsModel, choiceRenderer, 10, true);
and:
final IModel allConfigurationsModel = new AbstractReadOnlyModel()
{
private static final long serialVersionUID = 1L;
@Override
public Object getObject() {
final ListConfiguration allConfigs =
sageDal.getConfigurations();
allConfigs.remove(rolesCoverage.getMainConfiguration());
return allConfigs;
}
};
The page uses CompoundPropertModel: super(id, new
CompoundPropertyModel(rolesCoverage)); in the constructor.
The problem that I encountered is that if I added to the target of the
DropDown the palette, it kept remembering my selected values.
In order to change that I hacked a bit with our CustomPalette:
@Override
protected Component newChoicesComponent() {
final Component result = super.newChoicesComponent();
externalizedChoiceComponent = result;
externalizedChoiceComponent.setOutputMarkupId(true);
return result;
}
public Component getExternalizedChoiceComponent() {
return this.externalizedChoiceComponent;
}
And in the DropDown, instead of adding the palette, I used
target.addComponent(customPalette.getExternalizedChoiceComponent());
It works.
My question is if this is the correct way? Is there a better way doing
that?
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't print this e-mail unless it's really
necessary
Re: inmethod datagrid with a DropDownChoice cell
Hello Will! Have you solved this problem? I also need to have a data grid component with dropdown column and can not find any examples. Thanks in advance! //Zeljko -- View this message in context: http://www.nabble.com/inmethod-datagrid-with-a-DropDownChoice-cell-tp22068863p24025546.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
EmailAddressValidator does not conform RFC'
Hi all, The EmailAddressValidator is not conform RFC' and commonly used forms. The RFC' to look at are 5322 and 3696 (this RFC explains the details in a readable way). Has anyone else experienced this as well? regards, Harrie - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: EmailAddressValidator does not conform RFC'
see org.apache.wicket.extensions.validation.validator.RfcCompliantEmailAddressValidator -igor On Sun, Jun 14, 2009 at 1:54 PM, Harrie Hazewinkelhar...@tipspot.com wrote: Hi all, The EmailAddressValidator is not conform RFC' and commonly used forms. The RFC' to look at are 5322 and 3696 (this RFC explains the details in a readable way). Has anyone else experienced this as well? regards, Harrie - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
