Engroup 1.5 Milestone 1 released
eSoftHead is pleased to inform that Engroup 1.5 M1 of our Java/AIR groupware product has been release. You can download it at http://esofthead.com/node/25.
According to the Engroup 1.5 roadmap posted at http://blog.esofthead.com/engroup-15-roadmap/, the new features of Engroup 1.5 M1 are as follows:
- Upload single/multiple contents.
- Download single/multiple contents.
- Categorize contents via document type, status, and tag.
- Display simple transaction view.
If you want to view some screenshots before trying Engroup 1.5 M1, you could check them at http://www.flickr.com/photos/34441795@N06/sets/72157616946782473/. Besides adding Document Management module, Engroup 1.5 added some technical features:
- Improve caching by utilizing ehcache API that manages session-like variables.
- Utilize system resources and improve system responsive time by using Threadpool and asynchronous invocations.
- Engroup 1.0 promotes modular architecture by using Osgi event library to exchange messages among its modules. This approach does not persist messages if the server is down. Engroup 1.5 embeds messaging server (ActiveMQ - http://activemq.apache.org/) to provide persistent message and enterprise integration provider features
- Engroup 1.5 embeds a lightweight enterprise service bus - Spring Integration library. It applies Enterprise Integration patterns to establish message channels (direct, publish-suscribable) to exchange/transform messages among channels.
- RESTeasy is used to enable REST support to integrate data between third-party and Engroup.
All your suggestions/comments will be highly appreciated. Please do not hesitate to drop some lines to us at info@esofthead.com.
hi,i have some questions.
1.how to create wiki page in engroup.or only for ie foxfire
2.why your choose ibatis not orm like hibernate.
i modify the JSPWiki.policy in folder wiki/web-inf but no effect.and i try [{ALLOW view admin}] in page no effect too.
@Xie Here are my responses:
1. Create wiki page in engroup: simply click ‘Edit’ link page in the wiki page (for example: main page). Engroup embeded jspwiki, and you can follow guidelines of using jspwiki syntax. You do not need to do any extra tasks.
2. We choose iBatis due to several reasons:
+ Performance: iBatis has far better performance than Hibernate.
+ Complex SQL query: we use many complex SQL query. So a SQL map is better than ORM. If we use Hibernate we must use HQL, it is not necessary while we can use SQL and not sacrifice application performance.
+ Flat POJO: Hibernate causes cycle dependency among data objects (one-one, many-one, many-many, one-many), and data objects could be exchanged among applications, protocols (XML format – Web services, REST or remote object). Lazy loading collection objects in Hibernate causes our frameworks could not resolve data objects in runtime.
Moreover, though Hibernate is easy to use but iBatis is as simple as Hibernate. Though Hibernate is excellent tool but I prefer to use iBatis in our application due to above reasons. But all my clients prefer Hibernate over iBatis due to other reasons
. So we only can use iBatis in Engroup only 
.
@Xie thanks for discovering, I found that wiki module is broken due to developer has merged the code in branch to trunk incorrectly. We will update the build very soon. With the new build (I will inform to community when it is available), end user does not need to do anything (one main goal of engroup is reducing administrator effort) to make engroup module works like I answered above.