<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Some musings on JCA (Java Connector Architecture)</title>
	<atom:link href="http://technology.amis.nl/2006/03/09/some-musings-on-jca-java-connector-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://technology.amis.nl/2006/03/09/some-musings-on-jca-java-connector-architecture/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=some-musings-on-jca-java-connector-architecture</link>
	<description></description>
	<lastBuildDate>Fri, 12 Apr 2013 10:04:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: ral</title>
		<link>http://technology.amis.nl/2006/03/09/some-musings-on-jca-java-connector-architecture/#comment-2959</link>
		<dc:creator>ral</dc:creator>
		<pubDate>Thu, 16 Mar 2006 09:53:34 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=1087#comment-2959</guid>
		<description><![CDATA[Lucas, your impressions and descriptions over JCA are very interesting.

In the last days i have configurated Sun&#039;s JCA, to use it within ServiceMix.

The JCA was used for inbound &amp; outbound communications between ESB(ServiceMix) and Sun&#039;s Application-Server (Business-Intelligence).

With ServiceMix the JCA was used outside of the J2EE-Container, using Jencks-Container, Spring and POJO&#039;s.

This was my first configuration of JCA outside of a J2EE-Container and maybe a little bit stony - but the results and demonstrated potentialities was very impressiv for me.

cu]]></description>
		<content:encoded><![CDATA[<p>Lucas, your impressions and descriptions over JCA are very interesting.</p>
<p>In the last days i have configurated Sun&#8217;s JCA, to use it within ServiceMix.</p>
<p>The JCA was used for inbound &amp; outbound communications between ESB(ServiceMix) and Sun&#8217;s Application-Server (Business-Intelligence).</p>
<p>With ServiceMix the JCA was used outside of the J2EE-Container, using Jencks-Container, Spring and POJO&#8217;s.</p>
<p>This was my first configuration of JCA outside of a J2EE-Container and maybe a little bit stony &#8211; but the results and demonstrated potentialities was very impressiv for me.</p>
<p>cu</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy</title>
		<link>http://technology.amis.nl/2006/03/09/some-musings-on-jca-java-connector-architecture/#comment-2958</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Tue, 14 Mar 2006 17:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=1087#comment-2958</guid>
		<description><![CDATA[Lucas, I understand.  My point was that once you start adding transaction and resource management to the bbasic Spring IoC (as the statement in your article seemed to imply), you&#039;ve brought in a large part of the &quot;complexity&quot; as you put it, of what a JavaEE container does.

I&#039;d agree that basic Spring IoC is &quot;lightweight&quot; and is great for what it does.  Where I start to scratch my head is when people throw in the &quot;transaction and resource management&quot; aspects of Spring and still call it lightweight...when somehow a JavaEE container that&#039;s doing the same jobs (and requiring similar configuration) is called &quot;heavyweight.&quot;

Peace]]></description>
		<content:encoded><![CDATA[<p>Lucas, I understand.  My point was that once you start adding transaction and resource management to the bbasic Spring IoC (as the statement in your article seemed to imply), you&#8217;ve brought in a large part of the &#8220;complexity&#8221; as you put it, of what a JavaEE container does.</p>
<p>I&#8217;d agree that basic Spring IoC is &#8220;lightweight&#8221; and is great for what it does.  Where I start to scratch my head is when people throw in the &#8220;transaction and resource management&#8221; aspects of Spring and still call it lightweight&#8230;when somehow a JavaEE container that&#8217;s doing the same jobs (and requiring similar configuration) is called &#8220;heavyweight.&#8221;</p>
<p>Peace</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucas Jellema</title>
		<link>http://technology.amis.nl/2006/03/09/some-musings-on-jca-java-connector-architecture/#comment-2957</link>
		<dc:creator>Lucas Jellema</dc:creator>
		<pubDate>Sat, 11 Mar 2006 07:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=1087#comment-2957</guid>
		<description><![CDATA[Randy, You are right of course in your assessment that Spring is a Container. An IoC (inversion of Control) Container. However, Spring is not itself a formal container such as a J2EE container. When I say out of container, I mean out of the J2EE Container with its complexity, adminisrtation overhead and frequently license fees. Leveraging the Spring IoC Container is pretty easy: add a jar to the CLASSPATH and instantiate (certain) objects through the Spring Container (aka BeanFactory).

To leverage JCA from a standalone Java Application, having to use a fullblown J2EE container is extreme overkill, while bringing in Spring is quite lightweight. As of course would be using Apache WSIF.

best regards,
Lucas]]></description>
		<content:encoded><![CDATA[<p>Randy, You are right of course in your assessment that Spring is a Container. An IoC (inversion of Control) Container. However, Spring is not itself a formal container such as a J2EE container. When I say out of container, I mean out of the J2EE Container with its complexity, adminisrtation overhead and frequently license fees. Leveraging the Spring IoC Container is pretty easy: add a jar to the CLASSPATH and instantiate (certain) objects through the Spring Container (aka BeanFactory).</p>
<p>To leverage JCA from a standalone Java Application, having to use a fullblown J2EE container is extreme overkill, while bringing in Spring is quite lightweight. As of course would be using Apache WSIF.</p>
<p>best regards,<br />
Lucas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy</title>
		<link>http://technology.amis.nl/2006/03/09/some-musings-on-jca-java-connector-architecture/#comment-2956</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Fri, 10 Mar 2006 23:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=1087#comment-2956</guid>
		<description><![CDATA[&quot;The Spring Framework, since release 1.2, provides support for out-of-container access to JCA conectors...&quot;

&quot;The aim of the Spring CCI support...leverating Spring&#039;s general resource and transaction management facilities.&quot;

Hmm, isn&#039;t Spring then just another type of &quot;container&quot;?  What exactly about accessing a JCA connector from within Spring causes it to be &quot;out of container&quot;?]]></description>
		<content:encoded><![CDATA[<p>&#8220;The Spring Framework, since release 1.2, provides support for out-of-container access to JCA conectors&#8230;&#8221;</p>
<p>&#8220;The aim of the Spring CCI support&#8230;leverating Spring&#8217;s general resource and transaction management facilities.&#8221;</p>
<p>Hmm, isn&#8217;t Spring then just another type of &#8220;container&#8221;?  What exactly about accessing a JCA connector from within Spring causes it to be &#8220;out of container&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucas Jellema</title>
		<link>http://technology.amis.nl/2006/03/09/some-musings-on-jca-java-connector-architecture/#comment-2955</link>
		<dc:creator>Lucas Jellema</dc:creator>
		<pubDate>Fri, 10 Mar 2006 06:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=1087#comment-2955</guid>
		<description><![CDATA[The Server Side: I just stumbled across a reference to this article on  The Server Side. It&#039;s nice to be referenced in this way. See: http://www.theserverside.com/news/thread.tss?thread_id=39376]]></description>
		<content:encoded><![CDATA[<p>The Server Side: I just stumbled across a reference to this article on  The Server Side. It&#8217;s nice to be referenced in this way. See: <a href="http://www.theserverside.com/news/thread.tss?thread_id=39376" rel="nofollow">http://www.theserverside.com/news/thread.tss?thread_id=39376</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
