The objective of this project is to enable seamless integration between webMethods and the jasper intelligence suite. It allows pixel perfect reporting solutions with complex data integration requirements to be developed in minutes.
Swizzle started out as some stream-based parsing code I've had sitting around for quite some time. Once the project was established, it became my dumping ground for all things of a swizzling nature; poking at or mucking with unprocessed or unusable data. Generally, to swizzle unconsumable data into a consumable form.
Obba provides a bridge from spreadsheets to Java classes. With Obba, you can easily build spreadsheet GUIs (Excel or OpenOffice) to Java code. Its main features are:
* Loading of arbitrary jar or class files at runtime through an spreadsheet function.
* Instantiation of Java objects, storing the object reference under a given object label.
* Invocation of methods on objects referenced by their object handle, storing the handle to the result under a given object label.
* Asynchronous method invocation and tools for synchronization, turning your spreadsheet into a multi-threaded calculation tool.
* Allows arbitrary number of arguments for constructors or methods (avoids the limitation of the number of arguments for Excel worksheet functions).
* Serialization and de-serialization (save Serializable objects to a file, restore them any time later).
* All this though spreadsheet functions, without any additional line of code (no VBA needed, no additional Java code needed).
For a more detailed introduction see the Obba documentation
Components
Obba is small.
Obba for Excel consists of three files (these files will be installed by an an installer Install Obba for Excel.exe):
* Obba.xla: An Excel Add-in providing workbook functions like obMake(), obCall(), obGet().
* Obba.dll: The bridge from Excel to Java.
* Obba.jar: The Java object handler and the Obba control panel.
Obba for OpenOffice consists of one file:
* Obba.oxt: The Obba Add-in including the OpenOffice adapter and Obba.jar (the Java object handler and the Obba control panel).
JSF Flex goal is to provide users capability in creating standard Flex components as JSF components. So users would create the components as normal JSF components and the project will create the necessary SWC, SWF files and etcetera and link the values of the components back to the managed beans using JSON+Javascript and Actionscript. {standard Flex components has been open sourced through MPL license}
Currently many of the standard rich flex widgets (buttons, sliders, inputs [richTextEditor, textArea, ...], progressbars, colorpickers, various panels [accordion, tabBar, ...], and etcetera) have been written as intention of support.
Teaser for an interesting book...
EAI - The Broader Perspective
No one should have (or will) ever dared to build a 'Single System' which will take care of the entire business requirements of an enterprise. Instead, we build few (or many) systems,and each of them takes care of a set of functionalities in a single Line of Business (LOB). There is absolutely nothing wrong here, but the need of the hour is that these systems have to exchange information and interoperate in many new ways which have not been foreseen earlier. Business grows, enterprise boundaries expands and mergers and acquisition are all norms of the day. If IT cannot scale up with these volatile environments, the failure is not far.
OW2 is a global open-source software community which goal is the development of open-source distributed middleware, in the form of flexible and adaptable components. These components range from specific software frameworks and protocols to integrated platforms. OW2 developments follow a component-based approach.
The consortium is an independent non-profit organization open to companies, institutions and individuals.
OW2 mission is to develop open source code middleware and to foster a vibrant community and business ecosystem.
OW2 is committed to growing a community of open source code developers. The organization is dedicated to the creation of new technology: original code development is one of its fundamental characteristics. As the organization becomes part of the open source marketplace, it also stresses the quality and market usability of its software. It fosters a common technical architecture to be shared by its members and to facilitate the implementation of its technology by systems integrators and end-users.
The OW2 projects aim at facilitating the development, deployment and management of distributed applications with a focus on open source middleware and related development and management tools. In the open source software value chain, OW2 is positioned as an industry platform facilitating interaction between open source code Producers and open source code Consumers.
The XAware project provides real time data integration with a service-oriented flavor. XAware makes other tools and frameworks much more productive by hiding data complexity behind "XML views". XML views span any number of data sources, and can read data, write data, or transfer data between sets of sources, all within a distributed transaction.
ChainBuilder ESB is Java Business Integration (JBI) compliant open source solution for use in Service Oriented Architecture (SOA) environments. ChainBuilder ESB's graphical integration enables new and older applications to easily enter into SOA.
Apache Camel is a powerful rule based routing and mediation engine which provides a POJO based implementation of the Enterprise Integration Patterns using an extremely powerful fluent API (or declarative Java Domain Specific Language) to configure routing and mediation rules. The Domain Specific Language means that Apache Camel can support type-safe smart completion of routing rules in your IDE using regular Java code without huge amounts of XML configuration files; though Xml Configuration inside Spring is also supported.
PEtALS is the highly distributed Open Source ESB hosted by OW2. PEtALS delivers OW2 JavaTM Business Integration (JBI) platform.
PEtALS provides lightweight and packaged integration solutions, based on JSR-208 specifications, with a strong focus on distribution and clustering.
Aspose.Words enables .NET and Java applications to read, modify and write Word® documents without utilizing Microsoft Word®. Aspose.Words supports a wide array of features including document creation, content and formatting manipulation, powerful mail merge abilities, comprehensive support of DOC, RTF, WordprocessingML, HTML and PDF formats. Aspose.Words is truly the most affordable, fastest and feature rich Word component on the market.
Mule is the leading open source ESB (Enterprise Service Bus) and integration platform. It is a scalable, highly distributable object broker that can seamlessly handle interactions with services and applications using disparate transport and messaging technologies.
Pulse is an automated build or continuous integration server. Pulse regularly checks out your project's source code from your SCM, builds the project and reports on the results. A project build typically involves compiling the source code and running test
Funambol is open source mobile application server software that provides push email, address book and calendar (PIM) data synchronization, application provisioning, and device management for wireless devices and PCs, leveraging standard protocols. For use