[jira] [Commented] (JDO-748) Tyops in spec and dead link on homepage
[
https://issues.apache.org/jira/browse/JDO-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805288#comment-14805288
]
Tilmann Zäschke commented on JDO-748:
-
Thanks, yes, the ViewVC link works perfectly with http and https.
I haven't heard back from Infrastructure yet, I'll update when I get something.
> Tyops in spec and dead link on homepage
> ---
>
> Key: JDO-748
> URL: https://issues.apache.org/jira/browse/JDO-748
> Project: JDO
> Issue Type: Improvement
> Components: site and infrastructure, specification
>Reporter: Tilmann Zäschke
>Priority: Trivial
> Labels: documentation, homepage
> Fix For: JDO 3.2
>
>
> Section 12.10 uses a wrong font:
> 1) The last paragraph mentions "PersistenceManager.setMultithreaded"
> and "getMultithreaded". Both should presumably use code-font and possibly
> have trailing '()' added.
> Section 12.11 of the spec contains some typos:
> 3) The 3rd paragraph starts with a '.' which should presumably be at the end
> of paragraph 2.
> 4) The code after paragraph 5 should use a code font
> 5) The code after paragraph 6 should use a code font
> On the home page (https://db.apache.org/jdo/svn.html) in the second section
> ("Web Access to Subversion"):
> 6) The link for browsing SVN (http://svn.apache.org/viewcvs/db/jdo) reports
> "Not Found The requested URL /viewcvs/db/jdo was not found on this
> server."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (JDO-735) Make PersistenceManager and Query support AutoCloseable (JDK1.7+)
[ https://issues.apache.org/jira/browse/JDO-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen resolved JDO-735. -- Resolution: Fixed Removed old test class CloseThrowsExceptionWhenActiveTx > Make PersistenceManager and Query support AutoCloseable (JDK1.7+) > - > > Key: JDO-735 > URL: https://issues.apache.org/jira/browse/JDO-735 > Project: JDO > Issue Type: New Feature > Components: api, specification, tck >Reporter: Andy Jefferson >Assignee: Michael Bouschen > Fix For: JDO 3.2 > > Attachments: CloseWithActiveTxRollsBack.java > > > So then it can be used with JDK1.7+ try-with-resources, as per > http://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JDO-748) Tyops in spec and dead link on homepage
[
https://issues.apache.org/jira/browse/JDO-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876535#comment-14876535
]
Michael Bouschen commented on JDO-748:
--
I changed the link on the JDO web site to use ViewVC.
> Tyops in spec and dead link on homepage
> ---
>
> Key: JDO-748
> URL: https://issues.apache.org/jira/browse/JDO-748
> Project: JDO
> Issue Type: Improvement
> Components: site and infrastructure, specification
>Reporter: Tilmann Zäschke
>Priority: Trivial
> Labels: documentation, homepage
> Fix For: JDO 3.2
>
>
> Section 12.10 uses a wrong font:
> 1) The last paragraph mentions "PersistenceManager.setMultithreaded"
> and "getMultithreaded". Both should presumably use code-font and possibly
> have trailing '()' added.
> Section 12.11 of the spec contains some typos:
> 3) The 3rd paragraph starts with a '.' which should presumably be at the end
> of paragraph 2.
> 4) The code after paragraph 5 should use a code font
> 5) The code after paragraph 6 should use a code font
> On the home page (https://db.apache.org/jdo/svn.html) in the second section
> ("Web Access to Subversion"):
> 6) The link for browsing SVN (http://svn.apache.org/viewcvs/db/jdo) reports
> "Not Found The requested URL /viewcvs/db/jdo was not found on this
> server."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JDO-747) Behavior of delete() with multiple concurrent Transactions
[
https://issues.apache.org/jira/browse/JDO-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875949#comment-14875949
]
Craig L Russell commented on JDO-747:
-
I'm sympathetic to the idea that you should be able to recover a transaction
where there is a delete conflict that the current specification does not allow.
One effect of refresh on an object is that the object is removed from the list
of objects to be flushed to the database.
The change needed is in the life cycle for refresh of a deleted object which
could depend on the state of the object in the database. For example, refresh
where the object was not there would result in a state change to Hollow? And
refresh where the object was there would result in a state change to
Persistent-clean? And we can also open the discussion whether an exception
needs to be thrown on refresh.
Maybe it would help clarify our options for you to write a test case which has
a delete conflict and what can be done to recover. Begin a transaction, change
an object, insert an object, delete an object; in a second transaction do the
same and commit; in the first transaction flush to sync with the datastore,
catch the exception and now...
recover the failed objects so the transaction can succeed.
> Behavior of delete() with multiple concurrent Transactions
> --
>
> Key: JDO-747
> URL: https://issues.apache.org/jira/browse/JDO-747
> Project: JDO
> Issue Type: Improvement
> Components: specification
>Affects Versions: JDO 3.1
>Reporter: Tilmann Zäschke
>Priority: Minor
> Labels: concurrency, delete, documentation, refresh(),
> specification
>
> In the Spec I could not find any statement regarding on how a transaction
> should behave if an object is deleted in a different concurrent transaction.
> Related Sections are Section 5.8 (how different methods should behave for
> different object states) and Section 12.6.1 (the behavior of refresh() and
> related methods).
> For example I wonder about the following situations. Suppose I have two
> optimistic sessions, pm1 and pm2, both access the same object. pm1 deletes
> the object and commits. Then what happens in pm2 if:
> 1. pm2 deletes the object and tries to commit, should that work? It's
>wouldn't be a real conflict if both delete it.
> 2. pm2 modifies the object (make dirty) and calls {{refresh()}}. Should I
>get an {{ObjectNotFound}} exception?
> 3. pm2 deletes the object and calls {{refresh()}}. According to the spec,
>{{refresh()}} should not change the object's state. But should it
>still fail with {{ObjectNotFound}}? If refresh should fail, how can I
>ever recover from such a situation, because I can't undelete the
>object?
> Is there a common understanding how this should work?
> IF there an external definition JDO relies on, then I think a reference to an
> external document might useful.
> If not, should the Spec define concurrent behavior?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JDO-749) Support for java.time types, and querying using associated methods
[ https://issues.apache.org/jira/browse/JDO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875871#comment-14875871 ] Craig L Russell commented on JDO-749: - Is it possible to require this support only when the runtime is java 8? I like the functionality but have no interest in back-porting the new classes to java 7, which JDO still supports. > Support for java.time types, and querying using associated methods > -- > > Key: JDO-749 > URL: https://issues.apache.org/jira/browse/JDO-749 > Project: JDO > Issue Type: New Feature > Components: api, specification, tck >Reporter: Andy Jefferson > > Refer to an associated issue for JPA for what support should look like > https://java.net/jira/browse/JPA_SPEC-63 > The methods that should be supported in queries would initially be > LocalDateTime : getDayOfMonth, getMonth, getYear, getHour, getMinute, > getSecond > LocalTime : getHour, getMinute, getSecond > LocalDate : getDayOfMonth, getMonth, getYear > These would need to be part of JDOQL string-based, as well as the > JDOQLTypedQuery (hence have equivalent Expression classes). > Note that all of these are already implemented in DataNucleus, and there are > JDOQLTypedQuery expression classes available. > Timing of this simply depends on the JRE that the next release of JDO is > targetted at, since this needs Java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (JDO-735) Make PersistenceManager and Query support AutoCloseable (JDK1.7+)
[ https://issues.apache.org/jira/browse/JDO-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-735: Assignee: Michael Bouschen > Make PersistenceManager and Query support AutoCloseable (JDK1.7+) > - > > Key: JDO-735 > URL: https://issues.apache.org/jira/browse/JDO-735 > Project: JDO > Issue Type: New Feature > Components: api, specification, tck >Reporter: Andy Jefferson >Assignee: Michael Bouschen > Fix For: JDO 3.2 > > Attachments: CloseWithActiveTxRollsBack.java > > > So then it can be used with JDK1.7+ try-with-resources, as per > http://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JDO-749) Support for java.time types, and querying using associated methods
[ https://issues.apache.org/jira/browse/JDO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875955#comment-14875955 ] Andy Jefferson commented on JDO-749: The XXXExpression classes could be included in the JDO API, but with the proviso that the JDO API would need to be built using JDK 1.8 (though runnable for JRE 1.7+). > Support for java.time types, and querying using associated methods > -- > > Key: JDO-749 > URL: https://issues.apache.org/jira/browse/JDO-749 > Project: JDO > Issue Type: New Feature > Components: api, specification, tck >Reporter: Andy Jefferson > > Refer to an associated issue for JPA for what support should look like > https://java.net/jira/browse/JPA_SPEC-63 > The methods that should be supported in queries would initially be > LocalDateTime : getDayOfMonth, getMonth, getYear, getHour, getMinute, > getSecond > LocalTime : getHour, getMinute, getSecond > LocalDate : getDayOfMonth, getMonth, getYear > These would need to be part of JDOQL string-based, as well as the > JDOQLTypedQuery (hence have equivalent Expression classes). > Note that all of these are already implemented in DataNucleus, and there are > JDOQLTypedQuery expression classes available. > Timing of this simply depends on the JRE that the next release of JDO is > targetted at, since this needs Java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Minutes: JDO TCK Conference Call Friday September 18, 9 am Pacific Daylight Time (PDT)
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to
prepare JCP Change Log
2. JIRA JDO-735 "Make PersistenceManager and Query support AutoCloseable
(JDK1.7+)" https://issues.apache.org/jira/browse/JDO-735
try {add new test case} finally {remove incorrect test case} AI Michael
3. JIRA JDO-652 "Provision of a typesafe refactor-friendly query capability for
JDOQL" https://issues.apache.org/jira/browse/JDO-652
AI Craig will start the specification update.
4. JIRA JDO-748 "Tyops in spec and dead link on homepage"
https://issues.apache.org/jira/browse/JDO-748
The JDO page needs to be updated. AI Michael follow the instructions on
jdo/site/HOWTO and fix the link.
5. New JIRA JDO-749 "Support for java.time types, and querying using associated
methods" https://issues.apache.org/jira/browse/JDO-749
Good idea to keep up with new features of java 8. Is there a way to support
these features but only when running java 8?
6. JIRA JDO-747 "Behavior of delete() with multiple concurrent Transactions"
https://issues.apache.org/jira/browse/JDO-747
Discussion continues on the JIRA.
7. Other issues
Action Items from weeks past:
[May 15 2015] AI Craig Spec change for roll back an active transaction when
closing a persistence manager (JDO-735)
[Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP
Maintenance Release for JDO 3.1 is published
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL
datastores": https://issues.apache.org/jira/browse/JDO-651?
[Feb 28 2014] AI Everyone: take a look at
https://issues.apache.org/jira/browse/JDO-712
[Feb 28 2014] AI Everyone: take a look at
https://issues.apache.org/jira/browse/JDO-625
[Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as
persistent field types
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about
JDOHelper methods. In process.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!
