Hello all! The beta program for the JNBridge JMS Adapter is under way. Those of you who’ve already registered for the Beta Partner Program will receive an e-mail linking you to the download page for Beta1. If you haven’t registered, go to www.jnbridge.com/adapter  and I’ll follow up with the link.  

I’m Bill Heinzman. I will be the main contact for the beta program. Direct all your questions to beta@jnbridge.com.  I’ll be providing all technical support, receiving and replying to your questions and feedback.  I know you’re all busy, so if you run into a problem, or don’t understand the documentation—don’t waste your time, send me an e-mail and I’ll remedy the problem ASAP.

I’ll be blogging several times a week providing technical articles on the capabilities of the JNBridge JMS Adapter in combination with WCF, .Net and Visual Studio. I’ll start out each week with a summary of things learned (and the resulting new feature) ,  things fixed and directions to the latest documentation, patch or beta bits.

For those of you new to JNBridge’s technology and the JMS Adapter, here’s the synopsis:

The JNBridge WCF Adapter for JMS™ is a Windows Communication Foundation implementation that encapsulates Java Message Service client capabilities into a standard WCF Line of Business Adapter. The JNBridge JMS Adapter integrates JMS into into any .Net solution using Visual Studio 2005.

The JNBridge JMS Adapter exposes a simple, yet dynamic  interface for producing and consuming JMS messages to and from queues and topics without requiring knowledge of JMS classes, architecture—or even Java, for that matter. During the installation of the JNBridge JMS Adapter, a new plug–in is added to Visual Studio that provides design time integration in .Net applications. By using the new Add Adapter Service Reference plug–in, a developer can create a .Net C# WCF client proxy for integration into a .Net assembly, form or application.  The developer can browse specific send and receive operations particular to the queues and topics discovered on any JMS implementation including OpenJMS, JBoss, Websphere, Tibco EMS and WebLogic.

Bill