<!--
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sun May 19 18:42:18 UTC 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.doctrine-project.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+PHPCR+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC&tempMax=1000&field=key&field=summary
-->
<!-- If you wish to do custom client-side styling of RSS, uncomment this:
<?xml-stylesheet href="http://www.doctrine-project.org/jira/styles/jiraxml2html.xsl" type="text/xsl"?>
-->
<rss version="0.92">
    <channel>
        <title>Doctrine Project</title>
        <link>http://www.doctrine-project.org/jira/secure/IssueNavigator.jspa?reset=true&amp;jqlQuery=project+%3D+PHPCR+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC</link>
        <description>An XML representation of a search request</description>
                <language>en-us</language>
                        <issue start="0" end="34" total="34"/>
                <build-info>
            <version>5.2.7</version>
            <build-number>850</build-number>
            <build-date>21-02-2013</build-date>
        </build-info>
<item>
            <title>[PHPCR-61] review how the ORM and other ODM&apos;s initialize collection properties</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-61</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;right now when we for example have a @ReferenceMany but nothing is assigned, then when we read said object from the database that property is set to null. should it rather be initialized as an empty collection?&lt;/p&gt;</description>
                <environment></environment>
            <key id="13602">PHPCR-61</key>
            <summary>review how the ORM and other ODM&apos;s initialize collection properties</summary>
                <type id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/task.png">Task</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Wed, 4 Apr 2012 08:36:01 +0000</created>
                <updated>Thu, 18 Apr 2013 12:47:02 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-91] getSIngleResult throws ambiguous Exception</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-91</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;Query-&amp;gt;getSingleResult correctly throws an Exception when there are no results (or more than one), but it is an Exception that could also be produced by other things, so not guaranteed to mean that (&lt;br/&gt;
(&lt;a href=&quot;http://docs.doctrine-project.org/projects/doctrine-phpcr-odm/en/latest/reference/query.html#getsingleresult&quot; class=&quot;external-link&quot;&gt;http://docs.doctrine-project.org/projects/doctrine-phpcr-odm/en/latest/reference/query.html#getsingleresult&lt;/a&gt;)&lt;/p&gt;</description>
                <environment></environment>
            <key id="14501">PHPCR-91</key>
            <summary>getSIngleResult throws ambiguous Exception</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dantleech">Daniel Leech</reporter>
                        <labels>
                        <label>1.0</label>
                        <label>query</label>
                    </labels>
                <created>Tue, 19 Feb 2013 22:09:00 +0000</created>
                <updated>Thu, 18 Apr 2013 13:12:06 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-71] refactor exceptions</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-71</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;&lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/144#discussion_r963877&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/144#discussion_r963877&lt;/a&gt; reveiled that we should look into the exception concepts and streamline them.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13774">PHPCR-71</key>
            <summary>refactor exceptions</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Tue, 12 Jun 2012 08:33:35 +0000</created>
                <updated>Thu, 18 Apr 2013 13:09:42 +0000</updated>
                                                                            <due></due>
                    <votes>1</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-105] ensure xml and yml naming conventions are consistent</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-105</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;for yml, all mappings must use camelCase, while for xml it must be connected-text in all lowercase with the dash between. it seems at least fieldName is wrong.&lt;/p&gt;

&lt;p&gt;we should clean this up before the first release to avoid having to deal with inconsistent legacy from the beginning.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14709">PHPCR-105</key>
            <summary>ensure xml and yml naming conventions are consistent</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Thu, 21 Mar 2013 09:36:40 +0000</created>
                <updated>Fri, 19 Apr 2013 12:07:23 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="20066" author="dbu" created="Fri, 19 Apr 2013 12:06:01 +0000"  >&lt;p&gt;for xml, see this PR &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/279&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/279&lt;/a&gt;&lt;/p&gt;</comment>
                    <comment id="20068" author="dbu" created="Fri, 19 Apr 2013 12:07:23 +0000"  >&lt;p&gt;yml is using camelCase everywhere. should we rename fieldName to name as well or is that fine here?&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-77] document level options inheritance</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-77</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;documents extending other documents should inherit the global attributes unless overwritten explicitly.&lt;/p&gt;

