RE: Wicket and jQuery UI

[Hielke Hoeve]

Dear all,

Wiquery offers a wide range of Behaviors in order to make components Draggable. 
There are a few Components which demand a certain type of tag to be used. 
We have experienced that the more flexible you make your API the more dumb 
questions people ask and the less they use it. Apparently they expect a magic 
library which can be included and read peoples minds :) 

Posts like are imo very constructive and do keep us sharp. Thanks for that.

Hielke

From: Sebastien [seb...@gmail.com]
Sent: 02 October 2012 19:28
To: users@wicket.apache.org
Subject: Re: Wicket and jQuery UI

Hi,

I will provide an answer for wicket-jquery-ui and let people/users from
wiQuery answer about this last.

wicket-jquery-ui has several goals: the first one is to provide the jQuery
UI widget library as Wicket components, for both wicket 1.5.x and wicket
6.x. The work has mainly been focused to provide Wicket jQuery UI
components having (I hope) the same philosophy/logic as Wicket's built-in
ones, so the user deals with these components the same manner he usually
deals with the Wicket ones. This is the most important point IMO. In
addition, it provides - as Sebastien said - pure Behavior to allow users to
use it either directly or embed it in other components. The advantage of
using a Component versus a Behavior is that the Component can offers some
events handling (ajax, naturally). To answer Pointbreak, a Draggable - for
instance - is a Component for this specific reason, to be able to broadcast
events (using latest Wicket event mechanism) either to itself (most common
case for components) or to a Droppable object. It would have been really
much difficult to understand the event logic if only a Behavior would have
been supplied. For the Accordion, I did not provide the associated Behavior
because it straightforward to add it (as many others, but it is probably
not clear enough): add(new JQueryBehavior("#myId", "accordion")); I am
currently working on the accordion this week to provides its specific
Behavior and event handling...

The second goal is that the 'core' is also designed to integrate other
plugins, from simple Behaviors to complex Components. For instance, the
project provides an integration of the Calendar (from FullCalendar jQuery
plugin) and an integration of several components of the Kendo-UI widget
library. In the future, I think it will also provide an integration of a
really good charting library (but it's a secret! ;). I began to write the
tutorial series on how-to implement plugins but it is unfortunately not yet
finished.

wicket-jquery-ui is fairly new - the first version has been released about
6 months ago and has already been downloaded several hundred of time (I do
not have latest maven stats), the demo site recorded more than 2 000 visits
these last 30 days (11 700 page views). No just to give you some numbers,
just to say that it seems to be really in use; I use it myself - and my
colleges - at work on some big projects. And the number of opened issues
(very low) tends me to say that the API seems to be stable/reliable. (or
nobody use it in fact ;))

I do not have a lot a feedback about who - and how - the API is used.
However, I hope these few lines will help you to answer a part of your
question.

Best regards,
Sebastien.

On Tue, Oct 2, 2012 at 6:44 PM, Pointbreak
wrote:

> But why not for tabs, accordion, slider, and other jquery components?
> That gives you much more flexibility in separating what a component
> logically does (e.g. render various sections of data, widgets, etc.),
> from how it is shown and interacted with in the browser (view as tabs,
> steps in a widget, accordion, just plain sections, ...). In jquery-ui
> itself you also add it as a behavior to a DOM element. So why not offer
> that flexibility in the Wicket integration? Idem ditto for things like
> draggable, droppable, etc. Why not offer the possibility to make any
> existing wicket panel/component a draggable by having a
> DraggableBehavior? In wicket-jquery-ui you need to subclass a Draggable
> panel, which is obviously not possible with already existing
> components/panels.
>
> Just to clarify: this is my very personal opinion on how a jquery
> integration should be designed (and actually how I've done it for many
> projects so far). That's obviously very subjective. It looks like an
> impressive library nonetheless!
>
> On Tue, Oct 2, 2012, at 15:30, Sébastien Gautrin wrote:
> > Hi Pointbreak,
> >
> > At least for wicket-jquery-ui, it offers also pure behaviours
> > integration for jquery extensions that are pure behaviours (such as
> > Droppable). I think wiQuery does as well. For ease of defining such
> > things for you own component, it is the main goal of wicket-jquery-ui;
> > take a look at the three tutorials Sebastien made (sebfz1) for
> > wicket-jquery-ui:
> > http://code.google.com/p/wicket-jquery-ui/w/list?q=label:How-To (note:
> > Sebastien is the author of wicket-j

RE: DatePicker is not appear properly

[Hielke Hoeve]

Ernesto,

Per WiQuery 6.0.0 IWiQueryPlugin is deprecated. Users have to add the resources 
to the component themselves.



From: Ernesto Reinaldo Barreiro [reier...@gmail.com]
Sent: 18 September 2012 08:47
To: users@wicket.apache.org
Subject: Re: DatePicker is not appear properly

Hi,

If you mark a component on the page with interface  IWiQueryPlugin the
wiquery will add jquery to you page (whether you use the date picker  or
not) that way you will not have to add jquery manually.

On Tue, Sep 18, 2012 at 8:29 AM, Madasamy Sankarapandian <
madas...@mcruncher.com> wrote:

> Right now I'm migrating a application from wicket -1.4.x. to 1.5.8.
>
> We use wiQuery 1.5.7 (which depends on jQuery 1.6.4) in our project mainly
> for the date picker component.
> We also use jQuery 1.7.1 directly. The jQuery resource reference shall be
> added in the "renderHead" method of our base page.
>
> This use to work fine in wicket-1.4.x (of course with the older wiQuery
> version)
>
> But wiQuery components (date picker) are not displayed after migrating to
> wicket 1.5.8.
> Please note that when a wiQuery component is used in a page, it shall add
> it's bundled jQuery reference to head.
> May be there's a conflict between the jQuery versions, which I'm not sure.
>
> I also noted that in such cases, wiQuery's jQuery reference takes
> precedence rather than the one in my base page.
> May be the order in which the header contributions are added is causing the
> problem?
>
> When I don't add jQuery-1.7.1 in my base page, wiQuery components are
> displayed properly.
> But we do need jQuery reference to be added irrespective of whether the
> page uses wiQuery components or not as we use some of the jQuery functions
> in our pages.
>
> Instructing wiQuery not to add jQuery reference doesn't help either.
>



--
Regards - Ernesto Reinaldo Barreiro
Antilia Soft
http://antiliasoft.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

WiQuery 6.0.0 has been released!

[Hielke Hoeve]

We from WiQuery are happy to announce the release of WiQuery 6.0.0!

Unlike WiQuery 1.5 this release has become smaller. All of the resource 
management present in WiQuery 1.5 has been removed because Wickets resource 
management has been totally revamped and works nearly the same. This 
considerably decreases the footprint of WiQuery. Not only in LOC but also in 
performance. This allows us to start focusing completely on providing users 
with a JQuery statement API and JQuery UI components.

For backward compatibility purposes some of the 1.5 API has been marked 
deprecated instead of removing it completely. For example: all Behaviors in 
WiQuery will check if the statement() function is still used and if so use the 
new approach to render.

Our artifacts can be found at maven central. See listing here: 
http://mvnrepository.com/artifact/org.odlabs.wiquery/

Happy querying!

Hielke Hoeve
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: wicket-dnd strange situation

[Hielke Hoeve]

Hi Decebal,

Sorry for the late response but I was on holiday.

The 2 code snippets below do exactly the same. They look different but they 
both perform "new wicketdnd.DropTarget(...)" when the dom is loaded and ready. 
Can you provide a better/bigger example?

I checked your other posts and saw a link to a bug report. In this you say you 
use WiQuery for the modalwindows but WiQuery has no support for them as Wicket 
already provides this.

Regards,
Hielke

-Original Message-
From: Decebal Suiu [mailto:decebal.s...@asf.ro] 
Sent: donderdag 2 augustus 2012 12:18
To: users@wicket.apache.org
Subject: Re: wicket-dnd strange situation

Another technical question is who (I suppose wiquery) and why change

Wicket.Event.add(window, "domready", function(event) { new
wicketdnd.DropTarget(...) });


in 

$(document).ready(function(event){new wicketdnd.DropTarget(...)});


Best regards,
Decebal



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/wicket-dnd-strange-situation-tp4650918p4650951.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Status of wicketstuff jquery integration

[Hielke Hoeve]

WiQuery does depend on a small amount of libraries, we are working on 
minimizing this for Wicket 6.

Have fun.

Hielke

-Original Message-
From: Jesse Long [mailto:j...@unknown.za.net] 
Sent: woensdag 9 mei 2012 16:00
To: users@wicket.apache.org
Subject: Re: Status of wicketstuff jquery integration

Hi Hielke,

It seems I was using an outdated version of WiQuery (1.2.3), but even then, I 
cant reproduce the extra 10M.

It may be that I had the dependencies for WiQuery and something else added to 
the war at the same time, my apologies.

wiquery-core 1.5.5 (and dependencies) adds just over 2MB new quickstart. 
(Probably worth it).

Cheers,
Jesse

On 09/05/2012 10:38, Hielke Hoeve wrote:
> Hi Jesse,
>
> Your 10mb of WiQuery puzzles me. The wiquery-core jar is 256 KB and the 
> wiquery-jquery-ui jar is 857KB. I wonder which jars you include in your war. 
> If you do not use jQuery UI then there is no need for wiquery-jquery-ui.
>
> Hielke
>
> -Original Message-
> From: Jesse Long [mailto:j...@unknown.za.net]
> Sent: woensdag 2 mei 2012 10:48
> To: users@wicket.apache.org
> Subject: Status of wicketstuff jquery integration
>
> Hi All,
>
> I'm interested in using features of the jquery integration in wicketstuff, 
> but it seems it is not being maintained. The version of jquery packaged with 
> the wicketstuff-jquery jar seems to be 1.3.2, which is quite old already. Am 
> I missing something? Is there a preferred way of integrating jquery into 
> wicket?
>
> (WiQuery adds 10Mb to my war. JQWicket looks good, but why choose it over 
> wicketstuff-jquery)?
>
> I also note that the wicketstuff-jquery project does not make use of the 
> wicketstuff-jslibraries project. Why not? Is wicketstuff-jslibraries the 
> officially recommended way of including js libraries, or should I look 
> elsewhere? wicketstuff-jquery method of detecting jquery.js presence seems 
> like a hack.
>
> Thanks,
> Jesse
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Status of wicketstuff jquery integration

[Hielke Hoeve]

Hi Jesse,

Your 10mb of WiQuery puzzles me. The wiquery-core jar is 256 KB and the 
wiquery-jquery-ui jar is 857KB. I wonder which jars you include in your war. If 
you do not use jQuery UI then there is no need for wiquery-jquery-ui.

Hielke 

-Original Message-
From: Jesse Long [mailto:j...@unknown.za.net] 
Sent: woensdag 2 mei 2012 10:48
To: users@wicket.apache.org
Subject: Status of wicketstuff jquery integration

Hi All,

I'm interested in using features of the jquery integration in wicketstuff, but 
it seems it is not being maintained. The version of jquery packaged with the 
wicketstuff-jquery jar seems to be 1.3.2, which is quite old already. Am I 
missing something? Is there a preferred way of integrating jquery into wicket?

(WiQuery adds 10Mb to my war. JQWicket looks good, but why choose it over 
wicketstuff-jquery)?

I also note that the wicketstuff-jquery project does not make use of the 
wicketstuff-jslibraries project. Why not? Is wicketstuff-jslibraries the 
officially recommended way of including js libraries, or should I look 
elsewhere? wicketstuff-jquery method of detecting jquery.js presence seems like 
a hack.

Thanks,
Jesse

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: wicket 6.0

[Hielke Hoeve]

Hi Tom,

We now have a working WiQuery 6. I will release a new snapshot tonight, but you 
can clone it from github already.

Hielke

