UML2 FrontEndForward outgoing exception state, FrontEndActivityGraph.controller returns null.

Description

Compare the build output in cartridges\andromda-jsf\target\cartridge-test\actual to actualUML2: Controller has
forward = (($targetUseCase.controller.fullyQualifiedName)this.resolveVariable("$targetUseCase.controller.beanName")).${targetUseCase.controllerAction}();

and ControllerTV has
$controller.fullyQualifiedName controller =
($controller.fullyQualifiedName)FacesContextUtils.resolveVariable(
request, response,
"$controller.beanName");

The same model in UML14 has the correct variable substitutions.

Environment

Andromda 3.4-SNAPSHOT as of 7/27/10.

Activity

Show:
Bob Fields
July 30, 2010, 4:12 AM

JSF Cartridge was using the wrong UML2 Test model.There are now 337 files, with a few differences due to required/unique settings. The main remaining issue is with the Controller.java.vsl/vm templates: migrated UML2 $controller.useCase.actions $actionState.forward (transition) returns packagename.unknown for the name instead of the forward name, resulting in null for . See uml22 FrontEndForwardLogic.handleGetName. StateVertexFacadeLogicImpl.handleGetOutgoings returns nothing when the outgoing is an exception target.

FrontEndActivityGraph.handleGetController also returns null.

To simplify troubleshooting, it would be easiest to have a simple model with only a single exception transition.

I left some debug code commented out in the temaplates Controller.java.vsl and ActionForwars.java.vsl to demonstrate the issue when comparing UML14 and UML2 output. Further troubleshooting requires figuring out why the metafacade mappings are not working.

Assignee

Former user

Reporter

Bob Fields

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure