An auto-detected GAE-specific mode in Wicket core? I don't think this is a good idea...
On Mon, Sep 20, 2010 at 3:07 PM, Erik van Oosten <[email protected]>wrote: > > ...and those shouldn't change, since the defaults shoud target... >> ...I think nothing one could do would change the classification from >> semi-compatible to compatible... >> > > Sure you can, the defaults could change automatically by detecting that GAE > is the container. > > Regards, > Erik. > > > > Op 20-09-10 15:05, tetsuo wrote: > >> I think Wicket is listed as semi-compatible because it requires some >> customization (override some methods, change some configuration) to make >> it >> work, not because its internals are inherently incompatible to GAE, or >> because it has some incompatible visual components. >> >> Such customization are simply disabling resource polling, enabling >> sessions >> and persisting the session store in the HttpSession, and those shouldn't >> change, since the defaults shoud target to the plain-old Java web >> application, not GAE. >> >> Some things could be done to improve GAE support, such as eliminating >> javax.swing dependencies (from the Tree component), but I think nothing >> one >> could do would change the classification from semi-compatible to >> compatible >> in that listing. Unless, of course, GAE turns to be the main target for >> Wicket (which I don't think is the case). >> >> my 2c, >> >> Tetsuo >> >> >> > -- > Sent from my SMTP compliant software > Erik van Oosten > http://day-to-day-stuff.blogspot.com/ > > >
