The J2EE(TM) 1.4 Tutorial - The Diigo Meta page

• 24 Jun 09
  

  hanaliang

  java related

• 17 Jun 09
  

  Gary Wong
• 02 Jun 09
  

  Javier Neira

  j2ee java tutorial jsp jstl

• 01 Apr 09
  

  Brian Holland

  Software Development J2EE Training

• 17 Dec 08
  

  Carlos Moreira

  java

• 12 Nov 08
  

  jitesh Gangwani

  • Figure 1-6 EAR File Structure
    

    
    
    

    
    A J2EE module consists of one or more J2EE components for the same container type and one component deployment descriptor of that type. An enterprise bean module deployment descriptor, for example, declares transaction attributes and security authorizations for an enterprise bean. A J2EE module without an application deployment descriptor can be deployed as a stand-alone module. The four types of J2EE modules are as follows:
    

    
    
    • EJB modules, which contain class files for enterprise beans and an EJB deployment descriptor. EJB modules are packaged as JAR files with a .jar extension.
    • Web modules, which contain servlet class files, JSP files, supporting class files, GIF and HTML files, and a web application deployment descriptor. Web modules are packaged as JAR files with a .war (web archive) extension.
    • Application client modules, which contain class files and an application client deployment descriptor. Application client modules are packaged as JAR files with a .jar extension.
    • Resource adapter modules, which contain all Java interfaces, classes, native libraries, and other documentation, along with the resource adapter deployment descriptor. Together, these implement the Connector architecture (see J2EE Connector Architecture) for a particular EIS. Resource adapter modules are packaged as JAR files with an .rar (resource adapter archive) extension.
• 05 Nov 08
  

  Shine Chen

  java tutorial j2ee programming reference

• 04 Jul 08
  

  noureddine seddik

  tutorial,java,tm,ee,tutoriaux,ressources
  
  
  
  
  
  
  
  
  
  
  
  

  tutorial java tm ee tutoriaux ressources import simpy

• 28 May 08
  

  François Parmentier

  java j2ee tutorial dev webdev servlet jsp programming reference

• 02 May 08
  

  Lite

  for-supermemo java j2ee reference

