Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 62027 invoked from network); 27 Jan 2009 21:36:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jan 2009 21:36:16 -0000 Received: (qmail 82600 invoked by uid 500); 27 Jan 2009 07:54:51 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 82583 invoked by uid 500); 27 Jan 2009 07:54:50 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 82574 invoked by uid 99); 27 Jan 2009 07:54:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2009 23:54:50 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.136.44.63] (HELO smtp108.prem.mail.sp1.yahoo.com) (98.136.44.63) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 27 Jan 2009 07:54:41 +0000 Received: (qmail 17207 invoked from network); 27 Jan 2009 07:54:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Mime-Version:Subject:Date:References:X-Mailer; b=ZC7EH7J5qJh7b3Ws47VvPcP8aKWHWFzqOQTXrKu5UyZ+l9fA+FOu+d4c5sSSIXm7K+uB2TBwZ1clQnfoj50p+RwepC9uM6Vw4DnDSMTwI+HFtBZuGUF1kXRxpME1rsr9Xiti84J3Mm9H89IxbEekICLVt9I4f0/cZL+WDvQnKko= ; Received: from unknown (HELO ?10.11.55.10?) (david_jencks@76.76.148.215 with plain) by smtp108.prem.mail.sp1.yahoo.com with SMTP; 27 Jan 2009 07:54:18 -0000 X-YMail-OSG: EEzF4QgVM1l1irUSMtdaSCPk9JjuKJNPDEbQsav4CyxFCFkso_G5CkSX9xK90puu9tLNV8bdZ4X.hB6n9xgmUxGa_moDSFlTGzwkWwVVepPS.j_SHtSYijgs_.8JXZETRT7GMXHHIclDf6ew4OWN0dsv3RxhAAgS8UpSIxW8iq9YTUubjejpmf9C8iDJ39bBz_6Aaz_oRzokNYOvy1mfbXlWSduheOAXR._u8G8- X-Yahoo-Newman-Property: ymail-3 Message-Id: <641703A1-097F-4758-BA0F-92E4DBAEFAF7@yahoo.com> From: David Jencks To: user@geronimo.apache.org In-Reply-To: <21678653.post@talk.nabble.com> Content-Type: multipart/alternative; boundary=Apple-Mail-7--814896592 Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: Geronimo: connectionFactoryJndiName not recognized in MDB EJB 3.0 Date: Mon, 26 Jan 2009 23:54:17 -0800 References: <21674243.post@talk.nabble.com> <7B6CC781-8237-41B6-B726-FAFD9AD63E00@yahoo.com> <21678653.post@talk.nabble.com> X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-7--814896592 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Jan 26, 2009, at 6:42 PM, Lenin David Lozano Argel wrote: > > Well, The Oracle OC4J How To MDB 3,0 use these properties. > > You can look at > > http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-ejb30-mdb/doc/how-to-ejb30-mdb.html > > The sample in Oracle Oc4J uses these properties. I don't know how to > associate the Connection Factory with the MDB in Geronimo or WAS CE. > Unfortunately oracle doesn't really make clear where the activation config properties come from or how to tell which ones can be used. They come from the inbound messaging resource adapter. Unless you install something else, in geronimo that's activemq. Each inbound resource adapter comes with an ActivationSpec class that is a javabean that indicates the properties you can set on it. A few of these can also be documented in the ra.xml descriptor for the adapter. The standard properties for jms inbound adapters are: The recommended properties for JMS ActivationSpec JavaBean are: destination (required), destinationType (required), messageSelector, acknowledgeMode, subscriptionDurability, clientId, subscriptionName. As you can see, the oracle activation spec does not appear to support destination and uses the decidedly non-standard connectionFactoryJndiName. I'll update our documentation to make it clearer where the properties we use come from. However, the geronimo sample is more likely to be a useful guide to deploying an mdb on geronimo than the oracle documentation. thanks david jencks > > > Did you find documentation somewhere to support the properties you are > using? > > thanks > david jencks > > > > -- > View this message in context: http://www.nabble.com/Geronimo%3A-connectionFactoryJndiName-not-recognized-in-MDB-EJB-3.0-tp21674243s134p21678653.html > Sent from the Apache Geronimo - Users mailing list archive at > Nabble.com. > --Apple-Mail-7--814896592 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
On Jan 26, 2009, = at 6:42 PM, Lenin David Lozano Argel wrote:


Well, The Oracle OC4J How To MDB 3,0 use these = properties.

You can look at

http://www.oracle.com/technology/tec= h/java/oc4j/1013/how_to/how-to-ejb30-mdb/doc/how-to-ejb30-mdb.html
=
The sample in Oracle Oc4J uses these properties. I don't know how = to
associate the Connection Factory with the MDB in Geronimo or WAS = CE.


Unfortunately oracle = doesn't really make clear where the activation config properties come = from or how to tell which ones can be = used.

They come from the inbound messaging = resource adapter.  Unless you install something else, in geronimo = that's activemq.  Each inbound resource adapter comes with an = ActivationSpec class that is a javabean that indicates the properties = you can set on it.  A few of these can also be documented in the = ra.xml descriptor for the adapter.  The standard properties for jms = inbound adapters are:

The recommended properties = for JMS ActivationSpec JavaBean are: = destination 
(required), destinationType (required), messageSelector, acknowledgeMode, 
= clientId, = subscriptionName.

As you can see, the oracle = activation spec does not appear to support destination and uses the = decidedly non-standard 
I'll update our = documentation to make it clearer where the properties we use come from. =  However, the geronimo sample is more likely to be a useful guide = to deploying an mdb on geronimo than the oracle = documentation.

thanks
david jencks



Did = you find documentation somewhere to support the properties you are =  
using?

thanks
david jencks



-- =
View this message in context: http://www.nabble.co= m/Geronimo%3A-connectionFactoryJndiName-not-recognized-in-MDB-EJB-3.0-tp21= 674243s134p21678653.html
Sent from the Apache Geronimo - Users = mailing list archive at = Nabble.com.


= --Apple-Mail-7--814896592--