<?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: OpenEdge Dynamic OpenClient Java Example</title>
	<atom:link href="http://www.thesoftwaregorilla.com/2009/11/openedge-dynamic-openclient-java-example/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thesoftwaregorilla.com/2009/11/openedge-dynamic-openclient-java-example/</link>
	<description>The Software Gorilla</description>
	<lastBuildDate>Tue, 06 Dec 2011 03:33:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Bruce Gruenbaum</title>
		<link>http://www.thesoftwaregorilla.com/2009/11/openedge-dynamic-openclient-java-example/comment-page-1/#comment-224</link>
		<dc:creator>Bruce Gruenbaum</dc:creator>
		<pubDate>Thu, 08 Jul 2010 16:51:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesoftwaregorilla.com/?p=90#comment-224</guid>
		<description>Hi Jon.

This code is derived from code a while back before JPA became commercial. Now that I have done some work with JPA myself, I can see a lot of places where this could be done so much more effectively using JPA.  

I have written a parser that reads the OpenEdge R-Code (provided it is not encrypted) and produces the signature of the .p from the R-Code. The advantage is that it can construct the temp-table/ProDataSet structure on the Java side so that it can be created and passed to OpenEdge. 

Regards,
Bruce</description>
		<content:encoded><![CDATA[<p>Hi Jon.</p>
<p>This code is derived from code a while back before JPA became commercial. Now that I have done some work with JPA myself, I can see a lot of places where this could be done so much more effectively using JPA.  </p>
<p>I have written a parser that reads the OpenEdge R-Code (provided it is not encrypted) and produces the signature of the .p from the R-Code. The advantage is that it can construct the temp-table/ProDataSet structure on the Java side so that it can be created and passed to OpenEdge. </p>
<p>Regards,<br />
Bruce</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.thesoftwaregorilla.com/2009/11/openedge-dynamic-openclient-java-example/comment-page-1/#comment-220</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Thu, 08 Jul 2010 15:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesoftwaregorilla.com/?p=90#comment-220</guid>
		<description>Hi,
Nice example of using OpenClient. I&#039;m doing something similar but I use reflection and annotations on POJOs for the dataset/temp-table mapping. I borrowed the annotations and general architecture ideas from JPA. The big breakthrough for me was realizing I can define datasets normally in the .p files, and the parameter type to dataset-handle in Java. That lets the schema be defined dynamically on the Java side. Things will get much more complicated if I ever need to pass filled-out datasets from Java to Progress, but I&#039;ve avoided that so far. Simple parameters going in, datasets coming out.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Nice example of using OpenClient. I&#039;m doing something similar but I use reflection and annotations on POJOs for the dataset/temp-table mapping. I borrowed the annotations and general architecture ideas from JPA. The big breakthrough for me was realizing I can define datasets normally in the .p files, and the parameter type to dataset-handle in Java. That lets the schema be defined dynamically on the Java side. Things will get much more complicated if I ever need to pass filled-out datasets from Java to Progress, but I&#039;ve avoided that so far. Simple parameters going in, datasets coming out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchange Web Services &#8211; Subscriptions and Notifications &#124; The Software Gorilla</title>
		<link>http://www.thesoftwaregorilla.com/2009/11/openedge-dynamic-openclient-java-example/comment-page-1/#comment-199</link>
		<dc:creator>Exchange Web Services &#8211; Subscriptions and Notifications &#124; The Software Gorilla</dc:creator>
		<pubDate>Tue, 06 Jul 2010 21:16:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesoftwaregorilla.com/?p=90#comment-199</guid>
		<description>[...] walkthrough of some example code that actually demonstrates the functionality, like I did with the Dynamic OpenClient code late last year.&#160; GD Star Ratingloading...Exchange Web Services - Subscriptions and Notifications, 4.5 out of [...]</description>
		<content:encoded><![CDATA[<p>[...] walkthrough of some example code that actually demonstrates the functionality, like I did with the Dynamic OpenClient code late last year.&nbsp; GD Star Ratingloading&#8230;Exchange Web Services &#8211; Subscriptions and Notifications, 4.5 out of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchange Web Services Example &#8211; Part 1 &#8211; Introduction and Set up &#124; The Software Gorilla</title>
		<link>http://www.thesoftwaregorilla.com/2009/11/openedge-dynamic-openclient-java-example/comment-page-1/#comment-77</link>
		<dc:creator>Exchange Web Services Example &#8211; Part 1 &#8211; Introduction and Set up &#124; The Software Gorilla</dc:creator>
		<pubDate>Thu, 20 May 2010 14:55:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesoftwaregorilla.com/?p=90#comment-77</guid>
		<description>[...] through that shows how to do the stuff. I had thought of doing a complete walk through like the Dynamic OpenClient code that I did back in November last year, but I wasn&#039;t as busy back then as I am now, and I had the time to actually write up the [...]</description>
		<content:encoded><![CDATA[<p>[...] through that shows how to do the stuff. I had thought of doing a complete walk through like the Dynamic OpenClient code that I did back in November last year, but I wasn&#39;t as busy back then as I am now, and I had the time to actually write up the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

