iFDP / News: Recent posts

We have just made a decision about iFDP SOA plan, choosing AXIS2 as the engine. This include 2 aspects:
1. Outer accessing iFDP component as Web Service through AXIS2
2. iFDP component accessing outer web service (transparently) through AXIS2

All info are location in http://www.myipnet.com

iFDP-plugin 1.0 is finished, need Eclipse and GEF support

iFDP first rough version is completed! include the core framework and the plugin!

The core framework's programming will be completed within two weeks. This version we need Database support for configuration, and the implementation is base on Hibernate.

This project (iFDP) aim to develop a FDP(Flow Driven Programming) framework. There are two parts in the project. First is the core framework, and another is a visual developing entironment, which is designed as an Eclipse plugin.
With its help, our developing can drive by our business flows. That means we can develop with the guiding of business flow directly. And then our modules can compose to a component more easily and quickly. We can detect the business flow and data flow in our system, so the system's bottleneck, the modules which need to improve and something like that can be found out more quickly and correctly.
Developing with iFDP, we can follow the following steps:
1. Define Flows. Each flow is made up of several modules, and the flow can also be a module, so the flow can contain other flows.
2. Define Bridges. Bridge is define as the data format transfer between modules.
3. Fill Module Code guid by our business logic.
Dates are moving, and the customer's requirements are moving much faster. And now what we need to do may only be draying the bridges. Of course, it is an ideal condition, but we all are dreaming all the time, right?