Fred Aabedi

Fred Aabedi is currently working at Sun Microsystems, Monrovia CA and is responsible for the architecture and development of the JBI Binding Components in addition to the JavaCAPS adapters. He is also responsible for promoting the JBI Ecosystems and signing up and working with Open Source contributors that will contribute to Open JBI Components. He came to Sun through the acquisition of SeeBeyond where he worked on and managed architecture and development of adapters and addon products for the eGate 4.x, and ICAN 5.x Suite of products. At Sun, he continued to be responsible for architecture and development of adapters and addon products for the Java CAPS Suite of products and for the architecture and development of JBI Binding Components and related netbeans tooling. He is also responsible for building a community of Open Source Contributors/partners to Open ESB and JBI. He also has a blog on blogs.sun.com.

Articles

j1-2k8-mtT01: Enabling Semantic Web Technologies with JBI
Semantic web is a way to represent and manipulate informations that allows very high flexibility on the way the information are aggregated, accessed and presented. To leverage existing information base we need ways to get these information and translate them into a semantic form. There many standard ontologies broadly accepted like FOAF (for representing person data and person relationships), DOAP (for representing project data), Dublin Core (for representing document data) etc.... The act of transforming information from a proprietary format to a semantic representation is called rdf-alization. An ESB JBI can be the right integration middleware to perform this task because it can easily collect data in proprietary format from different sources and, by redefining rdf-alizers as JBI component, can feed semantic web enabled application. May. 13, 2008

j1-2k7-mtT13: Legacy Integration Components Under Open JBI Components From a Partner
JBI is a specification for the integration, it provides a standard for building integration projects, just as EJB provides a standard for transactional projects. One of our open source partners who has contributed several JBI binding components is here to present their views about JBI and JBI components. We think that for JBI to have broad acceptance there must be a way first of all to build bridges with existing application and services. Aug. 22, 2007

java.net RSS Feeds