[ http://jira.andromda.org/browse/EJB-89?page=all ]
     
Vance Karimi closed EJB-89:
---------------------------

    Resolution: Fixed

Fix in cvs.

> Bug in generating Accessor function in EJB3 Cartridge
> -----------------------------------------------------
>
>          Key: EJB-89
>          URL: http://jira.andromda.org/browse/EJB-89
>      Project: EJB Cartridge
>         Type: Bug

>     Reporter: Ali Abdel-Aziz
>     Assignee: Vance Karimi

>
> The  EntityEmbeddable.vsl  in andromda-ejb3-cartridge-1.0-SNAPSHOT used the 
> simple way for generating the setter and getter methods that is it add "get" 
> in front of any property to generate the getter 
> for example modeling property field with primitive data type boolean in 
> Entity class for example name it isActive property inside User class this 
> will yield getIsActive() in the Entity class (User.java).
> This will cause problem because this naming conventions is not the one used 
> in ValueObject.vsl in andromda-java-cartridge that it detects the boolean 
> properties to add "is" in front of property name and this yield isIsActive()
> in the Value Object class.
> and this causes a problem because there is interaction between VO and DAO, 
> and each one follows its naming conventions.
> I tried to find the place I need to alter to fix this and I found the 
> following function inside the EJB3EntityAttributeFacadeLogicImpl.java
> Code:
>     /**
>      * @see org.andromda.metafacades.uml.AttributeFacade#getGetterName()
>      */
>    public String getGetterName()
>    {
>         return "get" + StringUtils.capitalize(super.getName());
>    }
> But I decided to report this issue.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Reply via email to