• 29 Apr 08
  

  atin sood
  • messaging system that implements the JMS interfaces and provides administrative and control features
  • Messaging enables distributed communication that is loosely coupled. A component sends a message to a destination, and the recipient can retrieve the message from the destination.
  • 65 more annotations...
  • • However, the sender and the receiver do not have to be available at the same time in order to communicate.
    • JMS clients are the programs or components, written in the Java programming language, that produce and consume messages
    • The sender and the receiver need to know only which message format and which destination to use. In this respect, messaging differs from tightly coupled technologies, such as Remote Method Invocation (RMI), which require an application to know a remote application's methods.
    • Messages are the objects that communicate information between JMS clients.
    • Administered objects are preconfigured JMS objects created by an administrator for the use of clients.
    • destinations and connection factories
    • dministrative tools allow you to bind destinations and connection factories into a JNDI namespace
    • hrough the JMS provider.
    • llow programs written in the Java programming language to communicate with other messaging implementations.
    • -destinations and connection factories
    • Asynchronous
    • Reliable
    • point-to-point or the publish/subscribe approach to messaging.
    • A stand-alone JMS provider can implement one or both domains
    • A J2EE provider must implement both domains.
    • some JMS clients combine the use of both domains in a single application. In this way, the JMS API has extended the power and flexibility of messaging products.
    • factory encapsulates a set of connection configuration parameters that has been defined by an administrator
    • It provides common interfaces that enable you to use the JMS API in a way that is not specific to either domain.
    • The provider wants the components not to depend on information about other components' interfaces, so that components can be easily replaced
    • Each connection factory is an instance of the ConnectionFactory, QueueConnectionFactory, or TopicConnectionFactory interface
    • The provider wants the application to run whether or not all components are up and running simultaneously.
    • The application business model allows a component to send information to another and to continue to operate without receiving an immediate response.
    • message queues, senders, and receivers.
    • Each message is addressed to a specific queue, and receiving clients extract messages from the queues established to hold their messages
    • Queues retain all messages sent to them until the messages are consumed or until the messages expire.
    • In the PTP messaging domain, destinations are called queues. In the pub/sub messaging domain, destinations are called topics.
    • Each message has only one consumer.
    • You create a JMS destination resource that specifies the JNDI name of the destination. You also create a physical destination to which the JNDI name refers.
    • A sender and a receiver of a message have no timing dependencies. The receiver can fetch the message whether or not it was running when the client sent the message.
    • The receiver acknowledges the successful processing of a message
    • when every message you send must be processed successfully by one consumer.
    • A JMS application can use multiple queues or topics (or both).
    • Unlike connection factories, destinations are specific to one domain or the other.
    • clients address messages to a topic, which functions somewhat like a bulletin board
    • Topics retain messages only as long as it takes to distribute them to current subscribers.
    • Each message can have multiple consumers.
    • Publishers and subscribers have a timing dependency. A client that subscribes to a topic can consume only messages published after the client has created a subscription, and the subscriber must continue to be active in order for it to consume messages
    • You use a connection to create one or more sessions.
    • . Closing a connection also closes its sessions and their message producers and message consumers.
    • Before your application can consume messages, you must call the connection's start method; for details, see Message Consumers. If you want to stop message delivery temporarily without closing the connection, you call the stop method.
    • You use sessions to create message producers, message consumers, and messages. Sessions serialize the execution of message listeners;
    • single-threaded context f
    • the second means that the session automatically acknowledges messages when they have been received successfully.
    • created by a session
    • used for sending messages to a destination.
    • reate an unidentified producer by specifying null as the argument to createProducer
    • f you created an unidentified producer, use an overloaded send method that specifies the destination as the first parameter. For example:
    • created by a session and used for receiving messages sent to a destination.
    • ession.createDurableSubscriber
    • is method is valid only if you are using a topi
    • You can use the close method for a MessageConsumer to make the message consumer inactive.
    • Message delivery does not begin until you start the connection you created by calling its start method. (Remember always to call the start method; forgetting to start the connection is one of the most common JMS programming errors
    • o consume a message asynchronously, you use a message listen
    • cts as an asynchronous event handler for messag
    • plements the MessageListener interface,
    • ou define the actions to be taken when a message arrives.
    • egister the message listener with a specific MessageConsumer by using the setMessageListener method.
    • egister the message listener, you call the start method on the Connection to begin message delivery. (If you call start before you register the message listener, you are likely to miss messages.)
    • onMessage method takes one argument of type Message, which your implementation of the method can cast to any of the other message types
    • Your onMessage method should handle all exceptions. It must not throw checked exceptions, and throwing a RuntimeException is considered a programming error
    • At any time, only one of the session's message listeners is running.
    • allows a message consumer to specify the messages it is interested in
    • work of filtering messages to the JMS provider rather than to the application
    • MS message has three parts: a header, properties, and a body
    • redefined fields that contain values that both clients and providers use to identify and to route messages
• 25 Sep 07
  

  David Slattery

  development Java

• 14 Aug 07
  

  assyst assyst
• 17 Jul 07
  

  hari Prasad

  java personal toolbar folder

• 29 Jun 07
  

  DJHell .

  J2EE 1.4 Java JEE Sun tutorial development

• 24 Apr 07
  

  ggutkin

  reference

• 27 Mar 07
  

  matthieu bozec

  java j2ee programming tutorial

• 

  Danny

  delicious java tutorial

• 24 Mar 07
  

  Stefano Crosta

  imported WebDevelopment J2EE

• 06 Jan 07
  

  Benx Shen

  j2ee tutorial

• 02 Dec 06
  

  bogdan grosu

  imported imported:del.icio.us

• 14 Nov 06
  

  HJ Kim

  java tutorial

• 27 Oct 06
  

  Owen Mathews

  tutorial reference

• 25 Oct 06
  

  Seth

  java programming

• 22 Oct 06
  

  srinivkk

  Certification

• 05 Sep 06
  

  Art ist

  j2ee

• 16 Aug 06
  

  edoardo zari

  books j2ee java programming reference tutorial

• 06 Aug 06
  

  maknir

  j2ee java tutorial

• 02 Aug 06
  

  joe antony lawrence

  tutorials

• 

  David

  system:unfiled

• 01 Mar 06
  

  pickerel yee

  j2ee tutor

• 20 Jan 05
  

  bvbhavsar Bhavsar

  everything with SunOneAppServer

  J2EE 1.4 Tutorial... JAAS j2ee

  • Security
    
    The J2EE application programming model insulates developers from mechanism-specific implementation details of application security. The J2EE platform provides this insulation in a way that enhances the portability of applications, allowing them to be deployed in diverse security environments.
    
    Some of the material in this chapter assumes that you understand basic security concepts. To learn more about these concepts, we recommend that you explore http://java.sun.com/j2se/1.5.0/docs/guide/security/index.html before you begin this chapter.
    
    If you need to make changes to the Sun Java System Application Server 8, and have administrator privileges, read the Application Server's Administration Guide.
    
    If you are a developer who wants to add security to existing J2EE and web services applications, you are in the right place.
  • Security
    
    The J2EE application programming model insulates developers from mechanism-specific implementation details of application security. The J2EE platform provides this insulation in a way that enhances the portability of applications, allowing them to be deployed in diverse security environments.
    
    Some of the material in this chapter assumes that you understand basic security concepts. To learn more about these concepts, we recommend that you explore http://java.sun.com/j2se/1.5.0/docs/guide/security/index.html before you begin this chapter.
    
    If you need to make changes to the Sun Java System Application Server 8, and have administrator privileges, read the Application Server's Administration Guide.
    
    If you are a developer who wants to add security to existing J2EE and web services applications, you are in the right place.
  • 1 more annotations...
  • • Security
      
      The J2EE application programming model insulates developers from mechanism-specific implementation details of application security. The J2EE platform provides this insulation in a way that enhances the portability of applications, allowing them to be deployed in diverse security environments.
      
      Some of the material in this chapter assumes that you understand basic security concepts. To learn more about these concepts, we recommend that you explore http://java.sun.com/j2se/1.5.0/docs/guide/security/index.html before you begin this chapter.
      
      If you need to make changes to the Sun Java System Application Server 8, and have administrator privileges, read the Application Server's Administration Guide.
      
      If you are a developer who wants to add security to existing J2EE and web services applications, you are in the right place.
• 20 Dec 04
  

  Mikael Gyde Møller
• 20 Nov 04
  

  John Munsch

  development j2ee java tutorial

• 13 Nov 04
  

  ramiabbad

  Bookmarks Toolbar Folder personal old F jatkoo BGSBookmarks

• 30 Aug 04
  

  Derek Mahar

  j2ee java programming

Page Comments

• 
  Seth on 2006-10-25
  Sun's J2EE 1.4 tutorial

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.