-Original Message-
From: Tom Eugelink [mailto:t...@tbee.org] 
Sent: vrijdag 13 april 2012 14:44
To: users@wicket.apache.org
Subject: Re: wicket 6.0


On 2012-04-13 14:24, Martin Grigorov wrote:
>
> How many of you tried beta1 ?
>

I started off with 6, but was afraid things like wiquery would conflict in the 
usage of jquery, so I returned to safety using 1.5.5. Should that be a problem? 
Otherwise I'll upgrade back to 6.

Tom



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wicket authentication: how to store user?

[Hielke Hoeve]

Dan,

JSESSIONIDs are not inherently secure. Users can be so dumb as to copy/paste an 
url with an JSESSIONID as query parameter and send it to someone else via 
email/msn/etc. When that other person clicks the url, while the first person is 
logged in, he is logged in as well. Webapplications should always invalidate 
the wicket session before authenticating. (use Session.get().replaceSession() )

See also: http://www.owasp.org/index.php/Session_Fixation

Hielke

-Original Message-
From: Dan Retzlaff [mailto:dretzl...@gmail.com] 
Sent: maandag 5 maart 2012 3:53
To: users@wicket.apache.org
Subject: Re: Wicket authentication: how to store user?

Paolo, sessions are accessed with a JSESSIONID cookie or query parameter 
supplied with each request. It's not possible for one user to guess another 
user's session ID, so the approach Martin describes is inherently secure.
(Just be careful with your authentication code and form/query parameter 
validation elsewhere in your app!)

Dan

On Sat, Mar 3, 2012 at 4:40 AM, Paolo  wrote:

> Alle sabato 03 marzo 2012, Martin Grigorov ha scritto:
> > Hi,
> >
> > Save the logged in user id in the Session.
> >
> > MySession.java:
> >
> > private long userId;
> >
> > public User getUser() {
> >   return userService.getUserById(userId); }
> >
> >
> > AnyPage.java:
> > user = MySession.get().getUser();
> >
> Thank you, for support and explanation code, very useful because I am a
> newbie.
> Just one another answer: Is it secure?
> Can someone alter session data and change user data, so an hacher could
> log with own account but operate with other accounts?
> Do I need some random code like this "hdfds6yh6yhgtruifh4hf4frh9ruehfe" to
> store temporanealy in session and database and associate it to a specific
> user?
>
> > > I added registration and user/password sign-in and checking with
> database, instead of simple "wicket" as user and password.
> > > All works ok, but now I need in AdminPage to known which user is
> logged in.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: wiQuery and ivy

[Hielke Hoeve]

If you can specify what I need to add in the pom.xml of WiQuery then I am happy 
to add it, however this Ivy is unknown to me so I have no idea what to do.

Sources themselves are not a viable dependency for any java project using using 
dependency management or not, they are merely fetched so that an IDE can link 
the sources to the binaries so that the user can browse them or use them wihile 
debugging. Adding the sources as a required dependency seems odd to me... Maven 
knows what to do thanks to a plugin, perhaps this also available for Ivy?

Hielke

-Original Message-
From: Dirk Forchel [mailto:dirk.forc...@exedio.com] 
Sent: maandag 5 maart 2012 13:55
To: users@wicket.apache.org
Subject: wiQuery and ivy

I've a qestion regarding ivy and wiQuery. 
I'd like to use the wiQuery jars (wiquery-core and wiquery-jquery-ui) in the 
same way I do with all the Wicket libraries. For example, a configuration 
dependency for the Wicket core library in my project ivy.xml is written
like:



This means, ivy is looking for the wicket-core jar in the defined repositories 
and downloads the sources jar as well. 
In order to download the wiQuery libs, I've added a URL resolver within my 
global ivysettings.xml:



And in my ivy.xml I've added the following lines of code:



This works fine. But I can't download the sources jar, although the sources jar 
can be found on the wiquery respository
(https://wiquery.googlecode.com/svn/repo/org/odlabs/wiquery/wiquery-core/1.5.4/)
too. What I miss is the dependency configuration for sources in the pom.xml. 
Can this be added from one of the projects member? Or exists another way to 
download the sources jar with ivy?
Thank you.


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/wiQuery-and-ivy-tp4446057p4446057.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: wiquery css

[Hielke Hoeve]

Strange that the system cannot find it while it can in production. Are you sure 
the package is present on production, you did not forget a library?

Hielke

-Original Message-
From: N. Metzger [mailto:nmetz...@odu.edu] 
Sent: vrijdag 2 maart 2012 3:03
To: users@wicket.apache.org
Subject: RE: wiquery css

Me again, I figured it all out and it work beautifully ... when deployed in 
weblogic.

For my production environment I unfortunately have to use oc4j, and somehow I'm 
unable to load the resource in this environment:
2012-03-01 20:51:03,471 WARN  (PackageResource.java:594) - Unable to find 
package resource [path = 
org/odlabs/wiquery/ui/themes/mytheme/jquery-ui-1.8.18.custom.min.css, style = 
null, locale = null]

Maybe this is not the right forum, but perhaps someone has an idea.

Thanks!

Natalie

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/wiquery-css-tp4407116p4437198.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: WiQuery 1.5.4 and Wicket 1.5.4 Problem

[Hielke Hoeve]

Hi,

Sounds like you updated wiquery-core but not wiquery-jquery-ui. If you open 
IWiQueryInitializer in eclipse and open a type hierarchy you can see if 
WiQueryUIInitializer is a subclass or not. If not then you probably have a 
version difference somewhere.

Hielke

-Original Message-
From: rawe [mailto:ralph.wey...@dachser.com] 
Sent: donderdag 23 februari 2012 11:33
To: users@wicket.apache.org
Subject: WiQuery 1.5.4 and Wicket 1.5.4 Problem

Hi,

I changed my WiQuery version from 1.5M2 to 1.5.4 I'm running Wicket 1.5.4. I 
had no problem running my application with tomcat when using Wiquery 1.5M2.
Now after I changed to Wiquery 1.5.4 my tomcat (5.0) fails starting with 
following error:

java.lang.ClassCastException:
org.odlabs.wiquery.ui.listener.WiQueryUIInitializer
at
org.odlabs.wiquery.core.WiQueryInitializer.addInitializer(WiQueryInitializer.java:158)
at
org.odlabs.wiquery.core.WiQueryInitializer.load(WiQueryInitializer.java:146)
at
org.odlabs.wiquery.core.WiQueryInitializer.retrieveAndCallInitializers(WiQueryInitializer.java:121)
at
org.odlabs.wiquery.core.WiQueryInitializer.init(WiQueryInitializer.java:73)
at org.apache.wicket.Application.callInitializers(Application.java:605)


Does somebody now what's the problem?

Thanks in advance

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WiQuery-1-5-4-and-Wicket-1-5-4-Problem-tp4413486p4413486.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: wiquery css

[Hielke Hoeve]

To roll your own theme use www.themeroller.com and when done choose download. 
You can then use the contents of the zipfile to create your own 
resourcereference to use in IThemableApplication.

Hielke

-Original Message-
From: Ernesto Reinaldo Barreiro [mailto:reier...@gmail.com] 
Sent: woensdag 22 februari 2012 9:36
To: users@wicket.apache.org
Subject: Re: wiquery css

Natalie,

On Tue, Feb 21, 2012 at 3:10 PM, N. Metzger  wrote:

> Hi all,
>
> I'm having another of my blind mornings.
> I just tried wiquery for the first time and had an accordion running 
> within a few minutes, so first of all: thanks!!!
> Now: what's the best way to change the look and feel? I saw a that you 
> can define a jquery theme and upload if somehow. How?


You can roll your own theme(s) making your web application implement 
IThemableApplication...



> Or should I just define
> the css for my page? If the latter, what should I use as my base?
>

if changes are minor you can always override default theme rolling you own CSS.

Ernesto

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wicket in a Dot Net World

[Hielke Hoeve]

I have spend about 100 hours in creating a Wicket 1.3 port. Because half of 
Wicket consists of anonymous classes it is near impossible. I had to add about 
1000 new subclasses to get the core to work. When it compiled and actually 
wanted to start and bind to a port I was unable to get the pages to render. 
Because these 2 languages are so completely different it is not easy and it 
will mean that Wicket apps will be completely different to Wicket.NET apps.

Major problems I encountered:
property files not supported
threading impl works differently
anonymous classes not supported
loading of html files and getting them to inherit was really odd, maybe it was 
just me...

biggest frustration: finding compatible dependencies... There is a proper maven 
like system for .NET now but back then they all sucked.

Hielke

-Original Message-
From: shetc [mailto:sh...@bellsouth.net] 
Sent: dinsdag 7 februari 2012 20:57
To: users@wicket.apache.org
Subject: Wicket in a Dot Net World

Well friends, it's happened -- the company I work for has been bought by a 
larger competitor. Sadly, the new bosses prefer to work with .NET 

I don't suppose anyone has ported Wicket to .NET? 

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-in-a-Dot-Net-World-tp4366058p4366058.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wiquery and JQWicket crash each other!!!!

[Hielke Hoeve]

Better late than never:

To respond to your question again: why would you want to use both? They seem to 
do the same thing...

Hielke

-Original Message-
From: atomix [mailto:say_i_love_you_4e...@yahoo.com] 
Sent: donderdag 26 januari 2012 21:14
To: users@wicket.apache.org
Subject: Re: Wiquery and JQWicket crash each other

I got answer from Wiquey developer :

"Hi!

JQWicket and WiQuery do not work well together. Both aim to do the same but 
using a different approach. Choose either one, not both. 

When you add WiQuery to the classpath it installs itself using a Wicket 
Initializer and sets a HeaderResponseDecorator. The HeaderResponseDecorator 
manages all resource references when they are of a certain type and manages the 
jQuery initializing statements."

Now , my question is : Did anyone have a solution for Wiquery and JQWicket work 
together, it's really a pity that we can't use them both!

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wiquery-and-JQWicket-crash-each-other-tp4330840p4331638.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: jQuery Mobile styling disappears after Wicket ajax update

[Hielke Hoeve]

Correct. You need to use modifiers or appenders on your components if you 
manually apply the style or call any jquery functions to make sure that jquery 
reapplies the styles. The html gets replaced and with that any jquery additions 
generated on the client. You can use the renderHead(IHeaderResponse) function 
of any component to render resources and domready events for that component

Hielke
 
-Original Message-
From: Bodis, Jerome [mailto:bo...@uni-mainz.de] 
Sent: donderdag 26 januari 2012 9:03
To: 'users@wicket.apache.org'
Subject: RE: jQuery Mobile styling disappears after Wicket ajax update

Correct me if i'm wrong, but with normal jquery event handlers get lost if an 
element has changed. That's why you have to reattach them with on()/live(). 
Maybe this is the case? If it's only the css class you could try to add them 
with AttributeAppender/Modifier.


> -Original Message-
> From: wicket_newb [mailto:jceb...@hestonsystems.com]
> Sent: Wednesday, January 25, 2012 11:34 PM
> To: users@wicket.apache.org
> Subject: jQuery Mobile styling disappears after Wicket ajax update
> 
> I'm trying to implement a list that updates itself after a user clicks on a 
> link.
> The list is a ListView repeater and is a child of WebMarkupContainer.
> For each ListView item, I've attached an AjaxFallbackLink with the 
> WebMarkupContainer object as the sole ajax target.
> 
> My implementation mostly works except some jQuery Mobile styling in 
> the container disappear.  Looking at Firebug, I noticed that jQuery 
> Mobile's dynamically-generated class attributes are gone.
> 
> As an example, my repeating divs before Wicket ajax update looks like this:
> 
>   
>   etc...
>
> 
> After the ajax update:
> 
>   
>   etc...
>   
> 
> 
> Is there a way to tell Wicket to keep jQuery Mobile styling after an 
> ajax update?
> 
> --
> View this message in context: http://apache-
> wicket.1842946.n4.nabble.com/jQuery-Mobile-styling-disappears-after-
> Wicket-ajax-update-tp4328874p4328874.html
> Sent from the Users forum mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: WiQuery & disabling tabs

[Hielke Hoeve]

Yes I (and perhaps we) care. Unfortunately Google has decided that the WiQuery 
google group should die, leaving us with no mailinglist... Fortunately most of 
the WiQuery committers are also on this mailinglist.
Any suggestions you have will be taken into account during our ever lasting 
upgrade efforts for WiQuery.

Simply calling tab.disable(i); will not work as this function returns a jQuery 
statement. If you do not use that nothing changes :S You should use 
Tabs#setDisabled(ArrayItemOptions disabled). This will 
disable all tabs that you specify upon first render. If you want to disable any 
tab after first render you should use an ajax call and call 
Tabs#disable(AjaxRequestTarget, int).

If there is a bug in WiQuery then please report it here: 
http://code.google.com/p/wiquery/issues/entry

Hielke Hoeve

-Original Message-
From: Marco Springer [mailto:marcosprin...@gmail.com] 
Sent: dinsdag 17 januari 2012 9:16
To: users@wicket.apache.org
Subject: Re: WiQuery & disabling tabs

If anyone cares, I found "a" solution...

I'm guessing the previous solution isn't working because the statement is 
probably output before the page is actually rendered.
Therefore i did the following:

tabs.add(new AbstractBehavior() {
  @Override
  public void renderHead(IHeaderResponse response) {
super.renderHead(response);
StringBuilder js = new StringBuilder();
if (isNewObject) {
  for (int i = 1; i < 6; i++) {
js.append(tabs.disable(i).getStatement()).append(";");
  }
}
response.renderOnDomReadyJavascript(js.toString());
  }
});

If anyone thinks this is faulty or has a better solution, I'd like to know!

Kind regards,
Marco

On 16 January 2012 17:20, Marco Springer  wrote:

> Hi all,
>
> *The problem: *
> tabs not disabled on first render.
>
> *The source:*
> I'm adding the "Tabs" class from WiQuery 1.2.4 like so:
>
> tabs = new Tabs("tabs");
> tabs.setOutputMarkupId(true);
>
> CompoundPropertyModel waferModel = new 
> CompoundPropertyModel(getDefaultModel());
> tabs.add(new GeneralInfoPanel("general_info", waferModel)); 
> tabs.add(new MaterialSpecificationPanel("material_spec", waferModel)); 
> tabs.add(new LazyTabPanel("layers", waferModel, 
> LayersFragment.class)); tabs.add(new LazyTabPanel("batches", 
> waferModel, BatchFragment.class)); tabs.add(new 
> LazyTabPanel("logbook", waferModel, LogbookFragment.class)); 
> tabs.add(new DocumentsPanel("documents", waferModel));
>
> *// isNewObject set to true when the Wafer object contained in the 
> waferModel is a new Wafer.
> // When a new Wafer is show in this panel, disable the rest of the 
> tabs for now:* if (isNewObject) {  for (int i = 1; i < 6; i++)  
> tabs.disable(i); }
>
> add(tabs);
>
>
> *The question:*
> I thought this would be a proper way to disable those tabs, apparently 
> it isn't.
> If I call the disable function through ajax afterwards, like 
> "disable(target, 1)", it's fine.
>
> Anyone an idea how you would disable a single (or multiple) tabs on 
> the first initial render?
>
> Kind regards,
> Marco

RE: Wicket on Google App Engine

[Hielke Hoeve]

Hey Daniel,

Glad to hear you got it working as well. I have some apps on google app engine  
as well. Tried all the tutorials and 'useful' maven plugins but all just didn't 
do the trick for me.  I now use maven's resources plugin to copy the resources 
from the maven repository to the war/lib folder. Which allows me to update/add 
dependencies in the pom.xml, run maven and add the dependencies in eclipse 
manually. 

I have not found a maven plugin which just adds the google sdk as dependency 
for me so I don't have to mess around in eclipse everytime I run maven. Did you 
solve that?

Hielke 

-Original Message-
From: Daniel Watrous [mailto:daniel.watr...@gmail.com] 
Sent: donderdag 5 januari 2012 19:35
To: users@wicket.apache.org
Subject: Re: Wicket on Google App Engine

Thanks for all your help. I've just posted the steps required to get current 
versions of wicket and gae to work together.

http://software.danielwatrous.com/software-engineering/wordpress-plugin-licensing-wicket-on-google-app-engine

Daniel

On Thu, Jan 5, 2012 at 12:46 AM, Ernesto Reinaldo Barreiro 
 wrote:
> I think the class to use is
>
> http://code.google.com/p/kickat26/source/browse/trunk/src/de/kickat26/
> ui/wicket/GAEModificationWatcher.java
>
>
>
> On Thu, Jan 5, 2012 at 8:31 AM, Ernesto Reinaldo Barreiro < 
> ernesto.reina...@jweekend.com> wrote:
>
>> You could use a modified version of resource watcher that does not 
>> use threads and modify request cycle so that watcher is executed 
>> before each request cycle. I remember there was some blog somewhere 
>> explaining this technique... Maybe it was this...
>>
>>
>> http://stronglytypedblog.blogspot.com/2009/07/wicket-spring-jdo-on-go
>> ogle-app-engine.html
>>
>>
>>
>> On Wed, Jan 4, 2012 at 11:18 PM, Daniel Watrous 
>> wrote:
>>
>>> I tried putting in this:
>>> getResourceSettings().setResourcePollFrequency(Duration.ONE_SECOND);
>>>
>>> But the resource still doesn't update without restarting the google 
>>> app engine environment. I just tried it by running Start and that no 
>>> longer updates automatically either.
>>>
>>> In the process of trying to make it work with GAE, I changed the 
>>> pom.xml to have these lines in the build section
>>>            src/main/webapp/WEB-INF
>>>
>>>  src/main/webapp/WEB-INF/classes
>>>
>>> That means files are no longer placed in the target directory, but 
>>> in the WEB-INF folder. Could this affect it? Have I missed another 
>>> setting somewhere that relates to changing where the compiled 
>>> classes are placed?
>>>
>>> Daniel
>>>
>>> On Wed, Jan 4, 2012 at 3:01 PM, Sven Meier  wrote:
>>> > Read here:
>>> >
>>> >    https://cwiki.apache.org/WICKET/faqs.html#FAQs-Deployment
>>> >
>>> > The relevant setting is:
>>> >    getResourceSettings().setResourcePollFrequency(duration);
>>> >
>>> > Sven
>>> >
>>> >
>>> > On 01/04/2012 10:31 PM, Daniel Watrous wrote:
>>> >>
>>> >> Great. I now have it working with either the jar download or the 
>>> >> dependency in the pom.xml file. In the dependency xml snippet I 
>>> >> didn't realize that I needed to manually provide the version, but 
>>> >> after I did then it worked fine.
>>> >>
>>> >> Whenever I update a class and save it in Eclipse, that class is 
>>> >> updated in the running server and I don't have to restart to see 
>>> >> the changes. This is great.
>>> >>
>>> >> However, when I change an HTML page, it's not updated in the 
>>> >> running server, so I have to restart everything. I know that when 
>>> >> I run a quickstart app directly (using the Start class) that 
>>> >> updates to the HTML are updated without requiring a restart.
>>> >>
>>> >> Do you know how to make it so the HTML files are updated in the 
>>> >> live server?
>>> >>
>>> >> Thanks so much.
>>> >>
>>> >> Daniel
>>> >>
>>> >> On Wed, Jan 4, 2012 at 1:38 PM, Sven Meier  wrote:
>>> >>>
>>> >>> With maven it's very easy, just add the dependency to your pom 
>>> >>> as suggested and forget about it.
>>> >>>
>>> >>> Alternatively you can download the jar form maven central 
>>> >>> manually and add it to your project:
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> http://repo2.maven.org/maven2/org/wicketstuff/wicketstuff-gae-initia
>>> lizer/
>>> >>>
>>> >>> Hope this helps
>>> >>> Sven
>>> >>>
>>> >>>
>>> >>> On 01/04/2012 09:28 PM, Daniel Watrous wrote:
>>> 
>>>  I'm still not sure how to create the jar file. No one is 
>>>  commenting
>>> on
>>>  it so I feel a bit silly. Should it be obvious?
>>> 
>>>  Am I supposed to include the source with my project or a jar. 
>>>  If a jar, how should I build the jar?
>>> 
>>>  On Wed, Jan 4, 2012 at 1:11 PM, Sven Meier
>>>  wrote:
>>> >
>>> > Hi,
>>> >
>>> > make sure you have compatible versions for Wicket and
>>> gae-initializer,
>>> > i.e.
>>> > they should be the same.
>>> >
>>> > Sven
>>> >
>>> >
>>> >
>>> > On 01/04/2012 08:49 PM, Daniel Watrous wrote:
>>> >>
>>> >> I'm slowly makin

RE: Problem with wicket 1.5.3 and wiquery 1.5.3

[Hielke Hoeve]

Found it :) A silly bug... I squashed it and committed a fix and released a new 
snapshot version. Can you guys verify it is working now?

wiquery-core
1.5-SNAPSHOT

Hielke

-Original Message-
From: Hielke Hoeve [mailto:hielke.ho...@topicus.nl] 
Sent: woensdag 21 december 2011 8:06
To: users@wicket.apache.org
Subject: RE: Problem with wicket 1.5.3 and wiquery 1.5.3

Thats something that i would like to know once you stumble upon it. Adding 
dummy behaviors to fix things should not be necessary. I will try and fix the 
problem.

Hielke

-Original Message-
From: Chris Hawkins [mailto:ch...@chawkins.com]
Sent: dinsdag 20 december 2011 19:12
To: users@wicket.apache.org
Subject: Re: Problem with wicket 1.5.3 and wiquery 1.5.3

This sounds very similar to a problem that I had with WiQuery.  I found that if 
a page did not have any WiQuery components or behaviors on it I got errors with 
the Wicket ajax javascript due to the WiQueryDecoratingResponseHeader.  My 
solution was to force WiQuery to load jQuery by adding an empty WiQuery 
behavior to my base page.

/**
* This patch is intended to load jquery on every page because the 
WiQueryDecoratingHeaderResponse
* is rewriting every JS call regardless of if there is WiQuery code on the page
* @author chrish
*
*/
public class WiQueryJsPatch extends WiQueryAbstractBehavior {

private static final long serialVersionUID = 1L;

@Override
public JsStatement statement() {
return null;
}

}

On Dec 20, 2011, at 9:05 AM, dennisB wrote:

> hi Hielke
> 
> thanks for the fast reply.
> 
> I create a simple example to demonstrate my problem:
> 
> this is the scenario:
> 
> In my application i have wicket 1.5.3 and i am using AjaxLazyLoadPanel
> -
> 
> add(new AjaxLazyLoadPanel("testPanel") {
>@Override
>public Component getLazyLoadComponent(String markupId) {
>return new DataPanel(markupId);// simple panel which 
> includes only one Label
>}
> });
> 
> and it works fine...
> 
> when i add wiquery 1.5.3 you have this code
> 
> application.setHeaderResponseDecorator(new IHeaderResponseDecorator()
>   {
>   private static final long serialVersionUID = 1L;
> 
>   public IHeaderResponse decorate(IHeaderResponse 
> response)
>   {
>   return new 
> WiQueryDecoratingHeaderResponse(response);
>   }
>   });
> in  the WiQueryCoreInitializer class
> 
> now when i run this test it doesn't work correctly, and all 
> AjaxLazyLoadPanels in my application are not working. in ours real 
> application also other ajax events doesn't work correctly because of 
> wiquery .
> 
> Thanks.
> 
> 
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Problem-with-wicket-1-5-3-a
> nd-wiquery-1-5-3-tp4217860p4218578.html
> Sent from the Users forum mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Problem with wicket 1.5.3 and wiquery 1.5.3

[Hielke Hoeve]

Thats something that i would like to know once you stumble upon it. Adding 
dummy behaviors to fix things should not be necessary. I will try and fix the 
problem.

Hielke

-Original Message-
From: Chris Hawkins [mailto:ch...@chawkins.com] 
Sent: dinsdag 20 december 2011 19:12
To: users@wicket.apache.org
Subject: Re: Problem with wicket 1.5.3 and wiquery 1.5.3

This sounds very similar to a problem that I had with WiQuery.  I found that if 
a page did not have any WiQuery components or behaviors on it I got errors with 
the Wicket ajax javascript due to the WiQueryDecoratingResponseHeader.  My 
solution was to force WiQuery to load jQuery by adding an empty WiQuery 
behavior to my base page.

/**
* This patch is intended to load jquery on every page because the 
WiQueryDecoratingHeaderResponse
* is rewriting every JS call regardless of if there is WiQuery code on the page
* @author chrish
*
*/
public class WiQueryJsPatch extends WiQueryAbstractBehavior {

private static final long serialVersionUID = 1L;

@Override
public JsStatement statement() {
return null;
}

}

On Dec 20, 2011, at 9:05 AM, dennisB wrote:

> hi Hielke
> 
> thanks for the fast reply.
> 
> I create a simple example to demonstrate my problem:
> 
> this is the scenario:
> 
> In my application i have wicket 1.5.3 and i am using AjaxLazyLoadPanel 
> -
> 
> add(new AjaxLazyLoadPanel("testPanel") {
>@Override
>public Component getLazyLoadComponent(String markupId) {
>return new DataPanel(markupId);// simple panel which 
> includes only one Label
>}
> });
> 
> and it works fine...
> 
> when i add wiquery 1.5.3 you have this code
> 
> application.setHeaderResponseDecorator(new IHeaderResponseDecorator()
>   {
>   private static final long serialVersionUID = 1L;
> 
>   public IHeaderResponse decorate(IHeaderResponse 
> response)
>   {
>   return new 
> WiQueryDecoratingHeaderResponse(response);
>   }
>   });
> in  the WiQueryCoreInitializer class
> 
> now when i run this test it doesn't work correctly, and all 
> AjaxLazyLoadPanels in my application are not working. in ours real 
> application also other ajax events doesn't work correctly because of 
> wiquery .
> 
> Thanks.
> 
> 
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Problem-with-wicket-1-5-3-a
> nd-wiquery-1-5-3-tp4217860p4218578.html
> Sent from the Users forum mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Problem with wicket 1.5.3 and wiquery 1.5.3

[Hielke Hoeve]

Hi Dennis,

Unfortunately this is the (only) way how WiQuery can work. If you provide some 
code we can help you fix this, otherwise we'll have to try and read minds which 
is bound to fail :)

Hielke

-Original Message-
From: dennisB [mailto:dennisbo...@gmail.com] 
Sent: dinsdag 20 december 2011 14:52
To: users@wicket.apache.org
Subject: Problem with wicket 1.5.3 and wiquery 1.5.3

Hi all

We are performing upgrade to wicket 1.5.3 and wiquery 1.5.3 and we got some 
problem with the Response, the problem is that all my Responses is wrapped now 
with WiQueryDecoratingHeaderResponse class and the Ajax events doesn't work 
properly 

Thanks .

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Problem-with-wicket-1-5-3-and-wiquery-1-5-3-tp4217860p4217860.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Apache Wicket is a Flawed Framework

[Hielke Hoeve]

If you come here and try to start a flame about how bad Wicket is while you 
obviously have no clue how it works then atleast have the decency to write a 
propert post instead of a lame list of cons (and no pros) and a oneliner saying 
Spring MVC is the only other option...

Hielke

-Original Message-
From: Eric Kizaki [mailto:erickiz...@gmail.com] 
Sent: donderdag 17 november 2011 16:45
To: users@wicket.apache.org
Subject: Apache Wicket is a Flawed Framework

Violates Dry:  You must repeat the component hierarchy of your widgets that are 
in HTML in Java Code for no good reason.  If you move your widget around in the 
html it will break the Java and you get a stack trace if you change the 
nesting.  You have to keep these two files synched.  A JSP file is more 
maintainable.  At least the view code is in one place.
 
Not previewable:  One of the supposed benefits of Wicket is a clean template 
that could make pages previewable for designers.  First, we don't have seperate 
designers at my company.  Second, it is better if the samer person does 
development and design.  Third, if you use extends your page will not be 
priviewable outside an application server running Wicket.  This supposed 
benefit does not exist. 

Violates MVC:  It smashes view and controller code into the same Java file. 
You have code that regulates page flow and code that changes css attributes in 
the same file.  Even Spring MVC had better separation of concerns. 
JSP/Servlets with Spring MVC is better. 

Excessively verbose and complicated:  What is a LoadableDetachableModel? 
The learning curve for Wicket is immense.  

Breaks POJOS:  A real POJO does not need to implement an interface or extend a 
class.  Wicket forces your beans to be Serializable.  This is like using EJBs 
in how it forced you to implement interfaces. 

Terrible AJAX:  Compared to a few lines of jQuery AJAX is excessively 
complicated and verbose in Wicket.  A lot of things like “AJAX” links should 
not be done via “AJAX” at all.  Hiding a div on the client would simply be done 
with JavaScript on the client.  Wicket better not require a server request for 
that.  You also have no JSON support and good luck debugging any JavaScript or 
AJAX in Firefox.  Instead you have to use the subpar Wicket debugging. 

HTML5:  No support for HTML 5 form elements unless you upgrade to Wicket 1.5.  
You will get a stack trace.  The upgrade to Wicket 1.5 is painful and will 
break your code.  Good luck getting this to work with jQuery mobile. 

Bad Defaults:  Most pages are stateless.  The default for Wicket is stateful.  
So if I want a decent URL and a bookmarkable page I have to mount the page and 
use a bookmarkable page link with page parameters.  Using page parameters is 
worse than how Spring MVC does binding.  I have to keep doing this over and 
over for each page.  There is too much work involved to get a decent stateless 
page with a nice URL. This should be the default. 

Interferes with other libraries:  It screws up your jQuery code.  It forces you 
into a restrictive way of doing web-development:  the Wicket Way.  

Causes a redeploy whenever you add anything:  Maybe Java developers are used to 
this, but in any other web development environment I do not need to redeploy 
after adding a text box to the page.  It is completely absurd. 
Only with JRebel is this alleviated.  No, embedded Jetty in debug mode still 
slow.  Even a simple JSP file has hot reloading on Tomcat and if I make a 
change to my view code the changes are immediately viewable in the browser when 
I refresh.  This is WITHOUT JRebel.  

HTTPSession Objects are not hard:  Most pages do not need state.  If you do use 
HTTPSession it is simple.  Can you use a map?  Then you can use HTTPSession.  
This is less comlicated than most Wicket code. 

Stateful Component based framework are a terrible idea:  Even at the 
theoretical level this is a bad idea. It is a leaky abstraction over a simple 
request/response cycle.  It made something simple and made it overly 
complicated.  This remind me of Hibernate and ORMS.  I disagree that we should 
abstract things to this level and do everything in verbose Java. 
People are dropping Hibernate and going back to native SQL and Spring JDBC 
template.  SQL and the relational model are easy.  Working with HTTP requests 
is easy too.  What was wrong with JSPs/Servlets?  Keep it simple stupid.  We 
know JSF was too complicated and it was terrible.  Spring MVC is better and has 
rest support.  It just works with Spring and has great support for the JSON 
Jackson mapper.  

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-is-a-Flawed-Framework-tp4080411p4080411.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wicket 1.5.2, stalls on one tomcat

[Hielke Hoeve]

We have this problem with an application connecting to MS SQL Server. It seems 
that the applications stalls upon connecting  to the database. This issue has 
been reported: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7105007.
We had to revert to jdk 1.6_u25 to make it work. Java 7 works as well.

Not sure if this is the same issue though...

Hielke

-Original Message-
From: nino martinez wael [mailto:nino.martinez.w...@gmail.com] 
Sent: vrijdag 18 november 2011 8:20
To: users@wicket.apache.org
Subject: Re: Wicket 1.5.2, stalls on one tomcat

So I digged into this and discovered something strange.

On the server that was working it had jre 6u24 and on the one not working it 
had jre 6u29. I could'nt restart the server, but after installing jdk
6u25 it actually worked..


This is not good. It could prove hard to replicate with other framework stacks, 
Im using a combo of mybatis, guice 3, wicket 1.5.3.. Anybody else using this on 
jre 6u29 on tomcat 7?

regards Nino

2011/11/17 nino martinez wael 

> THANKS!
>
>
> 2011/11/17 Andrea Del Bene 
>
>> Profile the stalled server with Visual VM? It should detect existing 
>> deadlocks...
>>
>>> Hi
>>>
>>> I have a very strange problem. At a customers site we have 2 servers 
>>> with 1 Tomcat 7 installed each. One day on one of the servers our 
>>> application just stalled after loading the sign in page, when you 
>>> click the login button.
>>> Im
>>> not sure this is a wicket problem. Heres what I've tried so far:
>>>
>>>
>>>- Restart Tomcat
>>>- Point the working application at the non working servers sql 
>>> database,
>>>it still works.
>>>- Purge Tomcats session storage and temporary files
>>>- Restart the server
>>>- Redeploy the application, with the war from the working server 
>>> (just
>>>
>>>to be sure)
>>>
>>> I've even tried setting up SQL Profiler and sniffing on the database 
>>> connections, nothing strange goes on here. Just seems like the 
>>> application stalls when you try to login. Keep in mind that this 
>>> works without problems from the other server.
>>>
>>>
>>>
>>> regards Nino
>>>
>>>
>>
>> --**--**-
>>  To unsubscribe, e-mail: 
>> users-unsubscribe@wicket.**apache.org> .org> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

WiQuery 1.5 release

[Hielke Hoeve]

Hi everyone!

We have been working on improving WiQuery to use more and more (new) features 
of Wicket 1.5.  Now that Wicket 1.5 has its first release it is time for us to 
do the same. Last few weeks we released RCs and have pinpointed some bugs and 
flaws. Now that nearly all of them have been removed it is time for the first 
final release.

A lot has changed in WiQuery, most things invisible for end users. Here is a 
list of features of WiQuery (old and new):

 *   Components or Behaviours implementing the interface IWiQueryPlugin can 
define a jQuery statement which is gathered at the end of each requestcycle and 
send to the client to be executed on dom document ready. The jQuery JavaScript 
resource is automatically added for you.
 *   Components or Behaviours can now use the wicket function renderHead() 
instead of Wiquery's contribute() to render ResourceReferences or plain scripts 
to the HeaderResponse.
 *   ResourceReferences can have their dependencies defined so that end users 
do not have to add a long list of ResourceReferences but only 1 (or in worst 
case a few).
 *   ResourceReferences are rendered in a predefined sorted order (first 
wicket, then wiquery, then the rest) so that every resource has its 
dependencies loaded before itself. This can be configured to be different.
 *   WiQuery provides 2 YUI Compressors, one for JS and one for CSS, which have 
to be set manually. They compress your JavaScript or StyleSheet on the fly. 
Note that this increases server render time.
 *   WiQuery is split in 2 artifacts: wiquery-core and wiquery-jquery-ui. When 
using wiquery-jquery-ui Components or Behaviors which have the @WiQueryUIPlugin 
annotation automatically get the jQuery UI theme ResourceReferences added.
 *   Some API changes were necessary, this means your project will not compile 
but most errors are the same:
*   Most Wiquery ResourceReferences were renamed to reflect Wicket's 
ResourceReferences name change from Javascript to JavaScript.
*   The contribute() function is no longer present in IWiQueryPlugin, this 
can be done by using the Component.renderHead() or Behavior.

