Code Generation Templates > Java ...

[juanPablos]

Hello,

I want to modify the code gen templates for Java (as I'm generating ActionScript 3 code from EA - and Java is the closest match, both based on ECMA).

Here is what EA produces for Java auto accessor methods (or getter/setters if you like):

public function set setmyProperty(newVal:int): void
public function get getmyProperty(): int

I just want to modify the templates so that it doesn't generate the get and set keywords twice (as it currently appends these keywords to the front of property name), ie: I want it exactly the same as the 2 lines of code above, without the bolded text.

Cheers.

[juanPablos]

Furthermore, I think I've found what I need to modify.

I believe I need to modify a Transformation Template. Specifically the Properties template within the Java language.

Here's what it currently looks like:

Code: [Select]

$attName=$parameter1
$type=$parameter2
$propertyName=$attName
$propertyName=%REMOVE_PREFIX($propertyName,genOptPropertyPrefix)%
%if genOptGenCapitalisedProperties=="T"%
$propertyName=%CONVERT_NAME($propertyName, "camel case", "pascal case")%
%endIf%
Operation
{
  %TRANSFORM_REFERENCE()%
  name=%qt%%genOptJavaGetPrefix%$propertyName%qt%
  stereotype="property get"
  scope="Public"
  type=%qt%$type%qt%
  code=%qt%return $attName;%qt%
  Tag{name="attribute_name" value=%qt%$attName%qt%}
}

Operation
{
  %TRANSFORM_REFERENCE()%
  name=%qt%%genOptJavaSetPrefix%$propertyName%qt%
  stereotype="property set"
  scope="Public"
  type="void"
  Parameter
  {
    name="newVal"
    type=%qt%$type%qt%
  }
  code=%qt%$attName = newVal;%qt%
  Tag{name="attribute_name" value=%qt%$attName%qt%}
}
So can anyone advise how to remove the get and set prefixing?, or at least let me know what language this is above? I'll search meanwhile, I'm assume it's a C language.

Thanks.

[Krzysztof Swiatkowski]

Maybe you could just clear Get Prefix and Set Prefix in Options>Source Code Engineering > Java?

Regards
Kris

[juanPablos]

Thanks Kris - I'll set how it goes.

[Eve]

None of the Java templates will help you as they are not used when making these properties.  (The template you showed does copy the behavior though.)

Unfortunately I suspect that if the prefix options are cleared EA assumes a default.

[Krzysztof Swiatkowski]

Unfortunatelly Simon your suspicion is correct, but good old space does the trick

[Eve]

Just be aware, that it won't synchronize them correctly.  The parser won't see any methods in the code that match your model method.

That's why I didn't suggest modifying the actionscript property set and property get templates to remove the prefix.  The same problem applies.

[juanPablos]

so is there a way around this ?

[Eve]

There are always options, but not necessarily ones you would like.

1. Manually create the properties.
2. Manually remove the prefixes
3. Write an automation client, add-in or sql call to remove the prefixes.
4. Generate it once with the prefixes, modify it in code and reverse engineer.
5. Write a transformation to create the properties the way you want.

That's a start, but I'm sure it's nowhere near an exhaustive list.

[juanPablos]

Thanks Simon M - that's a little outside my range of skills and timeframe at the moment. I'll stick to running a macro across the generated files for now.

Thanks again.