[ http://issues.apache.org/jira/browse/BEEHIVE-364?page=all ]
Kyle Marvin updated BEEHIVE-364:
--------------------------------
type: Bug (was: Improvement)
Reclassifying as a bug since this is actually blocking a desired use case for
Pageflows.
> Enable classes to be used as contextual services for controls
> -------------------------------------------------------------
>
> Key: BEEHIVE-364
> URL: http://issues.apache.org/jira/browse/BEEHIVE-364
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Reporter: Kyle Marvin
> Assignee: Kyle Marvin
> Fix For: V1
>
> Currently, the Controls annotation processor requires that any field
> annotated by @Context be of an interface (not a class) type. There is
> really no reason why a class can't act as a contextual service... the base
> JavaBeans contextual service model upon which this is built does not require
> this.
> Rich Feit would like to expose PageFlowController for controls running inside
> of a pageflow, but it is a class.
> The core issue here is that APT control processing uses AptControlInterface
> for both control and context fields... but the validation rules actually need
> to differ.
> The right thing is to add an intermediate abstract AptEventSource that
> represents a type that can declare (and deliver events) and then have
> AptControlInterface and AptContextType that derive from it. So a little
> refactoring should enable it to be fixed.
--
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
