User: pra
Date: 01/02/28 01:25:48
Modified: src/main/org/jboss/metadata MessageDrivenMetaData.java
Log:
MDB deployment descriptor now follows the latest EJB2.0 DTD; code clean up done;
message receipt now allways transacted
Revision Changes Path
1.4 +9 -3 jboss/src/main/org/jboss/metadata/MessageDrivenMetaData.java
Index: MessageDrivenMetaData.java
===================================================================
RCS file:
/products/cvs/ejboss/jboss/src/main/org/jboss/metadata/MessageDrivenMetaData.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- MessageDrivenMetaData.java 2001/01/03 08:28:39 1.3
+++ MessageDrivenMetaData.java 2001/02/28 09:25:47 1.4
@@ -22,7 +22,7 @@
' * @author <a href="mailto:[EMAIL PROTECTED]">Sebastien Alborini</a>
* @author Peter Antman ([EMAIL PROTECTED])
- * @version $Revision: 1.3 $
+ * @version $Revision: 1.4 $
*/
public class MessageDrivenMetaData extends BeanMetaData {
// Constants -----------------------------------------------------
@@ -80,12 +80,12 @@
public void importEjbJarXml(Element element) throws DeploymentException {
super.importEjbJarXml(element);
- messageSelector = getElementContent(getUniqueChild(element,
"jms-message-selector"));
+ messageSelector = getElementContent(getUniqueChild(element,
"message-selector"));
// set
Element destination = getUniqueChild(element,
"message-driven-destination");
destinationType = getElementContent(getUniqueChild(destination
-, "jms-destination-type"));
+, "destination-type"));
if (destinationType.equals("javax.jms.Topic")) {
String subscr = getElementContent(getUniqueChild(destination,
"subscription-durability"));
@@ -126,6 +126,12 @@
But for NOT_SUPPORTED this is not true here we
should have AUTO_ACKNOWLEDGE_MODE
+
+ This is not true for now. For JBossMQ we relly
+ completely on transaction handling. For JBossMQ, the
+ ackmode is actually not relevant. We keep it here
+ anyway, if we find that this is needed for other
+ JMS provider, or is not good.
*/
