-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tommy,
On 8/14/12 7:24 PM, Tommy Lapierre wrote: > I am required to implement an OSGI bundle to listen to a JMS topic > and act accordingly. I am using Glassfish 3.1.2 with the embedded > JMS server. > > I am also required to implement another OSGI bundle to generate > JMS topics using the same technology. > > I am having diffculty connection to the JMS server, generating and > consuming messages. I need a very simple solution, localhost is > good for me. > > Can someone guide me in the right direction? Well, you can mix and match both OSGi as JEE technologies in Glassfish, so for starters you could create one OSGi bundle that registers a MDB for consuming your messages, which I think you should only annotate with "Export-EJB: None" in its manifest. And another OGSi bundle that produces those messages, which can be started from the bundle activator's start method. The only "problem" you face here is to obtain a valid pointer to a JMS session, but that can be solved by doing a manual JNDI lookup. I'm not sure whether Glassfish has some annotation-based injection mechanism present for this... > Also I would like to know if anyone has an opinion on managing > distributed osgi bundles. I have many server instances and need to > make sure all bundles are distributed among all servers. You could take a look at Apache ACE (http://ace.apache.org), which is probably the best option in your (short) scenario... - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is:/ Luminis Technologies B.V. IJsselburcht 3 6825 BS Arnhem +31 88 586 46 30 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQKp7/AAoJEKF/mP2eHDc4AdIQANFOHGftZXSh0IIltiR6Q6RR 5dcyC3pWnCMnQO+BasBZbvTdKtGqBOCStM+8YeLMOJmhDUgFsTeMIFPsSPXLfd+a xM3ikwM5CM1AFxvTCuQ8hUOqfOAmRDVEpl5lMYMn+8dfW7OzneLkQgy5s6vzeZcK BuPB2MOR+K+di46kRD6m+7dmcTKrfRGJJT1sGcjyHGarCJpHXCf95Q7VIBoo1byW K11/EfUaoqyNaOFpScQRiyLHT9soR6BHMyNth9hIsOTC9TEKaxvA+Q8iCqInSVoO cpeIHfSvOTqnnx98kuGQRKX94+DfRdlSQaH+bDHe9aOnD6kwlwdytA2WhPRF+4DP sP3ScBrWFqQTpHnY9cGTvUU4EKWLhgsPO9yaqKUPvdXGsHP7iXP8TxTZFiLXwh5t JQHGOhF78ES2nTjmHUYyCBqm4dYtRmv+PbWfwSryN/DDbeZY8Ir7e7eGNZMU0Z5G 63rTxpGWZeiTKie+kBhEY7wZ7xHIdA6EEV5vQ84dsvdTy3ZleVVT0iL2NcaU6bF4 km7rUNlYzDtHt++W0PKfZwFAizi5u4hW44NWjXnlCSn+XbTvCSKH5sxmKMXFfb1Q xN2nYr2iVgkUwHi5qHcqYUYXUoyYLrZ5eA4NZk6/UfrVp11p+ZYbb0wAzU9ygsYC GsfdnYD7wjFzH5Z8AQnC =+wCJ -----END PGP SIGNATURE----- _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
