db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Watzek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-311) Inheritance3 : should check if the JDO implementation supports "javax.jdo.option.mapping.RelationSubclassTable"
Date Wed, 01 Mar 2006 11:13:44 GMT
    [ http://issues.apache.org/jira/browse/JDO-311?page=comments#action_12368259 ] 

Michael Watzek commented on JDO-311:

I agree with 1. above. 
The removal of the package prefix in 2. above is consistent with other TCK test cases: All
calls of method "printUnsupportedOptionalFeatureNotTested" in TCK test classes pass a non-qualified
classnames. For this reason, I propose to pass a non-qualified classname here either, or to
adapt the calls in other TCK test cases as well.
Please let me know how to proceed.

> Inheritance3 : should check if the JDO implementation supports "javax.jdo.option.mapping.RelationSubclassTable"
> ---------------------------------------------------------------------------------------------------------------
>          Key: JDO-311
>          URL: http://issues.apache.org/jira/browse/JDO-311
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Versions: JDO 2 beta
>     Reporter: Andy Jefferson
>     Assignee: Michael Watzek
>      Fix For: JDO 2 final
>  Attachments: JDO-311.patch
> The inheritance3 test should check whether PMF.supportedOptions contains "javax.jdo.option.mapping.RelationSubclassTable"
before running the test. JPOX doesn't support this option yet the test still runs (and fails)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message