This is a feature of JBuilder Enterprise.
Use the JMS wizard to create a Java class that includes supporting code for the class to produce and consume messages in a Java Message Service (JMS) system. For information about JMS, see http://java.sun.com/products/jms/docs.html.
After the class is generated, you then add your code to actually publish or send the message if the class is a message producer. If the class is a message consumer, you add the code to receive the message and implement the onMessage()
method to handle messages subscribed to or received, depending on the type of message model you are using. The generated code contains comments that shows you where to add your code.
In this step, you specify the name of the class you want to generate and whether your class follows the publish/subscribe or point to point model.
The name of the package the class will belong to. The default value is the package the current project is in.
Specify the name of the class you want to generate. The default value is Jms<x> where x is a number. For example, the first default class name in a package is Jms1, the second is Jms2, and so on.
Specify the class you want the generated class to extend. The default value is java.lang.Object
.
These options determine which type of message system the generated class will model.
Determines that the generated class will be created for a publish and subscribe message system. A publish/subscribe system follows an event-driven model in which producers of messages send out or publish messges, and consumers of messages subscribe to or receive messages in which they are interested. Each published message is on a specific topic. Message consumers specify which topics they want to receive.
Determines that the generated class will be created for a point to point message system. A point to point system requires that message producers send a message to a particular message consumer. The message arrives at the consumer's incoming message queue.
This is a feature of JBuilder Enterprise.
This page appears if you selected the Publish And Subscribe option in Step 1.
Specify a connection factory JNDI name for the class.
Specify the name of the message topic.
Specify the name for a durable description if you want the description to be durable. See the Durable option.
Specify a unique name that identifies the client. This is required if the subscription is durable.
Specify whether the subscription is durable or non-durable. A durable subscription is one that endures even if there is no active subscriber. When an active subscriber returns, the subscription resumes in the same state as when the previous subscriber became inactive. No messages are missed. A non-durable subscription remains only for the lifetime of the subscriber. Therefore, a client sees just the messages published on a topic when its subscriber is active. Otherwise, the client misses an messages published on the topic.
Determines whether a session uses the commit()
and rollback()
methods to demarcate a local transaction.
Determines how messages are acknowedged when they are received.
Use this option to have the session automatically acknowledge the receipt of a message.
Use this option to have the session acknowledge all messages, performing no checks to prevent duplicates. This can improve processing time.
Selecting this option means the client acknowledges a message by calling the message's acknowledge()
method.
Select his option to add the title, description, copyright, author, and version partial source code comments above the class code, ready for you to fill in.
This is a feature of JBuilder Enterprise.
This page appears if you selected the Point To Point option in Step 1.
Specify a connection factory JNDI name for the class.
Specify the name of the message queue.
Determines whether a session uses the commit()
and rollback()
methods to demarcate a local transaction.
Determines how messages are acknowedged when they are received.
Use this option to have the session automatically acknowledge the receipt of a message.
Use this option to have the session acknowledge all messages, performing no checks to prevent duplicates. This can improve processing time.
Selecting this option means the client acknowledges a message by calling the message's acknowledge()
method.
Select his option to add the title, description, copyright, author, and version partial source code comments above the class code, ready for you to fill in.