[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-615:
---
Attachment: jdometadata-4.patch
Updated javax.jdo.metadata :-
1. Remove many enums dupd from
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652846#action_12652846
]
Andy Jefferson commented on JDO-615:
If you create JDOMetaData via a services entry
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652850#action_12652850
]
Andy Jefferson commented on JDO-615:
Maybe best to just skip the whole services thing
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: jdoenhancer-5.patch
Thx for reviewing the patch. Attached is updated patch with all
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12651966#action_12651966
]
Andy Jefferson commented on JDO-615:
To demonstrate a typical use-case for this API, have
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-615:
---
Attachment: jdometadata-3.patch
Further update with simple factory interface for generating metadata
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-615:
---
Attachment: (was: jdometadata-2.patch)
MetaData specification API
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: jdoenhancer-4.patch
Further updated to include Ilan's chaining of addXXX methods. Now has
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: (was: jdoenhancer-3.patch)
Enhancer Invocation API
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-615:
---
Attachment: (was: jdometadata.patch)
MetaData specification API
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-615:
---
Attachment: jdometadata-2.patch
Updated patch for basic MetaData bean-style components. Maybe some
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: (was: jdoenhancer-2.patch)
Enhancer Invocation API
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: jdoenhancer-3.patch
Updated patch adding JDOHelper.getEnhancer() method taking in class
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650018#action_12650018
]
Andy Jefferson commented on JDO-591:
The only problem with Ilan's chaining of class
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-615:
---
Attachment: jdometadata.patch
Work-in-progress patch to provide javax.jdo.metadata for use in having
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649628#action_12649628
]
Andy Jefferson commented on JDO-591:
Agree with setClassLoader(), use of varargs
MetaData specification API
--
Key: JDO-615
URL: https://issues.apache.org/jira/browse/JDO-615
Project: JDO
Issue Type: New Feature
Reporter: Andy Jefferson
Fix For: JDO 2 maintenance release
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: (was: jdoenhancer.patch)
Enhancer Invocation API
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: jdoenhancer-2.patch
Updated patch with varargs, chained setter capability, setClassLoader
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12647894#action_12647894
]
Andy Jefferson commented on JDO-591:
Re: replace class files
Yes, thats the obvious
[
https://issues.apache.org/jira/browse/JDO-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646069#action_12646069
]
Andy Jefferson commented on JDO-610:
By requesting this, you presumably have something
Components: api2
Reporter: Andy Jefferson
Fix For: JDO 2 maintenance release 3
jdo2-api.jar is in an M2 repository
http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/jdo/jdo2-api/2.2/
and the pom has
dependencies
dependency
groupIdjavax.transaction/groupId
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-591:
---
Attachment: jdoenhancer.patch
Patch for api2 project to add JDOEnhancer and JDOEnhanceException
All releases need publicity IMHO, so I publicised the JDO2.2 release in two
relevant places :-
http://java.dzone.com/announcements/jdo-22-released
http://www.javahispano.org/contenidos/es/jdo2_2_liberado/
PS. I noticed in Section 11.1.1 of the latest spec that the
property
the current spec is not explicit on using methods in the query result
expression, e.g.
select this.phoneNumbers.size() from Employee,
select this.phoneNumbers.get(home) from Employee,
select this.firstName.substring(1,4) from Employee
It looks like a good idea supporting these kind
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640611#action_12640611
]
Andy Jefferson commented on JDO-591:
Hi Richard,
There is no way of knowing the enhance
+1
DN 1.0 and 1.1 branches both pass the JDO2.2 TCK (tested against tck2)
--
Andy (DataNucleus - http://www.datanucleus.org)
[
https://issues.apache.org/jira/browse/JDO-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson reassigned JDO-608:
--
Assignee: Andy Jefferson
Move tck2 to run against DataNucleus 1.1 for JDO2.3 onwards
Reporter: Andy Jefferson
Fix For: JDO 2 maintenance release 3
DataNucleus AccessPlatform 1.1 moves to JDK1.5+ and will be where any further
JDO enhancements will be performed. The tck2 project needs updating to use
jars from this branch
--
This message
[
https://issues.apache.org/jira/browse/JDO-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-608.
Resolution: Fixed
tck2 project now uses
datanucleus-core 1.1-SNAPSHOT
datanucleus-rdbms 1.1-SNAPSHOT
Assuming that the DataNucleus 1.1 is not available today, let's change
the test for 2.2 to expect JDOUserException and file a bug report for
2.3 that expects JDOUnsupportedOptionException.
Hi Craig,
Ok with me.
For reference :-
DN 1.0.1 throws JDOUserException
DN 1.1.0.M1 throws
Ok, this is a case of wrong exception. It should be
JDOUnsupportedOptionException but DataNucleus throws JDOUserException.
Bad implementation.
True, but then I've been using/developing with DataNucleus 1.1 and you
presumably have been using 1.0 and I do seem to remember saying I backported
Hi Craig,
Please take a look. The next version will have the change bars removed
and the cover page, TOC, index, bookmarks added.
Section 11.6. Section about PMF.supportedOptions().
Needs a mention of the transaction isolation levels supported for the
datastore.
Please take a look. The next version will have the change bars removed
and the cover page, TOC, index, bookmarks added.
Need to add a row
Cacheable attribute cacheableWhether a class/field is cacheable
--
Andy (DataNucleus - http://www.datanucleus.org)
Currently, JDO 2.2 trunk depends on DataNucleus SNAPSHOT. When we
prepare JDO 2.2. trunk for a beta we should probably depend on a
DataNucleus beta release. Then, once the JCP approves the JDO 2.2
Change Log (October 13), we can spin an official release of both JDO
2.2 and the RI DataNucleus.
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633843#action_12633843
]
Andy Jefferson commented on JDO-554:
I've applied the FetchGroup API changes onto api2
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633845#action_12633845
]
Andy Jefferson commented on JDO-590:
Applied changes for API to api2-legacy. Without
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-590:
---
Attachment: jdo-590-pmf_by_api.patch
Patch to setTransactionIsolationLevelByAPI so that we create
[
https://issues.apache.org/jira/browse/JDO-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12630851#action_12630851
]
Andy Jefferson commented on JDO-607:
I just tried to build DataNucleus with the api2 jar
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12630854#action_12630854
]
Andy Jefferson commented on JDO-590:
A slight flaw with my previous suggestion of throwing
[
https://issues.apache.org/jira/browse/JDO-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12630907#action_12630907
]
Andy Jefferson commented on JDO-607:
Language spec. I'd guess at something like 8.4.8.2
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12630908#action_12630908
]
Andy Jefferson commented on JDO-590:
DataNucleus SVN for version 1.0 and version 1.1
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12630734#action_12630734
]
Andy Jefferson commented on JDO-590:
Only comment on the patch
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629762#action_12629762
]
Andy Jefferson commented on JDO-590:
DataNucleus now has the required methods implemented
Please take a look and see if you find anything of note
Not something specific to the spec text, but what was the status of
the supported JDK for JDO2.2 ?
Will it be JDK1.5+ ? or retain the api2-legacy/tck2-legacy for this
release?
--
Andy (DataNucleus - http://www.datanucleus.org)
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629149#action_12629149
]
Andy Jefferson commented on JDO-590:
I'd change my original comment of method names etc
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson reassigned JDO-591:
--
Assignee: Andy Jefferson
Enhancer Invocation API
---
Key
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629251#action_12629251
]
Andy Jefferson commented on JDO-590:
Agreed, they be better off knowing it. But then we
[
https://issues.apache.org/jira/browse/JDO-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625448#action_12625448
]
Andy Jefferson commented on JDO-606:
Fortunately we subvert the process and make them
2. There is one issue that is a bug in the reference implementation
https://issues.apache.org/jira/browse/JDO-573 Is this going to be fixed any
time soon?
The short answer is no.
The long answer is as follows. The JDOQL process used by the DataNucleus RDBMS
plugin uses the mechanism that
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12623359#action_12623359
]
Andy Jefferson commented on JDO-554:
DataNucleus SVN (and nightly build) passes all TCK
Hi,
all previous JDO releases have always supported JDKs 1.3 and above.
JDO2.1 started providing the api2-legacy for JDK1.3/4, and api2 for
JDK1.5+ specifics.
Just a note about DataNucleus AccessPlatform support levels.
1. AccessPlatform 1.0 will be the last release that will support
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622822#action_12622822
]
Andy Jefferson commented on JDO-554:
Also BASIC is defined (in FetchGroup javadocs
[
https://issues.apache.org/jira/browse/JDO-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622837#action_12622837
]
Andy Jefferson commented on JDO-597:
The latter two tests seem to have an error
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622496#action_12622496
]
Andy Jefferson commented on JDO-554:
DataNucleus SVN and nightly build jars all now build
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622566#action_12622566
]
Andy Jefferson commented on JDO-554:
Two problems so far with the TCK tests (DataNucleus
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622626#action_12622626
]
Andy Jefferson commented on JDO-554:
Hi Craig, also in the test you helpfully added
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12621916#action_12621916
]
Andy Jefferson commented on JDO-554:
Hi Craig,
shouldn't those new methods
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12621442#action_12621442
]
Andy Jefferson commented on JDO-554:
Re: FetchGroup addCategory/removeCategory
[
https://issues.apache.org/jira/browse/JDO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12619505#action_12619505
]
Andy Jefferson commented on JDO-590:
My requirements for this item are to provide
[+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
+1 (not tested). Though is only a character change so ...
--
Andy (DataNucleus - http://www.datanucleus.org)
[
https://issues.apache.org/jira/browse/JDO-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12618757#action_12618757
]
Andy Jefferson commented on JDO-602:
Dup of JDO-600 perhaps
Bundle-ManifestVersion entry
Hi Craig,
Here's a patch for JDOPersistenceManagerFactory that works for me; the
call might better be put somewhere else...
And the RDO security patch needed just a little more help. The
implementation of QueryUtils.getPublicPutMethodForResultClass fails in
security environments. So I
Hi Craig,
I looked at the datanucleus implementation and found that I'm totally
not qualified to propose a patch. I found the code that needs to be
changed in org/datanucleus/enhancer/bcel/method/
JdoReplaceStateManager.java and org/datanucleus/enhancer/asm/method/
4. ...
Andy suggests using DataNucleus as the starting point for this effort,
as they have already implemented a number of concrete store managers.
AI look at DataNucleus store manager interface to see what needs to be
done to run with a cloud data repository.
[
https://issues.apache.org/jira/browse/JDO-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614966#action_12614966
]
Andy Jefferson commented on JDO-555:
Class loading of HashMap is not now present
[
https://issues.apache.org/jira/browse/JDO-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-555.
Resolution: Fixed
DataNucleus nightly build runs fine for application and datastore id
[
https://issues.apache.org/jira/browse/JDO-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614063#action_12614063
]
Andy Jefferson commented on JDO-555:
Craig,
don't understand the patch since all calls
[
https://issues.apache.org/jira/browse/JDO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613254#action_12613254
]
Andy Jefferson commented on JDO-599:
All patches applied.
Level 2 Caching ability
[
https://issues.apache.org/jira/browse/JDO-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613256#action_12613256
]
Andy Jefferson commented on JDO-555:
Thx for the patch - variations on them were included
[
https://issues.apache.org/jira/browse/JDO-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613526#action_12613526
]
Andy Jefferson commented on JDO-555:
Craig,
I know I didn't include your patch as-is. I
[
https://issues.apache.org/jira/browse/JDO-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613530#action_12613530
]
Andy Jefferson commented on JDO-555:
AbstractClassMetaData.initialise checks if the PK
[
https://issues.apache.org/jira/browse/JDO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-599:
---
Attachment: api2_schema.patch
api2-legacy_schema.patch
[
https://issues.apache.org/jira/browse/JDO-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613066#action_12613066
]
Andy Jefferson commented on JDO-555:
DataNucleus access to JDOImplHelper now goes through
An interesting option for a JDO implementation is to use a RESTful
service like Amazon S3 or memcached for the back end. Some obvious
issues are transactions, object identity, and query. But having an
object front end for these would have clear productivity benefits
compared to a user writing
Having more control over what goes into an L2 cache is desirable for some
systems. Currently JDO(2) provides no control other than the pin/unpin/evict
methods on the DataStoreCache. One way of providing more control would be to
allow specification via metadata (XML/annotations) for
[
https://issues.apache.org/jira/browse/JDO-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608664#action_12608664
]
Andy Jefferson commented on JDO-598:
SVN trunk now has identity classes implementing
[
https://issues.apache.org/jira/browse/JDO-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-598:
---
Component/s: api2-legacy
Make SingleFieldIdentity classes implement Comparable
[
https://issues.apache.org/jira/browse/JDO-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608666#action_12608666
]
Andy Jefferson commented on JDO-597:
SVN trunk now has the JDOReadOnlyException
[
https://issues.apache.org/jira/browse/JDO-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-597:
---
Component/s: api2-legacy
PMF : Add readOnly setting for better handling of read-only datastores
Reporter: Andy Jefferson
Fix For: JDO 2 maintenance release 2
Would be preferable for javax.jdo.identity classes to implement Comparable so
that we can store them in a TreeSet etc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add
Does anybody have an objection to changing the SingleFieldIdentity
(javax.jdo.identity) classes so that they implement Comparable ?
Adding it means that they can be stored in a TreeSet, whereas currently they
cannot.
--
Andy (DataNucleus - http://www.datanucleus.org)
[
https://issues.apache.org/jira/browse/JDO-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-597:
---
Attachment: JDOReadOnlyException.patch
Patch to add JDOReadOnlyException to api2 project
PMF : Add
Feature
Components: api2, specification
Reporter: Andy Jefferson
Fix For: JDO 2 maintenance release 2
A user has a datastore that is outside their control and they either don't have
permission to write to it, or maybe they have permissions but don't want to
write
[
https://issues.apache.org/jira/browse/JDO-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-592.
Resolution: Fixed
All should run with datanucleus jars now.
Migrate TCK to use datanucleus instead
Issue Type: Task
Components: tck2, tck2-legacy
Reporter: Andy Jefferson
Assignee: Andy Jefferson
Fix For: JDO 2 maintenance release 2
Future development branch of JPOX is under the name DataNucleus. The TCK needs
to migrate to use jars
See http://www.jpox.org/servlet/forum/viewthread?thread=5041
--
Andy (Java Persistent Objects - http://www.jpox.org)
[
https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591380#action_12591380
]
Andy Jefferson commented on JDO-591:
Should have added that classpath should include
jdo2
[
https://issues.apache.org/jira/browse/JDO-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-554:
---
Fix Version/s: JDO 2 maintenance release 2
JDO2.2 : Dynamic fetch groups
Control over transaction isolation level
Key: JDO-590
URL: https://issues.apache.org/jira/browse/JDO-590
Project: JDO
Issue Type: New Feature
Components: api2
Reporter: Andy
Here are the new features I'd like to do for JDO 2.2:
+1 to all of those,
also a level of standardisation of transaction isolation - see mailing list
around 16th March.
--
Andy
The second problem is that you have an xpath syntax error in your custom
style sheet, line 154 in site.jsl should read:
jsl:applyTemplates select=$nav/body/menu[not(@type)] |
$nav/body/[EMAIL PROTECTED]'header'] | $nav/body/search/
This was inherited from the default site.jsl in the
Hi,
I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it works and I
don't trust the (lack of) backwards compatibility concerns of the Maven
project
I see the same error as Craig if I run 'maven site' in jdo/site. I also
have a site.jsl in my
It (project.properties) currently doesn't have ${basedir} prepended and
maybe should have (but that doesn't solve this issue anyway so ignore that).
With Maven 1.0.2 it will not work with ${basedir} prepended
on maven.xdoc.jsl either so definitely forget that comment !!
--
Andy (Java
maven-xdoc-plugin is *supposed* to allow overriding the default stylesheet
via the property maven.xdoc.jsl (not that they can be bothered to
document it)
and actually i did find a doc for Maven 1.1 for this
http://maven.apache.org/maven-1.x/plugins/xdoc/properties.html
and it says
The JSL
[+1] Release JDO 2.1 specification, api, tck, enhancer, model, and util
See below for results obtained, with JPOX 1.2.0. I'm not overly concerned that
it is against JPOX 1.2.0 since the changes since then to JPOX have no effect
on the JDO2 API/TCK and so don't prevent release.
jdo2-tck
Hi Christian,
Thx for your input.
these levels are not really appropriate for JDO, which is because of the
nature these are defined in the SQL spec:
I. with a database guarantee of only committed reads and using JDO
optimistic transactions, you effectively have an isolation level stronger
This has probably been mentioned by others but I'll request it for JDO2.2
since it has certainly been requested enough amongst users groups.
We should take the javax.jdo.Transaction interface and add the following
public static final int TRANSACTION_NONE = 0;
public static final int
I think it would be helpful to add the description of a recursion-depth
value of zero to section 12.7.4. Values -1 and 1 are discussed, but the
subsequent example uses a value of zero, which is special enough a value to
be called out explicitly.
Well I'd just fix the example :-). A value of
It seems to me that 0 would result in a no-op as far as recursion goes.
No-op sounds ok to me, and the same for values = -2
--
Andy (Java Persistent Objects - http://www.jpox.org)
601 - 700 of 1257 matches
Mail list logo
