Commons -

- <?xml version="1.0" encoding="UTF-8"?> - <manager> - -  - - <messenger name="topic"> - <jndi lookupName="TopicConnectionFactory"> - <property> - <name>com.sun.jms.internal.java.naming.factory.initial</name> - <value>com.sun.enterprise.naming.SerialInitContextFactory</value> - </property> - </jndi> - </messenger> - - <messenger name="queue"> - <jndi lookupName="QueueConnectionFactory"> - <property> - <name>com.sun.jms.internal.java.naming.factory.initial</name> - <value>com.sun.enterprise.naming.SerialInitContextFactory</value> - </property> - </jndi> - </messenger> - - </manager> -

- - // get a Messenger and Destination - Messenger messenger = MessengerManager.get( "topic" ); - Destination destination = messenger.getDestination( "CHAT.NEWBIES" ); - - // now lets send a message - TextMessage message = messenger.createTextMessage( "this is some text" ); - messenger.send( destination, message ); -

- - // get a Messenger and Destination - Messenger messenger = MessengerManager.get( "queue" ); - Destination destination = messenger.getDestination( "REQUEST.BUILD" ); - - // now lets receive a message - Message message = messenger.receive( destination ); -

- By default, Messenger will look for an XML document called Messenger.xml - on the CLASSPATH as soon as a Messenger instance is looked up via the following code. -

- An alternative approach is to define the system property org.apache.commons.messenger - to point to a URL of a Messenger deployment configuration document. For example -

- In servlet environments its often a good idea to explicitly configure the - singleton MessengerManager - in a Servlet initialisation method using servlet initialisation parameters. - Here's an example -

@@ -576,28 +450,16 @@ @@ -622,43 +484,25 @@

   
  -
  -
   public class MyServlet extends HttpServlet {
  -
       
  -
       public void init() throws ServletException {
  -
           // initialise the Messenger connections
  -
           String url = getInitParameter( "messenger" );
  -
           if ( url != null ) {
  -
               MessengerManager.configure( url );
  -
           }
  -
       }
  -
   }  
  -

- The Messenger project provides a Messagelet Engine which is - a JMS based Container which runs in any Servlet Engine - such as Tomcat 4.0. - The Messagelet Engine provides a simple framework for processing JMS messages in - a variety of ways using either regular JMS MessageListeners, Servlets or even JSP. -

- To deploy a Messagelet Container you need to add the ManagerServlet in a web - application giving it an XML configuration file describing all the various JMS connections - and an XML configuration file describing all the subscriptions. -

- Here are example - connections - and - subscriptions - XML configuration files. - There now follows the section you need to add to your web.xml configuration file to deploy the - Messagelet Manager Servlet. -
@@ -671,34 +515,19 @@ @@ -710,130 +539,69 @@
   
  -
  -
     <servlet>
  -
       <servlet-name>managerServlet</servlet-name>
  -
       <servlet-class>org.apache.commons.messagelet.ManagerServlet</servlet-class>
  -
       <init-param>
  -
         <param-name>connections</param-name>
  -
         <param-value>/WEB-INF/Messenger.xml</param-value>
  -
       </init-param> 
  -
       <init-param>
  -
         <param-name>subscriptions</param-name>
  -
         <param-value>/WEB-INF/subscriptions.xml</param-value>
  -
       </init-param> 
  -
       <load-on-startup>1</load-on-startup> 
  -
     </servlet>
  -
   
- Once you've done the above and the web application is started the Messagelet engine will - subscribe to the various JMS subscriptions and then dispatch JMS messages to the various - MessageListener objects, Servlets or JSP pages. -

- There are a variety of ways in which you can process JMS messages depending on your requirements. -

- -
- A MessageListener is a standard JMS listener of messages. -
- -
- A MessageDrivenObject is-a JMS MessageListener which has - extra servlet-based lifecycle methods just like a Servlet. - This allows - an MDO to know when its being initialised and when its being destroryed - and so do some resource management (such as creating or closing database - connections etc). Also on initialisation the MDO gets access to the - ServletContext so that it can read some initialization parameters from - the web application or perform web-app level logging and so on. -
- -
- A MessengerMDO is-a MessageDrivenObject - but also provides a number of helper methods such as access to the Messenger to - which its listening, so that responses can be sent back to the originator of the message, - as well as access to the ServletContext and some logging helper methods. -
- -
- A Servlet can be any GenericServlet or HttpServlet. - If the JMS message that is being dispatched is a TextMessage then the body of the message is - available via the ServletRequest.getReader() method, in the normal Servlet way. - Any output written to the ServletResponse.getWriter() will be converted into a TextMessage - and sent back to the originator. - All servlets and JSP pages have access to the originating JMS message and Messenger objects via - the "message" and "messenger" request attributes respectively. -
- -
- A Messagelet - is a JMS specific Servlet, just like a HttpServlet is a HTTP specific Servlet. It - provides access to a Messagelet specific - MessageletRequest - and - MessageletResponse - to allow access to the JMS Message and the Messenger for sending replies. -
- -
- A JSP page can be any piece of JSP, for example the standard JSP tag library can be used - to perform JavaScript, XPath, XSLT or SQL operations on the incoming message. - The request scope "message" and "messenger" attributes can be used to access the originating - JMS Message and Messenger objects. -
- -

There are some examples of an MDO, Servlet and Messagelet - here or - you can see example JSP - here -

1.23 +2 -0 jakarta-commons/docs/releases.html Index: releases.html =================================================================== RCS file: /home/cvs/jakarta-commons/docs/releases.html,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- releases.html 23 Apr 2002 01:45:26 -0000 1.22 +++ releases.html 23 Apr 2002 16:37:16 -0000 1.23 @@ -94,6 +94,8 @@

Betwixt
CLI +
Jelly

JJar 1.37 +2 -0 jakarta-commons/docs/sandbox.html Index: sandbox.html =================================================================== RCS file: /home/cvs/jakarta-commons/docs/sandbox.html,v retrieving revision 1.36 retrieving revision 1.37 diff -u -r1.36 -r1.37 --- sandbox.html 23 Apr 2002 01:45:26 -0000 1.36 +++ sandbox.html 23 Apr 2002 16:37:16 -0000 1.37 @@ -94,6 +94,8 @@

Betwixt
CLI +
Jelly

JJar 1.13 +2 -0 jakarta-commons/docs/versioning.html Index: versioning.html =================================================================== RCS file: /home/cvs/jakarta-commons/docs/versioning.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- versioning.html 23 Apr 2002 01:45:26 -0000 1.12 +++ versioning.html 23 Apr 2002 16:37:16 -0000 1.13 @@ -98,6 +98,8 @@

Betwixt
CLI +
Jelly

JJar 1.1 jakarta-commons/docs/cli.html Index: cli.html =================================================================== Commons -

Home

Jakarta Commons

About Us

Download

Information

Components Repository

Sandbox Components

Jakarta Community

Project Docs

CLI : Command Line Interface

Introduction

Documentation

Introduction

Proposed by : James Strachan

CLI

The CLI library provides a simple and easy to use API for working with the command line arguments and options.

CLI is based on ideas and code from

werken.opt by Bob Mcwhirter

The cli package in Avalon Excalibur by Peter Donald

Optz by John Keyes

Documentation

There is the status document. or the initial proposal.

The JavaDoc from the last nightly build is available online or you can download a nightly build.

-- To unsubscribe, e-mail: For additional commands, e-mail: