<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Opinion: Working around restricted JMS APIs in J2EE</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Thu, 20 Jun 2013 02:43:38 -0400</pubDate>


    <item>

        <title>Opinion: Working around restricted JMS APIs in J2EE</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=22392</link>

        

        
            <description><![CDATA[Of course, the right people can reproduce anything we do as vendors, it's all just code in the end. A better way of stating my point below is that you lose access to the vendor supplied plumbing, XA, pooling etc....]]></description>
        

        <pubDate>Thu, 13 Nov 2003 21:27:47 -0500</pubDate>

        

        <jf:creationDate>Thu, 13 Nov 2003 21:27:47 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 13 Nov 2003 21:27:47 -0500</jf:modificationDate>
        <jf:date>Nov 13, 2003</jf:date>
        <jf:author>Billy Newport</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Opinion: Working around restricted JMS APIs in J2EE</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=22392</link>

        

        
            <description><![CDATA[While I agree that some of the concepts in the article are useful, I think the &quot;BUT&quot; below overstates the case a bit:...]]></description>
        

        <pubDate>Thu, 13 Nov 2003 18:05:34 -0500</pubDate>

        

        <jf:creationDate>Thu, 13 Nov 2003 18:05:34 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 13 Nov 2003 18:05:34 -0500</jf:modificationDate>
        <jf:date>Nov 13, 2003</jf:date>
        <jf:author>Tom Barnes</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Opinion: Working around restricted JMS APIs in J2EE</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=22392</link>

        

        
            <description><![CDATA[JCA 1.5 won't solve this 'problem', the wrapper isn't the problem. JCA 1.5 will be cleaner in terms of the contract for XA between the server and the JMS provider. JCA 1.0 and JMS just don't work well together (mismatch between JCA requiring connections...]]></description>
        

        <pubDate>Thu, 13 Nov 2003 12:09:11 -0500</pubDate>

        

        <jf:creationDate>Thu, 13 Nov 2003 12:09:11 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 13 Nov 2003 12:09:11 -0500</jf:modificationDate>
        <jf:date>Nov 13, 2003</jf:date>
        <jf:author>Billy Newport</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Opinion: Working around restricted JMS APIs in J2EE</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=22392</link>

        

        
            <description><![CDATA[Billy Newport has written about restrictions that J2EE developers face when working with JMS. He explains that when you lookup a JMS provider that was declared in your application server, your code gets back a wrapped version (wrapped connection, wrapper...]]></description>
        

        <pubDate>Thu, 13 Nov 2003 11:26:15 -0500</pubDate>

        

        <jf:creationDate>Thu, 13 Nov 2003 11:26:15 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 13 Nov 2003 11:26:15 -0500</jf:modificationDate>
        <jf:date>Nov 13, 2003</jf:date>
        <jf:author>Dion Almaer</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>



</channel>
</rss>

