Spring 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. 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 defines standard packaging for composite applications: applications that are composed of service consumers and providers. JBI implementations The following open-source software JBI based ESB implementations are available: Books
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
XFire 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. Its primary use is in enterprise application integration (EAI) of heterogeneous and complex landscapes. 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 ESB as software ESB hive of commodity components Books
Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and ... - Robert Daigneau Spring Web Flow The sweet spot for Spring Web Flow are stateful web applications with controlled navigation such as checking in for a flight, applying for a loan, shopping cart checkout, or even adding a confirmation step to a form. What these scenarios have in common is one or more of the following traits: There is a clear start and an end point.The user must go through a set of screens in a specific order.The changes are not finalized until the last step.Once complete it shouldn't be possible to repeat a transaction accidentally Spring Web Flow provides a declarative flow definition language for authoring flows on a higher level of abstraction. It allows it to be integrated into a wide range of applications without any changes (to the flow programming model) including Spring MVC, JSF, and even Portlet web applications. Spring Web Flow provides a solution to the above issues.
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. 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: processing.js anything.html anything.pde The anything.html file will look like: Second Method
Patterns of Enterprise Application Architecture - Martin Fowler EhCache 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
Team Blog A bit over a year ago we released Vaadin 7 renewing the framework inside out. Then came push support with 7.1. Now what? Let’s take a look into the future. Vaadin 7 series will iteratively add features to the platform while maintaining backwards compatibility with 7.0. Vaadin 7.2 - Responsive tune-up Next up in the pipeline will be a minor release that continues building the infrastructure. Responsive layouts for components (currently available as add-on) Improved push channel with support for long polling, Tomcat 8, Wildfly 8, Glassfish 4, Jetty 9.1 Font icons that look great on high DPI displays and are lightweight Native support for Internet Explorer 11 and Windows Phone 8.1. The beta version of this 7.2 will be available later this month. Vaadin 7.3 - Let there be light The next big feature is called Valo. How should it look like? The SASS compiler built in Vaadin 7 enabled us to make it modular. Some of the defaults for Valo Vaadin 7.4 - Son of the Table 7.5 = 7.4 + 0.1. Scary?