Eclipse Community Forums: Eclipse Scout » Architecture for large systems (e.g. ERP)

Home » Eclipse Projects » Eclipse Scout » Architecture for large systems (e.g. ERP)

Architecture for large systems (e.g. ERP) [message #1091645]

Wed, 21 August 2013 15:56

Eclipse User

Does eclipse scout fit well for large systems that have a wide bredth of functionality? For example, would scout fit well for writing something as large as Apache ofbiz?

If scout is fit suitable, how would one structure such an application so that you dont end up with a single huge monolithic application?

I guess one option would be to create separate scout applications for each functional area, e.g.

Party management
Order management
Financial management
Product management
Etc

The question would then become how do you link the individual applications? E.g. an order in the order management application will need to point to two entities in the party management component, supplier party and ordering party.

Re: Architecture for large systems (e.g. ERP) [message #1091972 is a reply to message #1091645]

Thu, 22 August 2013 02:56

Eclipse User

Hi,

[Short answer]
Have you read the different material we have on the topic (I agree it a little spread everywhere):

Multi-Module Applications (Creating modularised applications using eclipse scout) (by Ivan Motsch)
Multi-Module Applications (by Stefan Mutschler)
Tutorial: modular application [wiki]
Modular Application (How to create Modular application using Eclipse Scout) (by Yassine MILHI)

I hope this give you a start. Let me know if you need more informations.
We should synthesize all this know-how in a new concept page.

Re: Architecture for large systems (e.g. ERP) [message #1093902 is a reply to message #1091972]

Sat, 24 August 2013 17:39

Eclipse User

Thanks for the info Jeremie.

Extensions look like a convenient way of partitioning an application. The info in the links above gives me a taste of what can be achieved, however, I can't see how one would create links between extensions. For example, if I have an extension for Party (E.g. Customer) and an extension for Order, in orders I would like to be able to set references to the customer party.

Is there any more detailed information available on extensions, or a demo that shows how to create references between extensions? Ideally in the interest of modulariy, the Party database schema and the Order database schema should be separate schemes, and the party schema should not be accessed directly by the Order extension.

[Updated on: Sat, 24 August 2013 17:41] by Moderator

Re: Architecture for large systems (e.g. ERP) [message #1094773 is a reply to message #1093902]

Mon, 26 August 2013 03:05

Eclipse User

I knew my answer isn't as complete as it could be. It is a good thing to precise the topic.

In my opinion, what you are describing is possible, because a big commercial Scout Application developed at our company (BSI CRM) is going in this direction. Through services, Extensions can "inject" fields into existing form.

So I assume you could have a PartyForm in your core application (to handle let say persons). The Order management Extensions adds a list of the orders in this form if it is installed.

We definitively want to improve this topic with Eclipse Scout Luna: better SDK tooling, some runtime modifications (we will have some modifications in our formdatas), examples of what you can do (a small demo application would be great).

I am afraid there isn't any open source example yet. This is something we could work on, if you are interested.

Re: Architecture for large systems (e.g. ERP) [message #1094808 is a reply to message #1094773]

Mon, 26 August 2013 04:08

Eclipse User

Hi Jeremie - thanks for the response.

Where can I find some more information how to inject fields into an existing form?

Re: Architecture for large systems (e.g. ERP) [message #1095131 is a reply to message #1094808]

Mon, 26 August 2013 13:15

Eclipse User

We are currently building a multiple-module (12 modules to date) application that supports dynamic fields. We build our forms as usual in Scout and include an AbstractWrappedFormField as a placeholder for additional fields which are injected based upon a set of custom extension points that expose the appropriate sub-form. We support user-customizable dashboards in the same way. I don't have a good stand-alone example of this right now, but if I get a chance to put one together I will post it.

Re: Architecture for large systems (e.g. ERP) [message #1095164 is a reply to message #1095131]

Mon, 26 August 2013 14:24

Eclipse User

Hi Jason,

A standalone-example would be awesome!!

Many thanks,

Chris

Re: Architecture for large systems (e.g. ERP) [message #1100641 is a reply to message #1095164]

Tue, 03 September 2013 07:34

Eclipse User

Created bugzilla issue to track this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=416425

Previous Topic:	are there any plans to move wiki content to eclipsedoc format?
Next Topic:	scout kepler SMTP service bug?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 19:05:10 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter