Upthrust

I’m planning to retire this domain and I have a new blog at milinda.pathirage.org.

Emotional intelligence (EI) is an ability, skill or, in the case of the trait EI model, a self-perceived ability to identify, assess, and control the emotions of oneself, of others, and of groups.

In following video Daniel Goleman discusses his book “Social Intelligence: The New Science of Human Relationships” as a part of the Authors@Google series.

It’s one thing to make the same mistake twice. Another thing to make it all of your life.

Sometimes, the best way to teach people how to get up is by letting them fall down. Sad to say, we don’t really know what’s best for others… and the best way to love them is by letting them be where they want to be…

Original Post

If you follow the below steps Mac OS X terminal app will open in fullscreen mode from that point onwards.

• Open Terminal
• Maximize the terminal window
• Go to ‘Shell’ -> ‘Use Settings As Default’

Steve Jobs does it right, famously saying, “Design is how it works, not how it looks,” but most firms copy his aesthetics and not his philosophy, applying design merely as marketing gloss in order to capture additional sales.

Read more….

WSO2 Carbon Studio team recently released 1.0.5 version of WSO2 Carbon Studio which is the fully functioned tooling environment which facilitate you to develop, test, deploy and test WSO2 Carbon Artifacts. WSO2 Carbon Studio is a collection of Eclipse plugins developed by WSO2 and available as open source distributions from third party vendors.

This release includes various new features and bug fixes for Carbon Studio components. This release also includes a BPEL editor fix which solves the BPEL process modeling issues when Carbon Studio installed in to Eclipse Helios.

You can download the new release from here.

Related Posts

• Developing BPEL processes using WSO2 Carbon Studio

With the recent advancements in cloud technologies some people think that cloud will solve their scalability issues and it’s easy to achieve scalability using available cloud technologies. But it’s not true. Building scalable systems are hard, you need to understand what your problem is and you need to plan your scalability architecture based on that. Cloud technologies will make your life easier to some extent, but depending on your requirements you may have to go for your own data center. And cloud is not the solution for every problem at hand.

So before architecting for scalability you need to understand your problem and the methods people already use for solving different scalability issues. This post from Will Larson introduce you to the world of architecting IT systems for scalability. This is a good read for beginners as well as experienced developers you want to make their systems scalable. In this post Will discribes load balancing, caching, off-line processing and platform layer concept which are the most fundamental mechanisms of achieving scalability. I must say that this post is just a introduction and there are lot of details behind scalable architectures.

Waruna and I conducted a webinar session on 17th March 2011 to demonstrate how you can develop BPEL process using WSO2 Carbon Studio. In this webinar we walked through the  complete development life-cycle of a BPEL process using WSO2 Carbon Studio and how you can deploy the process developed to the WSO2 Business Process Server through WSO2 Carbon Studio. You can find the webinar video here.

Web Service orchestration and composition can be consider as the main use cases of WS-BPEL. In both cases Web services from external parties or from different systems of same organisation are involved and interact with each other to provide the service(here I am considering process as a service we offer) described by WS-BPEL process. So there should be a way to model this relationship between BPEL process and partner services.

Figure 1

WSDL already provided the requirements which needs to describe service provided by a partner via port types. Partner link type concept in WS-BPEL extends the WSDL to define this relationship between partners and processes. In typical scenarios process it-self can be a service provider for some partners(clients of the process) or service consumer in other partner relationships. And partner link type binds  two port types; port type process offeres(myRole) to a partner and port type partner offeres(partnerRole) to a process. Figure 1, shows several partner links and their relationship with port types. If you consider ‘invoicing’ partner link, the process offer invoicingCallbackPT to it’s partner invoicing service while the partner(in this case invoicing service) offer computePricePT to the process. This partner link describes a asynchronous interaction among process and invoicing service.

Figure 2

Partner link can be think of as a instance of partner link type and partner interactions are modeled using partner links in WS-BPEL process. Above diagram Figure 2 describes the relationship between ‘Partner link type’ and a ‘partner link’. Partner link type is different for synchronous and asynchronous interactions, where we have only one role for synchronous interactions due to their uni-directional nature and two roles for asynchronous interactions. You can find more information from WS-BPEl specification and section 2 of BPEL Light paper. This partner link concept is the main concept which allows asynchronous communication between partners take part in business process.