In order to use WiQuery you need to add one of the artifacts below 
(wiquery-core contains no jquery ui, wiquery-jquery-ui contains a subset of 
jquery default components):


org.odlabs.wiquery
wiquery-core
1.5.0



org.odlabs.wiquery
wiquery-jquery-ui
1.5.0


We are working on updating our Wiki during the coming week. Here you will find 
more information about current and new classes and how to use them.


The WiQuery team.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: how to get HttpServletRequest in wicket 1.5

[Hielke Hoeve]

Roger, thanks for the clarification.

Hielke

-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org] 
Sent: woensdag 14 september 2011 9:54
To: users@wicket.apache.org
Subject: Re: how to get HttpServletRequest in wicket 1.5

java.lang.Object org.apache.wicket.request.Response.getContainerResponse()
javax.servlet.http.HttpServletResponse
org.apache.wicket.protocol.http.servlet.ServletWebResponse.getContainerResponse()

JDK1.5+ covariant return type

On Wed, Sep 14, 2011 at 10:24 AM, Hielke Hoeve  wrote:
> Why was the return type of getContainerRequest() altered to Object? 
> Everyone is now casting the result to HttpServletRequest anyway. So 
> changing the api kind of defeats the purpose :)
>
> Hielke
>
> -Original Message-
> From: Martin Grigorov [mailto:mgrigo...@apache.org]
> Sent: donderdag 8 september 2011 11:36
> To: users@wicket.apache.org
> Subject: Re: how to get HttpServletRequest in wicket 1.5
>
> HttpServletRequest servletReq = (HttpServletRequest) 
> getRequest().getContainerRequest();
>
> On Thu, Sep 8, 2011 at 12:26 PM, nhsoft.yhw  wrote:
>> in wicket 1.4.x, the code like :
>>
>> HttpServletRequest request =
>> getWebRequestCycle().getWebRequest().getHttpServletRequest();
>>
>> but i don't know how to get HttpServletRequest  in wicket 1.5
>>
>>
>> -
>> http://www.517wm.com
>> 外卖订餐分享工具
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/how-to-get-HttpServletRequ
>> e st-in-wicket-1-5-tp3798272p3798272.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: how to get HttpServletRequest in wicket 1.5

[Hielke Hoeve]

Why was the return type of getContainerRequest() altered to Object? Everyone is 
now casting the result to HttpServletRequest anyway. So changing the api kind 
of defeats the purpose :)

Hielke

-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org] 
Sent: donderdag 8 september 2011 11:36
To: users@wicket.apache.org
Subject: Re: how to get HttpServletRequest in wicket 1.5

HttpServletRequest servletReq = (HttpServletRequest) 
getRequest().getContainerRequest();

On Thu, Sep 8, 2011 at 12:26 PM, nhsoft.yhw  wrote:
> in wicket 1.4.x, the code like :
>
> HttpServletRequest request =
> getWebRequestCycle().getWebRequest().getHttpServletRequest();
>
> but i don't know how to get HttpServletRequest  in wicket 1.5
>
>
> -
> http://www.517wm.com
> 外卖订餐分享工具
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/how-to-get-HttpServletReque
> st-in-wicket-1-5-tp3798272p3798272.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Username gets cached

[Hielke Hoeve]

This is probably a browser 'feature' where certain form field get cached 
client-side. Very annoying especially since they can show unexpected 
behavior... autocomplete="off" is optional so not all browsers use it.

Hielke

-Original Message-
From: Anna Simbirtsev [mailto:asimbirt...@gmail.com] 
Sent: woensdag 3 augustus 2011 15:37
To: users@wicket.apache.org
Subject: Username gets cached

Hi,

On the login page I have a text field with wicket id username and Password text 
field with wicket id password.
If I have a password text field on a different page with different wicket id, 
it caches the values and populates the password field with password and the 
field before it with username.

How can I turn off auto populating the fields?

Thanks
Anna

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Ten things every Wicket programmer must know?

[Hielke Hoeve]

* How models work and best practices for wicket/hibernate
* how ajax behaviors should be used
* how are resources defined and used
* how to make a multilingual site using resource models 
etc

Hielke

-Original Message-
From: Jeremy Thomerson [mailto:jer...@wickettraining.com] 
Sent: donderdag 28 juli 2011 0:29
To: users@wicket.apache.org
Subject: RFC: Ten things every Wicket programmer must know?

Hello all,

  I'm writing an article for a Java magazine and would like to include
in it a list of "ten things every Wicket programmer must know".  Of
course, I have my list, but I'd be very curious to see what you think
should be on that list from your own experience.  Or, put another way,
maybe the question would be "what I wished I knew when I started Wicket"
- what tripped you up or what made you kick yourself later?

  Please reply back if you have input.  Please note that by replying,
you are granting me full permission to use your response as part of my
article without any attribution or payment.  If you disagree with those
terms, please respond anyway but in your response mention your own
terms.

Best regards,

--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket?  Use Brix! http://brixcms.org*

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: using saml2 for authentication

[Hielke Hoeve]

I find the documentation appalling. I have searched for 2 days for
proper libraries and all I could find was either half a library,
outdated libraries, old libraries, libraries with fuzzy documentation or
a full blown server installation (openaselectserver.org). I might be
spoiled as openid4java is easy as 1-2-3 to implement as it contains
examples...

I will look into Shibboleth, maybe I just looked wrong but I couldn't
make anything out of it. For one I find a product wrong when you need to
hire some chap at an insanely hourly rate just to plug a library into
your project...

Hielke

-Original Message-
From: Arjun Dhar [mailto:dhar...@yahoo.com] 
Sent: maandag 25 juli 2011 9:17
To: users@wicket.apache.org
Subject: RE: using saml2 for authentication

I dont think its justified to expect Wicket to directly provide that
Auth support.

My 2 cents to put you in the right directions AFAIK:

Typically, one should have an IDP or SP setup at either ends. For
instance, Shibboleth has good support for SAML2. Once you have that
setup, you can use any java based app to interact with your SSO.

Note: I've tried both CAS and Shibboleth. CAS current version for SAML2
is not reliable. So you should get familiar with Shibbolth I guess. I
have tried it for SalesForce Cloud, not directly via wicket but it will
be an interesting Blog for Wicket users, if you do figure it out!

-
Software documentation is like sex: when it is good, it is very, very
good; and when it is bad, it is still better than nothing!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/using-saml2-for-authenticatio
n-tp3680988p3691811.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: using saml2 for authentication

[Hielke Hoeve]

We have to use SAML2 in wicket as well, but there are absolutely no
libraries for java available. Let alone proper documentation... It seems
this is a wheel to be invented...

Hielke

-Original Message-
From: fachhoch [mailto:fachh...@gmail.com] 
Sent: woensdag 20 juli 2011 16:33
To: users@wicket.apache.org
Subject: using saml2 for authentication

my application uses wicket authentication which it turn uses spring
acegi security, now we along with our partner decided to use single sign
on for which saml2  is proposed,  I have to implement saml2 in my wicket
application we will the service provider and our partners will be
identity provider, did anybody used saml2 with wicket?







--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/using-saml2-for-authenticatio
n-tp3680988p3680988.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: GMap2 in a Wiquery Dialog

[Hielke Hoeve]

This looks like a styling issue as the google layer (controls and
buttons) does fill the window. Have you tried inspecting the html
elements (chrome and firefox+firebug are easiest to use) to see if maybe
one of the html elements in the window have wrong css classes assigned?

Hielke

-Original Message-
From: Philipp [mailto:philipp@gmail.com] 
Sent: maandag 27 juni 2011 12:25
To: users@wicket.apache.org
Subject: GMap2 in a Wiquery Dialog


I am trying to open a Google Map using GMap2 in a WiQuery Dialog modal
window. The goal is to use the modal window in order to show a large map
(800 x 500 px).

However, when I open the modal window only the small part of the map is
shown, whereas the rest is only a grey area. If I open the exact same
map in a regular panel, and not in a Wiquery Dialog the map is correctly
shown.

The following screenshot further illustrates this issue:

https://picasaweb.google.com/lh/photo/9iXCzDiZ9R9zGhN56N-mDy7NU3UNAKRLuG
ErIKOgVvA?feat=directlink


Here is the modal window implementation:

import org.apache.wicket.ajax.AjaxRequestTarget;
import org.apache.wicket.ajax.markup.html.AjaxLink;
import org.apache.wicket.markup.html.WebMarkupContainer;
import org.apache.wicket.model.ResourceModel;
import org.odlabs.wiquery.ui.dialog.Dialog;

import at.schuzalipo.w7.data.persistence.model.Address;
import at.schuzalipo.w7.web.W7BasePanel; import
at.schuzalipo.w7.web.common.GoogleMapsPanel;

public class ShowLargeMapPanel extends W7BasePanel {


 // Modal window
 private Dialog modalWindow;

 public ShowLargeMapPanel(String id, Address address) {
 super(id);


 //Add the link for opening the modal window
 AjaxLink openLink = new AjaxLink("openLargeLink") {
 @Override
 public void onClick(AjaxRequestTarget target) {
 modalWindow.open(target);
 }
 };
 add(openLink);


 // Add the modal window
 modalWindow = new Dialog("modal");
 modalWindow.setWidth(860);
 modalWindow.setHeight(630);
 modalWindow.setTitle(new
ResourceModel("winery.contactdetails.change").getObject());
 modalWindow.setModal(true);
 add(modalWindow);

 //Add the large google panel to the modal window
 WebMarkupContainer mapContainer = new
WebMarkupContainer("mapContainer");
 mapContainer.add(new GoogleMapsPanel("largeGoogleMap",address,
800, 500));
 modalWindow.add(mapContainer);


 }

}

And the HTML of the modal window:



















As you can see, I add the GoogleMapsPanel in the last few lines.

Here is the code for the GoogleMapsPanel itself:

import java.io.IOException;
import java.util.Locale;

import org.apache.wicket.behavior.SimpleAttributeModifier;
import org.apache.wicket.markup.html.panel.Panel;

import wicket.contrib.gmap.GMap2;
import wicket.contrib.gmap.api.GControl;
import wicket.contrib.gmap.api.GLatLng;
import wicket.contrib.gmap.api.GMarker;
import at.schuzalipo.w7.component.countryselector.Country;
import at.schuzalipo.w7.component.countryselector.CountryList;
import at.schuzalipo.w7.data.persistence.model.Address;
import at.schuzalipo.w7.util.Constants;
import at.schuzalipo.w7.util.ServerGeocoder;

/**
  * GoogleMapsPanel class.
  *
  * @author marco
  * @version $Id: $
  */
public class GoogleMapsPanel extends Panel {

 private static final long serialVersionUID = 1L;
 private static final ServerGeocoder geocoder = new ServerGeocoder(
 Constants.GMAP_API_KEY);

 private GMap2 googleMap;

