On the surface, I'd like to preserve the bookmarks. Like I said though, I could do that with URLRewrite -- not ideal, but guaranteed to work.
Digging further, I'm trying to wrap my head around how Tapestry resolves page names in T5, having been a T3 then a T4 user. The problems I'm running into seem like they really shouldn't be problems and should be a common case that Tapestry should make easy to handle. So, I'm willing to give the framework the benefit of the doubt and correct my understanding. If not, that's fine, too. I'll make a mental note not to try to do these things or reevaluate if it's to be my new framework of choice. For what it's worth, I'm working on migrating an application from django to T5. There are a variety of reasons for this, both technical and political. Ultimately, I'd like to see Java and Tapestry be a suitable replacement for the flexibility of Python and Django. -- Kevin On 10/30/07 7:51 PM, in article [EMAIL PROTECTED], "Jonathan Barker" <[EMAIL PROTECTED]> wrote: > I don't know. > > There have been some threads and I think JIRA issues over the months on > similar topics. They revolve around making Tapestry URL's friendly, and the > logic involved in having something like Order/EditOrder reduced down to > order/edit, and dealing with cases when the package name is the same as the > page name, or even worse, if a parameter looks like a page name. > > A search for those threads and issues might give you some ideas. > > Are you just trying to preserve bookmarks? Is this something where you > really need to code the logic to cope with the old URL's while migrating to > a new URL scheme? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
