Describe the problem
As you know the ERP is so complex, and I need best practice.
Well, the concept of
ERPis quite flexible - run any system through marketing and it will turn out
If you really are writing a largeish piece of software the recommendation is the same regardless framework/technology - hire people with experience.
http://www.nuxeo.com/en/ has Enterprise in the name and is written with Seam
:D :D Thanks a lot Nicklas, I've a bit experience on ERP development based on Java EE or previously J2EE (about 6 years). You are right, I'm talking about an ERP with following features:
Our product is as same as http://ofbiz.apache.org/feature-list.html and a bit more, the development plan is about 5 years. I meant this ERP.
I was seeking for Jboss Seam in Gartner, I've not found anything, if there's one please let me know. Besides, we are talking about 1'000 concurrent users and the data center is on HP blade servers. The company that they need this ERP solutions, they are one of the biggest manufacturer of Home Appliance in Middle East.
I believe the 2.1 series has (and will) do work on clustering. Profiling under load tests should reveal bottlenecks. You don't want to develop for 5 years only to find some fundamental flaw in the architechture when the doors are opened, anyway ;-) If you follow general performance guidelines I don't think there is any showstopper that would prevent the application from being Seam-based.
I would have thought that developing in-house ERP:s are rare nowadays. OK, SAP consultants can bring down most companies but there are other alternatives. Of course, if their need are special...
Nicklas, just as you are seam expert, hence would you mind to give me some Seam weak points? Of course if there is some. Or in a better way how do you offer me to use Seam? Is there any tip and tricks? Please check out the following URL and let me know because I'm going through Seam like this URL:
Farid, as our language (halet khube? :D) I've checked both one is in French and I did not understand what sore of ERP is. The other actually is not ERP is just HRM.
expertis an overstatement - I have only little experience with the core packages, just making general statements ;-)
It could be worth searching the forum (and site) for
performanceas it will probably turn up some tips as I believe that knowing how to bypassing interceptors in the right places etc. can be good (if applicable).
Chris, we're using Seam to develop a platform for rapid design of ERP-centric applications. We aren't in the list 'cause we do that in spare time and we're quite far from publishing.
From my perspective Seam have more advantages than disadvantages. It is certainly worth considering.
One disadvantage of the whole Seam + JSF platform is inability to generalize existing UI code with ease. And some pain for novices when troubleshooting problems related to combination of Facelets tags with JSF components. I would recommend to think once again when making decision to choose JSF.
The second disadvantage of Seam is implementatoin of the Leaking Abstraction Law. (Probably it is related to every OSS java project in the world.) Simple tasks are solved with ease for the first time. Once your progect has grew up to mature one you would find yourself in demand to know the implementation details. Some big area are Seam conversation model along with Seam persistence and Seam security. I think this disadvantage is brought by the ability to solve the same task using many approaches in Seam (and each of them has shortcomings or pitfalls). The Seam Refdoc can't cover all the cases.
If you can cope with those disavantages and your team has at least one experienced guy with strong problem-solving skills - you'll love Seam :)
I would recommend to consider Seam + Wicket 'cause the latter has already got a RAD framework (Wicket RAD) which is a pain to design for JSF but is must-have in ERP applications.
That was nice article, thank a lot. Just please check the following URL
http://www.chrisshayan.com/my/index.php?option=com_content&view=article&id=57:iparadise-development-framework&catid=38:iparadise-development-pattern it was what I've done before.
Right now I’m just thinking about how I could do following items:
1) Liferay is very well, but I want to have much more alternatives such as : Jboss Portal or Jahia,
2) I want to replace Struts by JSF, I’m looking for ICEfaces, myFaces, and …
3) I want to replace Spring-core by Seam,
What's your idea? Besides, let's discuss about ERP that you've mentioned. I'm totally keen on it.
please check the following URL http://www.chrisshayan.com/my/index.php?option=com_content&view=article&id=57:iparadise-development-framework&catid=38:iparadise-development-pattern it was what I've done before. Right now I’m just thinking about how I could do following items:
1) Liferay is very well, but I want to have much more alternatives such as : Jboss Portal or Jahia, 2) I want to replace Struts by JSF, I’m looking for ICEfaces, myFaces, and … 3) I want to replace Spring-core by Seam,
Nicklas, I'm not talking about performance tips.