 /**
  * Constructor for GoogleMapsPanel.
  *
  * @param id a {@link java.lang.String} object.
  * @param address a {@link 
at.schuzalipo.w7.data.persistence.model.Address} object.
  */
 public GoogleMapsPanel(String id, Address address, int width, int 
height) {
 super(id);
 this.setOutputMarkupId(true);

 // specify the google map
 googleMap = new GMap2("googleMap", Constants.GMAP_API_KEY);

 //Set the size of the map
 googleMap.add(new SimpleAttributeModifier("style", "width: 
"+width+"px; height: "+height+"px;"));


 googleMap.setDoubleClickZoomEnabled(false);
 googleMap.setZoom(10);
 googleMap.addControl(GControl.GLargeMapControl);
 googleMap.addControl(GControl.GMapTypeControl);
 googleMap.addControl(GControl.GScaleControl);


 GLatLng latLng = null;
 String location;
 if (address != null) {

 //Get the Englisch name of the country
 CountryList countrylist = new CountryList(Locale.ENGLISH);
 Country c = 
countrylist.getCountryFromCode(address.getCountry());

 location = address.getStreet() + ", " + address.getZip() + 
", " + address.getCity()
 + ", " + c.getName();

 }
 else {
 location = "USA";
 }


 //Try to get the location - as backu

RE: Major session problem [GAE]

[Hielke Hoeve]

Using static non-final fields in a multi user environment is very very
very very bad. The only cases you should use static are for example a
logger (log4j etc) a global variable defining a number or string.
If you do need to keep track of something using final then wrap this
using the ThreadLocal class.

final static Logger log;
final static String applicationName = "Zeldors application";
final static String maxNumUsers = 2; 

Hielke

-Original Message-
From: Zeldor [mailto:pgronkiew...@gmail.com] 
Sent: donderdag 9 juni 2011 11:32
To: users@wicket.apache.org
Subject: Re: Major session problem [GAE]

Yeah, no idea why Static is there, must be some leftover from early
code.
It's good to have someone else take a look at your code and point the
obvious :) I will check if it solves my problems.

--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Major-session-problem-GAE-tp3
584894p3585007.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: database

[Hielke Hoeve]

http://lmgtfy.com/?q=wicket+hibernate+spring+howto

First hit: 
http://wicketinaction.com/2009/06/wicketspringhibernate-configuration/


Hielke

-Original Message-
From: Miroslav F. [mailto:mir...@seznam.cz] 
Sent: dinsdag 7 juni 2011 11:42
To: users@wicket.apache.org
Subject: RE: database

The original question was "I would like to make my wicket app to store
images in database. No problem but I don't know how to configure tomcat
+ wicket for database."

No "is it good idea to store images in database?" ;-)

Still don't know how to work with database in wicket. Is anywhere
examples?
wicket phonebook example is not working:
http://wicketstuff.org/confluence/display/STUFFWIKI/wicket-phonebook/

I move to direction not use pure JDBC and using Hibernate. Does someone
know where to find docs for using Hibernate in webapp project? Where to
put config file or any other specific issues for using Hibernate in
webapp?

Thanks, Miro



> -Original Message-
> From: meduolis [mailto:meduol...@gmail.com]
> Sent: Sunday, 05. June 2011 12:19
> To: users@wicket.apache.org
> Subject: Re: database
> 
> Why do you want to store images in database? I think that is not a 
> very good idea. You better store images in your file system, and 
> persist into database only the paths to images.
> 
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/database-tp3573282p
3574812.html
> Sent from the Users forum mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 
> 


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: post request with wicket

[Hielke Hoeve]

You need to make an xml envelope, fill that with the right url to call
add arguments for the function, calling something like an ajax url that
returns json data is way quicker.

Hielke

-Original Message-
From: wmike1...@gmail.com [mailto:wmike1...@gmail.com] 
Sent: maandag 16 mei 2011 15:58
To: users@wicket.apache.org
Subject: RE: post request with wicket

I'm just calling a webservice, getting some data that I want to populate
some fields on the page. The soap call as of now is on the server-side,
inside an ajaxLink's onClick() method. Seems to be working fine.

Why would building the request on the cilent be expensive? Expensive in
terms of what?

thanks

--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/post-request-with-wicket-tp35
20861p3526264.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: post request with wicket

[Hielke Hoeve]

What is it exactly what you want to achieve? What is the use case? Why
would you want the browser to do a soap call? That is quite expensive as
you will need the browser to build a soap xml message and send it and
parse the soap response message. 

Hielke

-Original Message-
From: wmike1...@gmail.com [mailto:wmike1...@gmail.com] 
Sent: vrijdag 13 mei 2011 21:22
To: users@wicket.apache.org
Subject: Re: post request with wicket

just add something like this into my markup file?

# Send  

is this in keeping with wicket? I'm confused about this.

--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/post-request-with-wicket-tp35
20861p3520964.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Getting Parameters from URL

[Hielke Hoeve]

This is because a session is created only once for each user, until it
expires ofcourse...
If you wish to check url parameters for each request I would suggest you
do this in RequestCycle.onBeginRequest(). There is also
RequestCylce.onEndRequest() if you need to do anything at the end of the
cycle (letting go of variables and what not).

If you want to check parameters only for a few pages then you could also
choose to use the Page(PageParameters) constructor, wicket will give
that constructor a hashmap with all the parameters from the url. 

Hielke

-Original Message-
From: drf [mailto:davidrfi...@gmail.com] 
Sent: donderdag 12 mei 2011 15:49
To: users@wicket.apache.org
Subject: Getting Parameters from URL

We have code in our session object as follows:

public class OurSession extends WebSession {

   public OurSession(Request request)}{
   super(request)
   // GET PARAMETERS FROM REQUEST
   userId = request.getParameter("userId");
  }

}

This works the first time, so if the url has a parameter of userId=JOHN
then this can be picked up in the above code.
However, if the application is again requested from the browser (and the
session already exists), this code will not get called.
What is then the best way to pick up the parameters on the url?
Thanks


--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Getting-Parameters-from-URL-t
p3517499p3517499.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: warn on exit from browser

[Hielke Hoeve]

You could use an ajax callback to wicket in the onbeforeunload and do
something serverside but showing a modalwindow is probably impossible as
the onbeforeunload will continue after the ajax call is done...

Hielke

-Original Message-
From: Andrea Del Bene [mailto:adelb...@ciseonweb.it] 
Sent: donderdag 12 mei 2011 12:04
To: users@wicket.apache.org
Subject: Re: warn on exit from browser

So far as i know Wicket can't  help you that much since this is a "pure"

client side problem.
> Thank you andrea, but i already managed to use javascript to show a 
> confirm dialog.
>
> What I would like to know is if it is possible to change the default 
> behavior of the browser and to show a wicket popup instead of the 
> confirm dialog?
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/warn-on-exit-from-browser-t
> p3516569p3516849.html Sent from the Users forum mailing list archive 
> at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
>


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: building dynamic charts in wicket

[Hielke Hoeve]

Hey Daku,

Emond and I have been working on 2 little projects to render charts.
Each use a different jQuery plugin to draw the graphs client side and
both use WiQuery to facilitate the server side part. Maybe those
projects can help you in choosing the desired product. Both come with
examples, simply use Start.java to start the test webapplication.

https://github.com/hielkehoeve/wiquery-jqplot
https://github.com/hielkehoeve/wiquery-highcharts

Note that both projects only support ajax updating by redrawing the
chart from scratch.

Regards,

Hielke


-Original Message-
From: lambdad...@gmail.com [mailto:lambdad...@googlemail.com] 
Sent: maandag 9 mei 2011 15:43
To: users@wicket.apache.org
Subject: Re: building dynamic charts in wicket

Thanks for the prompt reply!

In the given scenario, the charts on the central web application
reflects the status of the individual machines which either shown as a
mashes of the charts which are suppose to be hosted on the individual
machines.
Alternatively, the metrics could be"push"ed directly to the central
wicket application or pulled periodically through some remote interface,
which (the central app) then can generate the chart - event based.

The former approach is lightweight but latter has some merits as well
(probably).

While on hunt, I have found the following two links. But unsure if the
libraries are fresh enough to be  consumed :)

wicket mashup
http://code.google.com/p/wicket-mashup/

from the Wicket stuff source base
https://github.com/wicketstuff/core/tree/master/jdk-1.5-parent/googlecha
rts-parent/googlecharts-examples/src/main/java/org/wicketstuff/googlecha
rts/examples

Daku

On Mon, May 9, 2011 at 2:41 PM, Wilhelmsen Tor Iver
wrote:

> Sounds like a combo of a dynamic image resource component (using e.g.
> JFreeChart or the like) and an AjaxSelfUpdatingTimerBehavior is
needed.
>
> mvh
> - Tor Iver Wilhelmsen, Arrive AS
>
> -Original Message-
> From: lambdad...@gmail.com [mailto:lambdad...@googlemail.com]
> Sent: 9. mai 2011 14:32
> To: users@wicket.apache.org
> Subject: building dynamic charts in wicket
>
> Hi,
>
> I would like add an extra page to my Web application which shows a 
> graph similar to jconsole or google charts (displaying time series 
> analysis). It is required to be dynamic in nature which means the 
> graph should update itself (using wicket ajax) as soon as the new new 
> readings/metrics are available. Are there any efforts have been made 
> so far relevant to this direction?
>
> cheers
> Daku
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Serve Json in request and response

[Hielke Hoeve]

And another: http://jackson.codehaus.org/  (This library is also used in
WiQuery)

Hielke

-Original Message-
From: jcgarciam [mailto:jcgarc...@gmail.com] 
Sent: dinsdag 3 mei 2011 13:48
To: users@wicket.apache.org
Subject: Re: Serve Json in request and response