&lt;p&gt;for example, having @Document(referenceable=true) should be kept for an extending class unless it explicitly sets it to false. currently, attributes are reset on each new @Document tag. (i assume we have the same issue for xml/yml mapping?)&lt;/p&gt;</description>
                <environment></environment>
            <key id="13940">PHPCR-77</key>
            <summary>document level options inheritance</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Mon, 6 Aug 2012 09:47:45 +0000</created>
                <updated>Sun, 5 May 2013 07:54:47 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="18901" author="dbu" created="Thu, 1 Nov 2012 11:28:55 +0000"  >&lt;p&gt;this is fixed for referenceable in &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/185&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/185&lt;/a&gt;&lt;/p&gt;</comment>
                    <comment id="20215" author="dbu" created="Sun, 5 May 2013 07:54:47 +0000"  >&lt;p&gt;when doing this, we should also fix MappedSuperclass annotation to support all attributes the Document has. in xml mappings mapped-superclass extends document&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-84] make the query API work with i18n</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-84</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;when searching there must be some way to ensure that for translateable documents the right fields are filters. f.e. when using the child strategy then for the given columns the node name needs to be checked (nodename = phpcr_locale:fr). for attributes strategy the property name needs to be rewritten (&quot;title&quot; vs &quot;phpcr_locale:fr-title&quot;).&lt;/p&gt;

&lt;p&gt;it might not be possible to easily automate this.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14161">PHPCR-84</key>
            <summary>make the query API work with i18n</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Tue, 23 Oct 2012 21:17:33 +0000</created>
                <updated>Tue, 14 May 2013 07:07:33 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>3</watches>
                        <comments>
                    <comment id="18871" author="dbu" created="Tue, 23 Oct 2012 21:45:43 +0000"  >&lt;p&gt;sounds like asking for a PHPCR-ODM DQL , then we could handle this perfectly transparent. as an intermediate, a method to build the criterion for a field of a mapped entity would be the right way i think. you could even do that for non-multilang in case you mapped the documents field to some differently named PHPCR property.&lt;/p&gt;</comment>
                    <comment id="18873" author="lsmith" created="Wed, 24 Oct 2012 09:09:19 +0000"  >&lt;p&gt;here is an example where i manually handle this:&lt;br/&gt;
&lt;a href=&quot;https://github.com/symfony-cmf/SearchBundle/blob/master/Controller/PhpcrSearchController.php&quot; class=&quot;external-link&quot;&gt;https://github.com/symfony-cmf/SearchBundle/blob/master/Controller/PhpcrSearchController.php&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;if we were to do it automatically we might not need our own DQL, we could do a QOMWalker. however i doubt that we can fully automate this, since everything can be mixed. ie. one path can have any number of different strategies.&lt;/p&gt;</comment>
                    <comment id="18874" author="lsmith" created="Wed, 24 Oct 2012 09:18:05 +0000"  >&lt;p&gt;btw .. it might make sense to always namespace the property names, even when using the child translation strategy. this could make it easier to deal with searching across mixed translation strategies.&lt;/p&gt;</comment>
                    <comment id="19279" author="lsmith" created="Fri, 11 Jan 2013 08:56:42 +0000"  >&lt;p&gt;if we do this change we should provide a migration script&lt;/p&gt;</comment>
                    <comment id="19894" author="dbu" created="Mon, 25 Mar 2013 15:01:24 +0000"  >&lt;p&gt;it gets even worse when translated and non-translated documents get mixed up. see for example the cmf sandbox menu admin (not multilang menu). it mixes translated and non-translated documents. since &lt;a href=&quot;https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/100&quot; class=&quot;external-link&quot;&gt;https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/100&lt;/a&gt; you can sort on columns, so sorting will half work half not.&lt;/p&gt;</comment>
                    <comment id="20371" author="dbu" created="Mon, 13 May 2013 08:51:11 +0000"  >&lt;p&gt;there seem to be other solutions like descendant, but if we had &lt;b&gt;join&lt;/b&gt; in jackalope-doctrine-dbal that could be a good option &lt;a href=&quot;https://github.com/jackalope/jackalope-doctrine-dbal/issues/15&quot; class=&quot;external-link&quot;&gt;https://github.com/jackalope/jackalope-doctrine-dbal/issues/15&lt;/a&gt;&lt;/p&gt;</comment>
                    <comment id="20375" author="wjzijderveld" created="Tue, 14 May 2013 07:07:33 +0000"  >&lt;p&gt;I started working on the Join issue and will start working on this issue when the Join feature is more or less stable.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-110] getAssociationTargetClass targetDocument not set</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-110</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;follow up of &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/279&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/279&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;ClassMetadata&lt;/p&gt;

