Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Mango Src
-
What version of Eclipse do you use to compile the src?
I have tried Eclipse 3.6.0 Classic and the latest version.
Also tried NetBeans but no luck. There are many errors generated that I have tried to work through but I can't seem to make any progress. A list of Jar libraries and versions would be a great help too if you have one because some of the current jar library downloads seems to have depreciated some function calls.My goal is to try to get something working with BlackBerry web access as the current version 1.9 does not display data on the browser.
thanks,
OldSmokey -
You can follow the steps below for building Mango:
(Thanks to Andras)
-get Eclipse IDE for Java EE Developers (I'm using "Eclipse Helios release")
-get Mango source code, unpack it (into your "workspace")
-add empty subdirectories lib, src_gen and src_test to Mango source folder
-in file build.properties, edit tomcat.home to point at the tomcat location on your system. For windows, make sure forward slashes "/" are used in the tomcat.home path
-In Eclipse choose import --> Existing projects into workspace --> browse to the mango source folder
-Remove the last WDSL related part of the build.xml as well. It's not needed for the "deploy" build target.
-right-click build.xml in the project explorer and choose run as->2.ant-build... -> choose the createconfigfiles target and run.
-right-click build.xml again and choose run as->2.ant-build...
choose the default deploy and run.That's it, your brand new Mango will be placed into tomcat_dir>/webapps/test
Regards
-
Welll not long after I had placed the post I had discovered that I was missing the env.properties file under classes. So I copied it over from the working web installation and things began to happen as expected. That was a couple of weeks lost trying to figure it out and it is my fault that I did not ask the question earlier. I did learn that checking the "choose the createconfigfiles target" checkbox also fixed the problem so many thanks for your reply. Life is good now. :D