Jms-enqueue - Revision history

G.dimaio at 15:46, 10 June 2015

2015-06-10T15:46:44Z

G.dimaio at 15:44, 10 June 2015

2015-06-10T15:44:28Z

Anonymous at 15:59, 27 December 2012

2012-12-27T15:59:33Z

Anonymous at 15:59, 27 December 2012

2012-12-27T15:59:11Z

Anonymous at 13:56, 23 November 2012

2012-11-23T13:56:38Z

Anonymous at 10:00, 27 February 2012

2012-02-27T10:00:24Z

Anonymous at 17:07, 9 February 2012

2012-02-09T17:07:45Z

Anonymous at 17:06, 9 February 2012

2012-02-09T17:06:45Z

Anonymous at 15:09, 3 February 2012

2012-02-03T15:09:16Z

Anonymous at 15:08, 3 February 2012

2012-02-03T15:08:42Z

@@ Line 65: / Line 65: @@
 ! Attribute !! Type !! Description
 |-
-| decorate-message || optional || If true the message to be enqueued is enriched with input GVBuffer properties value. Default true
+| decorate-message || optional || If true the message to be enqueued is enriched with input GVBuffer properties value. Default true. The attribute's admitted values are:
 |}
 </div>

@@ Line 61: / Line 61: @@
 | dump-message || optional || If true the message to be enqueued is dumped on log file, at DEBUG severity level. Default false
 |}
 Its subelements are:

@@ Line 36: / Line 36: @@
 |-
 | transacted || optional || Specifies whether the enqueue has to open his own transaction or fall in a global transaction.
-* 'true' open his own transaction and do not fall in the global transaction.
+* ''true'' open his own transaction and do not fall in the global transaction.
-* 'false' fall in the active global transaction. Must be used a XA connection factory.
+* ''false'' fall in the active global transaction. Must be used a XA connection factory.
 : This parameter is not relevant if the connection factory is not XA. Default: false.
 |-

← Older revision		Revision as of 15:59, 27 December 2012
Line 1:		Line 1:
−	The ''jms-~~dequeue~~'' element allows you to perform a enqueue on a JMS destination. It is used by [[Channel]] and [[routed-dequeue]].	+	The ''jms-enqueue'' element allows you to perform a enqueue on a JMS destination. It is used by [[Channel]] and [[routed-dequeue]].

	GVBuffer fields will be made available through the JMS message properties:		GVBuffer fields will be made available through the JMS message properties:

@@ Line 67: / Line 67: @@
 * [[JNDIHelper]]
 * [[ServiceAlias]]
-* XAHelper
+* [[XAHelper]]
-===XAHelper===
+{{VOTE}}

@@ Line 57: / Line 57: @@
 | invalidate-conn-on-pool-insertion || optional || Indicates whether connections should be marked as invalid before reinsertion on the pool. Is significant only if the pooling feature is enabled. Default: false
 |-
-| ref-dp || optional || Name of [[Data Provider]] to use. This Data Provider will return the JMS Message to send.
+| ref-dp || optional || Name of [[Data_provider|Data Provider]] to use. This Data Provider will return the JMS Message to send.
 |-
 | dump-message || optional || If true the message to be enqueued is dumped on log file, at DEBUG severity level. Default false

@@ Line 39: / Line 39: @@
 * 'false' fall in the active global transaction. Must be used a XA connection factory.
 : This parameter is not relevant if the connection factory is not XA. Default: false.
 | acknowledge-type || optional || In transactional enqueue acknowledgment is managed by the application server. <br/> This parameter is meaningful only for non-transactional enqueue and can take the following values:
 * auto-acknowledge: the acknowledgment from application server is automatically given upon delivery of the message.
 * client-acknowledge: the client must explicitly acknowledgment the message.
 * dups-ok-acknowledge: allows the JMS server to perform optimizations on the logic of acknowledgment messages, but can cause the redelivery of messages. Should only be used with systems that are tolerant to duplicated message. Default: auto-acknowledge
 | delivery-mode || optional || Specifies whether the JMS server must file on a persistent store the message before returning to the caller. <br/> Sending messages persistent slightly affects the performance but provides greater guarantees of delivery. The possible values for this parameter are:
 * persistent : guarantees delivery. Default value

@@ Line 18: / Line 18: @@
 It has the attributes:
+{|class="gvtable"
-* ''type'': enqueue.
+! Attribute !! Type !! Description
-* ''class'': it.greenvulcano.gvesb.virtual.j2ee.JMSEnqueueOperation.
+|-
-* ''name'': Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
+| type || fixed || This attribute must assume the value '''enqueue'''.
-* ''connection-factory'': JMS connection factory JNDI name.
+|-
-* ''destination-name'': Destination JNDI name. Set appropriately the ''destination-type'' parameter.
+| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.j2ee.JMSEnqueueOperation'''.
-* ''destination-type'': Destination type. Default: queue. <br/> The attribute's admitted values are:
+|-
-** queue
+| name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
-** topic
+|-
-* ''transacted'': Specifies whether the enqueue has to open his own transaction or fall in a global transaction.
+| connection-factory || required || JMS connection factory JNDI name.
-** 'true' open his own transaction and do not fall in the global transaction.
+|-
-** 'false' fall in the active global transaction. Must be used a XA connection factory.
+| destination-name || required || Destination JNDI name. Set appropriately the ''destination-type'' parameter.
 : This parameter is not relevant if the connection factory is not XA. Default: false.
-* ''acknowledge-type'':In transactional enqueue acknowledgment is managed by the application server. <br/> This parameter is meaningful only for non-transactional enqueue and can take the following values:
+| acknowledge-type || optional || In transactional enqueue acknowledgment is managed by the application server. <br/> This parameter is meaningful only for non-transactional enqueue and can take the following values:
-** auto-acknowledge: the acknowledgment from application server is automatically given upon delivery of the message.
+* auto-acknowledge: the acknowledgment from application server is automatically given upon delivery of the message.
-** client-acknowledge: the client must explicitly acknowledgment the message.
+* client-acknowledge: the client must explicitly acknowledgment the message.
-** dups-ok-acknowledge: allows the JMS server to perform optimizations on the logic of acknowledgment messages, but can cause the redelivery of messages. Should only be used with systems that are tolerant to duplicated message. Default: auto-acknowledge
+* dups-ok-acknowledge: allows the JMS server to perform optimizations on the logic of acknowledgment messages, but can cause the redelivery of messages. Should only be used with systems that are tolerant to duplicated message. Default: auto-acknowledge
-* ''delivery-mode'': Specifies whether the JMS server must file on a persistent store the message before returning to the caller. <br/> Sending messages persistent slightly affects the performance but provides greater guarantees of delivery. The possible values for this parameter are:
+| delivery-mode || optional || Specifies whether the JMS server must file on a persistent store the message before returning to the caller. <br/> Sending messages persistent slightly affects the performance but provides greater guarantees of delivery. The possible values for this parameter are:
-** persistent : guarantees delivery. Default value
+* persistent : guarantees delivery. Default value
-** non-persistent: don't guarantees delivery
+* non-persistent: don't guarantees delivery
-* ''priority'': Message priority. The messages with higher priority will be received before messages with lower priority. The priorities set for JMS ranging from 0 (lowest priority) to 9 (highest priority). The default priority of JMS messages is 4.
+|-
-* ''time-to-live'': Lifetime of sent messages, in milliseconds. <br/> Upon expiration of the time-to-live the JMS server is allowed to discard the message without delivering it. If not specified it is assumed a time-to-live of one year.
+| priority || optional || Message priority. The messages with higher priority will be received before messages with lower priority. The priorities set for JMS ranging from 0 (lowest priority) to 9 (highest priority). The default priority of JMS messages is 4.
-* ''use-vcl-pool'': Indicates whether to use connection pooling capabilities of the VCL. Set to false if the container provides pooling capabilities. Default: true
+|-
-* ''invalidate-conn-on-pool-insertion'': Indicates whether connections should be marked as invalid before reinsertion on the pool. Is significant only if the pooling feature is enabled. Default: false
+| time-to-live || optional || Lifetime of sent messages, in milliseconds. <br/> Upon expiration of the time-to-live the JMS server is allowed to discard the message without delivering it. If not specified it is assumed a time-to-live of one year.
-The attribute's admitted values are:
+|-
-* ''ref-dp'': Name of Data Provider to use. This Data Provider will return the JMS Message to send.
+| use-vcl-pool || optional || Indicates whether to use connection pooling capabilities of the VCL. Set to false if the container provides pooling capabilities. Default: true
-* ''dump-message'': If true the message to be enqueued is dumped on log file, at DEBUG severity level. Default false
+|-
 Its subelements are:
@@ Line 58: / Line 72: @@
 Its attributes are:
-* ''auto-enlist'': The attribute's default value is: false.
+{|class="gvtable"
-* ''transaction-status'': The attribute's admitted values are:
+! Attribute !! Type !! Description
-** TMSUCCESS: default value
+|-
-** TMFAIL
+| auto-enlist || optional || The attribute's default value is: false.
 and its subelements:
 * Description
 * [[JNDIHelper]]

← Older revision		Revision as of 15:08, 3 February 2012
Line 52:		Line 52:
	* [[ServiceAlias]]		* [[ServiceAlias]]
	* [[XAHelper]]		* [[XAHelper]]
		+
		+	===XAHelper===
		+
		+	The XAHelper Element is used by [[jms-dequeue]] and '''jms-enqueue'''.
		+
		+	Its attributes are:
		+	* ''auto-enlist'': The attribute's default value is: false.
		+	* ''transaction-status'': The attribute's admitted values are:
		+	** TMSUCCESS: default value
		+	** TMFAIL
		+
		+	and its subelements:
		+	* Description
		+	* [[JNDIHelper]]