&lt;p&gt;// TODO this may be not set. what happens if we would return null then?&lt;br/&gt;
return $this-&amp;gt;mappings&lt;span class=&quot;error&quot;&gt;&amp;#91;$fieldName&amp;#93;&lt;/span&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;&amp;#39;targetDocument&amp;#39;&amp;#93;&lt;/span&gt;;&lt;/p&gt;

&lt;p&gt;investigate and fix once 279 is merged.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14947">PHPCR-110</key>
            <summary>getAssociationTargetClass targetDocument not set</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Mon, 13 May 2013 20:50:00 +0000</created>
                <updated>Mon, 13 May 2013 20:50:00 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-81] Referrers should not return the frozen node of a version in version storage</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-81</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;In the document of phpcr.github.com (&lt;a href=&quot;http://phpcr.github.com/doc/html/phpcr/nodeinterface.html#getReferences%28%29&quot; class=&quot;external-link&quot;&gt;http://phpcr.github.com/doc/html/phpcr/nodeinterface.html#getReferences%28%29&lt;/a&gt;), I quote:&lt;/p&gt;

&lt;p&gt;&quot;In implementations that support versioning, this method does not return properties that are part of the frozen state of a version in version storage.&quot;&lt;/p&gt;

&lt;p&gt;But, the referrers returns some versioned node.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14068">PHPCR-81</key>
            <summary>Referrers should not return the frozen node of a version in version storage</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="laupifrpar">Pierre-Louis LAUNAY</reporter>
                        <labels>
                    </labels>
                <created>Wed, 26 Sep 2012 10:25:58 +0000</created>
                <updated>Wed, 26 Sep 2012 10:25:58 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-92] Join support in QueryBuilder</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-92</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;Joins are currently not supported in the QueryBuilder, the methods are there and some of the logic is partially coded, but they just havn&apos;t been implemented.&lt;/p&gt;

&lt;p&gt;At time of writing joins are not supported by doctrine-dbal (i think) but they are supported at least by Jackrabbit.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14502">PHPCR-92</key>
            <summary>Join support in QueryBuilder</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dantleech">Daniel Leech</reporter>
                        <labels>
                        <label>querybuilder,</label>
                    </labels>
                <created>Tue, 19 Feb 2013 22:11:48 +0000</created>
                <updated>Tue, 19 Feb 2013 22:14:26 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-85] implement querybuilder hydrate array option</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-85</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;the query builder can currently hydrate to documents and to phpcr nodes. it should also be possible to hydrate the result into a plain array to avoid creating documents and get the direct query result. (btw note that &apos;*&apos; in sql2 does not mean all properties of a document, but just the path and some other basic things - you always need to specify all fields you want to retrieve explicitly in this case)&lt;/p&gt;

&lt;p&gt;for the query builder base work and discussion see &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/204&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/204&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="14382">PHPCR-85</key>
            <summary>implement querybuilder hydrate array option</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Mon, 14 Jan 2013 09:12:13 +0000</created>
                <updated>Mon, 14 Jan 2013 09:12:13 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-60] add finalize step to mapping to calculate and validate</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-60</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;follow up of the discussion in &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/120&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/120&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;id strategy:&lt;/p&gt;

&lt;p&gt;1. if there is an id with a strategy always use that&lt;br/&gt;
2. if not and there is a parent and a node name mapping use the parent strategy&lt;br/&gt;
3. else use assigned strategy if there is an id field&lt;br/&gt;
4. throw an exception that you can&apos;t use this document&lt;/p&gt;

&lt;p&gt;finalizing the mapping could have the added benefit of combined validation. for example if assigned strategy is parent and name but there is no field mapped to the name, it would tell this is invalid.&lt;/p&gt;

