Is this something that should be in the javadoc for the class? :->




Stephen McConnell <[EMAIL PROTECTED]> on 12/06/2003 16:10:25

Please respond to "Avalon framework users" <[EMAIL PROTECTED]>

To:    Avalon framework users <[EMAIL PROTECTED]>
cc:

Subject:    Re: Merlin qdox tags



Daniel Krieg wrote:

>I am attempting to generate the meta-data files for Merlin using the
>meta-tools ant task o.a.a.m.t.a.MetaTask.  All documentation about
>Merlin suggests that it is looking for *.xinfo meta data files.
>

Merlin looks for meta info resources in the following order:

   a) serialized - from <classname>.stype
   b) xml using <classname>.xtype
   c) xml using <classname>.xinfo

Information generated by the mata info task is created as either
serialized or XML depending on the policy set when invoking the task.

>Furthermore a component does not seem to a recognized type unless the
>meta-data file is in fact an xinfo file.  However, the MetaTask outputs
>the meta-data file as xtype files.  I have copied the source below.
>
>Am I doing something wrong or is this something that needs patched?
>
>    /**
>     * Determine the file for the [EMAIL PROTECTED] Task}.
>     *
>     * @param classname the fully qualified name of file to generate
>     * @return the file for info
>     * @throws IOException if unable to determine base file
>     */
>    private File getOutputFileForClass( final String classname )
>        throws IOException
>    {
>        String filename =
>            classname.replace( '.', File.separatorChar );
>
>        if( SER_TYPE == m_format )
>        {
>            filename += ".stype";
>        }
>        else
>        {
>            filename += ".xtype";
>        }
>        return new File( m_destDir, filename ).getCanonicalFile();
>    }
>
>

The above code is only relative to the generation side of things.  We
don;t generate to xinfo because that would overrite Phoenix xinfo
descriptors, but during deployment we read stype first, if unavaiulable,
then Merlin reads xinfo - then Merling reads the content and determines
format based on the root element (either <type> or the legacy <blockinfo>).

The more relevant class (concerning reading semantics is the TypeBuilder
class in the meta package.

Cheers, Steve.

--

Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]











****************************************************************
NOTICE - This message is intended only for the use of the 
addressee named above and may contain privileged and 
confidential information.  If you are not the intended recipient
of this message you are hereby notified that you must not 
disseminate, copy or take any action based upon it.  If you 
received this message in error please notify HIC immediately.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of HIC.
****************************************************************


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to