On 10/2/01 1:05 AM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> on 10/1/01 8:22 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote: > >> I myself do not like this idea. The API for anything to do with locales >> should be independent of fulcrum. > > Why? We have a nice service in fulcrum that deals with localization. That's great, just don't directly couple it to turbine. I've spent an enormous amount of time splitting out the parts of turbine and I would really prefer not to see more of this coupling happen. In short I see turbine being an API for a web application and as such the final set of interfaces should be free of references to external packages. That being said DefaultTurbineRunData is pluggable so it probably isn't that big of a deal to couple fulcrum to a pluggable class but I don't want to see things creeping into the RunData interface due to the use of Fulcrum in DefaultTurbineRunData. I also feel that a service to pick off the locale is a bit of overkill in that there is a requirement for a service framework to process a header. > Are you saying that service should also use something external than it as > well? I don't understand the question. > -jon > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
