Re: Popup parent comunication
Not entirely sure about this, but i think this is because wicket is
smart enough to figure out it has already sent the header, so it won't
send it again. If you want to invoke that script again you should
trigger it from your ajax call with target.appendJavaScript().
Maurice
On Nov 7, 2007 6:11 PM, serban.balamaci <[EMAIL PROTECTED]> wrote:
>
> Yes, you must be right, another issue against the modal window is that the
> datepicker does not work inside it, and I pretty much decided to stick to
> normal popups.
>
> Well it seems that i may have something here:
>
> In the parent page:
> add(new AbstractDefaultAjaxBehavior() {
> protected void respond(AjaxRequestTarget ajaxRequestTarget) {
> System.out.println("Ajax Method invoked");
> }
>
> protected void onRenderHeadContribution(final Response response)
> {
> super.onRenderHeadContribution(response);
> StringHeaderContributor header =
> new StringHeaderContributor(" language=\"javascript\"> " +
> "function call() {" +
> getCallbackScript(false, true) + "};" +
> "");
> ((WebPage)getComponent().getPage()).add(header);
> }
> });
>
> In the popup window we have the link:
>
> Link link = new Link("addLink") {
> public void onClick() {
> System.out.println("Ajax Method invoked");
> }
>
> protected CharSequence getOnClickScript(CharSequence
> charSequence) {
> CharSequence click =
> super.getOnClickScript(charSequence);
> if(click == null) {
> return "self.opener.call();";
> }
> return click + "self.opener.call();";
> }
>
> };
>
>
> Current problem is that the method sometimes gets invoked sometimes it does
> not(the text "Ajax Method invoked" apears on the screen). Actually only the
> first time in most cases. The problem must be with the ajax call cause i
> added in the call function a debug message in javascript that gets always
> called(the call function).
>
> Anybody has any ideas why this is?
>
>
>
> Mr Mean wrote:
> >
> > if your modal dialog contains ajax tabs it should work, but all your
> > user interaction from withing the dialog must be ajax.
> >
> > Maurice
> >
> > On Nov 7, 2007 1:50 PM, serban.balamaci <[EMAIL PROTECTED]> wrote:
> >>
> >> I cannot use the modal windows.
> >> They are plain popups. I do not know if there is a difference beetween
> >> modal
> >> windows that have a content a panel or a page, but i need to have tabbed
> >> pannels(which are links) inside the popup and by using a modal page with
> >> a
> >> panel content when i press on another tab(a link), i get the message that
> >> "This action requires to navigate away from this page and the modal
> >> window
> >> will close" and after pressing it does close the modal window.
> >>
> >> I am currently trying the 3rd option, i think i can write the javascript
> >> for
> >> the ajax request.
> >> I will post the solution if i get it working.
> >>
> >>
> >>
> >> Mr Mean wrote:
> >> >
> >> > Are you using the ModalWindow? in that case you need to set the
> >> > PageCreator to return your page, don't use panels. Second you need to
> >> > set a callbackhandler for the windowclose event. There you must update
> >> > your combo.
> >> >
> >> > Maurice
> >> >
> >> > On Nov 7, 2007 12:09 PM, serban.balamaci <[EMAIL PROTECTED]> wrote:
> >> >>
> >> >> Hello!
> >> >> I have the following problem. I have a parent page, that opens a popup
> >> >> through a PageLink.
> >> >> The popup window is a window in which new records can be added, but i
> >> >> need a
> >> >> combo in the parent page to reflect and contain also the new choice
> >> added
> >> >> in
> >> >> the popup.
> >> >>
> >> >> 1. Reloading the whole parent page at popup close link pressed i would
> >> >> take
> >> >> as the last resolve because the user may have introduced data in the
> >> >> controls that would get lost in the reloading process. I could get
> >> around
> >> >> this by adding a submit behaviour to the link and save in session the
> >> >> values
> >> >> inserted till that moment and rehidrate the model with values from the
> >> >> session instead of the database, and so obtain the state that the page
> >> >> was
> >> >> in before the popup was opened, but i'm wondering if there is not a
> >> >> cleaner
> >> >> solution for this.
> >> >>
> >> >> 2. I also tried(didn't think this would work:) but had to try) to pass
> >> >> the
> >> >> combo to the popup page and tried to update through the pressing of an
> >> >> ajaxlink the combo. It said it could not find the markup id for the
> >> >> combo(expected since it tried in the popup and not in the parent) so i
> >> >> guess
> >> >> that this approach could
Re: IOException from ModalWindow
On Tue, 06 Nov 2007, JohannesK wrote: > 13:33:56.143 WARN!! Alias request of 'file:/C:/workspace/ordermanager/:/0' > for 'file:/C:/workspace/ordermanager/:/0' > > I'm assuming this has to do with the images the ModalWindow is using. > Any ideas? - try to reproduce the problem with WicketTester - try to reproduce with Winstone instead of Jetty - set some breakpoints to see what is being requested - make sure your HTML does not contain empty src attributes Lykkyä tykö, Timo -- Timo Rantalaiho Reaktor Innovations Oyhttp://www.ri.fi/ > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Regarding the use of AjaxFallbackDefaultDataTable
Hi,
I have a Search Form along with a AjaxFallbackDefaultDataTable on a page
that I am trying to create. How it is supposed to work is as follows:
1. User accesses page (only search form is visible)
2. User enters search parameters and submits request
3. The page returns search results. The page at this point should still
show the search form, and also now the results through the
AjaxFallbackDefaultDataTable.
The problem that I am having is as follows:
In the page constructor I add both the form and the
AjaxFallbackDefaultDataTable and then set the table to not be visible.
However I am finding that the table makes the call to the data provider when
it is initially instantiated. I only want it to make the call to the data
provider when the search request is made.
The following is the code that I am using in the constructor to add the
table.
SortableDataProvider dp = new ReconcileReportProvider(new
ReconcileReportManagerImpl());
reportTable = new AjaxFallbackDefaultDataTable("searchResults", columns, dp,
rows);
reportTable.setVisible(false);
add(reportTable);
I am not too sure if this is even the right way to go about it. Any
guidance would be appreciated.
Cheers.
--
View this message in context:
http://www.nabble.com/Regarding-the-use-of-AjaxFallbackDefaultDataTable-tf4768778.html#a13640684
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket portlet newbie questions
Ok now I already add wicket portlet page to liferay.But i have new problem :-) when i click in some wicket example i have error. 02:42:45,572 ERROR [jsp:52] java.lang.NullPointerException at org.apache.wicket.protocol.http.WebResponse.write(WebResponse.java:35 5) at org.apache.wicket.protocol.http.BufferedWebResponse.close(BufferedWeb Response.java:74) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java: 330) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.ja va:169) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:188) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:691) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:594) Can you pls help me. Thk you. Thijs wrote: > > Just download the source from SVN and build it. You'll have to change the > portlet.xml anyway > > > justment wrote: >> >> Hi Thijs,Please tell me about version of portlet wicket-exemples.war >> I can't find it on wicket site .Thank you >> >> >> Thijs wrote: >>> >>> Check out http://www.nabble.com/Portlet-howto-tf4587073.html#a13093514 >>> >>> justment wrote: I want to implements wicket portlet on liferay but I can't get any demo,documents from google :p Thanks in advance for any pointers and explanations thank you. >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Wicket-portlet-newbie-questions-tf4751827.html#a13640491 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New MEAP content for Wicket in Action available
Just bought the pdf book and it has been an excellent read so far. Kudos for the good work. Can't wait for the rest of the chapters. - rm3 Martijn Dashorst wrote: > > Last friday two new chapters of the upcoming Wicket in Action have > been released through the Manning early access program. > > This release concludes the first part of the book: Getting started > with Wicket. The chapters now available are: > > 1. What is Wicket? (FREE!) > 2. The architecture of Wicket (new) > 3. Setting up a Wicket project > 4. Building a cheesy Wicket application (new) > > We hope you will enjoy these additional chapters and we are working > hard to get the other chapters available asap. > > MEAP subscribers for Wicket in Action should have recieved a message > with the download link for their personal copy. If you have not > subscribed to the MEAP, and are anxious to see what this book is > about, you can download chapter 1 at no cost, nor any form of > registration. Just visit: > > http://manning.com/dashorst > > Best regards, > > Martijn Dashorst > > -- > Wicket joins the Apache Software Foundation as Apache Wicket > Apache Wicket 1.3.0-beta2 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/New-MEAP-content-for-Wicket-in-Action-available-tf4335090.html#a13640388 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Chris Colman wrote: heh, wellyou can be against this, but i think if we take a vote right now most core-devs with binding votes will vote this down I still can't see the reason for the negativity of some of the core-devs: this is an existing feature. No offense to anyone involved, but I'm getting very bored. This thread is about ten times longer than it needs to be, the arguments in it have been rather confused, and the same thing has been said by the same people about a hundred times. Please can we improve the signal-to-noise ratio? If you have anything concrete to add, please comment on the appropriate JIRA issue where hopefully people won't have such bad verbal diarrhea. Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> heh, wellyou can be against this, but i think if we take a vote > right now most core-devs with binding votes will vote this down I still can't see the reason for the negativity of some of the core-devs: this is an existing feature. If the feature sucks so bad why did people have the inspiration to add it in the first place in the beginning of wicket's life? We're just proposing to enhance an existing feature - evolution not revolution. > > so we can make this pluggable and someone can put it on wicket-stuff > or there is a chance it wont make it in at all... It seems strange to want to make a more powerful version of an already existing feature accessible only via a plug in. Maybe some of the core-devs are starting to lose a bit of their zing or their desire for a challenge - a zing that comes so naturally in a project's infancy. > > -igor > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How To Change Page Store Size in DiskPageStore?
There is a constructor parameter in DiskPageStore constructor (the last int parameter) that says how many handles DiskPageStore will keep opened. But the default number of file handles is 50. If this is causing your server file handle problems than you should consider changing the configuration. Are you sure there are no other file handles leaking? What are the files opened? -Matej On 11/8/07, Brandon Harper <[EMAIL PROTECTED]> wrote: > Hello All, > > Long story short, we're in the process of load testing an application > built against Wicket 1.3 snapshot. Unfortunately we've seen some > server issues with sessions/page maps in the file store during > testing, and I was wondering how I'd go about programatically changing > the default page map size in DiskPageStore just to see if changing > this value affects what we're seeing. > > FWIW, right now it looks like we're having issues under load with > Wicket creating too many open file handles on a fairly default install > of RHEL 5 which results in exceptions like this: > > java.lang.RuntimeException: java.io.FileNotFoundException: > /usr/local/jboss-4.2.1.GA/server/website/work/jboss.web/localhost/_/Website-filestore/688F01368693E1A90ED61C8060A51A3E.n1/pm-null > (No such file or directory) > at > org.apache.wicket.protocol.http.pagestore.FileChannelPool.newFileChannel(FileChannelPool.java:104) > at > org.apache.wicket.protocol.http.pagestore.FileChannelPool.getFileChannel(FileChannelPool.java:171) > at > org.apache.wicket.protocol.http.pagestore.DiskPageStore$SessionEntry.savePage(DiskPageStore.java:224) > at > org.apache.wicket.protocol.http.pagestore.DiskPageStore.flushPagesToSaveList(DiskPageStore.java:788) > at > org.apache.wicket.protocol.http.pagestore.DiskPageStore$PageSavingThread.run(DiskPageStore.java:851) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.io.FileNotFoundException: > /usr/local/jboss-4.2.1.GA/server/me.dium.com/work/jboss.web/localhost/_/MediumWebsite-filestore/688F01368693E1A90ED61C8060A51A3E.n1/pm-null > (No such file or directory) > at java.io.RandomAccessFile.open(Native Method) > at java.io.RandomAccessFile.(RandomAccessFile.java:212) > at > org.apache.wicket.protocol.http.pagestore.FileChannelPool.newFileChannel(FileChannelPool.java:99) > > Thanks, > > - Brandon > > -- > http://bharper.com > http://devnulled.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form: onSubmit not called
On 07 November 2007, 7:55:50 AM, Brill Pappin wrote: BP> For some reason onSubmit is never called on a simple form. Has BP> anyone seen this problem before? Validation errors but no feedback panel to see them? -- /Gwyn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rendering a fieldset class attribute
William Hoover wrote: Is it better to use AbstractBehavior and override onComponentTag? I assume that the AttributeModifier is only for cases when the attribute already exists in the markup, correct? Well, given the javadoc I told you to read for the second parameter there, no. ;-) It doesn't make much difference which you use. AbstractBehavior is more direct and concise. AttributeModifier is named such that people will find it. I tend to use the former for what you're doing, and the latter if I already have a model kicking around. There's also a SimpleAttributeModifier if you have a simple String, and an AttributeAppender if you wish to mess with what's currently there. IMO, the API here is far too broad - we should just give people AbstractBehavior and tell them to get on with it, but hey ho. Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Rendering a fieldset class attribute
Is it better to use AbstractBehavior and override onComponentTag?
I assume that the AttributeModifier is only for cases when the attribute
already exists in the markup, correct?
-Original Message-
From: Al Maw [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2007 7:48 PM
To: users@wicket.apache.org
Subject: Re: Rendering a fieldset class attribute
William Hoover wrote:
>
> final AttributeModifier levelModifier = new
> AttributeModifier("class",
> new Model() {
> @Override
> public Object getObject() {
> return "fieldset-class";
> }
> });
[...]
> The fieldset is not rendering the css class attribute?
This is because you need to provide a second constructor parameter of
true (read the javadoc for AttributeModifier).
Regards,
Al
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Real World Ajax Examples/Tutorials/Help
CC> The only difference between my java file and the WorldClock CC> example is that it extends BasePage and I extend Panel. I'm also CC> updating a label that is in a ListView. I'm trying to build a CC> table of data that updates dynamically. That might be significant. Could it be a case for ListView.setReuseItems()? -- /Gwyn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
heh, wellyou can be against this, but i think if we take a vote right now most core-devs with binding votes will vote this down so we can make this pluggable and someone can put it on wicket-stuff or there is a chance it wont make it in at all... -igor On Nov 7, 2007 3:59 PM, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: > Hi, > > I haven't really heard any real arguments against this patch. Basically > it's just relaxing a constraint on the current implementation of > child/extend. It's not so much a new feature as improving the current > feature. I am honestly interested in why people are so against it. > > Igor Vaynberg wrote: > > what do we need to refactor to make a plugin like this possible? > > Now this is something I am much more wary of. If people start developing > all sorts of "tag libraries" as extensions to Wicket, you'll get a > proliferation of incompatible stuff. Personally I think it's better NOT > to have this! Even though I'm in favor of the proposed extension to > child/extends, I'd rather give it up than have an explosion of custom tags. > > Regards, > Sebastiaan > > > > -igor > > > > > > On Nov 7, 2007 2:50 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > >>> some here like it and others dont like it, so wouldnt be an different > >>> project like wicket-extension the part for this? > >> That's what I'm arguing. Though thinking about it a little bit longer, > >> it should probably not even be a core project, but rather a > >> wicket-stuff one. > >> > >>> couldn't this be > >>> applied similar to the wicket-jmx plugin where you just dump the jar > >>> into the classpath and have it registering and enabling itself? > >> That would be ok only if it would apply to a whole different set of > >> tags. Which is probably the best way to go about this anyway. > >> > >> Is there anything in anyone's way to implement this right now as a > >> separate bunch of tags? > >> > >> > >> Eelco > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form: onSubmit not called
Brill Pappin wrote: For some reason onSubmit is never called on a simple form. Has anyone seen this problem before? Throw us a bone here... Some code please? Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rendering a fieldset class attribute
William Hoover wrote:
final AttributeModifier levelModifier = new
AttributeModifier("class",
new Model() {
@Override
public Object getObject() {
return "fieldset-class";
}
});
[...]
The fieldset is not rendering the css class attribute?
This is because you need to provide a second constructor parameter of
true (read the javadoc for AttributeModifier).
Regards,
Al
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Real World Ajax Examples/Tutorials/Help
Gwyn Evans wrote: > Hi Curtis, > > On 07 November 2007, 11:20:00 PM, Curtis Cooley wrote: > CC> Where can I get more info on using ajax with wicket? The examples I've > CC> found so far do not include round trips. Sure, writing a clock label is > CC> cool and all, but I have real time data on a page that I don't want to > CC> have to reload the whole page for all the time. > > http://wicket.apache.org/exampleajaxcounter.html > > http://wicketstuff.org/wicket13/ajax/ > > http://cwiki.apache.org/WICKET/dropdownchoice-examples.html#DropDownChoiceExamples-UsingAjax > > http://day-to-day-stuff.blogspot.com/2007/01/backward-compatible-ajax-development.html > > Thanks for the links. I'll absorb those. > CC> Also, I'm using a TabbedPanel with nested panels and even the simple > CC> ajax examples won't run. > > CC> Also, it seems that when I attempt to enable ajax, whenever I click on > CC> another tab, I get the "page expired" link. What's up with that? I'm > CC> assuming wicket has detected that the page has changed, but the labels > CC> on the page have not updated. Can this be disabled? > > Did you call .setOutputMarkupId(true) on any components you want to > update via Ajax (or setOutputMarkupPlaceholderTag(true) if they're > starting out invisible) & add them to the 'target' in the Ajax > callback? > I wasn't, but I found the WorldClock example that looks a lot more like the click counter example. I've modeled my page as closely as possible, but I still do not see the label updating dynamically. It updates fine on refresh. I seem to have fixed the expired page problem, though. The only difference between my java file and the WorldClock example is that it extends BasePage and I extend Panel. I'm also updating a label that is in a ListView. I'm trying to build a table of data that updates dynamically. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
> Now this is something I am much more wary of. If people start developing > all sorts of "tag libraries" as extensions to Wicket, you'll get a > proliferation of incompatible stuff. Personally I think it's better NOT > to have this! Even though I'm in favor of the proposed extension to > child/extends, I'd rather give it up than have an explosion of custom tags. It is already possible to do develop custom tags. It is not considered to be a best practice or anything, but personally, I like the fact that people can customize Wicket if they want. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Rendering a fieldset class attribute
never mind... my mistake i needed to use AbstractBehavior (below). Sorry for
the post :)
fieldset.add(new AbstractBehavior() {
@Override
public void onComponentTag(Component component,
ComponentTag tag) {
tag.put("class", "fieldset-class");
}
});
-Original Message-
From: William Hoover [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2007 6:26 PM
To: users@wicket.apache.org
Subject: Rendering a fieldset class attribute
Is it appropriate to have the following...
final WebMarkupContainerWithAssociatedMarkup fieldset = new
WebMarkupContainerWithAssociatedMarkup(
"fieldset");
final AttributeModifier levelModifier = new
AttributeModifier("class",
new Model() {
@Override
public Object getObject() {
return "fieldset-class";
}
});
fieldset.add(levelModifier);
add(fieldset);
with...
...
The fieldset is not rendering the css class attribute?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Real World Ajax Examples/Tutorials/Help
Hi Curtis, On 07 November 2007, 11:20:00 PM, Curtis Cooley wrote: CC> Where can I get more info on using ajax with wicket? The examples I've CC> found so far do not include round trips. Sure, writing a clock label is CC> cool and all, but I have real time data on a page that I don't want to CC> have to reload the whole page for all the time. http://wicket.apache.org/exampleajaxcounter.html http://wicketstuff.org/wicket13/ajax/ http://cwiki.apache.org/WICKET/dropdownchoice-examples.html#DropDownChoiceExamples-UsingAjax http://day-to-day-stuff.blogspot.com/2007/01/backward-compatible-ajax-development.html CC> Also, I'm using a TabbedPanel with nested panels and even the simple CC> ajax examples won't run. CC> Also, it seems that when I attempt to enable ajax, whenever I click on CC> another tab, I get the "page expired" link. What's up with that? I'm CC> assuming wicket has detected that the page has changed, but the labels CC> on the page have not updated. Can this be disabled? Did you call .setOutputMarkupId(true) on any components you want to update via Ajax (or setOutputMarkupPlaceholderTag(true) if they're starting out invisible) & add them to the 'target' in the Ajax callback? -- /Gwyn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Hi, I haven't really heard any real arguments against this patch. Basically it's just relaxing a constraint on the current implementation of child/extend. It's not so much a new feature as improving the current feature. I am honestly interested in why people are so against it. Igor Vaynberg wrote: what do we need to refactor to make a plugin like this possible? Now this is something I am much more wary of. If people start developing all sorts of "tag libraries" as extensions to Wicket, you'll get a proliferation of incompatible stuff. Personally I think it's better NOT to have this! Even though I'm in favor of the proposed extension to child/extends, I'd rather give it up than have an explosion of custom tags. Regards, Sebastiaan -igor On Nov 7, 2007 2:50 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: some here like it and others dont like it, so wouldnt be an different project like wicket-extension the part for this? That's what I'm arguing. Though thinking about it a little bit longer, it should probably not even be a core project, but rather a wicket-stuff one. couldn't this be applied similar to the wicket-jmx plugin where you just dump the jar into the classpath and have it registering and enabling itself? That would be ok only if it would apply to a whole different set of tags. Which is probably the best way to go about this anyway. Is there anything in anyone's way to implement this right now as a separate bunch of tags? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: Why dioes this error occur?
Hi,
Looking at the code, it's looking like there's some race condition
going on, with the request coming in for a component that no longer
exists. Comparing with the 1.3 code (in
AbstractRequestCycleProcessor#resolveListenerInterfaceTarget()),
there's an explicit check for a null, but there's nothing that can
really be done to recover, i.e. even the 1.3 code is as follows...
if (component == null)
{
throw new WicketRuntimeException("component " + pageRelativeComponentPath +
" not found on page " + page.getClass().getName() + "[id = " +
page.getNumericId() + "], listener interface = " + listener);
}
Maybe you could disable the button via client-side javascript once
clicked?
/Gwyn
On 07 November 2007, 9:45:24 PM, salmas wrote:
s> I tried disabling the button during the event and while this was easy enough
s> to implement it did not help. My page contains a table which has panels in
s> different cells. I swap these panels in and out depending on wether the user
s> is in 'edit' mode or 'submit' mode and also according to where they are in
s> the workflow.
s> I noticed that the method of PropertyColumn which I am overriding
s> populateItem(Item item, String componentId, IModel model) completes, as does
s> the event handling code at the button press so I am not sure what is
s> breaking down. It's easy to reproduce this error. All I have to do is to
s> click a button which is present in one of the panels rapidly, at every click
s> I do toggle the name of the button from "edit" to "save" so I don't know if
s> this has something to do with it.
s> I do need this problem resolved because this is not acceptable for a
s> production application. I would really appreciate any ideas that you have.
s> salmas wrote:
>>
>>
>> I am using wicket-1.2.6. Unfortunately it is not possible for me to
>> upgrade to a newer version.
>>
>>> Hi salmas,
>>>
>>> On 07 November 2007, 7:05:26 PM, salmas wrote:
>>> s> Every once in awhile if I am clicking around for awhile in the UI of
>>> my
>>> s> application I get the following error. What causes this?
>>>
>>> s> java.lang.NullPointerException
>>> s> at
>>> s>
>>> wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:295)
>>>
>>> What version of Wicket are you using?
>>>
>>> --
>>> /Gwyn
>>>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: UrlCodingStrategy with unmatched key/value pairs
As you're already overriding decodeParamaters(), what about a cut & paste of the code from there & appendParameters(), changing it to use some other character (that you won't have in your params), e.g. '|' or '^', leaving the '/' to become a non-special char? /Gwyn On 07 November 2007, 10:09:57 PM, green804 wrote: g> We are using 1.2.6 right now. The Food%2FDrink is one param. That param g> does have a /. Unfortunately, I can't change the param. I'm overriding the g> decodeParameters to handle the case with mismatched key/value pairs, but g> it's kind of a hack because I have to know which params might have a /. g> It's not a very generic solution. I'm hoping to track down where the decode g> is happening in the first place and override that instead. g> Johan Compagner wrote: >> >> what are you doing then in your own >> BookmarkablePageRequestTargetUrlCodingStrategy? >> >> who generates that url? and what is that Food%2FDrink? Should that be 1 >> param? And has the param a /? >> >> which version do you use? >> >> >> On 11/7/07, green804 <[EMAIL PROTECTED]> wrote: >>> >>> >>> I am having a problem with the UrlCodingStrategy. I'm currently >>> extending >>> BookmarkablePageRequestTargetUrlCodingStrategy. The problem is that the >>> app >>> is decoding some of the characters in the url before I get the url in the >>> decodeParameters method. >>> >>> For example, the url once encoded looks like this: >>> >>> /linkframe/item/187822/site/Wine/sitetopic/Food%2FDrink >>> >>> where the params are item=187822, site=Wine, and sitetopic=Food%2FDrink >>> >>> When the decode method in BookmarkablePageRequestTargetUrlCodingStrategy >>> calls requestParameters.getPath() the url looks like this: >>> >>> /linkframe/item/187822/site/Wine/sitetopic/Food/Drink >>> >>> This is causing a problem because the app thinks the URL fragment has >>> unmatched key/value pairs. I cannot seem to find where/why the %2F is >>> getting resolved to a /. Can someone help me with this? I need to keep >>> this from happening. It's causing null pointers all over the place. >>> -- >>> View this message in context: >>> http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13636974 >>> Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Rendering a fieldset class attribute
Is it appropriate to have the following...
final WebMarkupContainerWithAssociatedMarkup fieldset = new
WebMarkupContainerWithAssociatedMarkup(
"fieldset");
final AttributeModifier levelModifier = new
AttributeModifier("class",
new Model() {
@Override
public Object getObject() {
return "fieldset-class";
}
});
fieldset.add(levelModifier);
add(fieldset);
with...
...
The fieldset is not rendering the css class attribute?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Real World Ajax Examples/Tutorials/Help
Curtis Cooley wrote: Where can I get more info on using ajax with wicket? The examples I've found so far do not include round trips. Sure, writing a clock label is cool and all, but I have real time data on a page that I don't want to have to reload the whole page for all the time. Sorry, but I think you've missed the point somewhat... The clock example gets the time on every tick from the server, doing a round trip each time. Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How To Change Page Store Size in DiskPageStore?
Hello All, Long story short, we're in the process of load testing an application built against Wicket 1.3 snapshot. Unfortunately we've seen some server issues with sessions/page maps in the file store during testing, and I was wondering how I'd go about programatically changing the default page map size in DiskPageStore just to see if changing this value affects what we're seeing. FWIW, right now it looks like we're having issues under load with Wicket creating too many open file handles on a fairly default install of RHEL 5 which results in exceptions like this: java.lang.RuntimeException: java.io.FileNotFoundException: /usr/local/jboss-4.2.1.GA/server/website/work/jboss.web/localhost/_/Website-filestore/688F01368693E1A90ED61C8060A51A3E.n1/pm-null (No such file or directory) at org.apache.wicket.protocol.http.pagestore.FileChannelPool.newFileChannel(FileChannelPool.java:104) at org.apache.wicket.protocol.http.pagestore.FileChannelPool.getFileChannel(FileChannelPool.java:171) at org.apache.wicket.protocol.http.pagestore.DiskPageStore$SessionEntry.savePage(DiskPageStore.java:224) at org.apache.wicket.protocol.http.pagestore.DiskPageStore.flushPagesToSaveList(DiskPageStore.java:788) at org.apache.wicket.protocol.http.pagestore.DiskPageStore$PageSavingThread.run(DiskPageStore.java:851) at java.lang.Thread.run(Thread.java:619) Caused by: java.io.FileNotFoundException: /usr/local/jboss-4.2.1.GA/server/me.dium.com/work/jboss.web/localhost/_/MediumWebsite-filestore/688F01368693E1A90ED61C8060A51A3E.n1/pm-null (No such file or directory) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.(RandomAccessFile.java:212) at org.apache.wicket.protocol.http.pagestore.FileChannelPool.newFileChannel(FileChannelPool.java:99) Thanks, - Brandon -- http://bharper.com http://devnulled.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Real World Ajax Examples/Tutorials/Help
Where can I get more info on using ajax with wicket? The examples I've found so far do not include round trips. Sure, writing a clock label is cool and all, but I have real time data on a page that I don't want to have to reload the whole page for all the time. Also, I'm using a TabbedPanel with nested panels and even the simple ajax examples won't run. Also, it seems that when I attempt to enable ajax, whenever I click on another tab, I get the "page expired" link. What's up with that? I'm assuming wicket has detected that the page has changed, but the labels on the page have not updated. Can this be disabled? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disabling serialization/storage of pages in session?
> If need be, can we disable altogether the storage of pages (in the form of a > pageMap) in session, similarly on the disk ? Yep. One easy way to achieve this is to provide a dummy page store. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Disabling serialization/storage of pages in session?
Guys, If need be, can we disable altogether the storage of pages (in the form of a pageMap) in session, similarly on the disk ? Thanks and Regards, Farhan. -- View this message in context: http://www.nabble.com/Disabling-serialization-storage-of-pages-in-session--tf4768006.html#a13638150 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Attempted summary of multiple thread
> ... > > 5) Conclusion > > In conclusion, the proposed change: > - is useful > - does not have to be used if you don't like it > - is 100% backwards compatible > - it introduces no new tags (if using child/extends) > > I also do not see any real issues. This is purely about merging markup > when rendering, I think the analogies between this and OO concepts in > Java are clouding the issue! > > Regards, > Sebastiaan Great summary Sebastiaan! I just thought of a possible, even more powerful, improvement (whoops!) What if the base page sections (child or abstract tag) were "optionally" overridden in a derived page. Ie., the section in the derived page markup is used if supplied otherwise Wicket defaults to using that provided in the base page. That's immensely powerful because you could provide some default markup in the base page and that will be used if the derived page does not provide an implementation of that section. A derived page now only needs to provide override sections for sections that it actually needs to override. It makes 'abstract' not a good choice for a tag name because abstract implies there is no implementation in the base page. In this case we could drop the OO language terms and use easy to understand terms for the tags like " in a base page section and in a derived page section. Even my graphic designers could understand a tag pair called default/override! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
what do we need to refactor to make a plugin like this possible? -igor On Nov 7, 2007 2:50 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > some here like it and others dont like it, so wouldnt be an different > > project like wicket-extension the part for this? > > That's what I'm arguing. Though thinking about it a little bit longer, > it should probably not even be a core project, but rather a > wicket-stuff one. > > > couldn't this be > > applied similar to the wicket-jmx plugin where you just dump the jar > > into the classpath and have it registering and enabling itself? > > That would be ok only if it would apply to a whole different set of > tags. Which is probably the best way to go about this anyway. > > Is there anything in anyone's way to implement this right now as a > separate bunch of tags? > > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
> some here like it and others dont like it, so wouldnt be an different > project like wicket-extension the part for this? That's what I'm arguing. Though thinking about it a little bit longer, it should probably not even be a core project, but rather a wicket-stuff one. > couldn't this be > applied similar to the wicket-jmx plugin where you just dump the jar > into the classpath and have it registering and enabling itself? That would be ok only if it would apply to a whole different set of tags. Which is probably the best way to go about this anyway. Is there anything in anyone's way to implement this right now as a separate bunch of tags? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
just a question to you Igor and Eelco: some here like it and others dont like it, so wouldnt be an different project like wicket-extension the part for this? couldn't this be applied similar to the wicket-jmx plugin where you just dump the jar into the classpath and have it registering and enabling itself? I mean I personally would prefer to have a slim wicket-core but dont see a reason to forbid this as a dependencyjar (e.g: Special BasePage ala MultiWebPage) as this would mean a missing package and be shown in every IDE? Best Korbinian Igor Vaynberg schrieb: On Nov 7, 2007 1:39 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: You wouldn't write such a component for general purposes obviously. ok, that right there i really really dont like. define "general purpose"? so now we have features in wicket that are guaranteed to work and others that arent? this is going to turn the framework into an abysmal pile of crap. why should i only use some "safe" subset when writing a component im planning on reusing across projects? -igor Of course it can be optional (it might have to be a whole separate tag rather than building on wicket:extend); it's up to the users after that. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
> What's the point of making you jump through hoops to enable this? > - It'll require thought to not break reusable components, as Igor says. That's the responsibility of individual projects. People can create custom tags and stuff as well. > - It's extra config- and API-width we don't need; we'll have to > deprecate the method to turn it on once it becomes "standard", > mention it in migration docs for 1.5(?), support it on the mailing > list, etc. etc. > > - If we add it, it looks like lots of people will use it. We're then > stuck with it - it's a change that would never get backed out unless > someone comes up with a vastly better way of doing all this such that > it's completely obsolete. What I would be ready to do is ensure that people who want this can implement it. We could ship it with Wicket (but disabled), or just leave it outside altogether, leaving it up to users to create e.g. a wicket-stuff project for it. I agree we shouldn't make it our responsibility, not even a little bit, and certainly shouldn't hint that this would be the way to go when a couple of core developers don't agree with it in the first place. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
On Nov 7, 2007 2:02 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > On Nov 7, 2007 1:39 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > You wouldn't write such a component for general purposes obviously. > > ok, that right there i really really dont like. define "general > purpose"? so now we have features in wicket that are guaranteed to > work and others that arent? this is going to turn the framework into > an abysmal pile of crap. why should i only use some "safe" subset when > writing a component im planning on reusing across projects? Nah, you're over-reacting. It would just mean that people would use it for their internal projects, which would be fine with me really. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Hi Chris, i rewinded some part of your idea and the thread and now see bit clearer what you want - perhaps you shouldnt call i multiple extend/child but more precisely "inheritance with multiple areas" as you go: html-basepage: ... while each those areas are then subsidarily taken over by 1 single extended specialised class - so you somehow do nearly the same what I did but put the abstract part into the HTML part... is this right? If im right with this then its IMHO a bit shorter as my way, but on the tradeoff that you may get bitten by an HTML-java binding error at runtime as well as I still dont know how you want to solve the trouble with the name-space (the thing Igor mentioned) However, i know how hard the first steps in these directions are as i went through them by my own... now, after im not more so focused on a traditional way of doing webapps i often see things a different way - e.g.: I even like Model's now, which also caused me much headache at the first time Best, Korbinian Chris Colman schrieb: Chris Colman schrieb: The beauty of the multiple extend/child idea is that it's not a completely new concept we're talking about here - it's merely an issue of supporting n>1 instead of arbitrarily fixing n=1 like it is now. 1 Question: Who dominates Who and Why? If you extend 1 class by class you create specialisations that dominate each other, but here you just mess together some classes - so why should which class dominate? If we manipulate a headertag? If we have same namespace? If we have different securitylevels? Wich class is responsible for all this? Why? Dunno what you mean by "dominate" or "mess together some classes". No one is talking about mess - the whole point of this feature is avoidance of mess - in the same way OO brings about reduced complexity in code the same thing can happen with markup. We're not proposing multiple inheritance - which indeed causes mess. We're talking single inheritance which means single lineage. Each page only has a single base page. It's easy for Wicket to perform the resolutions and merge markup from base and derived pages. I know this because it already does it and it works fine. We're just proposing to remove the restriction that it can only do it for just one section of your base page - that's all, nothing revolutionary - just evolutionary. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: UrlCodingStrategy with unmatched key/value pairs
cant you just replace the / with a special char at the moment? I even don't know how the current head/trunk handles this.. would be nice to look at. johan On 11/7/07, green804 <[EMAIL PROTECTED]> wrote: > > > We are using 1.2.6 right now. The Food%2FDrink is one param. That param > does have a /. Unfortunately, I can't change the param. I'm overriding > the > decodeParameters to handle the case with mismatched key/value pairs, but > it's kind of a hack because I have to know which params might have a /. > It's not a very generic solution. I'm hoping to track down where the > decode > is happening in the first place and override that instead. > > > > Johan Compagner wrote: > > > > what are you doing then in your own > > BookmarkablePageRequestTargetUrlCodingStrategy? > > > > who generates that url? and what is that Food%2FDrink? Should that be 1 > > param? And has the param a /? > > > > which version do you use? > > > > > > On 11/7/07, green804 <[EMAIL PROTECTED]> wrote: > >> > >> > >> I am having a problem with the UrlCodingStrategy. I'm currently > >> extending > >> BookmarkablePageRequestTargetUrlCodingStrategy. The problem is that the > >> app > >> is decoding some of the characters in the url before I get the url in > the > >> decodeParameters method. > >> > >> For example, the url once encoded looks like this: > >> > >> /linkframe/item/187822/site/Wine/sitetopic/Food%2FDrink > >> > >> where the params are item=187822, site=Wine, and sitetopic=Food%2FDrink > >> > >> When the decode method in > BookmarkablePageRequestTargetUrlCodingStrategy > >> calls requestParameters.getPath() the url looks like this: > >> > >> /linkframe/item/187822/site/Wine/sitetopic/Food/Drink > >> > >> This is causing a problem because the app thinks the URL fragment has > >> unmatched key/value pairs. I cannot seem to find where/why the %2F is > >> getting resolved to a /. Can someone help me with this? I need to > keep > >> this from happening. It's causing null pointers all over the place. > >> -- > >> View this message in context: > >> > http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13636974 > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13637200 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: UrlCodingStrategy with unmatched key/value pairs
We are using 1.2.6 right now. The Food%2FDrink is one param. That param does have a /. Unfortunately, I can't change the param. I'm overriding the decodeParameters to handle the case with mismatched key/value pairs, but it's kind of a hack because I have to know which params might have a /. It's not a very generic solution. I'm hoping to track down where the decode is happening in the first place and override that instead. Johan Compagner wrote: > > what are you doing then in your own > BookmarkablePageRequestTargetUrlCodingStrategy? > > who generates that url? and what is that Food%2FDrink? Should that be 1 > param? And has the param a /? > > which version do you use? > > > On 11/7/07, green804 <[EMAIL PROTECTED]> wrote: >> >> >> I am having a problem with the UrlCodingStrategy. I'm currently >> extending >> BookmarkablePageRequestTargetUrlCodingStrategy. The problem is that the >> app >> is decoding some of the characters in the url before I get the url in the >> decodeParameters method. >> >> For example, the url once encoded looks like this: >> >> /linkframe/item/187822/site/Wine/sitetopic/Food%2FDrink >> >> where the params are item=187822, site=Wine, and sitetopic=Food%2FDrink >> >> When the decode method in BookmarkablePageRequestTargetUrlCodingStrategy >> calls requestParameters.getPath() the url looks like this: >> >> /linkframe/item/187822/site/Wine/sitetopic/Food/Drink >> >> This is causing a problem because the app thinks the URL fragment has >> unmatched key/value pairs. I cannot seem to find where/why the %2F is >> getting resolved to a /. Can someone help me with this? I need to keep >> this from happening. It's causing null pointers all over the place. >> -- >> View this message in context: >> http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13636974 >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13637200 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Attempted summary of multiple thread
Hi, Since the thread on multiple support is insanely long I'm going to try make a clear and concise summary of what has been proposed and what the arguments for and against were. Bear with me. :-) 1. What is proposed? Currently Wicket supports *merging* of markup on a base page with markup on an a page which extends it through the and tags. When the child page is rendered, the markup of the base page is used, but the ... part is *replaced* by what is between the ... part in the child page (thus *merging* the two). Currently only 1 child part is allowed in the base page and only 1 extend part in allowed in the child page. The request is to allow multiple such parts to be replaced during the murge. To know which part must be replaced with which, it is proposed that the above tags have an id attribute to match them pair by pair. As Chris Colman aptly put it: the *only* thing being requested is to remove the limitation of n=1 pairs and to allow n>1 pairs of parts to replaced during the merge. NOTE: This has been called markup inheritance (as suggested by the names child and extend), but in the thread has also been compared to abstract methods and implementing them. I recommend not using any analogies to confuse matters and just seeing it for what it is, a relaxation of the constraint that n=1 during merge. NOTE 2: A patch by Stefan Fussenegger which implements this feature request has been submitted to the Wicket JIRA. In his patch he used different tags names, but the behavior for the case n=1 is exactly that of the current feature. 2. Is even necessary? No, it's a convenience feature. You can get the same effect by making a BasePage.html, BasePage.java, ChildPage.java, ChildPanel.java and ChildPanel.html, and using an abstract method or onBeforeRender (see the thread). If you don't like child/extend, you don't have to use it. 3. Arguments *for* the change. It is (very) convenient (same reason as for the current child/extend) and does not change how current Wicket applications work (i.e., it is 100% backward compatible). Only when you *add* an extra identifier attribute and put in multiple child/extends pairs, are you using the new feature. If you don't like it, you don't have to use it. 4. Arguments *against* the change. I saw only a few arguments against the change: a) It can already be done using - wicket panels/fragments + abstract methods - wicket panels/fragments + onBeginRender Apart from the obvious problems with the above methods (calling an overridable method from the constructor or extra IMHO non-intuitive boilerplate code), I do not see how this is an argument against just *removing an arbitrary restriction* on . b) No more extra tags! We already have enough tags in Wicket! In principle, no extra tags required; there is *no* collision with the current and tags. But if it is done with other tags (I would suggest deprecating child/extend in the next version of wicket then), you don't have to use these extra tags. c) It creates a mess: all the components contained in any of the extend parts are added to the child page in the constructor: this can cause name collisions and a huge number of components to be added, which is bad. But I do not see the difference between this and any other normal page where you use components. A bunch of them are added to the page itself, and another bunch are separated into components. It is up to the developer to choose how to do this. A (real world) demonstration of the two different *use cases*, namely the reason why you would use a panel for one and a wicket/child for another, can be seen on the following page I recently built: http://www.denherdervarga.com/programma On the left there is a menu, in the center the content, on the right some context information for the page. The center (the content) is a clear use case of the current child/extend. The left is a panel, implemented with an abstract method getMenu(String id) on the base class. The MainMenu panel is reused across pages, and can change (in the admin section of the site the getMenu() method is overriden to return a completely different AdminMenu). The right is currently a with an abstract method on the base page. *But this a case where I would have preferred another child/extend.* The fact that the content is on the right is *PURE LAYOUT*. If I had chosen another layout where it was at the bottom of the content, it would have been *in* the content part. I would have had to add all the top level components to the page in the constructor, and I would have had to make sure that no wicket:id collisions occurred, *IN EXACTLY THE SAME WAY* as with multiple child/extends. Futhermore, there is no point in making a panel out of it, because it is specific to this page, and I'll *never* reuse it. Finally, in this (specific) case there is not even a wicket component in it, so if there would have been mu
Re: WicketNotSerializableException withi FileUpload
what is the full stack of the exception?
because who does have that field?
Streams should always be transient because those can't be serialized
whats the wicket version?
johan
On 11/6/07, James Perry <[EMAIL PROTECTED]> wrote:
>
> Hello fellow Wicket users,
>
> I am getting a
> org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
> Unable to serialize class:
> org.apache.wicket.util.io.DeferredFileOutputStream exception when I
> added a file upload feature to my AddProductForm.
>
> My form is serialiazable yet I don't which of its child components are
> not serializable. Can anyone shed any light on this?
>
> Cheers,
> James.
>
> Here is my Page class:
>
> public class AddProductPage extends AdminPage {
>
>private static final long serialVersionUID = 1L;
>
>@SpringBean(name="adminService")
>private AdminService adminService;
>
>public AddProductPage(Product product) {
>MenuBorder border = new MenuBorder("libBorder");
>border.add(new FeedbackPanel("feedback"));
>border.add(new AddProductForm("productForm", product));
>add(border);
>}
>
>private final class AddProductForm extends Form {
>
>private static final long serialVersionUID = 1L;
>
>private FileUploadField fileUploadField;
>
>public AddProductForm(String id, Product product) {
>super(id, new CompoundPropertyModel(product));
>setMultiPart(true);
>add(new RequiredTextField("name"));
>add(new RequiredTextArea("description"));
>add(new RequiredTextField("sellValue",
> BigDecimal.class));
>add(new RequiredTextField("units", Long.class));
>add(new CheckBox("onSell"));
>add(new DropDownChoice("category",
> catalogService.getCategories()));
>add(new DropDownChoice("manufacturer",
> catalogService.getManufacturers()));
>add(fileUploadField = new
> FileUploadField("fileInput", new
> Model(fileUploadField)));
>setMaxSize(Bytes.megabytes(100));
>}
>
>@Override
>protected void onSubmit() {
>final FileUpload upload =
> fileUploadField.getFileUpload();
>if (upload != null)
>System.out.println("File is not empty! Whoo
> hooo!");
>else
>System.out.println("File is empty! Whoo
> hooo!");
>fileUploadField.detachModels();
>/**Product product = (Product) getModelObject();
>product.setEntryDate(new Timestamp(
> System.currentTimeMillis()));
>product.setImageURL("uploads/");
>System.out.println(product.getCategory());
>adminService.saveProduct(product);
>setResponsePage(ViewProductsPage.class);**/
>}
>
>}
>
> }
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: Multiple tags on a single base page?
On Nov 7, 2007 1:39 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > You wouldn't write such a component for general purposes obviously. ok, that right there i really really dont like. define "general purpose"? so now we have features in wicket that are guaranteed to work and others that arent? this is going to turn the framework into an abysmal pile of crap. why should i only use some "safe" subset when writing a component im planning on reusing across projects? -igor Of > course it can be optional (it might have to be a whole separate tag > rather than building on wicket:extend); it's up to the users after > that. > > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: UrlCodingStrategy with unmatched key/value pairs
what are you doing then in your own BookmarkablePageRequestTargetUrlCodingStrategy? who generates that url? and what is that Food%2FDrink? Should that be 1 param? And has the param a /? which version do you use? On 11/7/07, green804 <[EMAIL PROTECTED]> wrote: > > > I am having a problem with the UrlCodingStrategy. I'm currently extending > BookmarkablePageRequestTargetUrlCodingStrategy. The problem is that the > app > is decoding some of the characters in the url before I get the url in the > decodeParameters method. > > For example, the url once encoded looks like this: > > /linkframe/item/187822/site/Wine/sitetopic/Food%2FDrink > > where the params are item=187822, site=Wine, and sitetopic=Food%2FDrink > > When the decode method in BookmarkablePageRequestTargetUrlCodingStrategy > calls requestParameters.getPath() the url looks like this: > > /linkframe/item/187822/site/Wine/sitetopic/Food/Drink > > This is causing a problem because the app thinks the URL fragment has > unmatched key/value pairs. I cannot seem to find where/why the %2F is > getting resolved to a /. Can someone help me with this? I need to keep > this from happening. It's causing null pointers all over the place. > -- > View this message in context: > http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13636974 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Multiple tags on a single base page?
Eelco Hillenius wrote: On Nov 7, 2007 1:32 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: this cannot be an option. it always has to be enabled. if i write a component that uses this and someone drops it into application where this is disabled what should happen? You wouldn't write such a component for general purposes obviously. Of course it can be optional (it might have to be a whole separate tag rather than building on wicket:extend); it's up to the users after that. Sorry, but I'm with Igor on this one. What's the point of making you jump through hoops to enable this? - It'll require thought to not break reusable components, as Igor says. - It's extra config- and API-width we don't need; we'll have to deprecate the method to turn it on once it becomes "standard", mention it in migration docs for 1.5(?), support it on the mailing list, etc. etc. - If we add it, it looks like lots of people will use it. We're then stuck with it - it's a change that would never get backed out unless someone comes up with a vastly better way of doing all this such that it's completely obsolete. Don't give users more knobs to twiddle than you absolutely must. ;-) FWIW, I've thought of a nice use-case for this: BasePage.html: ConcretePage.html: Here is my help text, complete with a table and other things that would be a pain to put in a properties file and use i18n for. Here is the main body of the page. I guess it'd be nice to be able to do this purely in markup without having to make a help Fragment, or add an EmptyPanel if there is no help. This issue/question is raised frequently enough on the mailing list that I think we should just implement it. I dunno about putting it in for 1.3, though. Probably a 1.4 feature? ;-) Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
UrlCodingStrategy with unmatched key/value pairs
I am having a problem with the UrlCodingStrategy. I'm currently extending BookmarkablePageRequestTargetUrlCodingStrategy. The problem is that the app is decoding some of the characters in the url before I get the url in the decodeParameters method. For example, the url once encoded looks like this: /linkframe/item/187822/site/Wine/sitetopic/Food%2FDrink where the params are item=187822, site=Wine, and sitetopic=Food%2FDrink When the decode method in BookmarkablePageRequestTargetUrlCodingStrategy calls requestParameters.getPath() the url looks like this: /linkframe/item/187822/site/Wine/sitetopic/Food/Drink This is causing a problem because the app thinks the URL fragment has unmatched key/value pairs. I cannot seem to find where/why the %2F is getting resolved to a /. Can someone help me with this? I need to keep this from happening. It's causing null pointers all over the place. -- View this message in context: http://www.nabble.com/UrlCodingStrategy-with-unmatched-key-value-pairs-tf4767649.html#a13636974 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ResourceReference with locale and style, for CSSs
Hi all,
I'm having trouble with localized and styled CSSs.
Everything works alright with HTML. For example, wicket finds
MyPage_mystyle.html instead of MyPage.html if i've called
session.setStyle("mystyle"). But for CSS i can't get it working.
i've tried different approaches like:
// inside the page constructor
add(HeaderContributor.forCss(new ResourceReference(MyPage.class,
"style.css")));
// inside renderHead
cResponse.getHeaderResponse().renderCSSReference(new
ResourceReference(MyPage.class, "style.css"));
None of this worked for me. However, it works if I call the full
constructor of ResourceReference:
new ResourceReference(MyPage.class, "style.css", getLocale(), getStyle())
But i'm not supposed to do that, because then the Locale and Style are
forced, and i want this only if the file is present. I know some
ResourceStreamLocator should be involved in the process, but i don't know
how. I see in the ResourceReference javadoc that the framework should be
calling the setStyle() method, but i debugged it and it doesn't happen.
What am i doing wrong?
Thanks in advance,
German
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why dioes this error occur?
I tried disabling the button during the event and while this was easy enough to implement it did not help. My page contains a table which has panels in different cells. I swap these panels in and out depending on wether the user is in 'edit' mode or 'submit' mode and also according to where they are in the workflow. I noticed that the method of PropertyColumn which I am overriding populateItem(Item item, String componentId, IModel model) completes, as does the event handling code at the button press so I am not sure what is breaking down. It's easy to reproduce this error. All I have to do is to click a button which is present in one of the panels rapidly, at every click I do toggle the name of the button from "edit" to "save" so I don't know if this has something to do with it. I do need this problem resolved because this is not acceptable for a production application. I would really appreciate any ideas that you have. salmas wrote: > > > I am using wicket-1.2.6. Unfortunately it is not possible for me to > upgrade to a newer version. > >> Hi salmas, >> >> On 07 November 2007, 7:05:26 PM, salmas wrote: >> s> Every once in awhile if I am clicking around for awhile in the UI of >> my >> s> application I get the following error. What causes this? >> >> s> java.lang.NullPointerException >> s> at >> s> >> wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:295) >> >> What version of Wicket are you using? >> >> -- >> /Gwyn >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Why-dioes-this-error-occur--tf4766684.html#a13636661 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
On Nov 7, 2007 1:32 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > this cannot be an option. it always has to be enabled. if i write a > component that uses this and someone drops it into application where > this is disabled what should happen? You wouldn't write such a component for general purposes obviously. Of course it can be optional (it might have to be a whole separate tag rather than building on wicket:extend); it's up to the users after that. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
or you can just use a factory that lets you create transparent borders :) -igor On Nov 7, 2007 12:05 PM, Chris Colman <[EMAIL PROTECTED]> wrote: > Presumably the coded work arounds that don't rely on child/extends mean > that the structural markup of each page is used instead of just that of > the base page - and that would spell maintenance issues. Without using > child/extend then ALL the structural markup in each page is used for > each render - NOTHING is pulled from the base page markup (kind of makes > me wonder why we need base page markup if not using child/extend - but > that's another topic!). > > A change of layout structure would mean changing all page markups - yuck > - or do you guys not care about your graphics designers - "arh, that's > their problem if they want to do a site wide change!" > > I think the fundamental thing that most people are missing is that each > component must be well formed XHTML, complete and self contained. If it > starts a (or ) then it must also end it. Divs (and tables) > are the basic structural elements of markup. > > One component can't be the start of a structural span of markup, the > next few components content sections for that span and then the last > component ends the structural span - that is not possible because each > component must be well formed and complete. > > So this infers that structural markup typically is stored in page markup > and "wraps" markup that inserts various self contained components. > > Now here's the thing: without using child/extends then that structural > markup must be carefully defined in EVERY page markup because wicket > does not do the funky inheritance merging when you don't use the > child/extends tag. > > So if you want to change a border in between two components you must > change it in EVERY page markup. That would suck. > > Alternatively, if you do use the current child/extend you end up having > to bang multiple components into the overridden section which means that > you also bang in the border that exists between them - so now the border > markup is duplicated many times. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
this cannot be an option. it always has to be enabled. if i write a component that uses this and someone drops it into application where this is disabled what should happen? -igor On Nov 7, 2007 1:05 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On Nov 7, 2007 11:19 AM, Scott Swank <[EMAIL PROTECTED]> wrote: > > I can see how and tags could be > > a nice enhancement to the current and > > tags. Do you have a working, or mostly working, patch? > > What I think we should do with this is make it an option. It would be > turned off by default, requiring users to an extra one or two lines of > configuration to turn this on (we've done this before), and let it > prove itself. Sounds to me like everyone would be happy. > > WDYT? > > Eelco > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
On Nov 7, 2007 11:22 AM, Chris Colman <[EMAIL PROTECTED]> wrote: > > > How can it get messy when it's not yet possible to do in wicket? > > > > i believe it has been shown multiple times already that it CAN be done > > with vanilla wicket... > > I didn't like the look of any of those 'coded' solutions. i dont like the look of a lot of code in wicket, but that is not a valid criteria > They were not from the coding elegance book I've read. that is extremely subjective, so once again - not a valid criteria. you have just as many people saying they prefer it... > They also mean I'm starting to > arrange, layout and compose my pages in Java instead of markup (meaning > my graphic designers lose control). not at all. in java you simply declare the areas that can be extended. this is no different then a page adding components that are meant to be in some wicket:implements tag. > The abilty to control layout completely at the markup level instead of > the Java level is why I moved to Wicket from another framework in the > first place and I guess a lot of others have too. like i said, you dont lose that at all > The division of > responsibility in Wicket is something not achieved by any other > framework I have used which is great because I don't think I'm going to > be able to teach my graphic designers Java any time soon. i can argue that now your graphics designer needs to know about the "hierarchy" of pages in order to know which wicekt:implement areas are available to them in some page, so... > > I also wouldn't classify as "vanilla" that alternative, workaround using > low level plumbing code that hooks into the lifecycle methods. there is nothing low-level about onbeforerender() - its not called internalOnBeforeRender() is it? > It's more > like a honeycomb chocolate fudge, banana sundae, with 1" thick caramel > sauce sprinkled with 100s and 1000s ;) - it sounds great on the menu > but after you've finished it you're left wondering if you made the right > decision. i have implemented code like that and was not left wondering at all, but maybe thats just me -igor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tree table colors
Hello everyone, Been using wicket for the past month on a prototype I am working on. Great framework !!! Have a question regarding the tree table, I am using it to display sub-totals and would like to give sub-total row a different color. How can I accomplish this? Thanks Gene
Re: Multiple tags on a single base page?
On Nov 7, 2007 11:19 AM, Scott Swank <[EMAIL PROTECTED]> wrote: > I can see how and tags could be > a nice enhancement to the current and > tags. Do you have a working, or mostly working, patch? What I think we should do with this is make it an option. It would be turned off by default, requiring users to an extra one or two lines of configuration to turn this on (we've done this before), and let it prove itself. Sounds to me like everyone would be happy. WDYT? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.2 or 1.3 beta 4 ?
sounds good and congrats... Gerolf On Nov 7, 2007 9:58 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > On 11/7/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > > On Nov 7, 2007 9:40 PM, Martijn Dashorst <[EMAIL PROTECTED]> > wrote: > > > As for 1.2 or 1.3.. .I suggest 1.3. It is running on a couple of > > > production systems already, and it has some great new stuff I couldn't > > > live without anymore. > > > > is the upgrade of vocus to 1.3 done? last thing i heard was that johan > is > > working on that. > > It is not deployed yet, but the conversion stuff is done. Now we need > to test it. But the biggest issue is business... A part of the system > is developed on a separate branch, needs to be merged in our current > production branch, and HEAD is our 1.3 branch. So we are properly > screwed in this regard. > > Fortunately I have other projects I could build with 1.3, and that was > really nice. And the book is also 1.3 based, which makes me biased :) > > Martijn > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-beta4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: 1.2 or 1.3 beta 4 ?
On 11/7/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > On Nov 7, 2007 9:40 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > As for 1.2 or 1.3.. .I suggest 1.3. It is running on a couple of > > production systems already, and it has some great new stuff I couldn't > > live without anymore. > > is the upgrade of vocus to 1.3 done? last thing i heard was that johan is > working on that. It is not deployed yet, but the conversion stuff is done. Now we need to test it. But the biggest issue is business... A part of the system is developed on a separate branch, needs to be merged in our current production branch, and HEAD is our 1.3 branch. So we are properly screwed in this regard. Fortunately I have other projects I could build with 1.3, and that was really nice. And the book is also 1.3 based, which makes me biased :) Martijn -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.2 or 1.3 beta 4 ?
On Nov 7, 2007 9:40 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > See the development list... We're working hard. > > As for 1.2 or 1.3.. .I suggest 1.3. It is running on a couple of > production systems already, and it has some great new stuff I couldn't > live without anymore. > is the upgrade of vocus to 1.3 done? last thing i heard was that johan is working on that. just curious... Gerolf > > Martijn > > On 11/7/07, Christofer Jennings <[EMAIL PROTECTED]> wrote: > > I want to pitch Wicket for a new project at work. Is 1.3 beta 4 stable > > enough? Is there a ballpark idea of when 1.3 final will be out? ... I > > know that's a dumb question on an open source project but I guy can > > dream. > > > > Thanks! > > ,boz > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-beta4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: 1.2 or 1.3 beta 4 ?
Martijn Dashorst wrote: As for 1.2 or 1.3.. .I suggest 1.3. It is running on a couple of production systems already [...] LOL. ;-) Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.2 or 1.3 beta 4 ?
See the development list... We're working hard. As for 1.2 or 1.3.. .I suggest 1.3. It is running on a couple of production systems already, and it has some great new stuff I couldn't live without anymore. Martijn On 11/7/07, Christofer Jennings <[EMAIL PROTECTED]> wrote: > I want to pitch Wicket for a new project at work. Is 1.3 beta 4 stable > enough? Is there a ballpark idea of when 1.3 final will be out? ... I > know that's a dumb question on an open source project but I guy can > dream. > > Thanks! > ,boz > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.2 or 1.3 beta 4 ?
On Nov 7, 2007 12:37 PM, Christofer Jennings <[EMAIL PROTECTED]> wrote: > I want to pitch Wicket for a new project at work. Is 1.3 beta 4 stable > enough? Is there a ballpark idea of when 1.3 final will be out? ... I > know that's a dumb question on an open source project but I guy can > dream. We're currently trying to get the first RC out (see dev list), so that means we are pushing towards final rather than adding more features etc. 1.3 is much improved compared to 1.2, so I think you should definitively go for 1.3 Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
1.2 or 1.3 beta 4 ?
I want to pitch Wicket for a new project at work. Is 1.3 beta 4 stable enough? Is there a ballpark idea of when 1.3 final will be out? ... I know that's a dumb question on an open source project but I guy can dream. Thanks! ,boz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: gmap2 and map creation
Jan Stette schrieb: I'm pretty sure I'm using the latest version: sorry I was just to tired yesterday look into that any deeper. I just committed a patch. Could you check if it suits your needs? Also could you check if the codechange in the ManyPanel is asking for the same as your code? Good night, Martin $ svn info Path: . URL: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-gmap2 Repository Root: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff Repository UUID: ef7698a4-5110-0410-9fc6-c7eb3693863f Revision: 3219 Node Kind: directory Schedule: normal Last Changed Author: funkattack Last Changed Rev: 3149 Last Changed Date: 2007-10-23 21:44:10 +0100 (Tue, 23 Oct 2007) Actually, that stack trace might have been misleading as I had been playing around with the code in GMap2... Here's a stack trace with the original version: Caused by: org.apache.wicket.WicketRuntimeException: This component is not (yet) coupled to a page. It has to be able to find the page it is supposed to operate in before you can call this method (Component#getMarkupId) at org.apache.wicket.Component.getMarkupId(Component.java:1201) at wicket.contrib.gmap.GMap2.getJSinvoke(GMap2.java:399) at wicket.contrib.gmap.GMap2.getJSsetCenter(GMap2.java:424) at wicket.contrib.gmap.GMap2.setCenter(GMap2.java:353) Jan On 06/11/2007, Martin Funk <[EMAIL PROTECTED]> wrote: Hi Jan, to operate in before you can call this method (Component#getMarkupId) at org.apache.wicket.Component.getMarkupId(Component.java:1201) at wicket.contrib.gmap.GMap2.getJSinvoke(GMap2.java:399) at wicket.contrib.gmap.GMap2.getJSsetZoom(GMap2.java:424) at wicket.contrib.gmap.GMap2.setZoom(GMap2.java:353) (This is with Wicket 1.3 beta 4, and the head of gmap2) Looking at the line numbers I'd ask, are you sure you are running the latest wicket-contrib-gmap2? like svn info Pfad: . URL: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-gmap2 Basis des Projektarchivs: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff UUID des Projektarchivs: ef7698a4-5110-0410-9fc6-c7eb3693863f Revision: 3219 Knotentyp: Verzeichnis Plan: normal Letzter Autor: funkattack Letzte geänderte Rev: 3149 Letztes Änderungsdatum: 2007-10-23 22:44:10 +0200 (Di, 23 Okt 2007) Also the description sounds like something we might have covered in the one of the last updates. Have fun, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with wicket authentication
Ok, I had just a look at the Swarm home page, and didn't go further, but promise I will look at it deeper, now I know it's simple. Swarm is designed to be plain and simple. In short this is what you need to do: 1 implement Principal (i could see about a reasonable default implementation , but my guess is you want to store this in a database anyway and i am not sure i want a dependency on jpa) 2 create policy files 3 implement WaspApplication (by extending SwarmApplication) Off the top of my hat, that is al you need to get the default running. Off course if you want something special you need something more, but where don't you need to do that. But if you feel we could improve on some areas, let me know. Maurice On Nov 6, 2007 10:35 PM, <[EMAIL PROTECTED]> wrote: > I wished to try the basic Wicket authentication because it looked plain > simple (and simplicity and fewer code is my mantra!) > I had seen the Swarm one, but it didn't look as straightforward. Maybe I > will give it a try if I can't go with the standard one. > > Regards, > Hugues > - Regards, Hugues -- View this message in context: http://www.nabble.com/Problem-with-wicket-authentication-tf4751663.html#a13635200 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help understaning AjaxCallDecorator problem
So the ultimate result of the onClick() method, in this case, is to move to a whole new page, i.e the last line is: setResponsePage(...);, so technically, it probably does not need to be an ajax request, but because of the way we are reusing some code it is. I commented out the setResponsePage() as a test and the Ajax Console still disappeared. Timo Rantalaiho wrote: > > On Wed, 07 Nov 2007, skatz wrote: >> The Ajax debug console disappears before I can read what it is saying, >> and > > Hmm, I think that normally the ajax debug console should > stay there for javascript executions and ajax requests. > Could it be that the whole page gets loaded somehow? > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oyhttp://www.ri.fi/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Help-understaning-AjaxCallDecorator-problem-tf4760426.html#a13635149 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
Presumably the coded work arounds that don't rely on child/extends mean that the structural markup of each page is used instead of just that of the base page - and that would spell maintenance issues. Without using child/extend then ALL the structural markup in each page is used for each render - NOTHING is pulled from the base page markup (kind of makes me wonder why we need base page markup if not using child/extend - but that's another topic!). A change of layout structure would mean changing all page markups - yuck - or do you guys not care about your graphics designers - "arh, that's their problem if they want to do a site wide change!" I think the fundamental thing that most people are missing is that each component must be well formed XHTML, complete and self contained. If it starts a (or ) then it must also end it. Divs (and tables) are the basic structural elements of markup. One component can't be the start of a structural span of markup, the next few components content sections for that span and then the last component ends the structural span - that is not possible because each component must be well formed and complete. So this infers that structural markup typically is stored in page markup and "wraps" markup that inserts various self contained components. Now here's the thing: without using child/extends then that structural markup must be carefully defined in EVERY page markup because wicket does not do the funky inheritance merging when you don't use the child/extends tag. So if you want to change a border in between two components you must change it in EVERY page markup. That would suck. Alternatively, if you do use the current child/extend you end up having to bang multiple components into the overridden section which means that you also bang in the border that exists between them - so now the border markup is duplicated many times. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why dioes this error occur?
I am using wicket-1.2.6. Unfortunately it is not possible for me to upgrade to a newer version. > Hi salmas, > > On 07 November 2007, 7:05:26 PM, salmas wrote: > s> Every once in awhile if I am clicking around for awhile in the UI of my > s> application I get the following error. What causes this? > > s> java.lang.NullPointerException > s> at > s> > wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:295) > > What version of Wicket are you using? > > -- > /Gwyn > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Yes! see: https://issues.apache.org/jira/browse/WICKET-1134 -- stefan Scott Swank wrote: > > I can see how and tags could be > a nice enhancement to the current and > tags. Do you have a working, or mostly working, patch? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - --- Stefan Fußenegger http://talk-on-tech.blogspot.com // looking for a nicer domain ;) -- View this message in context: http://www.nabble.com/Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4738673.html#a13634545 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eHour migrated to Wicket
Good looking app. What kinds of lessons did you learn in the migration? It would be interesting to collect them into a wiki page. -- Nick Heudecker Professional Wicket Training & Consulting http://www.systemmobile.com Eventful - Intelligent Event Management http://www.eventfulhq.com
Re: Help understaning AjaxCallDecorator problem
On Wed, 07 Nov 2007, skatz wrote: > The Ajax debug console disappears before I can read what it is saying, and Hmm, I think that normally the ajax debug console should stay there for javascript executions and ajax requests. Could it be that the whole page gets loaded somehow? Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oyhttp://www.ri.fi/ > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why dioes this error occur?
Hi salmas, On 07 November 2007, 7:05:26 PM, salmas wrote: s> Every once in awhile if I am clicking around for awhile in the UI of my s> application I get the following error. What causes this? s> java.lang.NullPointerException s> at s> wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:295) What version of Wicket are you using? -- /Gwyn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> > How can it get messy when it's not yet possible to do in wicket? > > i believe it has been shown multiple times already that it CAN be done > with vanilla wicket... I didn't like the look of any of those 'coded' solutions. They were not from the coding elegance book I've read. They also mean I'm starting to arrange, layout and compose my pages in Java instead of markup (meaning my graphic designers lose control). The abilty to control layout completely at the markup level instead of the Java level is why I moved to Wicket from another framework in the first place and I guess a lot of others have too. The division of responsibility in Wicket is something not achieved by any other framework I have used which is great because I don't think I'm going to be able to teach my graphic designers Java any time soon. I also wouldn't classify as "vanilla" that alternative, workaround using low level plumbing code that hooks into the lifecycle methods. It's more like a honeycomb chocolate fudge, banana sundae, with 1" thick caramel sauce sprinkled with 100s and 1000s ;) - it sounds great on the menu but after you've finished it you're left wondering if you made the right decision. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why dioes this error occur?
Hi. Well in my case this error apeared when the user clicked on a link that was directing the user to the next page, and while the user did not wait for the other page to load, or he thought that he did not press the mouse button and he clicked again. The server saw that the component(link) was no longer in the the new page and therefore the nullpointer. I got around this by disabling the link after the clicking. salmas wrote: > > Every once in awhile if I am clicking around for awhile in the UI of my > application I get the following error. What causes this? > > java.lang.NullPointerException > at > wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:295) > at > wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveRenderedPage(DefaultRequestTargetResolverStrategy.java:228) > at > wicket.request.compound.DefaultRequestTargetResolverStrategy.resolve(DefaultRequestTargetResolverStrategy.java:153) > at > wicket.request.compound.AbstractCompoundRequestCycleProcessor.resolve(AbstractCompoundRequestCycleProcessor.java:48) > at wicket.RequestCycle.step(RequestCycle.java:992) > at wicket.RequestCycle.steps(RequestCycle.java:1084) > at wicket.RequestCycle.request(RequestCycle.java:454) > at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) > at wicket.protocol.http.WicketServlet.doPost(WicketServlet.java:262) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) > at > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) > at > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) > at > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) > -- View this message in context: http://www.nabble.com/Why-dioes-this-error-occur--tf4766684.html#a13634076 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
I can see how and tags could be a nice enhancement to the current and tags. Do you have a working, or mostly working, patch? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> Chris Colman schrieb: > > The beauty of the multiple extend/child idea is that it's not a > > completely new concept we're talking about here - it's merely an issue > > of supporting n>1 instead of arbitrarily fixing n=1 like it is now. > > 1 Question: Who dominates Who and Why? > > If you extend 1 class by class you create specialisations that dominate > each other, but here you just mess together some classes - so why should > which class dominate? If we manipulate a headertag? If we have same > namespace? If we have different securitylevels? Wich class is > responsible for all this? Why? Dunno what you mean by "dominate" or "mess together some classes". No one is talking about mess - the whole point of this feature is avoidance of mess - in the same way OO brings about reduced complexity in code the same thing can happen with markup. We're not proposing multiple inheritance - which indeed causes mess. We're talking single inheritance which means single lineage. Each page only has a single base page. It's easy for Wicket to perform the resolutions and merge markup from base and derived pages. I know this because it already does it and it works fine. We're just proposing to remove the restriction that it can only do it for just one section of your base page - that's all, nothing revolutionary - just evolutionary. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
On Wed, Nov 07, 2007 at 07:14:01PM +0100, Korbinian Bachl wrote: > > Given these subtle problems with this approach, I admit I'm warming to > > the multiple extend/child idea. > > im oposite - if i have X extends in a page, whose extend should be > preferred (e.g: manipulating the head or a part outside of itself) ? Perhaps I don't understand your argument, but it sounds like you're interpreting this as some sort of multiple inheritance thing. I like to look at it this way: - a Wicket page is a Java class and some markup. - there are three ways a page can acquire its markup - it can have its own - it can inherit it from a base class - it can *mostly* inherit it from a base class, but inject some additional markup into the parent markup at a place specified by the parent markup All the current proposal does is allow the parent markup to advertise multiple places where children can inject their markup. Yes, there are difficulties with this. Child pages have to be careful about component ID collisions, the framework has to sort out multiple header contributions from children and grandchildren, etc., but these problems are present in the current single extend/child approach. I can't see any additional ambiguities introduced by allowing additional markup injection sites. > my override of onBeforeRender is secure from your point and IMHO more > easy... I suggest it's not so easy for average Java developers starting out with Wicket. In my experience, many Java developers are unaware of the "don't call non-private, non-final methods from constructors" rule. Further, once you've been bitten by that problem, it's not clear that using onBeforeRender is the answer. And once you've figured *that* out, it's not clear that you have to protect against multiple invocations. jk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Why dioes this error occur?
Every once in awhile if I am clicking around for awhile in the UI of my application I get the following error. What causes this? java.lang.NullPointerException at wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:295) at wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveRenderedPage(DefaultRequestTargetResolverStrategy.java:228) at wicket.request.compound.DefaultRequestTargetResolverStrategy.resolve(DefaultRequestTargetResolverStrategy.java:153) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.resolve(AbstractCompoundRequestCycleProcessor.java:48) at wicket.RequestCycle.step(RequestCycle.java:992) at wicket.RequestCycle.steps(RequestCycle.java:1084) at wicket.RequestCycle.request(RequestCycle.java:454) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219) at wicket.protocol.http.WicketServlet.doPost(WicketServlet.java:262) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) -- View this message in context: http://www.nabble.com/Why-dioes-this-error-occur--tf4766684.html#a13633697 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> > Given these subtle problems with this approach, I admit I'm warming to > > the multiple extend/child idea. > > im oposite - if i have X extends in a page, whose extend should be > preferred (e.g: manipulating the head or a part outside of itself) ? I'm not sure I understand the issue you raise but so please forgive me if I've misunderstood: Presumably you don't have an issue with multiple abstract methods in Java classes? As Java and Wicket only support single inheritance there is no issue as to which base class/page child section is being extended in a derived class/page (that only ever happens in a multiple inheritance paradigm and no one is proposing we go down that path!) - the identifier of an implements in a derived page will only ever resolve to a single abstract tag in a base page. There's no confusion here I don't believe. In Java you name methods carefully and appropriately and the compiler warns you if you have duplicated a function signature. Same would happen in wicket. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
You are wrong. I have a component (Panel) that has a method to return a
Fragment. This component returns a default implementation of that Fragment,
but pages can override that Fragment.
CRUDFormPanel extends Panel {
protected Fragment newFormFields(String id, Form form) {
if (property == null)
return null;
Fragment f = new Fragment(id, "defaultFormFields",
ListFormPanel.this);
RequiredTextField desc = new RequiredTextField("property",
new PropertyModel(form.getModel(), property));
desc.add(StringValidator.maximumLength(255));
f.add(desc);
f.add(new Label("propertyLabel", getString("propertyLabel")));
form.add(new ObjectExistanceValidator(service, desc, property));
return f;
}
// more code
}
Pages that want to have more fields in this form, can provide another
Fragment.
MyCustomPage extends WebPage {
MyCustomPage() {
add(new CRUDFormPanel("panel") {
protected Fragment newFormFields(String id, Form form) {
Fragment f = new Fragment(id, "customFormFields",
MyCustomPage.this);
RequiredTextField field = new
RequiredTextField("anotherProperty",
new PropertyModel(form.getModel(), "anotherProperty"));
desc.add(StringValidator.maximumLength(50));
f.add(field);
form.add(new ObjectExistanceValidator(service, desc, property));
return f;
}
});
}
}
This is how I override tags with vanilla Wicket. Do we really need another
markup?!
On Nov 7, 2007 4:51 PM, Chris Colman <[EMAIL PROTECTED]> wrote:
> > a lot of people are saying that this can be implemented with panels,
> > and that is true. but actually implementing this with fragments will
> > make it look very similar to this new strategy and does not have the
> > id collission problem, because components ARE nested in two different
> > containers:
>
> I've never used fragments but I just read up on them...
>
> I may be wrong but it looks as if you have to define all possible
> fragments that might appear in a page to that page. It doesn't seem to
> follow the natural, organic flow of markup inheritance where a base page
> can be enhanced by substituting base a page section with markup defined
> in derived/extended pages - that only happens with the child/extends
> feature from my understanding.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Bruno Borges
blog.brunoborges.com.br
+55 1185657739
"The glory of great men should always be
measured by the means they have used to
acquire it."
- Francois de La Rochefoucauld
Re: Multiple tags on a single base page?
read my previous reply more carefuly, instead of
abstract Component getTemplateOne(String id);
you can simply do: Component getTemplateOne(String id) { return new
EmptyPanel(id); }
now you have a "non-required" override of any part of markup's template...
-igor
On Nov 7, 2007 10:51 AM, Chris Colman <[EMAIL PROTECTED]> wrote:
> > a lot of people are saying that this can be implemented with panels,
> > and that is true. but actually implementing this with fragments will
> > make it look very similar to this new strategy and does not have the
> > id collission problem, because components ARE nested in two different
> > containers:
>
> I've never used fragments but I just read up on them...
>
> I may be wrong but it looks as if you have to define all possible
> fragments that might appear in a page to that page. It doesn't seem to
> follow the natural, organic flow of markup inheritance where a base page
> can be enhanced by substituting base a page section with markup defined
> in derived/extended pages - that only happens with the child/extends
> feature from my understanding.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: eHour migrated to Wicket
> I've finally migrated my time tracking tool, eHour, from Struts to Wicket ! > > eHour is a webbased time tracking tool for consultancy companies and > other project based businesses. > The primary objective is to keep time tracking as simple and user > friendly as possible while still being > very effective at measuring and reporting the amount of time your team > spends on a project. > More details at http://www.ehour.nl/ Congrats! Looks good. > I have to say that I underestimated the amount of time needed to do the > whole migration, mostly due to the amount > of JSP/JSTL/Struts code I had to migrate and the learning > curve/documentation of Wicket. But I'm still very happy I > did the migration. Development is fun again and Wicket feels a lot more > robust than a JSP/JSTL/Ajax/Struts combo. > Thanks to the Wicket team for this excellent framework ! And you, thanks for being part of the community! Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> a lot of people are saying that this can be implemented with panels, > and that is true. but actually implementing this with fragments will > make it look very similar to this new strategy and does not have the > id collission problem, because components ARE nested in two different > containers: I've never used fragments but I just read up on them... I may be wrong but it looks as if you have to define all possible fragments that might appear in a page to that page. It doesn't seem to follow the natural, organic flow of markup inheritance where a base page can be enhanced by substituting base a page section with markup defined in derived/extended pages - that only happens with the child/extends feature from my understanding. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
On Nov 7, 2007 10:38 AM, Chris Colman <[EMAIL PROTECTED]> wrote: > > How can it get messy when it's not yet possible to do in wicket? i believe it has been shown multiple times already that it CAN be done with vanilla wicket... -igor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> > And if somebody really needs 5 child areas, something else might be even > > messier than the page's constructor. I rather think that 2, 3 or in rare > > cases even 4 ids could make sense. > > i must disagree - i have a basepage which defines the default layout on a > project, i.e. header, top-nav-container (imprint etc), navigation, > content-left/-right/main, footer - this makes 7 panels which are added on > the > way down to the resulting page... > > but i don't use abstract methods for this, for it can get messy (as stated > in other comments). How can it get messy when it's not yet possible to do in wicket? You mention 7 different panels which is > 1 and so not currently supported by wicket's current child/extends feature. Unless you mean that trying to override 7 different sections with only one child/extends feature - but now my brain hurts - the anticipated messiness my be a result of trying to implement multiple specialized sections without support for it being in wicket yet ;) (but given that many people are starting to warm to the idea you might be able to do this sooner rather than later!) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Chris Colman schrieb: The beauty of the multiple extend/child idea is that it's not a completely new concept we're talking about here - it's merely an issue of supporting n>1 instead of arbitrarily fixing n=1 like it is now. 1 Question: Who dominates Who and Why? If you extend 1 class by class you create specialisations that dominate each other, but here you just mess together some classes - so why should which class dominate? If we manipulate a headertag? If we have same namespace? If we have different securitylevels? Wich class is responsible for all this? Why? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> Korbinian Bachl wrote: > > you missed solution3: > > the real-wicket-way(tm) for multiple content-places in a tied page-area: > > Whaaa, I seriously hope this is not the real-wicket-way! My brain hurts! > > A framework is supposed to make things easy and readable! The code below > is just way too complicated to achieve something that should be easy... > > Preferably when doing simple stuff like this, I don't want to be > confronted with things like rendering (and adding render hooks), or with > keeping extra state about components being or not being initalized. Also > I don't want to have to copy this boiler plate for every time I want to > place some kind of component "hole" in a base page! > Well said! I agree wholeheartedly. I suppose the reason I'm so passionate about this new multiple child/extends support is that it helps preserve simplicity for the wicket developer instead of making our more complex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple tags on a single base page?
> public DerivedPage extends BasePage {
>
> private String name;
>
> public DerivedPage(String name) {
> super();
> this.name = name;
> }
>
> public abstract addAbstract1(String abstractId1) {
> add(new NamePanel(abstractId1, name));
> }
> }
>
> This code is broken, since you're constructing NamePanel before name
has
> been initialized. Someone later in this thread shows a better way to
do
> this, by calling the overridable methods from onBeforeRender. But this
> is also tricky; because onBeforeRender can be called multiple times
you
> must maintain a flag to ensure you only add your panels once.
>
> Given these subtle problems with this approach, I admit I'm warming to
> the multiple extend/child idea.
Good to hear!! Multiple abstract/implements (child/extends) lets us
avoid the ugly plumbing code suggested in previous posts as an
alternative. I'd rather extend an elegant existing feature with
multiplicity than have to add low level plumbing code to my apps that
assumes a knowledge of the lifecycle methods (eg., onBeforeRender -
never needed to override that method for anything else before now) and
requires me to hook in to the lifecycle at various obscure places like
suggested. I think this goes against the wicket's simplicity motto way
more than supporting multiple child/extends sections does.
The beauty of the multiple extend/child idea is that it's not a
completely new concept we're talking about here - it's merely an issue
of supporting n>1 instead of arbitrarily fixing n=1 like it is now.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Sebastiaan van Erk schrieb: Korbinian Bachl wrote: you missed solution3: the real-wicket-way(tm) for multiple content-places in a tied page-area: Whaaa, I seriously hope this is not the real-wicket-way! My brain hurts! maybe you should go to a doctor then?... A framework is supposed to make things easy and readable! The code below is just way too complicated to achieve something that should be easy... whats difficult here? it gives you maximum flexibility and was just a example(tm) which can be further simplified if you use other container types - this was showed to me by Igor some time ago and it has proven its success for me... Preferably when doing simple stuff like this, I don't want to be confronted with things like rendering (and adding render hooks), or with keeping extra state about components being or not being initalized. Also I don't want to have to copy this boiler plate for every time I want to place some kind of component "hole" in a base page! usually this kind of code is present at 1 place within a project, not in every class, just the raw baseclass (maybe in 2 baseclasses if you have a designer who wants to have 2 completely different markups for 1 project) - compared to other existing poblems of webdeveloping (like security and authorization) these 2-minutes i spend on this at all is not really mattering... Best, Korbinian Regards, Sebastiaan eg: html: ... Place to put anything -zip- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
> Given these subtle problems with this approach, I admit I'm warming to
> the multiple extend/child idea.
im oposite - if i have X extends in a page, whose extend should be
preferred (e.g: manipulating the head or a part outside of itself) ?
my override of onBeforeRender is secure from your point and IMHO more
easy...
John Krasnay schrieb:
On Wed, Nov 07, 2007 at 11:31:12AM +0100, Mats Norén wrote:
Is the above statement really true considering that by adding abstract
methods to your page you defer the creation of the markup in just the
same way as the new proposed solution?
BasePage.java
public BasePage() {
addAbstract1("abstractId1");
addAbstract2("abstractId2);
}
public abstract addAbstract1(String abstractId1);
public abstract addAbstract2(String abstractId2);
BasePage.html
What is the difference between that and doing abstract / implements?
You've just illustrated one of the major problems with the
panel-from-a-subclass approach: it's easy to get it wrong. In your
example, addAbstract1 and addAbstract2 will be called in a class whose
constructor has not yet been called. Consider:
public DerivedPage extends BasePage {
private String name;
public DerivedPage(String name) {
super();
this.name = name;
}
public abstract addAbstract1(String abstractId1) {
add(new NamePanel(abstractId1, name));
}
}
This code is broken, since you're constructing NamePanel before name has
been initialized. Someone later in this thread shows a better way to do
this, by calling the overridable methods from onBeforeRender. But this
is also tricky; because onBeforeRender can be called multiple times you
must maintain a flag to ensure you only add your panels once.
Given these subtle problems with this approach, I admit I'm warming to
the multiple extend/child idea.
jk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JavaRebel experience
Java Rebel worked for me too. I had no such problem. -- View this message in context: http://www.nabble.com/JavaRebel-experience-tf4695671.html#a13632511 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Igor Vaynberg wrote:
... actually implementing this with fragments will
make it look very similar to this new strategy and does not have the
id collission problem, because components ARE nested in two different
containers:
class basepage extends webpage {
Fragment templateFoo1(String id) { return new emptyfragment(id); }
Fragment templateFoo2(String id) { return new emptyfragment(id); }
}
thoughts?
I've finally got around to reading (most) of this insanely long thread.
My first thought was, "why don't you just use Fragments for this?"
Obviously the person who extends BasePage needs to know what fragment
IDs they should be adding in.
But then, with the proposed extra tag, they'd need to
know what IDs to be using, so I can't see much
difference here.
The only issue is that you need to actually add some code, which you
don't with a pure tag-based solution.
On the other hand, you probably need to add some code anyway - I can't
think of many use-cases where you'd want to only put mark-up in one or
more of your blocks that isn't better handled using
localization with keys being overridden for the various
pages.
Regards,
Al
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Thanks for giving the best overview of my thoughts Igor. Are you reading my
mind?
On Nov 7, 2007 3:50 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> let me weigh in with my thoughts on this.
>
> a big problem with markup inheritance is the possibility of id collissions
>
> for example
>
> class basepage extends webpage {
> public basepage() {
>add(new label("label"));
> }
> }
>
> class concretepage extends basepage {
> public concretepage() {
>add(new label("label"));
> }
> }
>
> basepage:
> concretepage:
>
> now what you are proposing here makes this collission possibility
> significantly higher because essentially i CANNOT even have something
> like this:
>
>
>
>
> even though to me it looks like the nasting of foo1 and foo2 are
> seperate so i should be able to have a direct child with the same id
> in bothbut i cannot.
>
> a lot of people are saying that this can be implemented with panels,
> and that is true. but actually implementing this with fragments will
> make it look very similar to this new strategy and does not have the
> id collission problem, because components ARE nested in two different
> containers:
>
> class basepage extends webpage {
> Fragment templateFoo1(String id) { return new emptyfragment(id); }
> Fragment templateFoo2(String id) { return new emptyfragment(id); }
> }
>
> wicket:id="label">
> wicket:id="label">
>
> thoughts?
>
> -igor
>
>
>
>
> On 11/2/07, Stefan Fußenegger <[EMAIL PROTECTED]> wrote:
> >
> > Hi folks,
> >
> > I just stumbled on a situation where it would be useful to have two or
> more
> > tags in a base page. Just consider a layout that
> consists
> > of the usual footer, header, navigation, and content parts. But now, the
> > content should be arranged in two columns, e.g. two different s.
> >
> > To give a short example, the BasePage.html cloud look like this
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > And the Child.html markup would look like this:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Wouldn't that be a desirable feature? I tried to run the above example
> > expecting to get an exception. The second wicket:child/wicket:extend
> pair
> > was happily ignored though.
> >
> > Best regards, Stefan
> > --
> > View this message in context:
> http://www.nabble.com/Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4738673.html#a13551448
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Bruno Borges
blog.brunoborges.com.br
+55 1185657739
"The glory of great men should always be
measured by the means they have used to
acquire it."
- Francois de La Rochefoucauld
Re: Multiple tags on a single base page?
let me weigh in with my thoughts on this.
a big problem with markup inheritance is the possibility of id collissions
for example
class basepage extends webpage {
public basepage() {
add(new label("label"));
}
}
class concretepage extends basepage {
public concretepage() {
add(new label("label"));
}
}
basepage:
concretepage:
now what you are proposing here makes this collission possibility
significantly higher because essentially i CANNOT even have something
like this:
even though to me it looks like the nasting of foo1 and foo2 are
seperate so i should be able to have a direct child with the same id
in bothbut i cannot.
a lot of people are saying that this can be implemented with panels,
and that is true. but actually implementing this with fragments will
make it look very similar to this new strategy and does not have the
id collission problem, because components ARE nested in two different
containers:
class basepage extends webpage {
Fragment templateFoo1(String id) { return new emptyfragment(id); }
Fragment templateFoo2(String id) { return new emptyfragment(id); }
}
thoughts?
-igor
On 11/2/07, Stefan Fußenegger <[EMAIL PROTECTED]> wrote:
>
> Hi folks,
>
> I just stumbled on a situation where it would be useful to have two or more
> tags in a base page. Just consider a layout that consists
> of the usual footer, header, navigation, and content parts. But now, the
> content should be arranged in two columns, e.g. two different s.
>
> To give a short example, the BasePage.html cloud look like this
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> And the Child.html markup would look like this:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Wouldn't that be a desirable feature? I tried to run the above example
> expecting to get an exception. The second wicket:child/wicket:extend pair
> was happily ignored though.
>
> Best regards, Stefan
> --
> View this message in context:
> http://www.nabble.com/Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4738673.html#a13551448
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
>
> just a question: do i start to convince you? ;)
>
No... you are not... :D far far away from that
But don't take it personal, my opinion is technical... only!
On Nov 7, 2007 11:29 AM, Stefan Fußenegger <[EMAIL PROTECTED]>
wrote:
>
> Well, if naming is your only concern, the attribute's name can easily be
> replaced with something else than id ... e.g. name
>
>
>
>
> some text
>
>
> and remember that they can be optional as well:
>
>
>
>
> some text
>
>
> This way, its completely compatible with child/extend (which can be
> proofed
> with the existing junit test for markup inheritance)
>
> just a question: do i start to convince you? ;)
>
> best regards
>
>
> Bruno Borges wrote:
> >
> > Let me paste what I commented in WICKET-1134:
> >
> > *I think this improvement is just more of a way to "override" components
> > declared in markups of a super class. Because this is what really
> happens.
> > Let's check your example:
> >
> > In the BasePage, there are two fragments:
> > - subNavigation
> > - content
> >
> > What about if I want to have a fragment in SectionPage with id
> "content",
> > but not related with that content from BasePage? You see, the concept of
> > extend/child, is the same as in OOP's inheritance. What goes in child,
> is
> > from the subclass. Period.
> >
> > In Java, if you declare:
> > class BasePage ... {
> > protected Object someProperty;
> > }
> >
> > class SectionPage extends BasePage {
> > protected Object someProperty;
> > }
> >
> > What happens here is that SectionPage.someProperty does NOT
> > override/implement/whatever-you-wanna-call, BasePage.someProperty. What
> > you
> > want to do in HTML would be this in Java.
> >
> > I'm worry about people trying to subclass some WebMarkupContainer, and
> > having to be carefully with components ids, just to _not_ match
> something
> > that would generate strange output.
> >
> > If in SectionPage I add some component (like Label) with "content" id,
> > what
> > would happen? Throw a message: "You cannot use this id because there's
> an
> > abstract 'content' markup in BasePage.html". This would lead to code in
> > HTML
> > that has NO reference within it's Java class.
> >
> > This means that: what you don't see in Java, it *might* be possible to
> > exist
> > in the HTML.
> >
> > And what I like most of Wicket, is its ability to let me take control of
> > everything, just from one source: Java. But if I'm going to be obligated
> > of
> > taking care of what people declare in HTML files that I can't see in
> some
> > Java source code, then I will reconsider my framework's choice.
> >
> > Regards*
> >
> > Now, Stefan, let me reply your last comment in the issue:
> > *No, ids used with abstract/implement are completely different from
> > wicket:ids ... they are only used to construct (i.e. merge ... or link)
> > the
> > markup, so it is perfectly legal to use when there
> > is
> > a somewhere, as they won't be related.
> > Therefore,
> > no of the concerns you mention would apply, as ...
> >
> > The concept of abstract/implement is the same as in OOP's inheritance.
> > What
> > goes in child, is from the subclass! Exclamation mark! ;)*
> >
> > Ok, you propose a new attribute for extend/abstract, child/implement
> pair
> > tags. And you say that this id attribute will NOT have any relationship
> > with
> > wicket:id. Well, isn't this something... scary? The documentation will
> > have
> > to take care of this, because it will _not_ be intuitive.
> >
> > Regards,
> >
> >
> > On Nov 7, 2007 10:15 AM, Stefan Fußenegger <[EMAIL PROTECTED]>
> > wrote:
> >
> >>
> >> Hi Mats, let me try to explain what Chris and I see here that others
> >> don't
> >> -
> >> may it be there or not ;)
> >>
> >> You can of course do everything with panels that could be done with
> >> multiple
> >> abstract sections (may they be named wicket:child or wicket:abstract).
> >> However, if this is the only argument, you wouldn't need markup
> >> inheritance
> >> at all! The proposed change is just an extension of exactly this markup
> >> inheritance concept (that everybody loves) to make it even more
> powerful
> >> than it already is.
> >>
> >> I was quite new to wicket (which I still am) and came across a
> situation
> >> where I wanted to use two abstract sections: one for a sub-navigation
> >> that
> >> was common for several pages in a section and one for the actual
> content.
> >> For me, as a wicket newbie, it would have been most natural to use
> markup
> >> inheritance to solve this problem. Using abstract methods, while being
> a
> >> nice solution (workaround?), didn't come to my mind at once, nor did I
> >> find
> >> it somewhere in the docs.
> >>
> >> imho, there are two possible solution to this problem:
> >> 1. promote using abstract methods for this in the docs as the
> wicket-way
> >> of
> >> doing it
> >> 2. extend the current markup inheritance mechanism (which I tried to do
> >> with
> >> my patch/prototype)
> >>
> >> -- stefan
> >>
Re: Question about localization
application.init() {
getresourcesettings().setlocalizer(...);
}
you dont have to use the default resource model, just write your own
if you dont like the default one.
-igor
On 11/7/07, Pills <[EMAIL PROTECTED]> wrote:
>
> Yes, I'll make it part of the key.
>
> I searched but not found, how can I change the default localizer and the
> default resourcemodel?
>
> There is no method "setLocalizer"/"setResourceModel" in class
> WebApplication...
>
> Thank you for your help.
>
>
> igor.vaynberg wrote:
> >
> > you can override methods in localizer to bend it to your will, but
> > like i said beware if you do not expect to make style part of the key
> >
> > -igor
> >
>
> --
> View this message in context:
> http://www.nabble.com/Question-about-localization-tf4756837.html#a13623105
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
But the number of added panels needn't be the number of abstract section (though it could). -- stefan Jan Kriesten wrote: > > > hi stefan, > >> And if somebody really needs 5 child areas, something else might be even >> messier than the page's constructor. I rather think that 2, 3 or in rare >> cases even 4 ids could make sense. > > i must disagree - i have a basepage which defines the default layout on a > project, i.e. header, top-nav-container (imprint etc), navigation, > content-left/-right/main, footer - this makes 7 panels which are added on > the > way down to the resulting page... > > but i don't use abstract methods for this, for it can get messy (as stated > in > other comments). > > regards, --- jan. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - --- Stefan Fußenegger http://talk-on-tech.blogspot.com // looking for a nicer domain ;) -- View this message in context: http://www.nabble.com/Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4738673.html#a13631624 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
hi stefan, > And if somebody really needs 5 child areas, something else might be even > messier than the page's constructor. I rather think that 2, 3 or in rare > cases even 4 ids could make sense. i must disagree - i have a basepage which defines the default layout on a project, i.e. header, top-nav-container (imprint etc), navigation, content-left/-right/main, footer - this makes 7 panels which are added on the way down to the resulting page... but i don't use abstract methods for this, for it can get messy (as stated in other comments). regards, --- jan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Popup parent comunication
Yes, you must be right, another issue against the modal window is that the
datepicker does not work inside it, and I pretty much decided to stick to
normal popups.
Well it seems that i may have something here:
In the parent page:
add(new AbstractDefaultAjaxBehavior() {
protected void respond(AjaxRequestTarget ajaxRequestTarget) {
System.out.println("Ajax Method invoked");
}
protected void onRenderHeadContribution(final Response response)
{
super.onRenderHeadContribution(response);
StringHeaderContributor header =
new StringHeaderContributor(" " +
"function call() {" +
getCallbackScript(false, true) + "};" +
"");
((WebPage)getComponent().getPage()).add(header);
}
});
In the popup window we have the link:
Link link = new Link("addLink") {
public void onClick() {
System.out.println("Ajax Method invoked");
}
protected CharSequence getOnClickScript(CharSequence
charSequence) {
CharSequence click =
super.getOnClickScript(charSequence);
if(click == null) {
return "self.opener.call();";
}
return click + "self.opener.call();";
}
};
Current problem is that the method sometimes gets invoked sometimes it does
not(the text "Ajax Method invoked" apears on the screen). Actually only the
first time in most cases. The problem must be with the ajax call cause i
added in the call function a debug message in javascript that gets always
called(the call function).
Anybody has any ideas why this is?
Mr Mean wrote:
>
> if your modal dialog contains ajax tabs it should work, but all your
> user interaction from withing the dialog must be ajax.
>
> Maurice
>
> On Nov 7, 2007 1:50 PM, serban.balamaci <[EMAIL PROTECTED]> wrote:
>>
>> I cannot use the modal windows.
>> They are plain popups. I do not know if there is a difference beetween
>> modal
>> windows that have a content a panel or a page, but i need to have tabbed
>> pannels(which are links) inside the popup and by using a modal page with
>> a
>> panel content when i press on another tab(a link), i get the message that
>> "This action requires to navigate away from this page and the modal
>> window
>> will close" and after pressing it does close the modal window.
>>
>> I am currently trying the 3rd option, i think i can write the javascript
>> for
>> the ajax request.
>> I will post the solution if i get it working.
>>
>>
>>
>> Mr Mean wrote:
>> >
>> > Are you using the ModalWindow? in that case you need to set the
>> > PageCreator to return your page, don't use panels. Second you need to
>> > set a callbackhandler for the windowclose event. There you must update
>> > your combo.
>> >
>> > Maurice
>> >
>> > On Nov 7, 2007 12:09 PM, serban.balamaci <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hello!
>> >> I have the following problem. I have a parent page, that opens a popup
>> >> through a PageLink.
>> >> The popup window is a window in which new records can be added, but i
>> >> need a
>> >> combo in the parent page to reflect and contain also the new choice
>> added
>> >> in
>> >> the popup.
>> >>
>> >> 1. Reloading the whole parent page at popup close link pressed i would
>> >> take
>> >> as the last resolve because the user may have introduced data in the
>> >> controls that would get lost in the reloading process. I could get
>> around
>> >> this by adding a submit behaviour to the link and save in session the
>> >> values
>> >> inserted till that moment and rehidrate the model with values from the
>> >> session instead of the database, and so obtain the state that the page
>> >> was
>> >> in before the popup was opened, but i'm wondering if there is not a
>> >> cleaner
>> >> solution for this.
>> >>
>> >> 2. I also tried(didn't think this would work:) but had to try) to pass
>> >> the
>> >> combo to the popup page and tried to update through the pressing of an
>> >> ajaxlink the combo. It said it could not find the markup id for the
>> >> combo(expected since it tried in the popup and not in the parent) so i
>> >> guess
>> >> that this approach could be made valid if the ajax callback would be
>> >> directed at the parent page instead of the popup - i do not know how
>> to
>> >> do
>> >> this.
>> >>
>> >> 3. Another option I am considering is calling a self.opener.function
>> in
>> >> which i would have javascript code for the ajax update of the combo in
>> >> the
>> >> parent. What code that is doing the ajax update i still do not know
>> where
>> >> to
>> >> find-> maybe on the onselectionchange behaviour would be the way to
>> find
>> >> out, or if it breaks something in the way wicket is working
Re: Multiple tags on a single base page?
>From the Java-side, it isn't visible, whether a component will be placed in whatever html part. So you add all components in the constructor, yes. However, it's as messy as adding 5 components is right now ... they will just be added at different places. And if somebody really needs 5 child areas, something else might be even messier than the page's constructor. I rather think that 2, 3 or in rare cases even 4 ids could make sense. Is that what you meant? -- stefan Johan Compagner wrote: > > no not the merging of markup. > but inside the constructor of the child/sub page. > Where do you make all the root components of all the child parts? > you will add that to the page itself right? > > I just say that then it could be a bit messy when you have 5 child area's > > johan > > > > On 11/7/07, Stefan Fußenegger <[EMAIL PROTECTED]> wrote: >> >> >> hi johan, >> >> >> Johan Compagner wrote: >> > >> > 1 thing that does bother me a bit (but maybe i have to do a deeper look >> > into >> > the patch) how do you separate >> > the components in the constructor of the sub page.. i guess you just >> add >> > all >> > the components over all the child fragments >> > in the page itself. That's not a nice separation... That can lead to >> big >> a >> > big mess.. Because what component belong to what child part. " >> > >> >> I don't get what you mean here. However, my implementation is closely >> related to Juergen's MergedMarkup.java (and admittedly partially copied) >> and >> does the same. >> >> - >> --- >> Stefan Fußenegger >> http://talk-on-tech.blogspot.com // looking for a nicer domain ;) >> -- >> View this message in context: >> http://www.nabble.com/Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4738673.html#a13629154 >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - --- Stefan Fußenegger http://talk-on-tech.blogspot.com // looking for a nicer domain ;) -- View this message in context: http://www.nabble.com/Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4738673.html#a13631363 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
On Nov 7, 2007 5:13 PM, John Krasnay <[EMAIL PROTECTED]> wrote:
> You've just illustrated one of the major problems with the
> panel-from-a-subclass approach: it's easy to get it wrong. In your
> example, addAbstract1 and addAbstract2 will be called in a class whose
> constructor has not yet been called. Consider:
>
> public DerivedPage extends BasePage {
>
> private String name;
>
> public DerivedPage(String name) {
> super();
> this.name = name;
> }
>
> public abstract addAbstract1(String abstractId1) {
> add(new NamePanel(abstractId1, name));
> }
> }
>
> This code is broken, since you're constructing NamePanel before name has
> been initialized. Someone later in this thread shows a better way to do
> this, by calling the overridable methods from onBeforeRender. But this
> is also tricky; because onBeforeRender can be called multiple times you
> must maintain a flag to ensure you only add your panels once.
>
> Given these subtle problems with this approach, I admit I'm warming to
> the multiple extend/child idea.
I stand corrected! :)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple tags on a single base page?
Korbinian Bachl wrote:
you missed solution3:
the real-wicket-way(tm) for multiple content-places in a tied page-area:
Whaaa, I seriously hope this is not the real-wicket-way! My brain hurts!
A framework is supposed to make things easy and readable! The code below
is just way too complicated to achieve something that should be easy...
Preferably when doing simple stuff like this, I don't want to be
confronted with things like rendering (and adding render hooks), or with
keeping extra state about components being or not being initalized. Also
I don't want to have to copy this boiler plate for every time I want to
place some kind of component "hole" in a base page!
Regards,
Sebastiaan
eg: html:
...
Place to put anything
...
java:
public abstract MyPage extends AnyPageExtendingWicketsWebPage {
private boolean initialized = false;
private final RepeatingView anything;
MyPage() {
super();
anything = new RepeatingView("anything");
add(anything);
}
/**
* Abstract place to add content to the containers
*/
protected abstract void initialize();
@Override
protected void onBeforeRender() {
super.onBeforeRender();
if(!initialized) {
initialize();
initialized = true;
}
}
/**
* Adds the content-Component c to Column A
* (the smaller one on the left)
*
* @return
*/
public void addToAnthing(Component c) {
c.setRenderBodyOnly(true);
getAnything().addOrReplace(c);
}
public RepeatingView getAything() {
return anything;
}
}
and in extending classes you can easily do this:
protected void initialize() {
addToAnything(new AnyPanel("id"));
addToAnything(new AnyPanel2("id2"));
}
etc.
this is maximum flexible, fast implemented, beeing checked by the IDE
and nice OO behaviour as it allows you to chain this over several
levels, plus it aids you when it comes to security-limitations as you
have a logic hirarchy where you can use each step for more restricted
access-rules
e.g: BasePage -> SecureBasePage -> HighlySecuredBasePage -> MyPage
if you then need a panel manipulating other areas this is easily done by:
e.g:
(MyPage getPage()).getAnything().doWhatYouWantToDo(WhatYouWant)
(you could also make this final thing abstract and then only override it
in the page you place it in wich gives even more control and makes it
reusable over projects)
and this is sth. that happens more often than you expect IMHO
plus the biggest advancement: the HTML tied to the classes stays clean
and is not poluted with some fancy tags (wich is the bigest plague in
the Javaworld IMHO... i never understood how they could invent things
like JSP or JSF that are worse to even PHP code in a page)
Best
Korbinian
Stefan Fußenegger schrieb:
Hi Mats, let me try to explain what Chris and I see here that others
don't -
may it be there or not ;)
You can of course do everything with panels that could be done with
multiple
abstract sections (may they be named wicket:child or wicket:abstract).
However, if this is the only argument, you wouldn't need markup
inheritance
at all! The proposed change is just an extension of exactly this markup
inheritance concept (that everybody loves) to make it even more powerful
than it already is.
I was quite new to wicket (which I still am) and came across a situation
where I wanted to use two abstract sections: one for a sub-navigation
that
was common for several pages in a section and one for the actual content.
For me, as a wicket newbie, it would have been most natural to use markup
inheritance to solve this problem. Using abstract methods, while being a
nice solution (workaround?), didn't come to my mind at once, nor did I
find
it somewhere in the docs.
imho, there are two possible solution to this problem:
1. promote using abstract methods for this in the docs as the
wicket-way of
doing it
2. extend the current markup inheritance mechanism (which I tried to
do with
my patch/prototype)
-- stefan
Mats Norén-2 wrote:
On Nov 7, 2007 11:31 AM, Mats Norén <[EMAIL PROTECTED]> wrote:
Hmm...I'm interested in seeing the difference as well. I would love to
get it but right now I don't.
Chris Colman wrote:
"This new feature, or extension of the exiting feature, allows more
than
one section of markup to be "specialized" by derived (extended) markups
whereas currently wicket only supports the deferred
definition/implementation of a single markup section in any page. In
other words we want to make a powerful feature even more powerful."
Is the above statement really true considering that by adding abstract
methods to your page you defer the creation of the markup in just the
same way as the new proposed solution?
BasePage.java
public BasePage() {
addAbstract1("abstractId1");
addAbstract2("abstractId2);
}
public abstract addAbstract1(String abstractId1);
public abstract addAb
Re: Multiple tags on a single base page?
John Krasnay wrote:
You've just illustrated one of the major problems with the
panel-from-a-subclass approach: it's easy to get it wrong. In your
example, addAbstract1 and addAbstract2 will be called in a class whose
constructor has not yet been called. Consider:
public DerivedPage extends BasePage {
private String name;
public DerivedPage(String name) {
super();
this.name = name;
}
public abstract addAbstract1(String abstractId1) {
add(new NamePanel(abstractId1, name));
}
}
This code is broken, since you're constructing NamePanel before name has
been initialized. Someone later in this thread shows a better way to do
this, by calling the overridable methods from onBeforeRender. But this
is also tricky; because onBeforeRender can be called multiple times you
must maintain a flag to ensure you only add your panels once.
In fact, almost all official sources consider this an antipattern (e.g.
Effective Java #15), and specifically state that you should never call
overridable methods from a constructor at all. So either the method
called from the constructor should be private or it should be final.
I wonder what the "official" Wicket policy is on this? Careful
documentation?
Regards,
Sebastiaan
Given these subtle problems with this approach, I admit I'm warming to
the multiple extend/child idea.
jk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Multiple tags on a single base page?
On Wed, Nov 07, 2007 at 11:31:12AM +0100, Mats Norén wrote:
>
> Is the above statement really true considering that by adding abstract
> methods to your page you defer the creation of the markup in just the
> same way as the new proposed solution?
>
> BasePage.java
>
> public BasePage() {
> addAbstract1("abstractId1");
> addAbstract2("abstractId2);
> }
>
> public abstract addAbstract1(String abstractId1);
> public abstract addAbstract2(String abstractId2);
>
>
> BasePage.html
>
>
>
>
> What is the difference between that and doing abstract / implements?
You've just illustrated one of the major problems with the
panel-from-a-subclass approach: it's easy to get it wrong. In your
example, addAbstract1 and addAbstract2 will be called in a class whose
constructor has not yet been called. Consider:
public DerivedPage extends BasePage {
private String name;
public DerivedPage(String name) {
super();
this.name = name;
}
public abstract addAbstract1(String abstractId1) {
add(new NamePanel(abstractId1, name));
}
}
This code is broken, since you're constructing NamePanel before name has
been initialized. Someone later in this thread shows a better way to do
this, by calling the overridable methods from onBeforeRender. But this
is also tricky; because onBeforeRender can be called multiple times you
must maintain a flag to ensure you only add your panels once.
Given these subtle problems with this approach, I admit I'm warming to
the multiple extend/child idea.
jk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help understaning AjaxCallDecorator problem
I remove the decorator and the onClick method does get called (stop in debugger) and the resulting page I end up on is what I expect. The Ajax debug console disappears before I can read what it is saying, and the Javascript console does not report any problems. I will install firebug and see what that can tell me. Thanks!! Timo Rantalaiho wrote: > > Have you checked that onClick() gets called without the > decorator? > > Have you looked at the results on the Javascript console > of Firefox and Javascript debugger of FireBug? > > Have you looked at the wicket Ajax debug window (on > development mode) while clicking? > > I think so, yes, because I think that this is sometimes used > for Javascript confirmation popups. > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oyhttp://www.ri.fi/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Help-understaning-AjaxCallDecorator-problem-tf4760426.html#a13629634 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
