<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-29445477</atom:id><lastBuildDate>Thu, 10 Jul 2008 19:11:12 +0000</lastBuildDate><title>Devel Hell</title><description/><link>http://www.stoleetech.com/develhell/</link><managingEditor>noreply@blogger.com (stolee)</managingEditor><generator>Blogger</generator><openSearch:totalResults>34</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-764970826343822373</guid><pubDate>Thu, 10 Jul 2008 19:03:00 +0000</pubDate><atom:updated>2008-07-10T12:11:12.092-07:00</atom:updated><title>A Note on Downloading Images to a Java Client via HTTP requests</title><atom:summary type='text'>I've been working on a little Java client to grab some internet data and process it into a nice little picture.  In order to do this, I needed to be able to download pictures from an HTTP request into a BufferedImage.  

When initially trying to find a way to do this, Google only gave me worthless pages about using the URLConnection.getContent() method, or saving to a file and loading that file, </atom:summary><link>http://www.stoleetech.com/develhell/2008/07/note-on-downloading-images-to-java.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-995027939344084910</guid><pubDate>Fri, 09 Mar 2007 20:43:00 +0000</pubDate><atom:updated>2007-03-09T12:56:38.771-08:00</atom:updated><title>Documentation Time</title><atom:summary type='text'>I'm struggling with making my first draft to be as high-quality as I would like it, especially with my time limitations before and during break.  However, getting comments on what I have right now will be very good for future writing as well.  I'm currently running performance tests on the system.  My current test case is a long one.  It is for 3 dimensions, and runs over 25 requests for each of </atom:summary><link>http://www.stoleetech.com/develhell/2007/03/documentation-time.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-8338238423589190518</guid><pubDate>Fri, 23 Feb 2007 06:44:00 +0000</pubDate><atom:updated>2007-02-22T22:48:47.363-08:00</atom:updated><title>Success?</title><atom:summary type='text'>I had been having a hang up with my lazy writing to the cache, which was a major problem for me.  By changing my CacheManagerBean to stateless instead of stateful, I was able to keep the bean around long enough to have a thread run through my queue of requested cache orders.  This will most likely be a speed boost, since the stateful wasn't getting me much, anyway.

I've been running my </atom:summary><link>http://www.stoleetech.com/develhell/2007/02/success.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-5430766197027914581</guid><pubDate>Thu, 11 Jan 2007 13:35:00 +0000</pubDate><atom:updated>2007-01-11T05:38:12.847-08:00</atom:updated><title>Annotations are the Problem</title><atom:summary type='text'>I've been trying to work out how I can insert large data sets into SQL through Hibernate without requiring my data sets to fit an interface that splits when too large (the overhead of exception handling would be too much, anyway).  It would be best if I could just designate my value with extra parameters in the @Lob annotation.  However, the annotation has no such properties, even though the XML </atom:summary><link>http://www.stoleetech.com/develhell/2007/01/annotations-are-problem.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-8137678035083852685</guid><pubDate>Wed, 10 Jan 2007 07:38:00 +0000</pubDate><atom:updated>2007-01-09T23:40:50.602-08:00</atom:updated><title>It's Been a While</title><atom:summary type='text'>I haven't posted in a while, but here's a good post of frustration!

