In the OBA demo Part 1 we could see how we can build component-based applications by OBA Composition Reference Toolkit. But these are only the base things - these are really important, as in a building, but we can't move in yet. We're really happy to have it ready, it's an important step to our goals - so let's go away! Well, in the following demo I'll present you how we can build the next phases of our OBAs, what kind of possibilities we have, and what are the limitations.

So, let's see some interesting possibilities in the OBA Composition Reference Toolkit's currect version. For example, if we'd like to add further components to our existing OBA, we have more possibilities. First, we can choose a component from the filterable list (see OBA demo - Part 1).

Second, we have a chance to search for some related, compatible componets to our existing components (Related Components). We can do this, because we can define some interfaces to our OBAs, so they can communicate with others.

(Click on the picture for the short demo.)

That's good. But in this version we have a small trouble with this method. We create an OBA with related SharePoint site, then upload some content or make some customization. After that we'd like to add a new component, with a new Provisioning - we can do that, but all of the former contents will be lost! The OBA Composer will overwrite the full site. It could be really cumbersome. But here is a good news: we'll have a new version soon with incremental provisioning!...

Our house has its walls already. Let's go forward...