&lt;p&gt;think what should be validated at the finalize point.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13514">PHPCR-60</key>
            <summary>add finalize step to mapping to calculate and validate</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Fri, 9 Mar 2012 15:07:49 +0000</created>
                <updated>Thu, 4 Oct 2012 21:33:40 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="18772" author="lsmith" created="Thu, 4 Oct 2012 21:33:40 +0000"  >&lt;p&gt;added a method for final validation here &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/180&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/180&lt;/a&gt;&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-58] figure out how to handle dangling weak/path ReferenceOne/Many properties</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-58</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;this is a follow-up of&lt;br/&gt;
&lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/116&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/116&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;the problem is: what happens when a ReferenceOne path or weak reference property points to something non-existing? is the property null? is the currently invalid reference removed on save or kept (which would make sense, in case the node at path appears later). but if it is usually kept, how can we delete it if we want?&lt;/p&gt;</description>
                <environment></environment>
            <key id="13507">PHPCR-58</key>
            <summary>figure out how to handle dangling weak/path ReferenceOne/Many properties</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Wed, 7 Mar 2012 17:20:35 +0000</created>
                <updated>Wed, 7 Mar 2012 17:20:35 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-57] do not track the original/unmapped values separately</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-57</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;instead we should just use the current state of the underlying node.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13482">PHPCR-57</key>
            <summary>do not track the original/unmapped values separately</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Wed, 29 Feb 2012 11:11:00 +0000</created>
                <updated>Sat, 3 Mar 2012 21:30:00 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="17510" author="lsmith" created="Sat, 3 Mar 2012 21:30:00 +0000"  >&lt;p&gt;&lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/118&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/118&lt;/a&gt;&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-80] ChildrenCollection is not updated after flush although children where added before</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-80</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;If you create children of a document without adding them to the children collection of the parent (with a children annotation) the children collection is not updated after flush, you need to call $dm-&amp;gt;clear() to force a reread of the children. The current case was with a parent and its children created in the same flush.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14022">PHPCR-80</key>
            <summary>ChildrenCollection is not updated after flush although children where added before</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="uwej711">Uwe J&#228;ger</reporter>
                        <labels>
                    </labels>
                <created>Fri, 7 Sep 2012 22:15:02 +0000</created>
                <updated>Tue, 12 Mar 2013 14:10:07 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="18621" author="uwej711" created="Fri, 7 Sep 2012 22:18:59 +0000"  >&lt;p&gt;Try this code:&lt;/p&gt;

&lt;p&gt;  $node1 = new Generic();&lt;br/&gt;
  $node1-&amp;gt;setParent($parent);&lt;br/&gt;
  $node1-&amp;gt;setNodename(&apos;source&apos;);&lt;br/&gt;
  $this-&amp;gt;dm-&amp;gt;persist($node1);&lt;/p&gt;

&lt;p&gt;  $this-&amp;gt;childrenNames = array(&apos;first&apos;, &apos;second&apos;, &apos;third&apos;, &apos;fourth&apos;);&lt;br/&gt;
  foreach ($this-&amp;gt;childrenNames as $childName) &lt;/p&gt;
{
      $child = new Generic();
      $child-&amp;gt;setNodename($childName);
      $child-&amp;gt;setParent($node1);
      $this-&amp;gt;dm-&amp;gt;persist($child);
  }


&lt;p&gt;  $this-&amp;gt;dm-&amp;gt;flush();&lt;br/&gt;
  $this-&amp;gt;dm-&amp;gt;clear();&lt;/p&gt;

&lt;p&gt;  $node = $this-&amp;gt;dm-&amp;gt;find(null, &apos;/functional/source&apos;);&lt;br/&gt;
  $children = $node-&amp;gt;getChildren();&lt;/p&gt;

