[Andromda-devel] [ andromda-Patches-823276 ] Hibernate 2 cartridge

[SourceForge.net <no...@so...>]

Patches item #823276, was opened at 2003-10-14 08:19
Message generated for change (Comment added) made by peteroyle
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536547&aid=823276&group_id=73047

Category: Templates
Group: Unstable (example)
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Royle (peteroyle)
Assigned to: Nobody/Anonymous (nobody)
Summary: Hibernate 2 cartridge

Initial Comment:
This is a quick port from the original andromda-hibernate 
cartridge to support Hibernate2. 

I've so far made some "enhancements" which are 
hopefuly all documented in the "CHANGES..." section of 
the README file so you can easily find and undo them :). 
All working files are included in the src directory. The 
dist directory simply contains the packaged end result of 
the build process and can be deleted.

There's an example build.xml file in the dist/samples 
directory. Comparisons between all the build.xml and all 
the templates (between original and andromda-
hibernate2) for help of understanding can be found in 
the dist/diffs directory.

----------------------------------------------------------------------

>Comment By: Peter Royle (peteroyle)
Date: 2003-10-23 00:38

Message:
Logged In: YES 
user_id=883369

Please note a proper patch has been created for this and 
submitted as "[ 827237 ] Hibernate cartridge additions" 
because "[ 823276 ] Hibernate 2 cartridge" had dissapeared 
when i went to submit it.

----------------------------------------------------------------------

Comment By: Peter Royle (peteroyle)
Date: 2003-10-23 00:33

Message:
Logged In: YES 
user_id=883369

As far as I can tell, the only way to do that is to customise 
the ejb cartridge. Expand the cartridge and modify the 
templates and the andromda-cartridge.xml file, then 
repackage back into the jar file.

For example if you want all your xxxBeanImpl classes to land 
in a mybeanimpls package, change the EntityBeanImpl 
template to something like (and i haven't yet tried this so 
exact syntax may be out):

#set ($packagename = $transform.findPackageName
(${class.package}).mybeanimpls)
package $packagename;
...
...   and the rest remains the same

You will also need to change the entry in the andromda-
cartridge.xml file as follows:
...
    <template
        stereotype="Entity"
        sheet="templates/EntityBeanImpl.vsl"
        outputPattern="{0}/mybeanimpls/{1}BeanImpl.java"
        outlet="entity-impls"
        overWrite="false"
    />
...

Hope it helps.

Pete.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-22 15:06

Message:
Logged In: NO 

The problem is that I want to separate the files that 
generates each part of the cartridge

Imagine that I have that task

<outlet cartridge="ejb"       outlet="entity-beans"   
dir="${andromda.ejb.generated.dir}" />

All the files area generated on the 
${andromda.ejb.generated.dir} directory. But I need to put 
the Bean files into one directory and the interfaces files in 
other.

Thanks

----------------------------------------------------------------------

Comment By: Matthias Bohlen (mattes3)
Date: 2003-10-19 11:35

Message:
Logged In: YES 
user_id=269920

Hi Peter,

thanks for this patch. It goes beyond what Greg had already 
submitted. I have committed the basic things from Greg's 
patch and would ask you to diff your changes relative to CVS 
HEAD, again. Then, please submit a new patch.diff file that 
contains only those changes that you still think are necessary.

Here the patch instructions in detail:

If you have modified some files to fix something yourself, 
don't attach the modified files. Instead, make a patch 
(standing in the root folder of your local updated CVS copy): 
cvs -q diff -b -u -N > patch.diff Then attach patch.diff to an 
existing issue, or make a new Bug/Improvement issue if 
none exists. You should only attach entire files if they are 
new files (not yet in CVS). The developers will then be able 
to apply the patch by issuing the following command from 
the root folder: patch -p 0 < patch.diff Developers using 
windows will need CygWin to get the patch program.

Thanks!
Matthias


----------------------------------------------------------------------

Comment By: Peter Royle (peteroyle)
Date: 2003-10-16 01:44

Message:
Logged In: YES 
user_id=883369

hi lpienia,

The packages used for the generation of EJB related files are 
done through the andromda-ejb cartridge which i haven't 
changed at all. If you want to change them i think you will 
need to modify that cartridge.

I did however change the directories which they land when 
they're generated - something I forgot to explain! I use 
generated gode fom both poseidon and andromda so it was 
practical for me to segregate the output into directories 
specific to the type of code being generated 
(andromda/poseidon), (generated/modifiable), (cartridge 
used). Hence the ejbs land in a directory something like 
src/java/generated/andromda/ejb/your/package/name/YourBea
nCMP. And similar for the home/remote interfaces i suspect (I 
sont actualy use ejbs so i'm guessing acccording to the build 
file).

The place to change all this is in the section labeled "<!-- 
Output directories for generators -->" of the build.xml file. 
This creates all the references to output directories for 
struts, hibernate and ejb that wil be used for the rest of the 
process.

Has this answered your question or have i missunderstood?

pete.

----------------------------------------------------------------------

Comment By: Lionel Pieniazek (lpienia)
Date: 2003-10-15 16:04

Message:
Logged In: YES 
user_id=683837

There is any way to generate the Remote, Home and Util in 
other packages?



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536547&aid=823276&group_id=73047