Agreed, but that could be done as build time 'check' step. Something like JSP compiler task http://ant.apache.org/manual/OptionalTasks/jspc.html I think it could be easier to create than full IDE plugin and such core service might be a very good foundation for people willing to build IDE specific UI layer atop of it.
--- D&J Gredler <[EMAIL PROTECTED]> wrote: > I mostly agree with you that current tooling gets us > pretty far, but there's > a lot to be said for turning the most frequent > "runtime" errors into > "compile-time" errors, something that often requires > special Tapestry > awareness. > > On 8/29/06, Konstantin Ignatyev > <[EMAIL PROTECTED]> wrote: > > > > > My point is that in case of Tapestry/Wicket there > is > > no need to worry much about tools, because > existing > > ones provide pretty good environment to work > within. > > Therefore focus on APIs and conventions seems very > > reasonable to me. > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
