Comments on: Engroup 1.5 Milestone 1 released http://blog.esofthead.com/engroup-15-milestone-1-released/ The official blog of eSoftHead Company Mon, 15 Aug 2011 06:45:57 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: admin http://blog.esofthead.com/engroup-15-milestone-1-released/comment-page-1/#comment-103 admin Tue, 09 Jun 2009 14:21:07 +0000 http://blog.esofthead.com/engroup-15-milestone-1-released/#comment-103 @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. @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.

]]> By: admin http://blog.esofthead.com/engroup-15-milestone-1-released/comment-page-1/#comment-100 admin Sat, 06 Jun 2009 09:21:44 +0000 http://blog.esofthead.com/engroup-15-milestone-1-released/#comment-100 @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 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 :) .

]]> By: xie http://blog.esofthead.com/engroup-15-milestone-1-released/comment-page-1/#comment-98 xie Fri, 05 Jun 2009 02:59:45 +0000 http://blog.esofthead.com/engroup-15-milestone-1-released/#comment-98 i modify the JSPWiki.policy in folder wiki/web-inf but no effect.and i try [{ALLOW view admin}] in page no effect too. i modify the JSPWiki.policy in folder wiki/web-inf but no effect.and i try [{ALLOW view admin}] in page no effect too.

]]> By: xie http://blog.esofthead.com/engroup-15-milestone-1-released/comment-page-1/#comment-97 xie Thu, 04 Jun 2009 09:59:12 +0000 http://blog.esofthead.com/engroup-15-milestone-1-released/#comment-97 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. 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.

]]>