<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss version="2.0">
  <channel>
    <title>Jenkov.com - News</title>
      <link>http://jenkov.com/rss/rss_all.jsp</link>
      <description>News from Jenkov.com about new releases, new articles etc.</description>
      <language>en</language>
      
      
      <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/jenkov-com" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
  <title>172 Texts on Java, Flex and Software Development Related Topics</title>
  <link>http://tutorials.jenkov.com</link>
 <description>
     After about 18 months in action http://tutorials.jenkov.com now has 172 texts about
     Java, Flex and other software development related topics. That is an average of about
     10 texts per month. I hope to be able to keep the flow of tutorials coming at the
     same speed in the future! Send me suggestions by email and I'll see what I can do.
 </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com</guid>
  <pubDate>2009.07.01</pubDate>
</item>

<item>
  <title>Advanced Java Connection and Transaction Demarcation and Propagation</title>
  <link>http://tutorials.jenkov.com/java-persistence/advanced-connection-and-transaction-demarcation-and-propagation.html</link>
 <description>
     The Java Persistence tutorial has been extended with a text explaining a more advanced way of demarcating the life
     span of connections and transactions in JDBC. It is this method that will soon be implemented in Butterfly Persistence,
     by the way.
 </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/java-persistence/advanced-connection-and-transaction-demarcation-and-propagation.html</guid>
  <pubDate>2009.06.29</pubDate>
</item>

<item>
  <title>Conceptual Implementation of Tetris</title>
  <link>http://tutorials.jenkov.com/flex-tetris/conceptual-implementation.html</link>
 <description>
     The Flex Tetris tutorial has been enriched with a new text explaining how to implement Tetris
     conceptually, meaning the rules and pseudo code behind the game. It is explained in a programming
     language independent fashion, so JavaFX programmers can also benefit from it.
 </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/flex-tetris/conceptual-implementation.html</guid>
  <pubDate>2009.06.23</pubDate>
</item>

<item>
  <title>Understanding Dependencies</title>
  <link>http://tutorials.jenkov.com/ood/understanding-dependencies.html</link>
 <description>
    Have you ever read a text online saying that "factories and interfaces = 100% decoupling" ?
     This is nonsense! You can't write a sane application without dependencies.
     All you can do is to make either looser or tighter couplings.
     This text examines the topic of dependencies a step deeper than the "classes vs. interfaces"
     discussion it usually revolves around, and it could possibly be taken even further, with your input.
     So check it out now, and let me know what you think.
 </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/ood/understanding-dependencies.html</guid>
  <pubDate>2009.06.16</pubDate>
</item>

<item>
  <title>The Opportunities Missed by Annotation Based Dependency Injection</title>
  <link>http://tutorials.jenkov.com/dependency-injection/the-opportunities-missed-by-annotation-based-dependency-injection.html</link>
 <description>
     There has been a lot of fuss lately regarding the @Inject JSR.
     Personally, I think that we are missing out on a lot of opportunities by
     using annotations to configure dependency injection containers.
     In this text I explain how and why.
 </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/dependency-injection/the-opportunities-missed-by-annotation-based-dependency-injection.html</guid>
  <pubDate>2009.06.09</pubDate>
</item>

<item>
  <title>API Design: Design for Easy Configuration</title>
  <link>http://tutorials.jenkov.com/api-design/design-for-easy-configuration.html</link>
 <description>
     The eighth text in the API design tutorial discusses why it is a good idea to
     think hard about what configuraiton mechanism you choose for your API.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/design-for-easy-configuration.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Design for Testing</title>
  <link>http://tutorials.jenkov.com/api-design/design-for-testing.html</link>
 <description>
     The seventh text in the API design tutorial discusses why it is a good idea to
     think testing into the design of your API, and gives a few tips about how to do it.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/design-for-testing.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Avoid External Dependencies</title>
  <link>http://tutorials.jenkov.com/api-design/avoid-external-dependencies.html</link>
 <description>
    The sixth text in the API design tutorial discusses why it is a bad idea to
     include external dependencies in your API.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/avoid-external-dependencies.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Don't Force the User to Assemble Componets</title>
  <link>http://tutorials.jenkov.com/api-design/dont-force-the-user-to-assemble-components.html</link>
 <description>
    The fifth text in the API design tutorial discusses why it is a bad idea to
     force the user to assemble the components of your API, even if the user is
     using a dependency injection container.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/dont-force-the-user-to-assemble-components.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Central Point of Access</title>
  <link>http://tutorials.jenkov.com/api-design/central-point-of-access.html</link>
 <description>
    The fourth text in the API design tutorial discusses why it is a good idea to
     provide one (or a few) central point of access to the API.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/central-point-of-access.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Optinal Abstractions</title>
  <link>http://tutorials.jenkov.com/api-design/optional-abstractions.html</link>
 <description>
    The third text in the API design tutorial discusses why you should consider
     making your abstractions optional.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/optional-abstractions.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Sensible Defaults</title>
  <link>http://tutorials.jenkov.com/api-design/provide-sensible-defaults.html</link>
 <description>
    The second text in the API design tutorial discusses why it is a good idea to provide
     sensible defaults in your API's components, from a usability point of view.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/provide-sensible-defaults.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Don't Expose More than Necessary</title>
  <link>http://tutorials.jenkov.com/api-design/dont-expose-more-than-necessary.html</link>
 <description>
    The first text in the API design tutorial discusses why you should not expose more than
     necessary of the internals of your API.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/dont-expose-more-than-necessary.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