Just adding another json library (http://code.google.com/p/google-gson/)

As all saids, wicket brings nothing to the mix. Use a servlet+json
library to parse the request.

On Tue, May 3, 2011 at 8:22 AM, Wilhelmsen Tor Iver [via Apache Wicket]
<
ml-node+3492239-1708321586-65...@n4.nabble.com> wrote:

> > I can use dopost and doget but how to handle Json request?
>
> JSON is just data representation, there are some Java libraries out 
> there to deal with JSON formatted data (e.g. Jettison at 
> http://jettison.codehaus.org/ or JSON.simple at 
> http://code.google.com/p/json-simple/ ).
>
> But if you want to use the Jersey libraries directly they of course 
> deal with Java-JSON mapping out of the box. If you somehow need to 
> share info between Wicket and the REST services you should be able to 
> put that into the HTTP session which would be shared between them.
>
> - Tor Iver
>
> -
> To unsubscribe, e-mail: [hidden 
> email]
> For additional commands, e-mail: [hidden 
> email]
>
>
>
> --
>  If you reply to this email, your message will be added to the 
> discussion
> below:
>
> http://apache-wicket.1842946.n4.nabble.com/Serve-Json-in-request-and-r
> esponse-tp3491991p3492239.html  To start a new topic under Apache 
> Wicket, email
> ml-node+1842946-398011874-65...@n4.nabble.com
> To unsubscribe from Apache Wicket, click
here.
>
>



-- 

JC


--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Serve-Json-in-request-and-res
ponse-tp3491991p3492287.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: eclipse,jetty,wicket

[Hielke Hoeve]

You can also use the Start.java from the quickstart as example how to
start in eclipse without maven.

Hielke

-Original Message-
From: fachhoch [mailto:fachh...@gmail.com] 
Sent: vrijdag 15 april 2011 18:51
To: users@wicket.apache.org
Subject: eclipse,jetty,wicket

I am running my wicket app with jetty-maven-plugin  from  eclipse , when
run
in debug  mode   any change to .java  file  the changes are reflected
in
the app but if I change  html  the changes are not reflected, eclipse
does not even say hot code replace failed , please help me.

--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/eclipse-jetty-wicket-tp345252
6p3452526.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wiquery experiences

[Hielke Hoeve]

> 
>-Original Message-
>From: msj121 [mailto:msj...@gmail.com] 
>Sent: donderdag 7 april 2011 2:13
>To: users@wicket.apache.org
>Subject: Re: Wiquery experiences
>
>I both agree and disagree with the aforementioned comments.
>
>I don't think anyone would disagree that writing JavaScript from wicket
or using a decorator to write JavaScript is wrong. In fact quite often I
may not know the id of an object until run-time and I may want the
javascript to run on a specific textfield with no extra class names or
additional tags marking it. To say that you need an extra .js file for a
one-line or even 20 line simple js command is arguable I think.

Hence we created the JsScope.quickScope(). However others, like Maarten,
do not like this function as it allows people to write js code in a java
class. There are more than 1 way to use WiQuery and everyone can use
their favorite one.

>That being said, if you know JavaScript or jQuery, probably WiQuery is
not the most necessary, it is really an object oriented interface to
jQuery, not much more as I recall.

That and resource manager. That is all it needs to be, because otherwise
it would be slow, large in jar size and unmaintainable. 

>The best advantage to WiQuery I find is that JQuery at page ready can
run numerous sets of commands All you need to do with WiQuery is add
these commands and they are all grouped together and run in a single
document ready function. Similarly WiQuery will take care of keeping
track of what object id to run the script against, JavaScript files to
import etc It does simplify things, but do you NEED another library,
some people want to keep as few dependencies as possible, some don't
care.
>Remember the real engine is JQuery, WiQuery is just an interface to
simplify. But look at writing javascript plainly in Wicket. If it is
easy for you, probably don't bother, but if your getting a headache you
might want to use WiQuery.

Hooray for freedom of choice! :-)

>My main fear is how often it may be updated and how long will it be
around.
>I have WiQuery in a current project I may take it out, I notice I
mostly have been writing my own jQuery anyway.

Since January we have released 4 new 1.2 versions in which we fixed a
great deal of bugs and added new features, like the YUI compressor to
compress resources when in production mode. We have started to work on a
wicket 1.5 version and are nearing RC status.

Hielke

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wiquery experiences

[Hielke Hoeve]

>-Original Message-
>From: joseph.pac...@gmail.com [mailto:joseph.pac...@gmail.com] On
Behalf Of Live Nono
>Sent: donderdag 7 april 2011 13:47
>To: users@wicket.apache.org
>Subject: Re: Wiquery experiences
>- does wiquery support being used from a wicket ajax request nicely?

Yes! This is the main aim of WiQuery, if an component is ajax refreshed
it is replaced (or added for the first time because it was previously
invisible) in the DOM tree there by removing any jQuery functionality.
WiQuery will add all jQuery functionality again.

> If so, is it part of its "intended aims" and thus made across all its
wrappers or just some of the wrapper being properly done? How does it
handle the case of WiQuery dependent component made visible through an
ajax request? => Hielke already provided some answers which I'm glad to
have read, but it doesn't cover it all.

What do you mean by wrappers? In order for WiQuery to do its job a
component needs to implement an interface in order to be detected by
WiQuery. This is done through Wickets component initialization
listeners. If a component is not visible, the resources and js code is
not used by WiQuery. Once the component is visible (again) on the page
the resources and js code will be used by WiQuery.

>- ease to use with other libraries, like JSLibraries (and its CDN
integration) ?

WiQuery does not provide any java script utils like jQuery does. It does
have js files, but these are files that are component specific. WiQuery
itself will not conflict with JavaScript libraries, unless jQuery does.

> reliability now and in the future: what about eventual bug I would
find, would they be easy to fix on my own? Does the code make enough
sense to me? In there a proper community around to help in case ?
What's the plan for currently supported jquery versions and the future?
=> Ernesto also provided some answers, which is good, thanks

Issues can be reported on our google project site[1]. We have a google
group[2] where any question about WiQuery can be asked and all are
answered (at least that is what we strive for). If you have questions
about an official wiquery plugin[3] questions can be asked in that
corresponding google group[4].


If you still have any questions, ask here or in the wiquery google
group[2].

Hielke

[1] http://code.google.com/p/wiquery/issues/list
[2] http://groups.google.com/group/wiquery
[3] http://code.google.com/p/wiquery-plugins/
[4] http://groups.google.com/group/wiquery-plugins


-Original Message-
From: joseph.pac...@gmail.com [mailto:joseph.pac...@gmail.com] On Behalf
Of Live Nono
Sent: donderdag 7 april 2011 13:47
To: users@wicket.apache.org
Subject: Re: Wiquery experiences

Ernesto, Hielke

thanks a lot for your answers

At the time I looked at wiquery, it was for some specific task. This
task didn't include explorating whether a full blown jquery/wicket
integration framework would fit our needs. This is quite a task on its
own imho, and there the lack of documentation is a real issue.

For example, questions I had which would involve quite some time to
figure out:
- does wiquery support being used from a wicket ajax request nicely?
If so, is it part of its "intended aims" and thus made across all its
wrappers or just some of the wrapper being properly done? How does it
handle the case of wiquery dependent component made visible through an
ajax request? => Hielke already provided some answers which I'm glad to
have read, but it doesn't cover it all
- ease to use with other librairies, like JSLibraries (and its CDN
integration) ?
- reliability now and in the future: what about eventual bug I would
find, would they be easy to fix on my own? Does the code make enough
sense to me? In there a proper community around to help in case ?
What's the plan for currently supported jquery versions and the future?
=> Ernesto also provided some answers, which is good, thanks
:)

I hope you understand better the questions which arise and why it would
take a while to figure them out just by looking at the code.
That's where more documentation/tutorial/feedbacks would help, to make
the discovery cost lower.

as a side note, I was already bitten by being early adopting some new
frameworks, so now I tend to be more carefull, esp. for stuff that are
directly seen by the users...

regards

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Wiquery experiences

[Hielke Hoeve]

The wiki is quite outdated, except for a small and somewhat hidden area: 
http://code.google.com/p/wiquery/wiki/QuickStart
The WiQuery plugins project isn't really well known and our project site does 
not point to it, but it a good start to see how applications can be converted, 
as it also contains a simple WebApplication.
Any other pointers as how to improve documentation and tutorials are most 
welcome!

Hielke

-Original Message-
From: Ernesto Reinaldo Barreiro [mailto:reier...@gmail.com] 
Sent: donderdag 7 april 2011 12:26
To: users@wicket.apache.org
Subject: Re: Wiquery experiences

Joseph,

Well it is true the documentation is not updated and there is not much to start 
with... but mind that WiQuery is maintained by people that do this mostly on 
their free time... I think

1- support on the google group is rather good
2- the speed on fixing bugs and reacting to user input is hight...

Additionally some of use have tried to add some extensions integrating 
different jquery plugins (components) (e.g. see [1] and [2]).

So, what else do you need? Someone to teach you step by step how to use the 
projects?  What about getting the example project, see how the examples works, 
look to the source code... and learn from there? IMHO theses are basic skills 
someone trying to make a living as Java programmer should have... and once you 
have learned something...  Why not take your time and contribute some 
documentation?

Regards,

Ernesto

References,

1-http://code.google.com/p/wiquery-plugins/
2-https://github.com/hielkehoeve/wiquery-jqplot

