>-----Original Message----- >From: Paolo [mailto:[email protected]] >> Thoughts? >I support you! >I implemented class NoVersionMount thanks to pointbreak in my >MainApplication. >And It will be my template for future app. >But to do it, I needed to understood the problem, check on google, read a >lot of pages, >without found a solution, so post the question here, and after 3 post, got >a right reply for me. >Why an wicket user have to do all this????
>Why not, wicket use the NoVersionMount as default Mount? Like in wicket >1.4 and implement an VersionMount as an alternative for developer? I agree. It sounds like it might be useful for some scenarios (but none that I have discovered yet) but for most it seems like the 1.4 default works perfectly well. Maybe the NoVersionMount should be the default and if some developers have found a scenario that requires versioned pages they can turn it on somehow. Or, at least make the 1.4 default a 'configurable' option rather than have to implement a class to set up something which seems like a much more common requirement. > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
