<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 03:31:17 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Liip Blog: Jackalope - JCR for PHP started]]></title>
      <guid>http://www.phpdeveloper.org/news/12497</guid>
      <link>http://www.phpdeveloper.org/news/12497</link>
      <description><![CDATA[<p>
In <a href="http://blog.liip.ch/archive/2009/05/11/jackalope-started.html">this new post</a> to the Liip blog <i>Tobias Ebnother</i> looks at <a href="http://liip.to/jackalope">Jackalope</a> that's looking to bring <a href="http://jcp.org/en/jsr/detail?id=283">JCR functionality</a> into the toolset offered to PHP developers.
</p>
<blockquote>
We initiated a new open source project called <A href="http://liip.to/jackalope">Jackalope</a>. Its purpose is to bring <a href="http://jcp.org/en/jsr/detail?id=283">JCR</a> via <a href="http://jackrabbit.apache.org/">Jackrabbit</a> to the PHP world. [...] JCR provides a great standardized storage for hierarchical content and supports some nice features like full text search, versioning, transactions, observation, and more. Our main goal is to create a PHP Connector for Jackrabbit without using any Java.
</blockquote>
<p>
To accomplish this, they're doing things in two steps. First, they've created a setup with the Java bridge (from Zend Server) to make the connection back to the Jackrabbit server and making writing tests to that API. The second step is to swap out the Java bridge with the Jackalope connection piece. You can check out the current state of the project on its <a href="http://github.com/jackalope">Github page</a> or come and ask questions of the team on the <a href="http://freenode.net/">Freenode</a> IRC network (#jackalope).
</p>]]></description>
      <pubDate>Tue, 12 May 2009 10:21:15 -0500</pubDate>
    </item>
  </channel>
</rss>