On Thu, Apr 7, 2011 at 12:06 PM, Live Nono  wrote:
> Hi Hielke
>
> Nice to be able to discuss with some wiquery commiter.
>
> Acutally, I was willing to use it some time ago but I found wiquery 
> wasn't very good at selling itself. The wiki is pretty old and useless
> (http://code.google.com/p/wiquery/wiki/DocumentationHome?tm=6) and at 
> the time I found no tutorial or example... Did it change in some way?
> I would still love to be able to have a better clue of it, since it 
> looks intriguing, but I don't have enough time to do a proper 
> investigation on how to use it...
>
> Regards
>
> 2011/4/7 Hielke Hoeve :
>> WiQuery *has* matured a lot. We are working hard in our late hours to 
>> implement and test interfaces to all facets of jQuery and are getting ready 
>> for Wicket 1.5.
>>
>> Bruno is right that for some purposes it is easy using only jQuery, simply 
>> add the jQuery js files you want and write a script tag with the 
>> document.onready function. But I am curious how one handles ajax added 
>> panels with jQuery functionality on a page or components that consume data 
>> or jquery enabled components that have jQuery options set based on business 
>> logic or components that have their visibility set based on business logic. 
>> Once a component is replaced by an ajax call the jQuery functionality is 
>> removed from this component. Not to speak of being able to reuse numerous 
>> components on numerous pages... I don't even want to begin to think about 
>> how to handle jquery component options based on business data.
>>
>> Now I do agree that in some cases (which do not cover the ones I described 
>> above) WiQuery is absolutely not useful and a simple static js file and 
>> static jQuery initialization statement is good enough. Not every jQuery 
>> component is worth converting to a WiQuery component. The ones that are 
>> worth are often:
>> - components that are ajax enabled and/or;
>> - components that have their jQuery options depend on data or logic 
>> and/or;
>> - components that have their visibility or are enabled based on data 
>> or logic and/or;
>> - components that are added by an ajax request and not at page load;
>>
>>
>> The reason I started working on the WiQuery project is because my company 
>> creates enterprise administration applications where we have *a lot* of 
>> pages with ajax replaced panels, autocomplete text fields, accordion panels, 
>> tabbed panels, feedback popups... you name it we have it.
>> With WiQuery we create reusable components, define which resources this 
>> component needs and what bit of jQuery it needs to initialize after the page 
>> (or ajax response) has been loaded, and simple add them to the page. The 
>> page is on a need to know basis, it will define the layout not boss all 
>> components around... WiQuery checks which resources are loaded, removes 
>> duplicates, adds the jQuery Core, jQuery UI and jQuery UI Theme. While 
>> managing multiple projects with over 1000+ pages, this takes away quite a 
>> load off our shoulders.
>>
>> Maarten says:
>>        Writing

RE: Wiquery experiences

[Hielke Hoeve]

WiQuery *has* matured a lot. We are working hard in our late hours to implement 
and test interfaces to all facets of jQuery and are getting ready for Wicket 
1.5. 

Bruno is right that for some purposes it is easy using only jQuery, simply add 
the jQuery js files you want and write a script tag with the document.onready 
function. But I am curious how one handles ajax added panels with jQuery 
functionality on a page or components that consume data or jquery enabled 
components that have jQuery options set based on business logic or components 
that have their visibility set based on business logic. Once a component is 
replaced by an ajax call the jQuery functionality is removed from this 
component. Not to speak of being able to reuse numerous components on numerous 
pages... I don't even want to begin to think about how to handle jquery 
component options based on business data.

Now I do agree that in some cases (which do not cover the ones I described 
above) WiQuery is absolutely not useful and a simple static js file and static 
jQuery initialization statement is good enough. Not every jQuery component is 
worth converting to a WiQuery component. The ones that are worth are often:
- components that are ajax enabled and/or;
- components that have their jQuery options depend on data or logic and/or;
- components that have their visibility or are enabled based on data or logic 
and/or;
- components that are added by an ajax request and not at page load;


The reason I started working on the WiQuery project is because my company 
creates enterprise administration applications where we have *a lot* of pages 
with ajax replaced panels, autocomplete text fields, accordion panels, tabbed 
panels, feedback popups... you name it we have it. 
With WiQuery we create reusable components, define which resources this 
component needs and what bit of jQuery it needs to initialize after the page 
(or ajax response) has been loaded, and simple add them to the page. The page 
is on a need to know basis, it will define the layout not boss all components 
around... WiQuery checks which resources are loaded, removes duplicates, adds 
the jQuery Core, jQuery UI and jQuery UI Theme. While managing multiple 
projects with over 1000+ pages, this takes away quite a load off our shoulders.

Maarten says:
Writing what should be JavaScript in your wicket Java code is quite  
out-of-place, and generally all you need to do is place your code where it 
belongs, in a .js or your markup.

I wonder if he ever really used WiQuery or even looked how it's used. Or for 
that matter used jQuery. What you *don't* need to do with WiQuery is write js 
code in your java classes and we recommend to put all js code in js files and 
load them as a resource! To create a jQuery wicket component you:
- write your jQuery js file and the html file that comes with it;
- write the java code that you need to insert any application data, behaviors 
or validators;
- let your component implement an interface (so WiQuery can detect it upon 
creation) to define which js/css files you want to be added as a resource and 
define the jQuery initialization statement with java code (which is translated 
most often something like "document.onready(.);".


There are other libraries around that do about the same as WiQuery, and perhaps 
better or faster, but my rant above is to clarify why the project exists and 
why people are using it. And the best part of it is: you don't have to use it...

Regards,

Hielke

-Original Message-
From: Bruno Borges [mailto:bruno.bor...@gmail.com] 
Sent: donderdag 7 april 2011 0:32
To: users@wicket.apache.org
Cc: Maarten Billemont
Subject: Re: Wiquery experiences

Most of the things you want to do with jQuery, you don't need a library for.

I totally agree with Maarten


Bruno Borges
www.brunoborges.com.br
+55 21 76727099

"The glory of great men should always be measured by the means they have used 
to acquire it."
 - Francois de La Rochefoucauld



On Wed, Apr 6, 2011 at 6:15 AM, Maarten Billemont  wrote:

> Unless WiQuery has matured a *lot* lately and the code has been 
> cleaned up significantly, I can't recommend it, personally.
>
> Writing what should be JavaScript in your wicket Java code is quite 
> out-of-place, and generally all you need to do is place your code 
> where it belongs, in a .js or your markup.
>
> There may be some odd cases here or there where tighter integration of 
> jQuery and Wicket can be beneficial, but those can usually be resolved 
> some other way.
>
> I don't have enough experience or knowledge of the framework to cast a 
> final vote though, all I'm saying is: beware of the quality of this 
> library's code and make sure you actually need it first (I want to do 
> jQuery stuff in my Wicket application is generally not reason enough).
>
> On 06 Apr 2011, at 11:09, ha...@dds.nl wrote:
>
> > Hi,
> >
> > We are thinking of using wiquery for a project. We are interested in 
> > the

Re: jWicket & WiQuery

[Hielke Hoeve]

What is there to miss? You have the library and the examples. Is there any
specific example you need?

Hielke
On 22 Jan 2011 21:13, "flavius"  wrote:

new WiQuery version: 1.1.3 and 1.2!

[Hielke Hoeve]

As more and more people use WiQuery everyday and more and more people use
the 1.2 version the time has come to release a maintanance release of 1.1
series and release the first version of 1.2.

WiQuery 1.2 has been given a new resource management where all javascripts
are automatically compressed using YUI when wicket is running in deployment
mode. This is excludes all the default javascripts where a minified version
is available. The current supported JQuery version is 1.4.4 and the
supported JQuery UI version is 1.8.8.

WiQuery 1.1.3 only has 2 bugs fixes: servlet-api is now a provided
dependency and the generated javascript has mime type "text/javascript".


org.odlabs.wiquery

wiquery
1.1.3


or


org.odlabs.wiquery

wiquery
1.2




Happy querying,

The WiQuery developers.

Re: Modal widow slow?

[Hielke Hoeve]

Putting a lot of controls (select and input etc) on one page will make any
browser slow. Internet explorer is the worst though.

You could try and use jquery to replace the viewing component with an editor
onclick. This does mean your models won't be updated upon submit.

Hielke
On 12 Jan 2011 20:07, "Martin Makundi" 
wrote:

Re: Graph Drawing

[Hielke Hoeve]

Hey Rory,

Did you ask these questions on the flot forums/mailinglist? I think they
probably have more experience with Flot.

Hielke

On 2 January 2011 17:36, ror...@vodafone.co.nz wrote:

>
> Hello Flot Users
>
> I am new to Flot. I have spent hours on google and with the api and sample
> programs trying to find how to do the following:
> (i)Change the thickness of lines so that they’re really thin or dashed;
> (ii) Change the color  of lines without it being done by the program.
>
> These are the first two questions I have but I am sure there will be more.
> Rory Barrett
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Graph-Drawing-tp3171001p3171001.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: target.addComponent(Field) in Ajax erases that Field's values

[Hielke Hoeve]

Did the field2 have an initial value or did you set the value in your
browser and then let the ajax run?

Hielke

On 21 Dec 2010 20:51, "eugenebalt"  wrote:
>
>
> I have a piece of Ajax code, attached to some field (let's call it
> sourceField), which looks like this:
>
>
> sourceField.add(new AjaxFormChoiceComponentUpdatingBehavior()
> {
>
> protected void onUpdate(AjaxRequestTarget target)
> {
>   target.addComponent(Field2);
> }
> }
>
>
> As you can see, Field2 is not changed in any way, it is not cleared or
> modified (so this code shouldn't really do anything).
>
> However, when this Ajax runs on changing the sourceField, the Field2's
> values get erased! Field2 is actually a CheckBoxMultipleChoice, and all
the
> checkbox selections get erased as soon as I do target.addComponent().
>
> Why does this happen? Any ideas on what's causing this?
>
> (Field2 is a CheckBoxMultipleChoice, initially initialized with some list,
> and its outputMarkerId = true, to make it work with Ajax.)
>
> Thanks
> --
> View this message in context:
http://apache-wicket.1842946.n4.nabble.com/target-addComponent-Field-in-Ajax-erases-that-Field-s-values-tp3159543p3159543.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

Re: Wicket 1.5-M3 migration experiences

[Hielke Hoeve]

>So basically you
>need org.apache.wicket.request.resource.PackageResource.getResourceStream()
>to become "protected", right ?
>This way you can wrap super.getResourceStream() with compressing one.

That would be awesome, yes.

Hielke

Re: Page mounting

[Hielke Hoeve]

Its fairly simple. Create a class Login, give it a constructor with
pageparameters. Create two panels, one for each login type. Based on the
page parameters you show one or the other. Mount the page on 2 paths, each
with its own parameter.

Hielke
On 16 Dec 2010 00:43, "Jeffrey Schneller" 
wrote:

Re: Wicket resources (css, js and images)?

[Hielke Hoeve]

On 15 December 2010 21:05, Alex Objelean  wrote:

>
> Though this topic is quite old, I think it is still actual. Since the 1.5
> release is not far away, did anybody thought if the (at least) js resource
> merging should occur?
>

We at WiQuery have been discussing multiple approaches. All options so far
have downsides. Here is a shortlist:

- Merge all js resources and css into 1 js resource and 1 css resource.
Problem: the 2 merged resources could be different on each page,
rendering this option useless. Also this causes alot of bandwidth.
Fix: Serve 2 Mother Of All resources, meaning appending only new
resources to the 2 merged resources and serving them. This does not
illiminate the problem of having to serve resources per page.
- Serve deltas, meaning assessing which resources has already been served
and only serve the new resources, in a merged form, so the user still has
all the required resources.
Problem: The client could have more resources than necessary, but
since they were already at the client this should not matter.
Problem: Serving resources to the client possibly every page but the
size of the resources is considerable smaller than option 1.

I like option 2 more than option 1, simply because it costs less bandwidth.



> This is very useful when you have a page with a large number of components,
> each loading a large number of small resources. Having a single resource
> (js
> and/or css) as a result of page rendering could have a dramatic page
> loading
> time improvement.
>

This could be a problem yes, however there is no way to illiminate the fact
that a page has multiple resources.

Hielke

Re: help me please!!! Wicket/Spring/Hibernate configuration woes

[Hielke Hoeve]

Hey Adam,

This is still a spring error, you need a sessionfactory and
transactionfactory and link them together. The opensessioninview filter only
opens a transaction if you get this right. The spring forums are filled with
examples.

Hielke
On 15 Dec 2010 16:58, "adam.gibbons"  wrote:
>
>
> Ok, I think this is now back to a Wicket question. Start up is ok now.
> However when I try and invoke UserServiceImpl.authenticate(){
>final Temp1 temp1 = new Temp1();
>temp1.setValue(userName);
>temp1DAO.save(temp1);
>return testUserService.authenticate(userName, password);
> }
>
> I get the following error through the GUI:
>
> Method onFormSubmitted of interface
> org.apache.wicket.markup.html.form.IFormSubmitListener targeted at
component
> [MarkupContainer [Component id = signInForm]] threw an exception
>
> Root cause:
>
> org.hibernate.HibernateException: persist is not valid without active
> transaction
> at
>
org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:297)
> at $Proxy18.persist(Unknown Source)
> at
>
uk.co.company.product.persistance.hibernate.AbstractTemp1DAO.save(AbstractTemp1DAO.java:21)
> at
>
uk.co.company.product.persistance.hibernate.Temp1DAOImpl.save(Temp1DAOImpl.java:1)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
>
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
> at
>
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
> at
>
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
> at
>
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
> at
>
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
> at
>
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy9.save(Unknown Source)
> at
>
uk.co.company.product.business.spring.UserServiceImpl.authenticate(UserServiceImpl.java:42)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
>
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
> at
>
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
> at
>
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
> at
>
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
> at
>
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
> at
>
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy10.authenticate(Unknown Source)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
>
org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler.invoke(LazyInitProxyFactory.java:416)
> at org.apache.wicket.proxy.$Proxy15.authenticate(Unknown Source)
> at
>
uk.co.company.product.presentation.wicket.app.CustomAuthenticatedWebSession.authenticate(CustomAuthenticatedWebSession.java:29)
>
> I was under the impression that the OpenSessionInViewFilter was supposed
to
> do this for us?
>
>
> Once again here is the source code:
>
>
> web.xml:
>
> 
> xmlns="http://java.sun.com/xml/ns/j2ee";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="
>http://java.sun.com/xml/ns/j2ee
>http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
>"
>version="2.4"
> >
>ZenTemplate
>
>contextConfigLocation
>classpath:applicationContext.xml
>
>
>
>
org.springframework.web.context.ContextLoaderListener
>
>
>opensessioninview
>
>
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter
>
>
>wicket-spring-hibernate
>
> org.apache.wicket.protocol.http.WicketFilter
>
>applicationFactoryClassName
>
>
org.apache.wicket.spring.SpringWebApplicationFactory
>
>
>applicationClassName
>
>
uk.co.company.product.presentation.wicket.app.WicketApplication
>
>
>
>opensessioninview
>/*
>
>
>wicket-spring-hibernate
>/*
>
> 
>
>
>
> applicationContext.xml:
>
> 
> xmlns="http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xmlns:aop="http://www.springframework.org/schema/aop";
>xmlns:tx="http://www.springframework.org/schema/tx";
>xmlns:context="http://www.springframework.org/schema/context";
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>http://www.springframework.org/schema/aop
> http://www.springframework.org/schema/aop/spring-aop-2.5.xsd

Fwd: Wicket 1.5-M3 migration experiences

[Hielke Hoeve]

Hi all,

I have been working on a 1.5 WiQuery branch to see if we can get an
experimental version online. I am facing several problems, most of which I
can find a workaround for. One, though, I can't seem to tackle. We provide
ResourceReferences, Resources and ResourceStreams for the plugin developers,
in Wicket 1.5 this has all been changeD but I can't seem to get my head
around how to use the new system. The migration guide speaks only of an
extra option called variation but does not speak of the fact that
subclassing resources is nearly impossible. I hope someone can point me in
the right direction.

We have a Resource[1] which extends from PackageResource and get the bytes
the PackageResource would normally serve to the user and runs this through
the YUI compressor. Previously this meant subclassing PackageResources
ResourceStream[2], catching the original bytes, running them through the YUI
compressor and returning them to the user. Now, however, it is impossible to
intercept the original bytes because this is all locked in a private method
of PackageResource and using a WriteCallback is useless as this does not
provide us access to the original bytes. This would mean we would have to
create a near exact copy of PackageResource in order to achieve this.

Am I missing anything here, is there anyone who knows another way to achieve
the same thing as with wicket 1.4? I do not mind rewriting wiquery
completely as long as it's solid and maintainable.


Regards,

Hielke Hoeve


[1]
http://code.google.com/p/wiquery/source/browse/trunk/src/main/java/org/odlabs/wiquery/core/commons/compressed/WiQueryYUICompressedJavaScriptResource.java
[2]
http://code.google.com/p/wiquery/source/browse/trunk/src/main/java/org/odlabs/wiquery/core/commons/compressed/WiQueryYUICompressedJavascriptResourceStream.java