Axis2 - Apache Axis2/Java - Next Generation Web Services Apache Axis2™ is a Web Services / SOAP / WSDL engine, the successor to the widely used Apache Axis SOAP stack. There are two implementations of the Apache Axis2 Web services engine - Apache Axis2/Java and Apache Axis2/C While you will find all the information on Apache Axis2/Java here, you can visit the Apache Axis2/C Web site for Axis2/C implementation information. Apache Axis2, Axis2, Apache, the Apache feather logo, and the Apache Axis2 project logo are trademarks of The Apache Software Foundation. Why Apache Axis2: A new architecture for Axis2 was introduced during the August 2004 Summit in Colombo, Sri Lanka. Apache Axis2 not only supports SOAP 1.1 and SOAP 1.2, but it also has integrated support for the widely popular REST style of Web services. Apache Axis2 is more efficient, more modular and more XML-oriented than the older version. Apache Axis2 is built on Apache AXIOM, a new high performant, pull-based XML object model. We hope you enjoy using Axis2. Let us know what you think!
Java Business Integration Java Business Integration (JBI) is a specification developed under the Java Community Process (JCP) for an approach to implementing a service-oriented architecture (SOA). The JCP reference is JSR 208 for JBI 1.0 and JSR 312 for JBI 2.0. JBI is built on a Web Services model and provides a pluggable architecture for a container that hosts service producer and consumer components. Services connect to the container via binding components (BC) or can be hosted inside the container as part of a service engine (SE). The services model used is Web Services Description Language 2.0. In-Only: A standard one-way messaging exchange where the consumer sends a message to the provider that provides only a status response.Robust In-Only: This pattern is for reliable one-way message exchanges. To handle functionality that deals with installation, deployment, monitoring and lifecycle concerns amongst BCs and SEs, Java Management Extensions (JMX) is used. JBI implementations Books Binildas A.
JBoss Fuse - Overview JBoss Fuse is an open source, lightweight and modular integration platform with a new-style Enterprise Service Bus (ESB) that supports integration beyond the data center. The capability to connect all enterprise assets and the ability to deploy JBoss Fuse in several different configurations advances intelligent integration to all facets of your business – on premise or in the Cloud. JBoss Fuse for xPaaS extends the integration capabilities to OpenShift Platform-as-a-Service (PaaS) solution. Pattern based Integration framework Leverage Apache Camel to provide a full-featured, easy-to-use and intuitive framework for quicker integration solutions. Dynamic configuration and management Change configuration while container is running. Multiple connectivity options Connect to external applications with connectors for JDBC, FTP/SFTP, HTTP/HTTPS, file, SalesForce.com, SAP, Twitter, and more. Fabric Management Console is based on the hawtio web console. New Features Try the exciting new features: Buzz
BeanUtils - Commons Commons BeanUtils Most Java developers are used to creating Java classes that conform to the JavaBeans naming patterns for property getters and setters. It is natural to then access these methods directly, using calls to the corresponding getXxx and setXxx methods. However, there are some occasions where dynamic access to Java object properties (without compiled-in knowledge of the property getter and setter methods to be called) is needed. Building scripting languages that interact with the Java object model (such as the Bean Scripting Framework). The Java language provides Reflection and Introspection APIs (see the java.lang.reflect and java.beans packages in the JDK Javadocs). BeanUtils Core And Modules The 1.7.x and 1.8.x releases of BeanUtils have distributed three jars: Version 1.9.0 reverts this split for reasons outlined at BEANUTILS-379. Bean Collections Bean collections is a library combining BeanUtils with Commons Collections to provide services for collections of beans. Support
Enterprise service bus All customer services communicate in the same way with the ESB: the ESB translates a message to the correct message type and sends the message to the correct producer service. An enterprise service bus (ESB) is a software architecture model used for designing and implementing communication between mutually interacting software applications in a service-oriented architecture (SOA). As a software architectural model for distributed computing it is a specialty variant of the more general client server model and promotes agility and flexibility with regard to communication between applications. Overview Duties An ESB transports the design concept of modern operating systems to networks of disparate and independent computers. The prime duties of an ESB are: Ambiguous use of the term ESB in commerce History The first published usage of the term "enterprise service bus" is attributed to Roy W. ESB as software ESB hive of commodity components Characteristics
Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and ... - Robert Daigneau Commons CLI - Home Commons CLI The Apache Commons CLI library provides an API for parsing command line options passed to programs. It's also able to print help messages detailing the options available for a command line tool. Commons CLI supports different types of options: POSIX like options (ie. tar -zxvf foo.tar.gz) GNU like long options (ie. du --human-readable --max-depth=1) Java like properties (ie. java -Djava.awt.headless=true -Djava.net.useSystemProxies=true Foo) Short options with value attached (ie. gcc -O2 foo.c) long options with single hyphen (ie. ant -projecthelp) A typical help message displayed by Commons CLI looks like this: usage: ls -A,--almost-all do not list implied . and .. Check out the introduction page for a detailed presentation. Commons CLI 1.0 was formed from the merger of ideas and code from three different libraries - Werken, Avalon and Optz. The current plan is to continue to maintain the 1.x line. Support The commons mailing lists act as the main support forum.
Processing.js Basic Syntax A brief look at the structure of a Processing sketch reveals how easy it is to program interactive visualizations. As with any language, you begin by defining your global variables. Then you create a setup() function, where you control the visualization's properties, like the canvas size, frame rate and perhaps variables such as the stoke-weight or background-color. The next step is to create your draw() function, which controls the behavior of each frame in your animation. The draw function loops continuously unless you tell it otherwise by using the exit() command. To the right is a basic example of Processing.js in action. Adding interactivity to your visualization is incredibly simple. Processing.js also tracks a range of pre-defined variables like key, which stores the value of the last key pressed; or mouseX and mouseY, which store the last recorded position of the mouse pointer. Using Processing There are two ways of implementing processing. First Method Needed files:
Patterns of Enterprise Application Architecture - Martin Fowler Commons Chain - Overview Commons Chain A popular technique for organizing the execution of complex processing flows is the "Chain of Responsibility" pattern, as described (among many other places) in the classic "Gang of Four" design patterns book. Although the fundamental API contracts required to implement this design patten are extremely simple, it is useful to have a base API that facilitates using the pattern, and (more importantly) encouraging composition of command implementations from multiple diverse sources. Towards that end, the Chain API models a computation as a series of "commands" that can be combined into a "chain". The API for a command consists of a single method (execute()), which is passed a "context" parameter containing the dynamic state of the computation, and whose return value is a boolean that determines whether or not processing for the current chain has been completed (true), or whether processing should be delegated to the next command in the chain (false). Downloading Chain Support
Home | Wappalyzer Tuning Java Virtual Machines (JVMs) WebLogic Server Performance and Tuning The Java virtual machine (JVM) is a virtual "execution engine" instance that executes the bytecodes in Java class files on a microprocessor. How you tune your JVM affects the performance of WebLogic Server and your applications. The following sections discuss JVM tuning options for WebLogic Server: Table 3-1 presents general JVM tuning considerations for WebLogic Server. Table 3-1 General JVM Tuning Considerations Although this section focuses on Sun Microsystems' J2SE 1.4 JVM for the Windows, UNIX, and Linux platforms, the BEA WebLogic JRockit JVM was developed expressly for server-side applications and optimized for Intel architectures to ensure reliability, scalability, manageability, and flexibility for Java applications. For more information on JVMs in general, see the Introduction to the JVM specification. Changing To a Different JVM The JVM heap size determines how often and how long the VM spends collecting garbage. Java Heap Size Options
Collections - Home Commons Collections The Java Collections Framework was a major addition in JDK 1.2. It added many powerful data structures that accelerate development of most significant Java applications. Since that time it has become the recognised standard for collection handling in Java. Commons-Collections seek to build upon the JDK classes by providing new interfaces, implementations and utilities. There are many features, including: Support The commons mailing lists act as the main support forum. Issues may be reported via ASF JIRA. Mercurial SCM