Difference between revisions of "Stardust/FAQ"
|Line 82:||Line 82:|
Revision as of 09:13, 20 October 2011
What is the Eclipse Process Manager / the Eclipse project Startdust?
Where did Stardust come from?
Who is building commercial products based on Stardust?
How is Stardust licensed?
How can I get help?
Can I get commercial support?
On which Java versions can I use Stardust?
Does Stardust work on IBM's JDK?
Which Application Server does Stardust support?
Which Databases does Startdust support?
Which environments can Stardust run in?
Can I use Stardust from a .NET environement?
Bug Reporting & Contributing
How do I report a bug in Stardust?
How can I search the existing list of bugs in Stardust?
How can I contribute to Startdust?
Build, Dependencies & Source Code
How can I get the source code?
As a regular part of the project incubation phase the source code is currently under review by the Eclipse legal team. It will be published when the legal review is completed. Check for the latest news on the Stardust main page.
What are the dependencies?
How do I get acces to the Maven repository?
For the time being, please procure an account as described here.
What jars do I need for a Java Client?
Please check the product documentaton chapter suitabel for your environment (Spring, EJB). Maven POM files to generate a client project will soon be added to the maven repository.
What languages are supported?
The supported languages are English, German, Simplified Chinese and Japanese.
Can I get Stardust in another language?
A: Stardust's portal, error messages and Eclipse plugins are fully i18ned and can be translated by anyone into additional languages. One only has to create and translate the corresponding resource bundles. We found a convenient way to do this using excelbundle and create a script to make the rountrip (translation-update-review-adjustment) easier. This way also non technical people can work on the translation in an Excel sheet.
How can I prevent OutOfMemoryErrros on Tomcat?
The default Tomcat settings (in a RAD scenario) do not allocate much memory. Hence the application may run often out of memory quite frequently. The console log will often throw a java.lang.OutOfMemoryError exception. To avoid this, just add a different memory settings in the Tomcat launch configuration:
Servers > Open Launch Configuration > Arguments > VM arguments > at the very bottom add >
-Xms128m -Xmx512m -XX:MaxPermSize=128m
On a standalone server (outside eclipse RAD environment) start tomcat using:
set JAVA_OPTS=-Xms128m -Xmx512m -XX:MaxPermSize=128m
How to change the default port on Oracle XE?
c:\> sqlplus '/ as sysdba'
SQL> EXEC DBMS_XDB.SETHTTPPOR SQL> SELECT dbms_xdb.gethttpport, dbms_xdb.getftpport FROM dual;T(8081);