|Re: Eclipse Scout Roadmap [message #908662 is a reply to message #908462]
||Wed, 05 September 2012 18:57
| Tore Van Grembergen
Registered: August 2012
Good tutorials on the items mentioned (reporting, rule engine, proces flow, esb) would (in my opinion) have for a consequence that you as a company need to make a selection on these. The workload involved for documentation, creating examples etc would be forcing you to make a selection on these items. Even if available resourcing would be unlimited, it is nearly impossible to document several possible solutions on these items. Hence the selection proces itself would have been done, and I think for most developers this would already give a kick start.
The documenting of the use of the mentioned items would force you to look at the Scout environment as a full solution for modern development techniques.
Personally I think that the days of developing everything yourself are gone. You need to have a fully integrated platform allowing you to create a UI, put business logic in a combination of ruling engines and proces flow engines and glue different systems to each other with an "ESB" like tool.
The uses cases should focus in this setup to demonstrating the combined strength of the platform.
- The Scout Platform allows for getting very easy from the user interface to the server.
- At the server you could put complex validation / calculation rules in the ruling system.
- Once validations have been done, an approval proces could be started by the proces flow engine
- part of the approval proces could be publishing information on a webservice. As we are not sure if the webservice is available we put the information on the ESB who is acting as a local proxy with a message queue in case the service is unavailable.
Take the following example
You need to create a transportation from a warehouse to other warehouses.
First step create transport and add delivery notes to it.
Second step : calculate routing based on the delivery notes you have added to the transport you created. -> this would be executed by the ruling engine.
Third step : request delivery slots in the different warehouses and update status of the delivery notes -> this would be executed by proces flow in combination with the ESB
Fourth step : if necessary re-calculate routing based on the delivery slots obtained from the warehouses.- > this would be executed by the ruling engine.
Fifth step : inform the initiator of the transport that the transport is ready for dispatching and request approval -> this would be executed by proces flow
This example is something that can be done with Scout in combination with some tools and shows the strength of the total platform.
With regards to the products I would recommend : I am still myself in the "pain" of doing the selection.
For the moment it looks like i would consider a combination of Scout with for
- reporting :Jasperreports
- rule engine + process flow : drools
- ESB like : camel in combination with Active MQ.
As said I am still in the proces of putting the puzzle together on the platform I need.
I am also stil trying to figure out what would be the best way to approach the DB : the traditional way via SQL statements or with something as Hibernate.
Lastly what realy would be a big help is the autogenaration of the base screens based on the database layout (or object layout if hibernate is used).
For each of table or object you need to create maintenance screens, having these created automatically for most part would drastically improve development performance.
Powered by FUDForum
. Page generated in 0.03133 seconds