Michael,
Looks like the Presto Mashlet Hub has failed to initialise itself correctly.
Can you try the following:
Locate the presto.config properties file, which you will find in
<jboss web apps dir>/presto/WEB-INF/classes/presto.config
In this properties file there should be an entry named mashlets.path, the value of which should be the absolute path to the expanded mashlets directory, so for example on my local tomcat installation it says:
mashlets.path=C\:\\Program Files\\JackBe\\Presto2.6.2\\server\\apache-tomcat-5.5.20\\webapps\\mashlets\\
Delete this line and then restart JBoss, Presto should then detect it is missing and
should be able to work out where the mashlet directory is and add the mashlet.path entry to presto.config again, pointing to the correct directory.
If this fails then you can just set up the path manually.
There is some info on this JBoss install issue in the documentation here:
http://www.jackbe.com/prestodocs/v2.7.0/prestoadmin/wwhelp/wwhimpl/js/ht...
Good luck
I copied my instance of jboss including presto and gave it to someone else to load on their computer. He is running into the same problem of "Mashlet directory not found." so we tried the steps above. We removed the path from presto.config and restarted, it never re-added that path. So we configured it manually and still no luck. Any ideas? It works fine on my computer, the only difference in the path name is /Users/<userid>/....
Hi,
This is the link to the documentation on how to deploy mashlets on JBoss. There is one more step. Apart from taking care of the the mashlets.path, you should also change the webApproot if not already done. Could you please check the same and make required changes.
Let us know how it goes.
Installed Presto 2.6.1 on another machine and moved my mashlets.war directory over to it. I'm running Presto in JBoss, fyi, and have had no problems with any other setups of 2.6.1. In fact, I normally just copy everything from my main machine to whatever machine I need, lock stock and barrel and this works fine for me.
When I attempt to create a mashlet from type, however, I get a stack trace on the console and the following error in the mashlet builder:
Mashlet directory not found.
The stack trace is attached as error.txt.