Forum LAMS for Tech-Heads - General Forum: Problems with ToolBuilder and LAMS 2.3.1

By: Glenn Moloney

[ Reply | Forward ]

OK - found the cause of this problem. The default beanRefContext.xml in lams_common only load bean definitions from tools defined in the org.lamsfoundation.lams.tool* domains. I was using a different domain for my toy tools. I just had to add a new line to match the domain of my tools.

Could this be added to the documentation for the ToolBuilder?

After resolving the bean issue, there is still a problem with an exception while getting the content for the cloned tool (ContentId = ?).

This is resolved by changing my organisation name to "lamsfoundation" - AND I have a working cloned tool .

I guess there are some remaining assumptions about the organisation name.

I will investigate and follow up with all the places I can find where assumptions are made about the "lamsfoundation" domain.

cheers,
glenn.

PS. Thanks for a great learning tool.

Posted by Glenn Moloney

By: Luke Foxton

[ Reply | Forward ]

Hi Glen!

Looks like you found the found the source of the problem... Thanks. The ToolBuilder was done almost two years ago now and unfortunately it appears to be out-of-date. Since 2.3 and our performance improvements, the tool's hibernate objects have been referenced in the central BeanRefContext under the org.lamsfoundation.lams.tool* path, so changing that path kills them.

This will be added to the documentation.

Many thanks for notcing this problem,

Luke

Posted by Luke Foxton

By: Luke Foxton

[ Reply | Forward ]

Also,

You may notice in commonContext.xml there is a reference to the hibernate files for all the tools. Like so:

<value>classpath*:org/lamsfoundation/lams/tool/**/**/*.hbm.xml</value>

You will need to add another line here like this one changing "lamsfoundation" to your vendor name.

Luke

Posted by Luke Foxton