Re: Optional wrapping H1 tag
Thanks for the answers, everyone!
On Sat, Nov 23, 2013 at 5:20 AM, Bas Gooren wrote:
> I'd do it like this:
>
>
> ...
>
>
> add(new WebMarkupContainer("logo-h1") {
> void onConfigure() {
> super.onConfigure();
> setRenderBodyOnly(!getPage().getClass().equals(Homepage.class));
> }
> }.add(new Link...));
>
> In other words: only render the H1 body when not on the homepage.
> setRenderBodyOnly() allows you to control if a tag should be fully
> rendered, or just it's body.
>
> onConfigure() can be overriden to update a components settings whenever it
> is about to be rendered.
>
> Met vriendelijke groet,
> Kind regards,
>
> Bas Gooren
>
> schreef Scott Carpenter op 22-11-2013 19:24:
>
> Suppose you have a web site with a logo in the header which links to the
>> home page. On the home page itself, you have the same logo and the link,
>> but you also want to wrap the logo with an H1 tag.
>>
>> (Or maybe it's not that you have a burning desire to do this, but your
>> client has requested it.)
>>
>> In my Wicket inexperiencedness, I might try this:
>>
>>
>>ABC,
>> Inc.
>>
>>
>>ABC, Inc.
>>
>>
>> And then on the Java side, set one or the other to be invisible.
>>
>> That works, but I'd like to know if there's a better way.
>>
>> Thank you!
>>
>>
>
Optional wrapping H1 tag
Suppose you have a web site with a logo in the header which links to the home page. On the home page itself, you have the same logo and the link, but you also want to wrap the logo with an H1 tag. (Or maybe it's not that you have a burning desire to do this, but your client has requested it.) In my Wicket inexperiencedness, I might try this: ABC, Inc. ABC, Inc. And then on the Java side, set one or the other to be invisible. That works, but I'd like to know if there's a better way. Thank you!
Re: Advice for upgrading from an old version of Wicket
On another angle, suppose you're looking at also upgrading Hibernate and other supporting libraries/frameworks. Would you recommend starting with any particular component? It seems to me that starting with Wicket might be a good idea, since it would hopefully be backwards compatible with other libraries, and have updates to support newer versions of those supporting libraries? Thanks, Scott On Tue, Nov 19, 2013 at 7:19 AM, Scott Carpenter wrote: > Thank you, Martin. I'll do that. > > > On Mon, Nov 18, 2013 at 2:00 AM, Martin Grigorov wrote: > >> Hi, >> >> I'd advice you to read the migration guides 1.4->1.5 and 1.5->6.0. >> Then start migrating the app and ask here if you have specific problems. >> >> >> On Sun, Nov 17, 2013 at 11:33 PM, Scott Carpenter > >wrote: >> >> > Hi -- I've inherited a wicket site that was first developed four years >> ago. >> > It is running on version 1.4 and I've been asked to estimate an upgrade >> to >> > a more current version, and I was hoping to get some advice from this >> list >> > about gotchas and so on. >> > >> > I've been working on the site for several months but consider myself a >> > newcomer to Wicket. That is, I haven't done a deep dive into learning >> the >> > framework yet. I've been updating things based on what I find in the >> > existing code base. So please forgive me my newbieness and let me know >> what >> > details would be helpful. >> > >> > Furthermore, I'm a newcomer to Java web frameworks in general. There is >> > Spring and Hibernate involved with this thing, which I've also been >> able to >> > update based on the existing state of affairs. The backend is an Oracle >> > database. >> > >> > Your thoughts and advice would be greatly appreciated. >> > >> > Thank you! >> > >> > Scott >> > >> > >
Re: Wicket Sessions and Akamai Caching
Thanks, guys. I'll take a look! On Wed, Nov 20, 2013 at 2:13 AM, Martin Funk wrote: > Hi, > > the explanation in wicket guide might give further insight: > http://wicket.apache.org/guide/guide/chapter11.html#chapter11_9 > > mf > > > Am 20.11.2013 um 06:04 schrieb Jeremy Thomerson >: > > > Pages that are session-specific should not be cached in a way that allows > > the cached response to be given to multiple users. Stateful forms are > > session-specific. > > > > > > On Tue, Nov 19, 2013 at 6:59 PM, Scott Carpenter >wrote: > > > >> I have a client Wicket web site and they are using Akamai for caching. > They > >> wanted to cache more aggressively but it seems there's an issue with > >> expired sessions. When a user hits a cached version of a page with a > form > >> and tries to submit it, a 500 error is raised. (I'm relaying this from > at > >> least two sources removed, so by now I might have the details thoroughly > >> obfuscated.) > >> > >> I was hoping from this list I could get some pointers on best taking > >> advantage of Akamai, and how I might work around issues like this. > Please > >> let me know if and what further information would be useful in > answering. > >> > >> Thank you! > >> > >> Scott > >> > > > > > > > > -- > > Jeremy Thomerson > > http://wickettraining.com > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Wicket Sessions and Akamai Caching
I have a client Wicket web site and they are using Akamai for caching. They wanted to cache more aggressively but it seems there's an issue with expired sessions. When a user hits a cached version of a page with a form and tries to submit it, a 500 error is raised. (I'm relaying this from at least two sources removed, so by now I might have the details thoroughly obfuscated.) I was hoping from this list I could get some pointers on best taking advantage of Akamai, and how I might work around issues like this. Please let me know if and what further information would be useful in answering. Thank you! Scott
Re: Advice for upgrading from an old version of Wicket
Thank you, Martin. I'll do that. On Mon, Nov 18, 2013 at 2:00 AM, Martin Grigorov wrote: > Hi, > > I'd advice you to read the migration guides 1.4->1.5 and 1.5->6.0. > Then start migrating the app and ask here if you have specific problems. > > > On Sun, Nov 17, 2013 at 11:33 PM, Scott Carpenter >wrote: > > > Hi -- I've inherited a wicket site that was first developed four years > ago. > > It is running on version 1.4 and I've been asked to estimate an upgrade > to > > a more current version, and I was hoping to get some advice from this > list > > about gotchas and so on. > > > > I've been working on the site for several months but consider myself a > > newcomer to Wicket. That is, I haven't done a deep dive into learning the > > framework yet. I've been updating things based on what I find in the > > existing code base. So please forgive me my newbieness and let me know > what > > details would be helpful. > > > > Furthermore, I'm a newcomer to Java web frameworks in general. There is > > Spring and Hibernate involved with this thing, which I've also been able > to > > update based on the existing state of affairs. The backend is an Oracle > > database. > > > > Your thoughts and advice would be greatly appreciated. > > > > Thank you! > > > > Scott > > >
Advice for upgrading from an old version of Wicket
Hi -- I've inherited a wicket site that was first developed four years ago. It is running on version 1.4 and I've been asked to estimate an upgrade to a more current version, and I was hoping to get some advice from this list about gotchas and so on. I've been working on the site for several months but consider myself a newcomer to Wicket. That is, I haven't done a deep dive into learning the framework yet. I've been updating things based on what I find in the existing code base. So please forgive me my newbieness and let me know what details would be helpful. Furthermore, I'm a newcomer to Java web frameworks in general. There is Spring and Hibernate involved with this thing, which I've also been able to update based on the existing state of affairs. The backend is an Oracle database. Your thoughts and advice would be greatly appreciated. Thank you! Scott
