<?xml version="1.0" encoding="iso-8859-1" standalone="yes"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns="http://purl.org/rss/1.0/"
> 

  <channel rdf:about="https://dev.blogger.de/">
    <title>John Developer</title>
    <link>https://dev.blogger.de/</link>
    <description></description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>fuel</dc:creator>
    <dc:date>2009-02-05T10:54:17Z</dc:date>
    <dc:language>en</dc:language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T00:00:00Z</sy:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="https://dev.blogger.de/stories/1171995/" />
        <rdf:li rdf:resource="https://dev.blogger.de/stories/1288565/" />
        <rdf:li rdf:resource="https://dev.blogger.de/stories/1191655/" />
        <rdf:li rdf:resource="https://dev.blogger.de/stories/1184495/" />
        <rdf:li rdf:resource="https://dev.blogger.de/stories/1180615/" />
        <rdf:li rdf:resource="https://dev.blogger.de/stories/1174447/" />
        <rdf:li rdf:resource="https://dev.blogger.de/stories/1171746/" />

    </rdf:Seq>
    </items>
<textinput rdf:resource="https://dev.blogger.de/search" />
  </channel>

  <item rdf:about="https://dev.blogger.de/stories/1171995/">
    <title>EJB3: PostGIS and Hibernate</title> 
    <link>https://dev.blogger.de/stories/1171995/</link>
    <description>Ever dreamed of container managed persistence for your PostGIS database? Here&apos;s one solution.

PostGIS is a spatial extension to the PostgreSQL database which adds support for geographic objects and operations. Because of these new database types special treatment is needed when defining your persistent unit and generating your entity beans.

First of all you have to download the hibernate spatial extension libraries hibernate-spatial-1.0-M1.jar and hibernate-spatial-postgis-1.0-M1.jar from http://www.hibernatespatial.org....</description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>bq</dc:creator>
    <dc:subject>EJB3</dc:subject>
    <dc:rights>Copyright &#169; 2008 bq</dc:rights>
    <dc:date>2008-07-08T22:20:06Z</dc:date>
  </item> 
  <item rdf:about="https://dev.blogger.de/stories/1288565/">
    <title>Netbeans Collaboration works with normal Jabber accounts</title> 
    <link>https://dev.blogger.de/stories/1288565/</link>
    <description>Netbeans 6.5 ships with Developer Collaboration as default. It may not be obvious from the description or from the dialogs, but it seems the feature works with any normal Jabber account. So there&apos;s no need to create yet another account on share.java.net, but you can use an existing account on a public or in-house Jabber server. We have tried it with two accounts on jabber.ccc.de and were able to use the Collaboration successfully.

There is a major drawback, though: Collaboration doesn&amp;#8217;t implement...</description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>fuel</dc:creator>
    <dc:subject>Netbeans</dc:subject>
    <dc:rights>Copyright &#169; 2008 fuel</dc:rights>
    <dc:date>2008-12-11T15:13:07Z</dc:date>
  </item> 
  <item rdf:about="https://dev.blogger.de/stories/1191655/">
    <title>Using &amp;#8216;+&amp;#8217; and &amp;#8216;-&amp;#8217; for Shell...</title> 
    <link>https://dev.blogger.de/stories/1191655/</link>
    <description>The directory stack of Unix shells is a useful feature to set temporary &amp;#8220;bookmarks&amp;#8221; to directories, but I find pushd and popd long and cumbersome to type. I can recommend to alias them to &amp;#8216;+&amp;#8217; and &amp;#8216;-&amp;#8217;, which are easy to remember and fast to type:


alias +=&apos;pushd .&apos;
alias -- -=&apos;popd&apos;
</description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>fuel</dc:creator>
    <dc:subject>Shell</dc:subject>
    <dc:rights>Copyright &#169; 2008 fuel</dc:rights>
    <dc:date>2008-08-04T18:37:20Z</dc:date>
  </item> 
  <item rdf:about="https://dev.blogger.de/stories/1184495/">
    <title>Konsole &amp;#8211; the scriptable terminal emulator</title> 
    <link>https://dev.blogger.de/stories/1184495/</link>
    <description>Konsole, the terminal emulator of KDE, is scriptable via DCOP (the IPC mechanism of KDE3). I use this feature to start a Konsole session with several tabs. Each tab has its title set to a meaningful name and possibly a command executed. I use this when running an application in JBoss. In the first tab JBoss is run, in the next I let the JBoss log scroll through, in the next I watch the application log, and so on. You may find your own usage for tasks you do daily.

One &amp;#8220;trick&amp;#8221; is to start...</description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>fuel</dc:creator>
    <dc:subject>Shell</dc:subject>
    <dc:rights>Copyright &#169; 2008 fuel</dc:rights>
    <dc:date>2008-07-24T18:40:30Z</dc:date>
  </item> 
  <item rdf:about="https://dev.blogger.de/stories/1180615/">
    <title>Vim tip: soft textwidth for source code &amp;#8211; highlight...</title> 
    <link>https://dev.blogger.de/stories/1180615/</link>
    <description>When editing source code in Vim I want to have a soft limit on 80 columns. I try to generally format code to fit this convention, but with the possibility to escape it if it gets too ugly. That&apos;s why I wouldn&apos;t :set textwidth=80. Instead set an additional syntax highlighting rule, by adding to your .vimrc:

&quot; Highlight column 80
match CursorColumn /\%80v./

This adds to an existing syntax highlighting, so you can keep your existing highlighting or file type settings as they are.

See :help \%v for...</description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>fuel</dc:creator>
    <dc:subject>Vim</dc:subject>
    <dc:rights>Copyright &#169; 2008 fuel</dc:rights>
    <dc:date>2008-07-19T19:27:08Z</dc:date>
  </item> 
  <item rdf:about="https://dev.blogger.de/stories/1174447/">
    <title>A software quality metric for JBoss AS</title> 
    <link>https://dev.blogger.de/stories/1174447/</link>
    <description>When you thought about creating a global keyboard shortcut to restart your development JBoss, then software quality is not good enough!</description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>fuel</dc:creator>
    <dc:subject>EJB3</dc:subject>
    <dc:rights>Copyright &#169; 2008 fuel</dc:rights>
    <dc:date>2008-07-11T16:28:00Z</dc:date>
  </item> 
  <item rdf:about="https://dev.blogger.de/stories/1171746/">
    <title>Restart JBoss after changes to datasources</title> 
    <link>https://dev.blogger.de/stories/1171746/</link>
    <description>Have you tried turning it off and on again? If you make changes to a data source descriptor (a *-ds.xml file), after deployment restart JBoss to put them into effect! JBoss will log that it has successfully deployed the file, but not actually adopt the changes. The first database operation will fail and very misleading error messages follow.

(This may be well be a problem on my side. Any hints?)</description>
    <dc:publisher>Blogger.de</dc:publisher>
    <dc:creator>fuel</dc:creator>
    <dc:subject>JBoss</dc:subject>
    <dc:rights>Copyright &#169; 2008 fuel</dc:rights>
    <dc:date>2008-07-08T18:11:36Z</dc:date>
  </item> 


   <textinput rdf:about="https://dev.blogger.de/search">
      <title>find</title>
      <description>Search this site:</description>
      <name>q</name>
      <link>https://dev.blogger.de/search</link>
   </textinput>
</rdf:RDF>
