I personally don't use anything from Turbine, because it's design seems to
predicate certain skills and page concepts that don't necessarily occur in
my projects.
As for reusing code within Turbine, the major factor stopping me from doing
that is lack of knowledge and accessibility. Having 'reusable' code stuck
inside a project like Struts or Turbine limits its reusability. There's
been lots of discussion on the general list about this recently.
"user access control module?"
I'd guess most struts users would have no idea that Turbine had one.
Turbine's home page and features page don't mention "user access", but do
mention ACLs and roles. The Velocity/WebMacro focus and deemphasis of JSP
throughout Turbine made the impression on me that I'd be using technology
that duplicate existing JSP/Struts concepts and make the project more
complex.
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
NetRexx: http://www.multitask.com.au/NetRexx.nsf
