[
https://issues.apache.org/jira/browse/JDO-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509935
]
Andy Jefferson commented on JDO-507:
The classes in SVN use @PersistenceCapable, @Field whereas they need to use
[
https://issues.apache.org/jira/browse/JDO-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509950
]
Andy Jefferson commented on JDO-504:
My environment is Linux, Maven 1.0.2, tcsh, JVM 1.5.0_11 and wildcards
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509972
]
Andy Jefferson commented on JDO-403:
Re: @Table, @JoinTable, @SecondaryTable - these were only added after (unnamed
It would be nice if we could have @Column(DEPARTMENT) instead of
@Column(name=DEPARTMENT).
I've no particular problem with that but would point out that when you need to
specify more than just the column name you would have
@Column(value=DEPARTMENT jdbc-type=BLOB)
i.e value and not name (and
Hi Craig,
This might be controversial, but my Annotations Feature Request #3 is
to allow the annotation to declare which element is the default if
there is only one value specified. In this case, it would be name.
I was thinking of the same thing :-)
Can't see why that should be
Hi Michelle,
Has JPOX implemented support for annotations on persistent interfaces or
persistent properties? Wondering, since we're writing some tests for
this now.
Not yet. Only got as far as defining the @nnotations for contributing.
Shouldn't take long to do. Track it via
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508127
]
Andy Jefferson commented on JDO-403:
Re: PK, FK I agree with Michelle. It's a hack but probably the best
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508269
]
Andy Jefferson commented on JDO-403:
Hi Craig,
If the issue here is to justify having columns (plural) in @Field
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508309
]
Andy Jefferson commented on JDO-403:
2. I'd like to talk about mapping org.apache.jdo.tck.pc.mylib.PCRect
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507700
]
Andy Jefferson commented on JDO-403:
Why does field accept multiple column elements ? because it is possible
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507559
]
Andy Jefferson commented on JDO-403:
Why @JoinTable, @SecondaryTable, @Table ?
@Table is the equivalent of class
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507561
]
Andy Jefferson commented on JDO-403:
Re: ForeignKey under Element. Please see my comment of 26 Apr There is a user
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506994
]
Andy Jefferson commented on JDO-403:
What is trouble ? it would maybe make it easier to understand because I have
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505445
]
Andy Jefferson commented on JDO-403:
While changing those XXXStrategyType names to XXXStrategy you may also like
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505064
]
Andy Jefferson commented on JDO-403:
Thx for applying the patch Michelle. Something I hadnt noticed earlier
3. Update TCK to use 2.1 xsd: Enhancer has a problem with 2.1 xsd
definition. AI Michael file a blocker JIRA to get the JPOX fixed.
You mean this ?
http://www.jpox.org/servlet/jira/browse/CORE-3300
--
Andy (Java Persistent Objects - http://www.jpox.org)
Hi Craig,
Looks like this will be available for testing this weekend (once the
HEAD gets pushed out). Right?
HEAD (and RELEASE_1_1) is built every night at approx 01:00 GMT, so yes.
PS. Any JDO2.1 TCK will, at some point, need jpox-java5-1.2-SNAPSHOT.jar
including in its project.xml. This
The errors that I see now are related to changing boolean to String in
the annotations classes. Presumably this will be fixed in an upcoming
build of jpox and I can proceed with the test development.
All handling changes for boolean/String were made earlier today and I've just
run the
Hi Craig,
So how was this page generated? Is it directly from the javadoc? The
only difference between a javadoc format and this is the examples.
the page in our docs wasn't generated from the javadocs (unfortunately). It is
in XDOC format (Maven1/Velocity docs format), and was generated
Hi Craig,
This part of the use case was not in mind when I wrote the change
request. The user asks for PMF by name MyPMF but then the
PersistenceUnitName in MyPMF refers to a PersistenceUnit in the
persistence.xml.
Is that what JPOX does with the PersistenceUnitName today?
JPOX current
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502348
]
Andy Jefferson commented on JDO-403:
Please update the provided Field annotation (in the attached jar) to include
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502430
]
Andy Jefferson commented on JDO-403:
In addition to the previous addition, please update the provided Field
On 6 June 2007 07:04, Andy Jefferson wrote:
I now believe that the PersistenceUnit part of the property name is
distracting, and the real property name should be simply Name. That
is, PersistenceManagerFactories can have a Name property. The javadoc
and other documentation can call out
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501998
]
Andy Jefferson commented on JDO-403:
Need the ability to specify column information on embedded fields. We
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492197
]
Andy Jefferson commented on JDO-403:
There is a user requirement to add ForeignKey, PrimaryKey annotations under
[
https://issues.apache.org/jira/browse/JDO-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-486.
Resolution: Duplicate
Redirect this to the real JDO2 annotations issue which is still open
[
https://issues.apache.org/jira/browse/JDO-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-476.
Resolution: Fixed
Assignee: Andy Jefferson (was: Erik Bengtson)
Fixed in JPOX CVS HEAD
Change to use JPOX 1.2
--
Key: JDO-485
URL: https://issues.apache.org/jira/browse/JDO-485
Project: JDO
Issue Type: Task
Components: tck2
Reporter: Andy Jefferson
Fix For: JDO 2
[
https://issues.apache.org/jira/browse/JDO-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485706
]
Andy Jefferson commented on JDO-390:
Don't totally understand what this test is checking for :-
The comments say
[
https://issues.apache.org/jira/browse/JDO-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485710
]
Andy Jefferson commented on JDO-390:
SCO wrappers are not returned ... its a java.util.Date that is returned :-P
[
https://issues.apache.org/jira/browse/JDO-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson reassigned JDO-476:
--
Assignee: Erik Bengtson (was: Andy Jefferson)
Regression: Exception on pm.newInstance(Interface
Hi,
to accompany the PMF method setServerTimeZoneId(String) is there also a PMF
property to allow the same ?
Something like javax.jdo.option.ServerTimeZoneID ? (the same case as for the
method i.e ID both in capitals).
Thanks.
- Andy (Java Persistent Objects - http://www.jpox.org)
Hi Matthew,
Some comments, or rather questions :-
1. Why call this file javax.jdo.xml ?, why not jdo.xml ?, or even why not
persistence.xml ?
2. Why not just use same definition of persistence.xml from aforementioned
JPA spec ? When JDO2.1 has annotations not everything is always defined in a
Call it what you want -- I only proposed these names. I wouldn't call
it persistence.xml, as the contents are not the same as the
JPA-specified content. If the persistence.xml is found, its contents
are of course interpretable by the JDO implementation according to our
JPA alignment verbage
[
https://issues.apache.org/jira/browse/JDO-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474120
]
Andy Jefferson commented on JDO-466:
The PK class for the OrderItem has an incorrect equals() method. It uses
[
https://issues.apache.org/jira/browse/JDO-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-460.
Resolution: Fixed
Fixed in JPOX CVS HEAD and RELEASE_1_1
StateTransitions test fails on detachCopy
Please approve the changes to PersistenceManager and
PersistenceManagerFactory as documented in https://issues.apache.org/
jira/browse/JDO-449 https://issues.apache.org/jira/browse/JDO-445 and
https://issues.apache.org/jira/browse/JDO-462.
+1 from me too.
--
Andy
[
https://issues.apache.org/jira/browse/JDO-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473364
]
Andy Jefferson commented on JDO-460:
In the test we perform
pc2 = pm.detachCopy(pc1);
1. pc1 in HOLLOW should
What's RESOURCE_LOCAL? Non JCA?
See JPA spec 6.2.1.2. Non JTA
--
Andy
Section 18.15.8 says
spec
If the array or list field is mapped using the mapped-by attribute in the
field metadata, then the ordering can be mapped to a field in the same class.
In this case, use the mapped-by attribute in the order metadata to name the
field containing the ordering data.
/spec
[
https://issues.apache.org/jira/browse/JDO-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-461.
Resolution: Fixed
Fixed in JPOX CVS HEAD
executingWithMap of SQL query fails with extra parameters
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468004
]
Andy Jefferson commented on JDO-403:
For anyone wanting to review the annotations without opening up the jar, you
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466319
]
Andy Jefferson commented on JDO-403:
Just remembered why I had Field.fieldType, Element.type, Key.type, Value.type
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-403:
---
Attachment: jdo_2_1_annotations.jar
JDO2 Annotations
Key: JDO-403
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-403:
---
Attachment: (was: jdo_2_1_annotations.jar)
JDO2 Annotations
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466329
]
Andy Jefferson commented on JDO-403:
Further updated jar attached.
1. Added @PersistentInterface, and @Property
2
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-403:
---
Attachment: jdo_2_1_annotations.jar
JDO2 Annotations
Key: JDO-403
[
https://issues.apache.org/jira/browse/JDO-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465390
]
Andy Jefferson commented on JDO-460:
Not sure exactly what has changed on that test (which clearly passed in its
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-403:
---
Attachment: annotations.jar
JDO2 Annotations
Key: JDO-403
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-403:
---
Attachment: (was: annotations.jar)
JDO2 Annotations
Key: JDO
[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465440
]
Andy Jefferson commented on JDO-403:
Updated annotations.jar following recent discussions on jdo-dev mailing list
[
https://issues.apache.org/jira/browse/JDO-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465551
]
Andy Jefferson commented on JDO-460:
Test is wrong.
Take the example of detachCopy outside Txn without
Hi Ilan,
At least @PrimaryKey should be a separate annotation.
Yes. Of course it already exists ... only it wasn't defined for Field/Method
usage.
I think that should be
Class fieldType() void.class;
because otherwise it becomes required.
Similarly PersistenceCapable.objectIdClass
Same for @Serialized and @Dependent, @Index and @Unique
(mainly for collections, but maybe also for maps when keys and values
should share the same setting, or maybe @Serialized and @Dependent should
only cover map values and @Index and @Unique only map keys).
@Serialized is a valid
Hi Ilan,
always good to see some ideas on improving the annotations
1. Using simple annotations instead of complex attributes
For instance:
@PrimaryKey
instead of:
@Field(primaryKey=true)
(or simply @Id as in JPA).
OK, but the other point of view is where we have a field that
Hi Michelle,
When I attempt to build tck20, I get errors retrieving artifacts from
ibiblio. Does anyone know what's going on?
It appears that the people at IBiblio kindly decided to move the Maven repo to
another machine without considering the repercussions, and then to link to
the new
Components: specification
Affects Versions: JDO 2 final
Reporter: Andy Jefferson
Fix For: JDO 2 maintenance release 1
There are two issues.
1. The JDO2 spec 21.21.3 has a suggested implementation of jdoIsDetached. This
was clearly written before we added jdoDetachedState
21.17 states that :-
spec
public final boolean jdoIsDetached();
This method checks if the instance is detached. If so, it returns true.
/spec
If I have
class A {}
class B extends A {}
and A is not detachable yet B is, then what should the jdoIsDetached() method
be in A ?
When A is enhanced, it
Hi Craig,
I haven't looked closely at this, but the spec says that this is a
sample implementation:
public final boolean jdoIsDetached(){
return jdoStateManager==null?false:
jdoStateManager.isDetached(this);
}
Well that sample doesn't work for me since it assumes that a StateManager
Hi Craig,
I think what I put into the spec as a sample was before the experts
agreed on a detached state field.
OK.
The implementation that you
propose, using the jdoStateManager and jdoDetachedState works, and I
can update the spec if no one sees any issues. In fact, we should
file a
Focus now on the changes that need updated interfaces so we can give
JPOX advance notice of the change. Looking in particular at the Query
Chapter 14 and BNF.
For information, JPOX 1.2.0-beta-1 is out and JPOX 1.2 will form the basis of
where all changes for JDO2.1 will be performed (on JPOX
Information for those people using JPOX, and accessing nightly builds from
the JPOX Maven repo at (http://www.jpox.org/downloads/maven).
JPOX 1.1 (CVS branch : RELEASE_1_1)
This is the stable branch of JPOX and releases are currently up to 1.1.4,
but will soon have a 1.1.5.
Nightly builds from
Hi,
in the JDO2-final spec 13.4.5
spec
Once a transaction has been marked for rollback via setRollbackOnly, the
commit method will always fail with JDOFatalDataStoreException. The JDO
implementation must not try to make any changes to the database during commit
when the transaction has been
Just having checked out the latest TCK, I get a lack of a transaction-api.
I'm assuming that this is jta. Nothing in the README. I found some jar
claiming to be that in some Maven2 repo somewhere
1. Is this jar planned to be added to a Maven1 repository such as IBiblio ?
2. Can the README add
Hi Michael,
maven remote repository I added to the list of remote repositories:
https://maven-repository.dev.java.net/nonav/repository
Did you check out the files in the root directory (I mean in trunk)?.
Yep.
I added the following line to trunk/project.properties:
maven.repo.remote
[ http://issues.apache.org/jira/browse/JDO-403?page=all ]
Andy Jefferson updated JDO-403:
---
Attachment: (was: annotations.jar)
JDO2 Annotations
Key: JDO-403
URL: http://issues.apache.org/jira/browse
[ http://issues.apache.org/jira/browse/JDO-403?page=all ]
Andy Jefferson updated JDO-403:
---
Attachment: annotations.jar
Updated annotations jar with split JDO/ORM packages.
Should be much more acceptable to those who originally requested split JDO-ORM
[
http://issues.apache.org/jira/browse/JDO-379?page=comments#action_12444852 ]
Andy Jefferson commented on JDO-379:
Is there anything that can be done to get these DTDs/XSDs up on *some* server
somewhere (apart from JPOX's server
By reading this thread and an article posted by Linda DeMichiel and Craig
Russell (http://java.sun.com/j2ee/letter/persistence.html), I was quite
confused about which one (JDO or JPA) to choose as many efforts have been
pushed towards JSR-220 so far. I know JPA is mainly driven by vendors,
[
http://issues.apache.org/jira/browse/JDO-432?page=comments#action_12443201 ]
Andy Jefferson commented on JDO-432:
The 2 remaining issues are due to JPOX implementing part of an earlier version
of the JDO2 spec. Some time ago it used
Hi Craig,
I believe that you cannot map a Calendar to a single column in the
datastore because Calendar has a few features that you don't want to
lose:
Thanks. I only had the storage of time and timezone in mind ... ie. part 1,
forgetting the strangeness of Calendar.
Withdraw the request
An initial split of JDO and ORM annotations is at :-
JDO :-
http://jpox.cvs.sourceforge.net/jpox/JPOX/Plugins/Java5/src/java/org/jpox/annotations/
ORM:-
http://jpox.cvs.sourceforge.net/jpox/JPOX/Plugins/Java5/src/java/org/jpox/annotations/orm/
Still to do :
@DatastoreIdentity currently has
Hi Ilan,
I agree that mappedBy should remain in Field. Same is true for indexed,
unique, deleteAction, sequence and valueStrategy, which can all be
useful also for object databases. I think that only table, column and
columns are specific for relational databases. Same is applied also for
indexed and unique are certainly being used - also in Element, Key
and Value. I do not use deleteAction, sequence and valueStrategy
yet, but I think that it might make sense to use them in the future.
OK.
The point that this raises is that my understanding of the split JDO-ORM was
to separate
I agree. After reading only the header of every option I though that 3 is
the best and 1 is the worst, but after reading the cons of 2 and 3 it seems
that 1 is the only feasible option. I am afraid that plans for 6-8 months
might eventually take much longer and because the project is under
This test still fails.
Did this one slip through the cracks, or is there an issue with the test?
Not had time too look at it. Will obviously be looked at before any JDO2.1
release (when we have approximate timescales for such a momentous event).
--
Andy
I always introduce JPA as a subset of JDO, which is true in terms of
concepts
A while back we compiled a table of the differences (between JDO2 and JPA1) to
assist users in choosing what they want. You can find it here :-
http://www.jpox.org/docs/persistence_technology.html
The table is not
I would expect they return null. I found the following in the spec,
section 12.6 Interface PersistenceManager on page 110:
Thanks Michael!
That's what they do but just couldn't find that section to make my mind up :-)
--
Andy
Components: tck20
Affects Versions: JDO 2 final
Reporter: Andy Jefferson
Priority: Minor
The JDO2 spec adequately defines (section 12.6.0 Null Management) behaviour
when null values are passed in to the PersistenceManager methods
makePersistent, detachCopy
I continue to believe that the largest backers of JPA were against
JDO because of it being binary compatible across object and
relational databases.
Agreed.
JPA was invented to be so weak that Hibernate and TopLink could be
considered standards compliant and to water down any such
[
http://issues.apache.org/jira/browse/JDO-421?page=comments#action_12437221 ]
Andy Jefferson commented on JDO-421:
JPOX CVS supports XSD validation using local copies of xsd files assuming that
the underlying SAXParser supports
[ http://issues.apache.org/jira/browse/JDO-420?page=all ]
Andy Jefferson resolved JDO-420.
Fix Version/s: JDO 2 maintenance release 1
Resolution: Fixed
Fixed in JPOX CVS
JPOX fails new test CompletenessTestMap, configuration
[ http://issues.apache.org/jira/browse/JDO-430?page=all ]
Andy Jefferson reassigned JDO-430:
--
Assignee: Michelle Caisse (was: Andy Jefferson)
The MetaData (for Department.employees) is incorrect. You have
order column=HIREDATE/
This means that your
[
http://issues.apache.org/jira/browse/JDO-420?page=comments#action_12436129 ]
Andy Jefferson commented on JDO-420:
Map test passes with JPOX CVS.
Perhaps move your List issue to a different JIRA since it is unrelated to Maps.
JPOX fails
[
http://issues.apache.org/jira/browse/JDO-420?page=comments#action_12436132 ]
Andy Jefferson commented on JDO-420:
On the issue of a ListWithoutJoin please look at the file
src/orm/datastoreidentity/org/apache/jdo/tck/pc
[
http://issues.apache.org/jira/browse/JDO-421?page=comments#action_12434065 ]
Andy Jefferson commented on JDO-421:
Sorry for the lack of description of the log changes.
This line removes duplicate entries in the Log4J log (a message
[
http://issues.apache.org/jira/browse/JDO-421?page=comments#action_12433567 ]
Andy Jefferson commented on JDO-421:
These are warnings in JPOX CVS.
As I posted on the mailing list a long time ago, if you add
org.jpox.metadata.validate=false
[ http://issues.apache.org/jira/browse/JDO-421?page=all ]
Andy Jefferson updated JDO-421:
---
Attachment: jdori-pmf.properties.patch
Enhancer log contains ERRORs, but output appears to be fine
[ http://issues.apache.org/jira/browse/JDO-420?page=all ]
Andy Jefferson updated JDO-420:
---
Attachment: project.properties.patch
Patch to fix broken enhancement due to typo
JPOX fails new test CompletenessTestMap, configuration companyMapWithoutJoin
[
http://issues.apache.org/jira/browse/JDO-420?page=comments#action_12433578 ]
Andy Jefferson commented on JDO-420:
The ORM file contains no field mappings for the role field of Employee (the
key in the Map). Not the cause of the issue
[ http://issues.apache.org/jira/browse/JDO-420?page=all ]
Andy Jefferson reassigned JDO-420:
--
Assignee: Michelle Caisse (was: Andy Jefferson)
JPOX has had some changes in CVS to allow for value class using
superclass-table when also having a (map
[
http://issues.apache.org/jira/browse/JDO-421?page=comments#action_12433630 ]
Andy Jefferson commented on JDO-421:
It isn't a question of having xsd cached somewhere. JPOX metadata parsing does
not support validation using XML Schema, only
For information :-
JPOX Core/Enhancer/Plugins 1.1.2 released and include (amongst other things)
1. All JPOX jars are Eclipse OSGi-compliant, allowing direct use in OSGi
environments (e.g Eclipse).
2. The majority of JPOX components are now pluggable via the plugin registry
mechanism
Type: Bug
Affects Versions: JDO 2 final
Reporter: Andy Jefferson
Fix For: JDO 2 maintenance release 1
Spec p222 (section 18.5.1) should not have autoassign as a valid value. This
was merged into identity before JDO2-final.
--
This message is automatically generated
Hi,
Typing in the command
svn checkout http://svn.apache.org/repos/asf/db/jdo
kindly gives
svn: PROPFIND request failed on '/repos/asf/db/jdo'
svn: PROPFIND of '/repos/asf/db/jdo': 403 Forbidden (http://svn.apache.org)
Have Apache also moved Subversion *as well as* the JAR download ?
Thanks
svn: PROPFIND request failed on '/repos/asf/db/jdo'
svn: PROPFIND of '/repos/asf/db/jdo': 403 Forbidden (http://svn.apache.org)
Never mind. It seems to be back now. I'm sure someone in Apache can explain
it :-)
--
Andy
Current TCK against the current JPOX snapshot fails in tearDown due
to foreign key constraint violations. The TCK might need to change
based on the resolution of JDO-392. AI Erik change JPOX to allow the
TCK to use the old behavior; the TCK might need a PMF flag for interim.
JPOX (nightly
The downloads for JARs from Apache have always been from
http://www.apache.org/dyn/closer.cgi/java-repository/javax.jdo/jars
I've been to several and find this java-repository empty. My default mirror
(apache.rediris.es) is one such. Another in my list of closest
mirrors.hostalia.com is similar
[
http://issues.apache.org/jira/browse/JDO-402?page=comments#action_12426035 ]
Andy Jefferson commented on JDO-402:
Understood. The original test does fail with the change to backing store copy
(in JPOX CVS). Just need someone to apply
[
http://issues.apache.org/jira/browse/JDO-402?page=comments#action_12424399 ]
Andy Jefferson commented on JDO-402:
The spec isnt totally silent (12.7.5 comment line in the code for getGroups).
Erik asked the question on the mailing list
901 - 1000 of 1257 matches
Mail list logo
