[Hibernate-JIRA] Moved: (HBX-747) Exporters : Clarify template context and classes responsabilities
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-747?page=all ]
Max Rydahl Andersen moved ANN-429 to HBX-747:
---------------------------------------------
Project: Hibernate Tools (was: Hibernate Annotations)
Key: HBX-747 (was: ANN-429)
Component: (was: documentation)
Version: (was: 3.2.0.cr1)
> Exporters : Clarify template context and classes responsabilities
> -----------------------------------------------------------------
>
> Key: HBX-747
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-747
> Project: Hibernate Tools
> Type: Task
> Reporter: Michelle Baert
>
>
> As you said in HBX-745, there's an importContext problem again when trying to use the query parameter types
> from templates.
> I built another exporter with an ImportContext field added, and automatic destination package detection, and tried to see if it couldn't be done directly in Generic Exporter.
> It arises that through the exportClasses() method, the destination package may change from one mapped class to another.
> But difficulties come when confusion is made between referred mapped class and newly generated referring class.
> The freemarker datamodel is filled with tons of properties, objects and methods for which it is very difficult to find out which deals with what.
> My (sub)project of building new templates leads to reverse engineer alone too much of the *uncommented* code of the actual release.
> Maybe defining classes responsabilities could lead to some changes in project architecture, and allow to clean-up many work-arounds, but, ;) , this is not *my* role .
> But it should worth it :)
> Best regards,
> Michelle Baert
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 3 months
[Hibernate-JIRA] Created: (HBX-746) Exporters : Clarify template context and classes responsabilities
by Michelle Baert (JIRA)
Exporters : Clarify template context and classes responsabilities
-----------------------------------------------------------------
Key: HBX-746
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-746
Project: Hibernate Tools
Type: Task
Components: hbm2java
Versions: 3.2beta7
Reporter: Michelle Baert
As you said in HBX-745, there's an importContext problem again when trying to use the query parameter types
from templates.
I built another exporter with an ImportContext field added, and automatic destination package detection, and tried to see if it couldn't be done directly in Generic Exporter.
It arises that through the exportClasses() method, the destination package may change from one mapped class to another.
But difficulties come when confusion is made between referred mapped class and newly generated referring class.
The freemarker datamodel is filled with tons of properties, objects and methods for which it is very difficult to find out which deals with what.
My (sub)project of building new templates leads to reverse engineer alone too much of the *uncommented* code of the actual release.
Maybe defining classes responsabilities could lead to some changes in project architecture, and allow to clean-up many work-arounds, but, ;) , this is not *my* role .
But it should worth it :)
Best regards,
Michelle Baert
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 3 months