I have been working on my thesis project, but have and issue with my Blobs... The default type of blob used by Hibernate is too small for my data.  So, I need to find a way to make it create a column of type LONGBLOB, or at least MEDIUMBLOB, but it makes me sad.  This one issue is (hopefully) all that stands between me and good </atom:summary><link>http://www.stoleetech.com/develhell/2007/01/its-been-while.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115507136499820953</guid><pubDate>Tue, 08 Aug 2006 21:09:00 +0000</pubDate><atom:updated>2006-08-08T14:09:25.013-07:00</atom:updated><title>Single Request Test Suite</title><atom:summary type='text'>Today, I created a new test program that I have programmed to make HTTP requests and time the important results.  Now, I can list a few parameters and run several tests over all three types to see how long it takes to request a region with a certain volume, number of cache hits, and percentage hit.  The framework is there to work, but for some reason I'm getting exceptions on the server.  I'll </atom:summary><link>http://www.stoleetech.com/develhell/2006/08/single-request-test-suite.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115323979121722178</guid><pubDate>Tue, 18 Jul 2006 16:18:00 +0000</pubDate><atom:updated>2006-07-18T09:25:10.493-07:00</atom:updated><title>Creating Test Suites</title><atom:summary type='text'>My current task is creating a plan for the performance testing.  One thing I know I'll need is a way to generate test cases.  My plan is to make servlets that create certain types of test cases dependent on a certain set of parameters.  Right now, I'm making the test case for creating a set of regions (of a defined number) that intersect a region with a certain hit percentage.  This will be used </atom:summary><link>http://www.stoleetech.com/develhell/2006/07/creating-test-suites.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115291668736153670</guid><pubDate>Fri, 14 Jul 2006 22:33:00 +0000</pubDate><atom:updated>2006-07-14T15:38:07.366-07:00</atom:updated><title>Singleton</title><atom:summary type='text'>I went ahead and made the EntityManagerFactory for the LazyWriter a singleton.  This caused me to pull the LazyWriter out of the CacheManagerBean and into a top-level class.  That is probably a good move, anyway.  Now, the hassle of loading the properties only needs to happen once per run of the server. </atom:summary><link>http://www.stoleetech.com/develhell/2006/07/singleton.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115291534961638053</guid><pubDate>Fri, 14 Jul 2006 22:11:00 +0000</pubDate><atom:updated>2006-07-14T15:15:49.663-07:00</atom:updated><title>Sometimes the Cutting Edge Hurts</title><atom:summary type='text'>I got lazy writing to work today.  The reason I didn't get it to work before was that I got frustrated with the meaningless error messages that I got while working with Hibernate.  It turns out that I was getting an error because an exception that was trying to be thrown couldn't be found.  Hibernate didn't include a necessary library with their deployment.  So, I got the latest stable version of</atom:summary><link>http://www.stoleetech.com/develhell/2006/07/sometimes-cutting-edge-hurts.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115289543068859250</guid><pubDate>Fri, 14 Jul 2006 16:39:00 +0000</pubDate><atom:updated>2006-07-14T09:43:56.363-07:00</atom:updated><title>Some First Results</title><atom:summary type='text'>Here is a screenshot of some performance testing on my cache.  This is using active database writes, over 50 requests randomly selected from 5 different, intersecting regions.  I am using a high multiple and high request volume, but not even close to the timing standards of a NADSS map.    </atom:summary><link>http://www.stoleetech.com/develhell/2006/07/some-first-results_14.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115273523542598689</guid><pubDate>Wed, 12 Jul 2006 20:09:00 +0000</pubDate><atom:updated>2006-07-12T13:13:55.443-07:00</atom:updated><title>So I Celebrated Early...</title><atom:summary type='text'>I guess I forgot to test lazy writes.  It seems that my EntityManager loses it's persistence context when my Statefule Session Bean is removed partially through the process.  Perhaps calling it the unmanaged way could do the trick. </atom:summary><link>http://www.stoleetech.com/develhell/2006/07/so-i-celebrated-early.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115273371285202949</guid><pubDate>Wed, 12 Jul 2006 19:44:00 +0000</pubDate><atom:updated>2006-07-12T12:48:32.910-07:00</atom:updated><title>It works!</title><atom:summary type='text'>After many sad hours of debugging my persistence model, I now have a working n-dimensional spatial cache!  Finally, results can now be found.  I need to put together a performance testing suite, and quickly.  Here are a few of the variables I can define:  No Cache vs. Active Write vs. Lazy WriteFor any test, it should be run three ways: without a cache at all, with active writing (wait for </atom:summary><link>http://www.stoleetech.com/develhell/2006/07/it-works.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115213446303064936</guid><pubDate>Wed, 05 Jul 2006 21:16:00 +0000</pubDate><atom:updated>2006-07-05T14:21:03.086-07:00</atom:updated><title>A Different Direction</title><atom:summary type='text'>I spent some time today thinking of a different way to approach the partitioning problem.  Instead of finding a minimal chord sequence (which gets really complicated and involves non-convex pivots and chords) I should think of maximal convex regions.  Expand regions in every direction from every unit block of the null space.  This is similar to the approach I had last summer, but instead of </atom:summary><link>http://www.stoleetech.com/develhell/2006/07/different-direction.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115161478090693123</guid><pubDate>Thu, 29 Jun 2006 20:55:00 +0000</pubDate><atom:updated>2006-06-29T13:59:40.910-07:00</atom:updated><title>Past the Biggest Bugs</title><atom:summary type='text'>Now that I have fixed all current crashes, it is time to nit pick and find things wrong with my implementation.  I need to set up a programmatic test suite, runnable by servlet, that tests the following things:    Caching completed data.     Loading cached information.     Combining data items after computing and caching.  There will be more on the way, but I need to get this suite set up and </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/past-biggest-bugs_29.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115161469322763872</guid><pubDate>Thu, 29 Jun 2006 20:54:00 +0000</pubDate><atom:updated>2006-06-29T13:58:13.390-07:00</atom:updated><title>Past the Biggest Bugs</title><atom:summary type='text'>Now that I have fixed all current crashes, it is time to nit pick and find things wrong with my implementation.  I need to set up a programmatic test suite, runnable by servlet, that tests the following things:    Caching completed data.     Loading cached information.     Combining data items after computing and caching.  There will be more on the way, but I need to get this suite set up and </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/past-biggest-bugs.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115160263436667559</guid><pubDate>Thu, 29 Jun 2006 17:33:00 +0000</pubDate><atom:updated>2006-06-29T10:37:14.410-07:00</atom:updated><title>And Now to More Important Issues</title><atom:summary type='text'>This morning, I fixed all of the immediate errors with persistence.  Apparently, using Object as a BLOB column generates a ClassCastException if you don't have exactly and Object there, but if you use Serializable as your member type then any serializable object can be put in there.  Now my biggest issue is figuring out how to call the cacheable method multiple times.  I was thinking that I could</atom:summary><link>http://www.stoleetech.com/develhell/2006/06/and-now-to-more-important-issues.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115153036335999505</guid><pubDate>Wed, 28 Jun 2006 21:29:00 +0000</pubDate><atom:updated>2006-06-28T14:32:43.410-07:00</atom:updated><title>It's in the Details</title><atom:summary type='text'>Sometimes I can really ignore the simplest of details when in a hurry.  I wasn't paying attention to which properties I added to my persistence.xml file and was using the wrong dialect for Hibernate and I needed just "update" as the auto property.  That's why my tables were not being created.  After swapping the values with the proper ones &lt;em&gt;easily seen in another file&lt;/em&gt; it worked properly.</atom:summary><link>http://www.stoleetech.com/develhell/2006/06/its-in-details.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115152290159991277</guid><pubDate>Wed, 28 Jun 2006 19:24:00 +0000</pubDate><atom:updated>2006-06-28T12:28:23.336-07:00</atom:updated><title>Some Notes on Debugging</title><atom:summary type='text'>I have the web project up and linked with the EAR and I'm tracking problems with my implementation.  Here are a few things that have gone wrong so far.  Some are fixed. Fixed: Cached annotation did not exist at runtime.Apparently, annotations only exist at compile time by default.  An extra annotation must be added to the @interface definition: @Retention(RetentionPolicy.RUNTIME).Fixed: </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/some-notes-on-debugging.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115142360457590076</guid><pubDate>Tue, 27 Jun 2006 15:49:00 +0000</pubDate><atom:updated>2006-06-27T08:53:24.620-07:00</atom:updated><title>Web Project Built</title><atom:summary type='text'>I got a web project built today.  I used my laptop with the Eclipse Web Tools plugin (doesn't work on intel macs until Friday) to create the project directories and an initial web.xml.  From that, I copied it into my Eclipse 3.2 framework and customized the build.xml plugin from Orangepeel.  I have a loose grasp of the directory structure now, and what all the xml configuration files do.  Now, I </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/web-project-built.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115134989180963236</guid><pubDate>Mon, 26 Jun 2006 19:21:00 +0000</pubDate><atom:updated>2006-06-26T12:24:52.576-07:00</atom:updated><title>Entity Tests Pass</title><atom:summary type='text'>The RTreeEntity structure now passes all POJO test cases.  Now, I need to set up the persisting and proplerly create, persist, and remove the data.  This will be a challenge as well.  I may need to recursively persist the nodes.  Also, I'll need to synchronize the tree between deletes and inserts, because that could cause all sorts of problems with the tree.  Cached data may not always be </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/entity-tests-pass.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115134052108989593</guid><pubDate>Mon, 26 Jun 2006 16:44:00 +0000</pubDate><atom:updated>2006-06-26T09:48:41.120-07:00</atom:updated><title>Persisting Trees</title><atom:summary type='text'>I'm not sure if it is a good idea to jump into spatial query trees in my first attempt at using persistence, but that's what I'm working on.  I need to finish rewriting my R-Tree, which wouldn't be that hard if I didn't need to use Collections instead of arrays.  Now, the conversion requires more thought.  After I test it in POJO form, I'll need to find a way to test it as it persists.  The </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/persisting-trees.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115091953594636213</guid><pubDate>Wed, 21 Jun 2006 19:48:00 +0000</pubDate><atom:updated>2006-06-21T12:52:19.860-07:00</atom:updated><title>The Solution?</title><atom:summary type='text'>I've developed an interface to help me with this dilemma I have.  The immediate benefit is that I never have to rewrite a method header, and I never have to rewrite the cache.  However, there will need to be a new object written that implements the CacheHelper interface for almost every new method (unless they become very similar).  Here are the three methods that are required:  public IRegion </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/solution.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115091084463994185</guid><pubDate>Wed, 21 Jun 2006 17:23:00 +0000</pubDate><atom:updated>2006-06-21T10:27:24.710-07:00</atom:updated><title>A Question of Parameters</title><atom:summary type='text'>I've thought about how to handle the dimension parameters in detail, but haven't quite decided.  There are several concerns that I have for this crucial section of my research.     First, I need to be able to get numerical limits on the spatial query.  I need a low and a high point for each defined dimension.  If the method signature contains a list of integers or floats listed "lowX, highX, lowY</atom:summary><link>http://www.stoleetech.com/develhell/2006/06/question-of-parameters.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115083273175305139</guid><pubDate>Tue, 20 Jun 2006 19:41:00 +0000</pubDate><atom:updated>2006-06-20T12:45:31.793-07:00</atom:updated><title>Bug Fixed with the Power of Testing</title><atom:summary type='text'>I seem to have fixed the deletion bug.  It passes my random test for dimensions 1,2,3,4,5, and 10 after several executions.  It used to fail every run, so hopefully it isn't just hiding.  I made my tests using TestNG, a relatively new framework for testing in Java. </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/bug-fixed-with-power-of-testing.html</link><author>noreply@blogger.com (stolee)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-29445477.post-115082546711748475</guid><pubDate>Tue, 20 Jun 2006 17:40:00 +0000</pubDate><atom:updated>2006-06-20T10:44:27.126-07:00</atom:updated><title>RTree Delays</title><atom:summary type='text'>My RTree implementation has a bug during deletion.  When I delete a node, it sometimes doesn't adjust the above nodes properly, so searching for nodes later causes a problem because the parent nodes no longer contain their children. </atom:summary><link>http://www.stoleetech.com/develhell/2006/06/rtree-delays.html</link><author>noreply@blogger.com (stolee)</author></item></channel></rss>