View RSS Feed

JBoss

  1. What is JBoss Web

    by , 04-27-2012 at 05:42 PM
    JBoss Web Server is an enterprise ready web server designed for medium and large applications, based on Tomcat.

    JBoss Web a component of the JBoss Application Server, there are no more standalone version of JBoss Web you need the Application Server to get the Servlet/JSP container.,

    JBoss Web Server provides organizations with a single deployment platform for Java Server Pages (JSP) and Java Servlet technologies, PHP, and CGI. It uses a genuine high performance hybrid ...
    Categories
    JBoss Web
  2. The Need for JBoss Seam

    by , 04-27-2012 at 05:41 PM
    Let us exactly define what JBoss seam is. JBoss Seam provides a Light-weight Container for J2EE standards and it addresses the long-standing issues in any Typical Web Application like State Management and Better Browser Navigation. It also neatly provides an integration between the two popular technologies, Java Server Faces (in the UI tier) and Enterprise Java Beans (EJB 3 in the Server Side). Before getting into the various details about JBoss Seam let us see the common set of problems that are ...
  3. JBoss Seam: A Deep Integration Framework

    by , 04-27-2012 at 05:40 PM
    Software frameworks are very useful tools for enterprise Java developers. They are widely used to package reusable software components and services. Each framework provides a set of design patterns, APIs, and component models, which can be used in applications built on top of the framework. Examples of popular Java EE frameworks include both open source projects such as Hibernate, Spring, Struts, etc., and standard-based products such as various implementations for Servlet/JSP, JSF, EJB, JMS, Web ...
    Categories
    JBoss Seam
  4. Seam - Avoid XML Abuse

    by , 04-27-2012 at 05:39 PM
    As you probably noticed, Java annotations play a crucial role in expressing and managing Seam configuration metadata. That is done by design to make the framework easier to work with.

    In the early days of J2EE, XML was viewed as the "holy grail" for configuration management. Framework designers throw all kinds of configuration information, including Java class and method names, in XML files without much thought about the consequence to developers. In retrospect, that was ...
    Categories
    JBoss Seam
  5. Seam - Configuration by Exception

    by , 04-27-2012 at 05:38 PM
    The key design principal that makes Seam so easy to use is "Configuration by exception". The idea is to have a set of common-sense default behavior for the components. The developer only needs to configure the component explicitly when the desired behavior is not the default. For instance, when Seam injects component A as a property of component B, the Seam name of component A defaults to the recipient property name in component B. There are many little things like that in Seam. The overall ...
    Categories
    JBoss Seam
  6. Seam - POJO Services via Dependency Bijection

    by , 04-27-2012 at 05:38 PM
    Seam is a "lightweight framework" because it promotes the use of POJO (plain old Java objects) as service components. There are no framework interfaces or abstract classes to "hook" components into the application. The question, of course, is how do those POJOs interact with each other to form an application? How do they interact with container services (e.g., the database persistence service)?

    Seam wires POJO components together using a popular design pattern ...
    Categories
    JBoss Seam
  7. Seam - Web 2.0 Ready

    by , 04-27-2012 at 05:37 PM
    Seam is fully optimized for Web 2.0 style applications. It provides multiple ways for AJAX (Asynchronous JavaScript And XML, a technology to add interactivity to web pages) support -- from drop-in JavaScript-less AJAX components, AJAX-enabling existing JSF components, to a custom JavaScript library that provide direct access to Seam server components from the browser as Javascript objects. Internally, Seam provides an advanced concurrency model to efficiently manage multiple AJAX requests from the ...
    Categories
    JBoss Seam
  8. Seam - Designed for Stateful Web Applications

    by , 04-27-2012 at 05:36 PM
    Seam is designed for stateful web applications. Web applications are inherently multi-user applications, and e-commerce applications are inherently stateful and transactional. However, most existing web application frameworks are geared toward stateless applications. You have to fiddle with the HTTP session objects to manage user states. That not only clutters your application with code un-related to the core business logic, but also brings on an array of performance issues.

    In Seam, ...
  9. Seam - A Web Frameworks that Understands ORM

    by , 04-27-2012 at 05:35 PM
    Object Relational Mapping (ORM) solutions are widely used in today's enterprise applications. However, most current business and web frameworks are not designed for ORM. They do not manage the persistence context over the entire web interaction lifecycle from the request comes in to the response is fully rendered. That has resulted in all kinds of ORM errors included the dreaded LazyInitializationException, and gave rise to ugly hacks like the "Data Transfer Object" (DTO).

    ...
    Tags: seam and orm Add / Edit Tags
    Categories
    JBoss Seam
  10. Seam - Integrate and Enhance Java EE Frameworks

    by , 04-27-2012 at 05:35 PM
    The core frameworks in Java EE 5.0 are EJB (Enterprise JavaBeans) 3.0 and JSF (JavaServer Faces) 1.2. EJB 3.0 (EJB3, hereafter) is a POJO (Plain Old Java Objects) based lightweight framework for business services and database persistence. JSF is a MVC (Model-View-Controller) component framework for web applications. Most Java EE 5.0 web applications will have both EJB3 modules for business logic and JSF modules for the web front end. However, while EJB3 and JSF are complementary to each other, they ...
    Categories
    JBoss Seam
  11. The Seam Framework

    by , 04-27-2012 at 05:34 PM
    Seam is a powerful open source development platform for building rich Internet applications in Java. Seam integrates technologies such as Asynchronous JavaScript and XML (AJAX), JavaServer Faces (JSF), Java Persistence (JPA), Enterprise Java Beans (EJB 3.0) and Business Process Management (BPM) into a unified full-stack solution, complete with sophisticated tooling.

    Seam has been designed from the ground up to eliminate complexity at both architecture and API levels. It enables developers ...
    Categories
    JBoss Seam
  12. EAR Class Loading

    by , 04-27-2012 at 05:33 PM
    Ear deployments are multi-module deployments. This means that not all classes inside an ear will necessarily have access to all other classes in the ear, unless explicit dependencies have been defined. By default the EAR/lib directory is a single module, and every WAR or EJB jar deployment is also a separate module. Sub deployments (wars and ejb-jars) always have a dependency on the parent module, which gives them access to classes in EAR/lib, however they do not always have an automatic dependency ...
    Categories
    JBoss7
  13. Class Loading Precedence

    by , 04-27-2012 at 05:32 PM
    A common source of errors in Java applications is including API classes in a deployment that are also provided by the container. This can result in multiple versions of the class being created and the deployment failing to deploy properly. To prevent this in AS7, module dependencies are added in a specific order that should prevent this situation from occurring.

    In order of highest priority to lowest priority

    1. System Dependencies - These are dependencies that are
    ...
    Categories
    JBoss7
  14. Automatic Dependencies

    by , 04-27-2012 at 05:32 PM
    Even though in AS7 modules are isolated by default, as part of the deployment process some dependencies on modules defined by the application server are set up for you automatically. For instance, if you are deploying a Java EE application a dependency on the Java EE API's will be added to your module automatically. Similarly if your module contains a beans.xml file a dependency on Weld will be added automatically, along with any supporting modules that weld needs to operate.

    Automatic ...
    Categories
    JBoss7
  15. Domain Directory Structure

    by , 04-27-2012 at 05:31 PM
    A key feature of AS 7 is the managing multiple servers from a single control point. A collection of multiple servers are referred to as a "domain". Domains can span multiple physical (or virtual) machines with all JBoss Application Server 7 instances on a given host under the control of a Host Controller process. The Host Controllers interact with the Domain Controller to control the lifecycle of the JBoss Application Server 7 instances running on that host and to assist the Domain ...
    Categories
    JBoss7
  16. Standalone Directory Structure

    by , 04-27-2012 at 05:29 PM
    In "standalone" mode each JBoss Application Server 7 instance is an independent process (similar to previous JBoss AS versions; e.g., 3, 4, 5, or 6). The configuration files, deployment content and writable areas used by the single standalone server run from a JBoss Application Server installation are found in the following subdirectories under the top level "standalone" directory:

    configuration: Configuration files for the standalone server that runs off of this ...
  17. Deciding between running standalone servers or a managed domain

    by , 04-27-2012 at 05:27 PM
    Which use cases are appropriate for managed domain and which are appropriate for standalone servers? A managed domain is all about coordinated multi-server management -- with it JBoss AS 7 provides a central point through which users can manage multiple servers, with rich capabilities to keep those servers' configurations consistent and the ability to roll out configuration changes (including deployments) to the servers in a coordinated fashion.
    It's important to understand that the choice ...
    Categories
    JBoss7
  18. JBoss7 Server Group

    by , 04-27-2012 at 05:26 PM
    A server group is set of server instances that will be managed and configured as one. In a managed domain each application server instance is a member of a server group. (Even if the group only has a single server, the server is still a member of a group.) It is the responsibility of the Domain Controller and the Host Controllers to ensure that all servers in a server group have a consistent configuration. They should all be configured with the same profile and they should have the same deployment ...
    Categories
    JBoss7
  19. JBoss7 Domain Controller

    by , 04-27-2012 at 05:25 PM
    One Host Controller instance is configured to act as the central management point for the entire domain, i.e. to be the Domain Controller. The primary responsibility of the Domain Controller is to maintain the domain's central management policy, to ensure all Host Controllers are aware of its current contents, and to assist the Host Controllers in ensuring any running application server instances are configured in accordance with this policy. This central management policy is stored by default in ...
    Categories
    JBoss7
  20. JBoss7 Host Controller

    by , 04-27-2012 at 05:25 PM
    When the domain.sh or domain.bat script is run on a host, a process known as a Host Controller is launched. The Host Controller is solely concerned with server management; it does not itself handle application server workloads. The Host Controller is responsible for starting and stopping the individual application server processes that run on its host, and interacts with the Domain Controller to help manage them.

    Each Host Controller by default reads its configuration from the domain/configuration/host.xml ...
    Categories
    JBoss7
  21. JBoss7 Managed Domain

    by , 04-27-2012 at 05:24 PM
    One of the primary new features of JBoss Application Server 7 is the ability to manage multiple JBoss Application Server 7 instances from a single control point. A collection of such servers is referred to as the members of a "domain" with a single Domain Controller process acting as the central management control point. All of the JBoss Application Server 7 instances in the domain share a common management policy, with the Domain Controller acting to ensure that each server is configured ...
    Categories
    JBoss7