Friday, December 29, 2006
Teamwork and technological updates
Teamwork's best year so far is ending; we finally had a little time to breathe, so in this days we have been refining Teamwork interface and updating the underlying technology: now Teamwork runs fine on JDK 6, and on Hibernate 3.2. We also switched to c3p0 connection pool technology, and updated the Install4j to version 4. In a following post we will share our ideas concerning web interfaces and the novelties introduced by Ajax. We have also first alphas of next release, with the Outlook synch module, which will surely be part of it, and a new testing framework; we will soon launch a "vote for features", as done for version 3, to fix the priorities.
In the meantime, Teamwork's customers are growing at good pace. Interesting is that the JavaBlackBelt community too is using Teamwork for their management.
In the meantime, Teamwork's customers are growing at good pace. Interesting is that the JavaBlackBelt community too is using Teamwork for their management. Labels: java
Thursday, December 07, 2006
Teamwork and web services
We can now supply any Teamwork API through web services, by using Apache's Axis. Axis is surprisingly simple to use; we tested stubs from Java and Word's VBA, and works like a charm. You can satisfy wild needs, like having in Word the list of Teamwork's open tasks.
This can be particularly useful for Teamwork with workflow, and using web services to push and pull info on external services. We plan to give more visibility to the workflow suite in the next months, and how nicely it can work bundled with Teamwork.
This can be particularly useful for Teamwork with workflow, and using web services to push and pull info on external services. We plan to give more visibility to the workflow suite in the next months, and how nicely it can work bundled with Teamwork.
Labels: web services, workflow