&lt;p&gt;  // without the clear above $children === NULL, with the clear it works as expected&lt;/p&gt;
</comment>
                    <comment id="19316" author="dbu" created="Mon, 14 Jan 2013 09:08:59 +0000"  >&lt;p&gt;lukas, is this fixed with the work you did on cascading?&lt;/p&gt;</comment>
                    <comment id="19831" author="dbu" created="Tue, 12 Mar 2013 14:10:07 +0000"  >&lt;p&gt;we did a lot of refactoring on cascading lately. uwe, can you check if the problem still exists and do a pull request with a failing test if it exists?&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-103] map node autoname feature</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-103</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;we should map the Node::addNodeAutonamed as an option for the nodename field to have nodes that generate their own name (i.e. useful in children collection)&lt;/p&gt;</description>
                <environment></environment>
            <key id="14692">PHPCR-103</key>
            <summary>map node autoname feature</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Wed, 13 Mar 2013 17:12:18 +0000</created>
                <updated>Thu, 14 Mar 2013 09:30:48 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="19851" author="dbu" created="Thu, 14 Mar 2013 09:30:48 +0000"  >&lt;p&gt;probably this should be a special id generator strategy like parent and nodename, where nodename is generated. is there a way to pass a parameter to the strategy? or would this need to be a separate option on the &quot;@Id&quot;? addNodeAutoname can accept an optional parameter to control parts of the generated name.&lt;br/&gt;
btw, this will be funny as this strategy can not really &quot;generate&quot; an id, it needs to actually create the node to have the name generated. so actually we have no id until we actually flush...  &lt;/p&gt;

&lt;p&gt;and there is this issue to handle as well&lt;br/&gt;
&lt;a href=&quot;https://github.com/doctrine/phpcr-odm/commit/a4075caadd97312cc53bccf57ff8baf593df65d4&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/commit/a4075caadd97312cc53bccf57ff8baf593df65d4&lt;/a&gt;&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-101] MissingTranslationException when parent is not translated</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-101</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;Getting a MissingTranslationException when displaying a banner on the frontend. It seems to be caused in the refreshDocumentForProxy method on line 496 of UOW, the parent document does not have a locale and therefore the fallback hint is false. The banner block is not translated and the banner images are (title property). &lt;/p&gt;

&lt;p&gt;See for a stacktrace: &lt;a href=&quot;https://gist.github.com/rmsint/2c6700e00c47c95dc30e&quot; class=&quot;external-link&quot;&gt;https://gist.github.com/rmsint/2c6700e00c47c95dc30e&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="14649">PHPCR-101</key>
            <summary>MissingTranslationException when parent is not translated</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="rmsint">Roel Sint</reporter>
                        <labels>
                    </labels>
                <created>Fri, 1 Mar 2013 16:30:49 +0000</created>
                <updated>Thu, 18 Apr 2013 12:53:58 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="20043" author="dbu" created="Thu, 18 Apr 2013 12:53:58 +0000"  >&lt;p&gt;roel, can you please test with the latest phpcr-odm? we think this should be fixed now.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-100] The mixin `jcr:lastModified` is not updated</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-100</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;If the document have `jcr:lastModified`, this attribute is filled on create but not updated when a document is modified.&lt;/p&gt;

&lt;p&gt;I tried to set manually this attribute and it is not updated too.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14645">PHPCR-100</key>
            <summary>The mixin `jcr:lastModified` is not updated</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="laupifrpar">Pierre-Louis LAUNAY</reporter>
                        <labels>
                    </labels>
                <created>Fri, 1 Mar 2013 11:39:41 +0000</created>
                <updated>Fri, 19 Apr 2013 10:29:13 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="20042" author="dbu" created="Thu, 18 Apr 2013 12:52:57 +0000"  >&lt;p&gt;jackrabbit for example does not automatically update this field. but setting it manually should work, so this could be a bug of phpcr-odm&lt;/p&gt;</comment>
                    <comment id="20064" author="dbu" created="Fri, 19 Apr 2013 10:29:13 +0000"  >&lt;p&gt;&lt;a href=&quot;http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=laupifrpar&quot; class=&quot;user-hover&quot; rel=&quot;laupifrpar&quot;&gt;Pierre-Louis LAUNAY&lt;/a&gt; could you investigate why manually setting the field does not work? it could be that the phpcr-odm UnitOfWork ignores the field, or also that jackalope ignores changes to the field...&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-109] Why Generic::getNodename and not camelcase?</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-109</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;Is there a reason why the get node name method on the generic document is -&amp;gt;getNodename and not -&amp;gt;getNodeName?&lt;/p&gt;</description>
                <environment></environment>
            <key id="14940">PHPCR-109</key>
            <summary>Why Generic::getNodename and not camelcase?</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dantleech">Daniel Leech</reporter>
                        <labels>
                    </labels>
                <created>Sat, 11 May 2013 18:42:01 +0000</created>
                <updated>Mon, 13 May 2013 20:48:39 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="20374" author="dbu" created="Mon, 13 May 2013 20:48:39 +0000"  >&lt;p&gt;because the field is mapped as nodename, not nodeName. its representing $node-&amp;gt;getName() - calling it just name seemed to confusing. &lt;/p&gt;

