Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <782439158.1242830445980.JavaMail.jira@brutus>
Date: Wed, 20 May 2009 07:40:45 -0700 (PDT)
From: "Matthew T. Adams (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Updated: (JDO-615) MetaData specification API
In-Reply-To: <765362411.1227258524356.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew T. Adams updated JDO-615:
---------------------------------

    Attachment: type.patch

Naming comment.  I suggest renaming ComponentMetadata to TypeMetadata.  "Component" is much more overloaded term than "type", IMHO:  anything can be a component (class, widget, service, system, subsystem, etc), but classes and interfaces are types.  See patch.

Sorry for not getting to this so late in the game.

> MetaData specification API
> --------------------------
>
>                 Key: JDO-615
>                 URL: https://issues.apache.org/jira/browse/JDO-615
>             Project: JDO
>          Issue Type: New Feature
>          Components: api2, specification, tck2
>            Reporter: Andy Jefferson
>            Assignee: Craig Russell
>             Fix For: JDO 2 maintenance release 3
>
>         Attachments: BooleanProperties.patch, jdometadata-6.patch, type.patch
>
>
> We can specify MetaData via XML or annotations. The only way missing is via an API. I propose mirroring the XML structure with interfaces of the form
> public interface MetaData
> {
>     addExtension(String key, String value);
>     removeExtension(String key, String value);
>     ...
> }
> public interface FileMetaData
> {
>     addPackage(PackageMetaData pmd);
>     ...
> }
> public interface PackageMetaData
> {
>     addClass(ClassMetaData cmd)
>     ...
> }
> public interface ClassMetaData
> {
>     addField(FieldMetaData fmd)
>     ...
> }
> public interface FieldMetaData
> {
>     setInheritance(InheritanceMetaData inhmd)
>     ...
> }
> and so on.
> We would then require a method on the PMF to register the metadata.
> If there are no objections to such a feature I'll propose a patch to try to provide all current JDO2 capabilities.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.