[ http://jira.andromda.org/browse/CORE-129?page=all ]
Cyril Combe updated CORE-129:
-----------------------------
Attachment: CORE-129-MetafacadeFactory.java.diff
> In MetafacadeFactory, contextRoot is not reset when retrieving a metafacade
> from the cache
> ------------------------------------------------------------------------------------------
>
> Key: CORE-129
> URL: http://jira.andromda.org/browse/CORE-129
> Project: AndroMDA Core
> Type: Bug
> Versions: 3.2
> Reporter: Cyril Combe
> Assignee: Chad Brandon
> Attachments: CORE-129-MetafacadeFactory.java.diff
>
> When retrieving a metafacade from the cache, MetafacadeFactory.getMetafacade
> does not properly reset the contextRoot property of the metafacade. So if the
> metafacade has been instanciated a first time with contextRoot = true and
> then retrieved to be used a "super metafacade" by another metafacade, all
> the call to setMetafacadeContext() will have no effects and the retrieved
> metafacade will be used with the wrong context.
> As an example, this causes
> SpringManageableEntity.getManageableAssociationEnds() to return
> ManageableAssociationEnd instances instead of
> SpringManageableEntityAssociationEnd instances. This results in errors in
> generated ManageableDaoBase classes when using inheritance.
> See this forum thread : http://galaxy.andromda.org/forum/viewtopic.php?t=2843
> Here is a workaround in the following patch.
--
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
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
