[ http://issues.apache.org/jira/browse/BEEHIVE-1150?page=all ]
Carlin Rogers resolved BEEHIVE-1150.
------------------------------------
Resolution: Fixed
Assignee: Julie Zhuo (was: Carlin Rogers)
This is fixed with SVN revision 462841.
To check this, add the validatorVersion attribute to the @Jpf.Controller
annotation of a page flow controller and compile with the option
-Xlint:deprecation.
@Jpf.Controller(
validatorVersion = Jpf.ValidatorVersion.oneOne,
...
)
You receive the deprecated warning before the fix, but not after.
> Compiler warning that Jpf.ValidatorVersion is deprecated though the enum has
> not been deprecated
> ------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-1150
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1150
> Project: Beehive
> Issue Type: Bug
> Components: NetUI
> Affects Versions: 1.0.1, v.next
> Reporter: Carlin Rogers
> Assigned To: Julie Zhuo
> Priority: Minor
> Fix For: v.next
>
>
> Tory Toupin pointed out the following issue and solution...
> When you compile a page flow controller with the validatorVersion attribute
> set to a value of the Jpf.ValidatorVersion enum in the @Jpf.Controller
> annotation, you get a compiler warning... "[deprecation]
> org.apache.beehive.netui.pageflow.annotations.Jpf.ValidatorVersion in
> org.apache.beehive.netui.pageflow.annotations.Jpf has been deprecated"
> Seems the javadoc @deprecated on "page" in the NavigateTo enum immediately
> preceding the ValidatorVersion, causes the ValidatorVersion enum to be marked
> as deprecated. However, this is corrected if the javadoc annotation is
> removed and an @Deprecated annotation is used instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
