Do not use BEA Beehive @jpf:controller annotations

BEA Beehive @jpf:controller Javadoc tags in the migrated JPF files are flagged by this rule. The rule has a quick fix that converts the tag to a @Jpf.Controller class-level annotation that is required on page flow classes.

The following example shows BEA Beehive @jpf:controller Javadoc tags:

/**
* This is a controller example.
*
* @jpf:controller
* @jpf:view-properties view-properties::
* <view-properties>
* <pageflow-object id="pageflow:/Controller.jpf"/>
. . .
* </view-properties>
* ::
* @jpf:message-resources resources="messages.Validation"
*/
public class Controller extends PageFlowController

The quick fix migrates these tags as shown in the following example:

/*
* This is a controller example.
*
* @jpf:controller
* @jpf:view-properties view-properties::
* <view-properties>
* <pageflow-object id="pageflow:/Controller.jpf"/>
. . .
* </view-properties>
* ::
* @jpf:message-resources resources="messages.Validation"
*/
@Jpf.Controller(
messageBundles = { @Jpf.MessageBundle(bundlePath = "messages.Validation") }
)
public class Controller extends PageFlowController

The Javadoc is converted to regular Java™ comments so that the rule does not continue to detect the @jpf tag.

Also, you do not need to migrate the @jpf:view-properties tags because they are intended for display purposes in the WebLogic Workshop IDE.