turbine-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From brian janaszek <bjanas...@collaborativefusion.com>
Subject RE: Custom PullTool Issue
Date Thu, 08 Jan 2004 21:28:53 GMT
On Thu, 2004-01-08 at 16:16, David Demner wrote:
> Hi Brian,
> 
> I had something exactly like this happen to me last week.  It turns out that
> the name I had chosen for a class conflicted with something.  My tool was
> called $navigation, and I changed it to $navigationtool and all was well
> again.  Maybe 'pulltool' conflicts with something (it sounds common enough)?
> 
> Maybe try changing the name of the tool?  (In TurbineResources.properties I
> had tool.authorized.navigation=mypackage.Navigation which I changed to
> tool.authorized.navigationTool=mypackage.Navigation and in my .vm files I
> changed $navigation to $navigationtool).

Well.  Your response got me on the right track.  It was so much the name
of tool (I used "pulltool" as an example), but the fact that the
template screen class, in certain circumstances, puts an object in the
Velocity context with the same name as the tool -- thus causing the
conflict.

Thanks...
b

Mime
View raw message