Process Orchestration with Morfik

The ease with which you can create an appealing Web based application interface with Morfik makes it an ideal tool for rapid prototyping.  It is possible to go from scratch to a full application interface in the space of a few hours.

When you combine this with the ability to easily import Web Services you have the makings of what could become a powerful tool for process orchestration.  Morfik makes it very easy for you to write your own Web Services and tends to make the usage of third party Web Services. These capabilities can combine to make it a prime environment for putting creating applications that provide the glue for creating useful applications out of Service Components.

I am quite confident that the same team that made Morfik a great visual design environment for creating sophisticated interfaces could surprise us with the ability to visually design the interaction of Web Services with one another and with the application's browser side components.   This would move Morfik one step closer to enabling even non-developers to create useful Web applications.

Making the case for anonymous methods

I don't know about you, but I make a lot of use of WebMethods when developing a less than trivial Morfik application.  WebMethods are extremely useful and actually quite easy to use, once you've got the hang of it. Depending on how much and what kind of information you want to exchange between your browser and server code, it can as simple as just invoking the RunWebMethod procedure.

One thing always leaves me with the feeling that I'm missing something, though.  When you are using a Web Method from an imported Web Service, or even one of your own that requires more and more complex parameters, you end up having to use a callback to handle the method's return.  I have no problem with the concept there, but the implementation could be easier to write.  Wouldn't it be nice if you could just type your code for handling the method's return in line with the method invocation?