The licensing is a pain. We started using ExtJS when it was LGPL, then they
switched to GPL. By then we were already invested, so we bought a commercial
license -- kind of feel like we got suckered into that one. If I had a
chance to do it again I would just use YUI. We use ExtJS on top of YUI.
However, ExtJS is a good product, even though they made a poor licensing

The licensing problem is just a fact that we have to deal with now, so I'm
trying to find out what the easiest path is for integrating ExtJS 2.2 with
Wicket. If someone else has already done the effort or started the effort,
then that would help. The amount of work involved in integrating ExtJS 2.2
with Wicket is part of our new web framework evaluation criteria.

Richard Allen

On Wed, Oct 22, 2008 at 2:05 PM, Nino Saturnino Martinez Vazquez Wael <

> I thought there were a licensing issue! Could'nt just remember if it were
> the guy doing the wicket contrib or ext js..
> Martijn Dashorst wrote:
>> The GPL licensing of ExtJS is really a brain damage inflicting mess.
>> Personally I would stay very far away from JS libraries that are GPL
>> licensed (it is not clear how the viral aspect infects your server
>> side code, possibly requiring you to ship your server side code to
>> your users—you *are* distributing the GPL licensed code, which is
>> linked to your product)
>> Martijn
> --
> -Wicket for love
> Nino Martinez Wael
> Java Specialist @ Jayway DK
> +45 2936 7684
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to