Author: kwsutter
Date: Fri Sep 20 20:14:01 2013
New Revision: 1525125
URL: http://svn.apache.org/r1525125
Log:
change p to br
Modified:
openjpa/site/trunk/content/jpa-2.1-tasks.mdtext
Modified: openjpa/site/trunk/content/jpa-2.1-tasks.mdtext
URL:
http://svn.apache.org/viewvc/openjpa/site/trunk/content/jpa-2.1-tasks.mdtext?rev=1525125&r1=1525124&r2=1525125&view=diff
==============================================================================
--- openjpa/site/trunk/content/jpa-2.1-tasks.mdtext (original)
+++ openjpa/site/trunk/content/jpa-2.1-tasks.mdtext Fri Sep 20 20:14:01 2013
@@ -39,11 +39,11 @@ Reference(s) </th></tr>
<tr><td class="border"> <font color="red">Not Started</font> </td><td
class="border"> <a
href="https://issues.apache.org/jira/browse/OPENJPA-????";>OPENJPA-????</a>
</td><td class="border"> High </td><td class="border"> Add ON condition to
JPQL query.
-<p>Will require BNF change (see jpql.jjt). Can ripple across the codebase.
</td><td class="border"> ??? </td><td class="border">
+<br><br>Will require BNF change (see jpql.jjt). Can ripple across the
codebase. </td><td class="border"> ??? </td><td class="border">
4.4.5.2 </td></tr>
<tr><td class="border"> <font color="red">Not Started</font> </td><td
class="border"> <a
href="https://issues.apache.org/jira/browse/OPENJPA-????";>OPENJPA-????</a>
</td><td class="border"> High </td><td class="border"> Downcast relation
paths with TREAT operator in JPQL queries. Will require BNF change. The BNF
changes will be non-trivial as TREAT can appear as a path component e.g.
p.TREAT(p.items as Book).pageCount.
-<p>JPQLEpressionBuilder will require change to process the treated path. The
downstream changes on building the appropriate expression will not be a heavy
task as the current kernel expressions support the notion of implicit
types.</td><td class="border"> ??? </td><td class="border">
+<br><br>JPQLEpressionBuilder will require change to process the treated path.
The downstream changes on building the appropriate expression will not be a
heavy task as the current kernel expressions support the notion of implicit
types.</td><td class="border"> ??? </td><td class="border">
4.4.9 </td></tr>
<tr><td class="border"> <font color="red">Not Started</font> </td><td
class="border"> <a
href="https://issues.apache.org/jira/browse/OPENJPA-????";>OPENJPA-????</a>
</td><td class="border"> Low </td><td class="border"> Use database function
or user-defined function with FUNCTION operator in JPQL queries The support for
this feature exists. The task is mainly to parse (JPQLEpressionBuilder) and
connect to the appropriate kernel expression.
@@ -83,10 +83,10 @@ Reference(s) </th></tr>
3.5 </td></tr>
<tr><td class="border"> <font color="red">Not Started</font> </td><td
class="border"> <a
href="https://issues.apache.org/jira/browse/OPENJPA-????";>OPENJPA-????</a>
</td><td class="border"> Medium </td><td class="border"> Create EntityManager
with SynchronizationType.UNSYNCHRONIZED. Unsynchorized context requires to be
explicitly joined to a JTA transaction, as opposed to SYNCHRONIZED contexts
that are automatically joined to a JTA transaction if available.
-<p>If an unsynchronized context is not joined to a transaction, queries with
pessimistic locks, bulk update or delete queries will throw the
TransactionRequiredException.
-<p>The context propgation rules differ and certain restrictions apply when the
context is unsynchronized.
-<p>A new method of EntityManager affirms if a context has joined a transaction.
-<p>It is recommended that a non-JTA datasource be specified for use by the
persistence provider for a persistence context of type
SynchronizationType.UNSYNCHRONIZED that has not been joined to a JTA
transaction in order to alleviate the risk of integrating uncommitted changes
into the persistence context in the event that the transaction is later rolled
back.
+<br><br>If an unsynchronized context is not joined to a transaction, queries
with pessimistic locks, bulk update or delete queries will throw the
TransactionRequiredException.
+<br><br>The context propgation rules differ and certain restrictions apply
when the context is unsynchronized.
+<br><br>A new method of EntityManager affirms if a context has joined a
transaction.
+<br><br>It is recommended that a non-JTA datasource be specified for use by
the persistence provider for a persistence context of type
SynchronizationType.UNSYNCHRONIZED that has not been joined to a JTA
transaction in order to alleviate the risk of integrating uncommitted changes
into the persistence context in the event that the transaction is later rolled
back.
</td><td class="border"> ??? </td><td class="border">
7.6.1 </td></tr>
