Indeed, wasp and swarm are compiled against jdk 1.4. However, as much
i like you to use swarm, swarm is not a drop in replacement for
auth-roles. So you might want to consider the pro's and con's before
you do that. More info about swarm can be found here
http://wicketstuff.org/confluence/display/S
I doubt the jar will run with jdk 1.4 -> it is compiled using jdk 1.5,
so the version will be not compatible.
However, the auth-roles project is typically a really, really basic
security package. If you want more, then I suggest you look at
swarm/wasp from wicket stuff. This has the additional ben
Thank you very much!
I'll try that.
Juan
On 10/10/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> not sure, as long as you dont need the annotation part of it should be
> fine
>
> -igor
>
>
> On 10/10/07, Juan Gabriel Arias <[EMAIL PROTECTED]> wrote:
> > Thanks for the quick answer!
> >
> > And
not sure, as long as you dont need the annotation part of it should be fine
-igor
On 10/10/07, Juan Gabriel Arias <[EMAIL PROTECTED]> wrote:
> Thanks for the quick answer!
>
> And what about wicket-auth-roles?
> We are using auth-roles 1.2.2 compliant with Java 1.4 and we get that from
> the use
Thanks for the quick answer!
And what about wicket-auth-roles?
We are using auth-roles 1.2.2 compliant with Java 1.4 and we get that from
the users list.
Thanks again!
Juan
wicket-core, extensions, and spring all still support 1.4
-igor
On 10/10/07, Juan Gabriel Arias <[EMAIL PROTECTED]> wrote:
> Hi all,
> i'm using Java 1.4 and, by now, Wicket 1.2.6 (with wicket-spring,
> wicket-auth-roles and wicket-extensions)
>
> We need to migrate to Wicket 1.3 (and spring, ro
Hi all,
i'm using Java 1.4 and, by now, Wicket 1.2.6 (with wicket-spring,
wicket-auth-roles and wicket-extensions)
We need to migrate to Wicket 1.3 (and spring, roles and extensions), but
stay in Java 1.4.
Is any chance to do that?
I mean, Wicket core has two versions, for Java 1.4 and Java 5.
Bu
