;) sorry if that was a little condescending. I was rushing and assumed I knew what you were asking.
I don't recall seeing any checks, although it might be a good idea if it's not already there. On Jan 19, 2011 6:52 PM, "Bob Harner" <[email protected]> wrote: > > Understood, but what I was really trying to ask is whether Tapestry > now (as of 5.2) in some way "forces" you to set the application > version number (or yells when you don't) or whether -- as I'm assuming > -- you'll just generate unnecessary extra requests to the app because > of the URLs changing. > > On Wed, Jan 19, 2011 at 9:30 PM, Josh Canfield <[email protected]> wrote: > > The default gives a new url every time you start the server, and on every > > server in the cluster. It really only works in a dev environment. > > On Jan 19, 2011 5:54 PM, "Bob Harner" <[email protected]> wrote: > >> Hi everybody, > >> > >> I was reviewing/updating the Confluence-based documentation and have a > >> question. The 5.2.0 release notes say: > >> > >> "It is now quite necessary to configure the application version > >> number: all assets are exposed via a URL that incorporates the > >> application version number; in previous releases, each library could > >> configure its own version number. By implication, changing library > >> versions and nothing else will now require a change to the application > >> version number." > >> > >> I understand the part about the application version number now > >> affecting library-based assets, but strictly speaking is it really > >> mandatory to set the application version number now? Or just very > >> highly recommended? > >> > >> As far as I can tell in the code, Tapestry will still generate a > >> random application version number for you: > >> > >> configuration.add(SymbolConstants.APPLICATION_VERSION, > >> Long.toHexString(random.nextLong())); > >> > >> My intent is to make the documentation consistent, which it isn't yet. > >> > >> Thanks! > >> > >> --------------------------------------------------------------------- > >> 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] >
