[jira] Updated: (XDP-210) Generating subclass in a single file, even super class source code is not avaliable

     [ http://jira.codehaus.org/browse/XDP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Pribluda updated XDP-210:
------------------------------------

    Affects Version/s:     (was: 1.0.4)
                       1.0.5
        Fix Version/s:     (was: 1.0.4)
                       1.0.5

This could be big change, as for now we use @hibernate.class  to indicate 
entry point of generation, and subclasses are placed in the same file

by doing this, we will produce separate file for each subclass  greatly increasing their
amount. ( but in turn simplifying them ). This is also allowed by hibernate mapping. 
But properties defined in superclasses where source is not available, 
will be not accesible  for subclasses and thus not available. 

I will reschedule this after the release of 1.0.4.  Patches are welcome

> Generating subclass in a single file, even super class source code is not avaliable
> -----------------------------------------------------------------------------------
>
>                 Key: XDP-210
>                 URL: http://jira.codehaus.org/browse/XDP-210
>             Project: XDoclet 2 Plugins
>          Issue Type: New Feature
>          Components: hibernate
>    Affects Versions: 1.0.5
>         Environment: XDoclet2
>            Reporter: Alan She
>             Fix For: 1.0.5
>
>
> Since Hibernate support putting subclass in a single mapping file, it should better be supported in plugin-hibernate.
> A typical use case is separating a system into several modules.
> While developers of 'module B' do not need to see the code of 'module A' even B depends A.
> When it comes to generating the hbm files. 'Module B' don't have the source of A, but it is
> possible that some classes in B (e.g. Student) is a subclass of a class in module A (e.g. Person). At this time, putting <subclass> tag in the hbm of Person does not make sense (and impossible, because it don't have module A' s source now).
> It is obvisously that in this case we should use a single hbm file which define the subclass Student and put this in module B.
> Therefore, it is suggested that add a "extend" attribute for @hibernate.subclass, @hibernate.joined-subclass and @hibernate.union-subclass, and these tags are scaned for generating a hbm file if the "extend" attribute is provided.
> While the "extend" attribute is provided, no matter the super class source file in or not in the fileset, a hbm file can be generated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/