<item>
  <title>API Design: Introduction</title>
  <link>http://tutorials.jenkov.com/api-design/index.html</link>
 <description>
     Having developed API's for about 8 years now, some of that time
     open source API's like Butterfly Components,
     I have put together a few guidelines for API design. I am writing these down in this
     trail both for myself to remember, and as inspiration for anyone else interested.
     It is currently 9 texts with 9 different guidelines.
  </description>
  <guid isPermaLink="true">http://tutorials.jenkov.com/api-design/index.html</guid>
  <pubDate>2009.06.03</pubDate>
</item>

























      <item>
  <title>Butterfly Persistence 5.1.15-beta</title>
  <link>http://butterfly.jenkov.com</link>
  <description>
    Version 5.1.15 contains support for connection and transaction scoping.
      via the ScopingDataSource.
    This is something that can otherwise be quite messy to handle yourself.
  </description>
  <guid isPermaLink="false">http://butterfly.jenkov.com/21</guid>
  <pubDate>2009.07.01</pubDate>
</item>
<item>
  <title>Butterfly Web UI 1.0.12</title>
  <link>http://butterfly.jenkov.com</link>
  <description>
    In this version it has been made a lot easier to map components to URL's.
  </description>
  <guid isPermaLink="false">http://butterfly.jenkov.com/21</guid>
  <pubDate>2009.06.29</pubDate>
</item>
<item>
  <title>Butterfly Persistence 5.1.14-beta</title>
  <link>http://butterfly.jenkov.com</link>
  <description>
    Version 5.1.14 contains support for creating and upgrading databases from
      within your application (or a separate application if you like).
  </description>
  <guid isPermaLink="false">http://butterfly.jenkov.com/20</guid>
  <pubDate>2009.06.29</pubDate>
</item>
<item>
  <title>Butterfly DI Container 2.9.9-beta</title>
  <link>http://butterfly.jenkov.com</link>
  <description>
      Version 2.9.9 contains support for using Butterfly Container as an
      internationalization mechanism for both components and texts.
  </description>
  <guid isPermaLink="false">http://butterfly.jenkov.com/19</guid>
  <pubDate>2009.06.29</pubDate>
</item>











      <item>
  <title>Book Review: Dependency Injection</title>
  <link>http://jenkov.com/book-reviews/dependency-injection.html</link>
  <description>
      I as approached by Manning Publications and asked if I would be interested in writing a book review
      of their upcoming book "Dependency Injection" by Dhanji R. Prasanna. Being the developer of the
      dependency injection container for Java, Butterfly Container, and having written about dependency
      injection before, I was naturally interested in what this book had to offer. It turned out to be a
      very good book. Want to know more about this book? Then go ahead and read the review now!
  </description>
  <guid isPermaLink="true">http://jenkov.com/book-reviews/dependency-injection.html</guid>
  <pubDate>2009.02.19</pubDate>
</item>





      <item>
  <title>ScriptDraw 1.2.0 Released</title>
  <link>http://scriptdraw.com</link>
  <description>
      Version 1.2.0 of ScriptDraw.com - the free online SVG editor -
      contains buttons for left, right, up and down arrows. These
      arrows are generated using the SVG path element.
  </description>
  <guid isPermaLink="false">http://scriptdraw.com/3</guid>
  <pubDate>2009.04.03</pubDate>
</item>

<item>
  <title>ScriptDraw 1.1.10 Released</title>
  <link>http://scriptdraw.com</link>
  <description>
      Version 1.1.10 of ScriptDraw.com - the free online SVG editor -
      contains support for "undo", meaning it is now possible to undo
      the last 20 actions. In addition, buttons have been added for
      inserting SVG for basic shapes (rect, circle, ellipse, line etc.).
      Finally, all buttons have now also been given keyboard shortcuts.
      These are visible when you hover the mouse over the buttons, in
      the tooltips. These changes make ScriptDraw a lot easier to work
      with!
  </description>
  <guid isPermaLink="false">http://scriptdraw.com/2</guid>
  <pubDate>2009.02.03</pubDate>
</item>

<item>
  <title>ScriptDraw 1.0 Released</title>
  <link>http://scriptdraw.com</link>
  <description>
      ScriptDraw is a simple free online SVG editor. You type in the
      SVG XML and press a button to see the SVG image as it is rendered
      in your browser. More features will be added in the future.
  </description>
  <guid isPermaLink="false">http://scriptdraw.com/1</guid>
  <pubDate>2009.01.15</pubDate>
</item>









  </channel>
</rss>