&lt;p&gt;i vote against it, but if we want to change the mapping, we should do that right now, as i am breaking everything anyways in &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/279&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/279&lt;/a&gt;&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-9] add logging capabilities</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-9</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;see also &lt;a href=&quot;http://www.doctrine-project.org/docs/mongodb_odm/1.0/en/reference/logging.html&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/docs/mongodb_odm/1.0/en/reference/logging.html&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="12778">PHPCR-9</key>
            <summary>add logging capabilities</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="seldaek">Jordi Boggiano</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Fri, 1 Jul 2011 17:56:39 +0000</created>
                <updated>Sat, 30 Jul 2011 15:50:06 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-7] add support for &quot;eventual migrations&quot;</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-7</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;&lt;a href=&quot;https://doctrine-mongodb-odm.readthedocs.org/en/latest/reference/migrating-schemas.html&quot; class=&quot;external-link&quot;&gt;https://doctrine-mongodb-odm.readthedocs.org/en/latest/reference/migrating-schemas.html&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="12776">PHPCR-7</key>
            <summary>add support for &quot;eventual migrations&quot;</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="seldaek">Jordi Boggiano</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Fri, 1 Jul 2011 17:55:14 +0000</created>
                <updated>Mon, 8 Oct 2012 07:31:08 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                            <issuelinks>
                        <issuelinktype id="10001">
                <name>Reference</name>
                                                <inwardlinks description="is referenced by">
                            <issuelink>
            <issuekey id="13197">PHPCR-36</issuekey>
        </issuelink>
                    </inwardlinks>
                            </issuelinktype>
                    </issuelinks>
                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-30] add support for result caching</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-30</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description></description>
                <environment></environment>
            <key id="13113">PHPCR-30</key>
            <summary>add support for result caching</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="seldaek">Jordi Boggiano</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Sat, 22 Oct 2011 13:28:07 +0000</created>
                <updated>Thu, 19 Jul 2012 18:26:54 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-44] implement configurable change tracking</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-44</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;&lt;a href=&quot;http://www.doctrine-project.org/docs/orm/2.2/en/reference/change-tracking-policies.html&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/docs/orm/2.2/en/reference/change-tracking-policies.html&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="13403">PHPCR-44</key>
            <summary>implement configurable change tracking</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Tue, 31 Jan 2012 10:06:45 +0000</created>
                <updated>Mon, 8 Oct 2012 07:33:36 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-43] Custom data type</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-43</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;It will be great to be able to store array as a json in a property. There is no way to define custom mapping type (it is possible with doctrine ORM)&lt;/p&gt;</description>
                <environment></environment>
            <key id="13397">PHPCR-43</key>
            <summary>Custom data type</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="rande">Thomas Rabaix</reporter>
                        <labels>
                    </labels>
                <created>Sun, 29 Jan 2012 19:44:52 +0000</created>
                <updated>Thu, 19 Jul 2012 18:27:59 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="17622" author="dbu" created="Mon, 19 Mar 2012 13:04:03 +0000"  >&lt;p&gt;would this be a general solution for &lt;a href=&quot;http://www.doctrine-project.org/jira/browse/PHPCR-56&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/jira/browse/PHPCR-56&lt;/a&gt; ?&lt;/p&gt;</comment>
                    <comment id="18341" author="lsmith" created="Thu, 19 Jul 2012 18:27:40 +0000"  >&lt;p&gt;yes&lt;/p&gt;</comment>
                </comments>
                <issuelinks>
                        <issuelinktype id="10001">
                <name>Reference</name>
                                <outwardlinks description="relates to">
                            <issuelink>
            <issuekey id="13475">PHPCR-56</issuekey>
        </issuelink>
                    </outwardlinks>
                                            </issuelinktype>
                    </issuelinks>
                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-38] make it possible to inject a custom UUID service</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-38</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;right now we have hardcoded \PHPCR\Util\UUIDHelper::generateUUID(), but that is a very simplistic implementation and the spec is much broader ..&lt;/p&gt;</description>
                <environment></environment>
            <key id="13269">PHPCR-38</key>
            <summary>make it possible to inject a custom UUID service</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="seldaek">Jordi Boggiano</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Wed, 14 Dec 2011 20:36:53 +0000</created>
                <updated>Thu, 19 Jul 2012 18:27:11 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-36] Provide migrations tool</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-36</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;when i have existing content and later change the document class to have referenceable=true, this is not updated even on persisting the document again.&lt;/p&gt;

