Are You Adapting Your architecture TO suit a vendor??? Learn how to find a vendor who adapts to your architecture?

Countless vendors, including proprietary middleware industry giants like IBM and Oracle, and open source platform companies like WSO2, have built products that enable SOA to varying extents.

But no middleware product has taken a componentized approach to their own middleware “silos”. The features and functions of each middleware product have been predetermined by the vendor’s software designers, not built to each individual customer’s specification.

WSO2 is presenting this nice little article and explaining how we can benefit by using there all new componentized Carbon as a solution for this problem.
http://wso2.org/project/carbon/making_good_soa_great.pdf

Content

Componentization reaches enterprise it

The need for modular middleware

Use case base explanation

Painless service creation & integration

Set the pace of your SOA adoptions

WSO2 Carbon: the evolution of middleware

Comments

Overriding default look and feel of GREG - 5.3.0

Following list explains what are the best approach for different use cases. 1 ) - You created a new asset type, and you need to change the look and feel of the details page in the listing page just for that new asset type. To create a new asset type you need to login to the carbon console (username:admin, password:admin) https:// :9443/carbon/ Navigate to Extensions > Configure > Artifacts Click "Add new Artifact" link at the bottom of the page. By default in the "Generic Artifact" area "application" asset type is loaded. Note the shortName="applications" in the root node. "applications" is the name of the asset type. Browse in to /repository/deployment/server/jaggeryapps/store/extensions/assets Create a folder with name "applications" Now we can override the files in /repository/deployment/server/jaggeryapps/store/extensions/app/greg-store-defaults Since we are overriding the details page we need to...

Using javascript to Include a html file inside another html file

When there is no server side functionality needed we create the whole site in plain html. Usually these sites have left/right side menu, top header, footer etc.. If the site grows in to 20, 30 pages, it will be a headache to do a simple change like changing footer text. We will have to change each page. If we were using a server side technology like PHP, JSP, etc.., we will have the chance to keep the common areas in the site in different pages and include these parts in each page using a “include” statements. We can do the same thing with the plain old html and javascript. But how? First you need to create the site main layout using divs and give them unique ids. <html> <title>HTML Includes</title> <script language="javascript" src="js/main.js"></script> <script src="js/prototype.js" type="text/javascript"></script> <script language="javascript" xml:space="preserve"> // <...

Projecting HTML Elements on a circle using Javascript

Recently I wonted to create a tree control with a different approach. The requirement was to represent a node tree with main node on the circle center and it's child nodes projected on a circle around it. This is what i wanted. My solution has 5 files prototype.js This is a handy javascript framework. You can download the latest version from there website ( www.prototypejs.org/download ). I am using this to simply handle the onload event in the page. circle.html script.js node-main-left.gif node-sub-left.gif The circle.html, prototype.js and the script.js files are in the root folder and the two images are inside a folder named “images”. This is how the html file looks(circle.html). <html> <head> <script src="prototype.js" type="text/javascript"></script> <script src="script.js" type="text/javascript"></script> <script language="javascript" xml:space...

My Notes

Search This Blog