Support Forum

[admin]

TrackStudio 2.5 beta1 released. This release supports Jetty, Resin, Tomcat, JRun4, MySQL, and more. It has a new hibernate-based persistence engine and full i18n support with English and Russian localizations. It's easy to configure, install, and use. Also, please check out our new pricing http://www.trackstudio.com/products-epricing.html

1) Download 90-day trial http://www.trackstudio.com/tse-25/TSE-25b1.zip (6.5MB)

2) Edit etc/trackstudio.*.properties, please ensure that upload directory exists and siteURL correct.

3) Create database from script in sql. Please refer http://www.trackstudio.com/documentation.html for more info

4) Start your application server with -Dtrackstudio.Home=<path to
directory with .properties>

5) Deploy .war

6) Login as root/root

Also, you can add properties files to WEB-INF directory of war (you should not use trackstudio.Home this way).

This version should support all application servers and DBMS as 2.2 plus
Jetty, Tomcat 4.x, Resin, JRun4. Also we add experimental mysql support (InnoDB required).

If you can test our application with (but not only) Sun ONE, WebSphere - please notify us about your experience.

WARNING:
Please note that this is early beta version. We does not provide
data migration to/from this version. Please DO NOT USE THIS VERSION
in production environment.

[awaragi]

Maxim,

I had installed this beta application in no time including the setup of JRun server, datasource connection, fixing the properties files and running the mysql script (total time: 10 minutes). The only issue that I had was with the mysql version which does not support foreign keys so the last few sql statements gave errors. Given that your code should check for data constraints without depending on the database to throw exceptions, I assume that it should work just fine even without database constraints.

My first impressions are the same when I saw version 2.2. Not much of change to the user interface but definitly happy to get the application running on JRun/Mysql.

The only recommendation that I have right now is the way I would setup the Trackstudio*.properties files is via classpath rather than -D parameter use
---------------------------------------------------
Properties p = new Properties();
p.load(this.getClass().getClassLoader().getResourceAsStream("Trackstudio.properties"));
---------------------------------------------------


I will do more testing of the application but you are definitly on the right way of true java universal application.

Pierre.

[admin]

I had installed this beta application in no time including the setup of JRun server, datasource connection, fixing the properties files and running the mysql script (total time: 10 minutes).

OK, great. We also plan standalone version such as in 2.2, very easy to install and use.

The only issue that I had was with the mysql version which does not support foreign keys so the last few sql statements gave errors. Given that your code should check for data constraints without depending on the database to throw exceptions, I assume that it should work just fine even without database constraints.

You should use InnoDB with mysql. This is because foreign keys required - we use hibernate for persistence and its difficult to implement right cascade delete without foreign keys. Without FK many problems with referential integrity possible after you delete used category or workflow.

My first impressions are the same when I saw version 2.2. Not much of change to the user interface but definitly happy to get the application running on JRun/Mysql.

Yes, we plan add only very minor changes to user interface in 2.5, but some interesting features will be available in 2.5beta2 (start of next week).

The only recommendation that I have right now is the way I would setup the Trackstudio*.properties files is via classpath rather than -D parameter use
---------------------------------------------------
Properties p = new Properties();
p.load(this.getClass().getClassLoader().getResourceAsStream("Trackstudio.properties"));
---------------------------------------------------

We has troubles this way with Weblogic - they can't load properties from /WEB-INF/classes in .war.
Please note, that you can delete -D and just put .properties to WEB-INF directory.

I will do more testing of the application but you are definitly on the right way of true java universal application.

Thank you !

[osmedd]

I saw the same problems getting the foreign key definitions accepted in Mysql. The tables got setup correctly as InnoDB (I'm running mysql 4.0.12) but I still get syntax errors on those foreign key constraints. I keep meaning to go and figure out what the right syntax would be but I haven't had time yet.

I was very impressed by the documentation and hope to have the demo up and running here soon.

[osmedd]

Okay, I took a few minutes and looked again at the mysql schema. There appear to be a couple general problems.

First, the foreign key constraints don't seem to include the second index column name. For example, one is "alter table GR_CATEGORY add constraint F_CATEGORY1 foreign key (category_task) references GR_TASK;". By adding the second column index name (I'm guessing it shoudl be task_category) to this ddl (first adding the task_category index to GR_TASK of course) it adds the constraint.

So... in summary... to get the first foreign key alter to work I did:
alter table GR_TASK add key itask_3 (task_category);
alter table GR_CATEGORY add constraint F_CATEGORY1 foreign key (category_task) references GR_TASK (task_category);

Does this seem correct?

[admin]

First, the foreign key constraints don't seem to include the second index column name. For example, one is "alter table GR_CATEGORY add constraint F_CATEGORY1 foreign key (category_task) references GR_TASK;". By adding the second column index name (I'm guessing it shoudl be task_category) to this ddl (first adding the task_category index to GR_TASK of course) it adds the constraint.

Yes, you right. We already fix this problem and I just send new sql script to you by mail.

Also, we plan to release beta 2 tomorrow.

[osmedd]

Using the mysql schema that Max emailed me and fixing the uploadDir property which was causing servlet exceptions got me almost up and running. Now when I go to login, I get a new hibernate exception, which seems to be due to assuming that table names are case-insensitive. The error is: Hibernate lazy instantiation problem: General error: Table 'trackstudio.gr_user' doesn't exist. The table is created as GR_USER.

Did I miss some configuration switch which would fix this?

[admin]

Now when I go to login, I get a new hibernate exception, which seems to be due to assuming that table names are case-insensitive. The error is: Hibernate lazy instantiation problem: General error: Table 'trackstudio.gr_user' doesn't exist. The table is created as GR_USER.

Hmm, I think that SQL is case insensetive language...
Please send me your config files and full debug log

[osmedd]

Case sensitivity of table and column names differs on a database by database basis, while SQL reserved words are treated in a case insensitive manner. In general, it is recommended that you refer to the the tables in the same manner as which you create them.

MySQL utilizes case sensitive table names on Unix and Unix-like operating systems, but forces table names to lowercase (by default) on Windows and similar systems (these settings are generally based on the ability of the underlying filesystem to deal with mixed case filenames).

I guess I will try altering all the table names to lowercase.

[admin]

MySQL utilizes case sensitive table names on Unix and Unix-like operating systems, but forces table names to lowercase (by default) on Windows and similar systems (these settings are generally based on the ability of the underlying filesystem to deal with mixed case filenames).

Ok, thank you. I think that we'll resolve this issue in beta 2.