&lt;p&gt;uwe: I think there are several other things that fail when you have existing content in the repository - maybe the solution to think about is something like migrations ... that would prevent the performance penalty on ordinary code and still give you the change to change the structure of your documents.&lt;/p&gt;

&lt;p&gt;things that come to mind&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;change document class name&lt;/li&gt;
	&lt;li&gt;removing fields&lt;/li&gt;
	&lt;li&gt;change field type&lt;/li&gt;
	&lt;li&gt;bulk changing the values in some field&lt;/li&gt;
	&lt;li&gt;everything related to node types (though, as an additional challenge at least jackrabbit does not allow to remove things from node types through the davex remoting we use in jackalope)&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
            <key id="13197">PHPCR-36</key>
            <summary>Provide migrations tool</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="seldaek">Jordi Boggiano</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Thu, 17 Nov 2011 08:01:05 +0000</created>
                <updated>Mon, 8 Oct 2012 07:31:08 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                            <issuelinks>
                        <issuelinktype id="10001">
                <name>Reference</name>
                                <outwardlinks description="relates to">
                            <issuelink>
            <issuekey id="12776">PHPCR-7</issuekey>
        </issuelink>
                    </outwardlinks>
                                            </issuelinktype>
                    </issuelinks>
                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-97] Allow QB / XB to sepcify objects as targets</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-97</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;Allow the query builder expression to specify an object as a target.&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;div class=&quot;error&quot;&gt;&lt;span class=&quot;error&quot;&gt;Unable to find source-code formatter for language: querybuilder.&lt;/span&gt; Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml&lt;/div&gt;&lt;pre&gt;
$qb-&amp;gt;where($qb-&amp;gt;expr()-&amp;gt;eq(&apos;someObjectReference&apos;, $someObject);
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;So if the target passed is mapped and it is referenceable then replace the object instance with its UUID.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14509">PHPCR-97</key>
            <summary>Allow QB / XB to sepcify objects as targets</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dantleech">Daniel Leech</reporter>
                        <labels>
                        <label>querybuilder,</label>
                    </labels>
                <created>Wed, 20 Feb 2013 18:21:46 +0000</created>
                <updated>Wed, 20 Feb 2013 18:21:46 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-94] Implement -&gt;iterate on Query object</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-94</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;Implement the Query-&amp;gt;iterate method which will return an IteratableResultSet as per the ORM.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14504">PHPCR-94</key>
            <summary>Implement -&gt;iterate on Query object</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dantleech">Daniel Leech</reporter>
                        <labels>
                        <label>query</label>
                    </labels>
                <created>Tue, 19 Feb 2013 22:15:30 +0000</created>
                <updated>Tue, 19 Feb 2013 22:15:30 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-93] Implement -&gt;clone() method on Query object</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-93</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;As with the ORM query object, implement the -&amp;gt;clone() method.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14503">PHPCR-93</key>
            <summary>Implement -&gt;clone() method on Query object</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dantleech">Daniel Leech</reporter>
                        <labels>
                    </labels>
                <created>Tue, 19 Feb 2013 22:13:45 +0000</created>
                <updated>Tue, 19 Feb 2013 22:13:45 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-59] have a strategy for ReferenceOne/Many PATH to make it relative</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-59</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;this is a follow-up of&lt;br/&gt;
&lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/116&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/116&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;i think a user might need to attach his own strategy to the document manager. we could call this path_relative= and provide &quot;max&quot; that string-compares the target path and the node path and puts as few ../ as necessary. but again this does not block this pull request.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13508">PHPCR-59</key>
            <summary>have a strategy for ReferenceOne/Many PATH to make it relative</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Wed, 7 Mar 2012 17:24:37 +0000</created>
                <updated>Mon, 8 Oct 2012 07:34:03 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-95] Support parameter binding in QueryBuilder (depends Jackalope support)</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-95</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;Parameter binding is not currently implemented in the QueryBuilder, and the comments seem to indicate that this is because jackalope does not support it at the moment.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14505">PHPCR-95</key>
            <summary>Support parameter binding in QueryBuilder (depends Jackalope support)</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dantleech">Daniel Leech</reporter>
                        <labels>
                        <label>querybuilder,</label>
                    </labels>
                <created>Tue, 19 Feb 2013 22:19:34 +0000</created>
                <updated>Tue, 12 Mar 2013 14:18:20 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="19835" author="dbu" created="Tue, 12 Mar 2013 14:18:20 +0000"  >&lt;p&gt;this would be possible once &lt;a href=&quot;https://github.com/jackalope/jackalope/issues/59&quot; class=&quot;external-link&quot;&gt;https://github.com/jackalope/jackalope/issues/59&lt;/a&gt; has been done&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-73] add support for custom ID generators</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-73</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;&lt;a href=&quot;https://github.com/doctrine/doctrine2/pull/206&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/doctrine2/pull/206&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="13861">PHPCR-73</key>
            <summary>add support for custom ID generators</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="lsmith">Lukas Kahwe</reporter>
                        <labels>
                    </labels>
                <created>Tue, 17 Jul 2012 06:18:31 +0000</created>
                <updated>Tue, 12 Mar 2013 14:17:05 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="19834" author="dbu" created="Tue, 12 Mar 2013 14:17:05 +0000"  >&lt;p&gt;note that id for phpcr-odm is the phpcr path. so this is not the same as &lt;a href=&quot;http://www.doctrine-project.org/jira/browse/PHPCR-38&quot; title=&quot;make it possible to inject a custom UUID service&quot;&gt;PHPCR-38&lt;/a&gt; where we talk about the uuid generator.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-104] implement unitofwork isScheduledDocument</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-104</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;as discussed in &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/268&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/268&lt;/a&gt; we should implement UnitOfWork::isScheduledDocument and isScheduledFor* other than isScheduledForInsert.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14702">PHPCR-104</key>
            <summary>implement unitofwork isScheduledDocument</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Tue, 19 Mar 2013 12:41:05 +0000</created>
                <updated>Tue, 19 Mar 2013 12:41:05 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-108] suport entity listeners resp document listeners</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-108</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;see &lt;a href=&quot;http://docs.doctrine-project.org/en/latest/reference/events.html#entity-listeners&quot; class=&quot;external-link&quot;&gt;http://docs.doctrine-project.org/en/latest/reference/events.html#entity-listeners&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="14829">PHPCR-108</key>
            <summary>suport entity listeners resp document listeners</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Sun, 5 May 2013 07:42:37 +0000</created>
                <updated>Sun, 5 May 2013 07:42:37 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[PHPCR-86] QueryBuilder QOMFactory access</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-86</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;There is getQOMFactory method in PHPCR\Util\QOM\QueryBuilder (very useful) but it isn&apos;t in Doctrine\ODM\PHPCR\Query\QueryBuilder (it breaks bc).&lt;/p&gt;

&lt;p&gt;Is it mistake or there is/will be another method to access QOMFactory instance?&lt;/p&gt;</description>
                <environment></environment>
            <key id="14385">PHPCR-86</key>
            <summary>QueryBuilder QOMFactory access</summary>
                <type id="6" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/documentation.png">Documentation</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbojdo">Daniel Bojdo</reporter>
                        <labels>
                        <label>builder,</label>
                        <label>qomfactory</label>
                        <label>query</label>
                    </labels>
                <created>Mon, 14 Jan 2013 17:56:48 +0000</created>
                <updated>Tue, 15 Jan 2013 10:22:42 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="19319" author="dbojdo" created="Tue, 15 Jan 2013 10:22:42 +0000"  >&lt;p&gt;In fact it&apos;s not a bug, there is no docs about DocumentManager methods refactor. &lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>