On 10/18/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
Suppose it was Spring we were talking about. You're saying that you'd be OK with forking Spring and supporting it as part of Struts? Sure, JXP is on a much smaller scale, but the principle is the same.
If the Spring group went insane, and we didn't want to switch to HiveMind or Pico or Plexus, yes I'd fork the part that we use in a heart beat. It wasn't so long ago that WW had its own IOC container.
I think the bigger danger would be relying on other projects to solve > our problems for us. We're doing that already.
Yes, and it's a problem. OGNL is inactive and J5 issues are starting to surface, so we may need to adopt that codebase soon, or write our own version as Wicket did. Likewise, we've had known issues with the FreeMarker templates for some time, and since there is little or no crossover with the FreeMarker group, those issues are not being addressed. Some projects, like iBATIS, work hard to eliminate dependencies like these. We might want to start to consider copying more and importing less. In terms of the taglib templates, we use only a handful of constructs (over and over again). If we were having problems, it might makes sense to reduce the templates to a "little language" that did only what we need it to do, and then take what we need from FreeMarker or Velocity or JXP to implement our template taglib API. But, as it stands, if we can fix the caching issues, and make the themes easier to extend or subclass, then I don't see that the templates we have are broken. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
