You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by be...@incubator.apache.org on 2004/10/14 21:16:51 UTC

[jira] Commented: (BEEHIVE-7) Integrate declarative controls support into WSM

The following comment has been added to this issue:

     Author: Michael Merz
    Created: Thu, 14 Oct 2004 12:16 PM
       Body:
Note that only wsm-axis, WSM's jar that contains Axis-specific code, depends on controls. The core wsm.jar can still be built without controls.jar and without the Axis jars.
In other words, the (annotation aware) Axis engine performs the context initialization and all other tasks that are related to controls.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/BEEHIVE-7?page=comments#action_54077

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/BEEHIVE-7

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: BEEHIVE-7
    Summary: Integrate declarative controls support into WSM
       Type: Task

     Status: Resolved
   Priority: Major
 Resolution: FIXED

    Project: Beehive
 Components: 
             Web Services (181)
   Fix Fors:
             TBD
   Versions:
             TBD

   Assignee: Michael Merz
   Reporter: Kenneth Tam

    Created: Wed, 6 Oct 2004 7:52 PM
    Updated: Thu, 14 Oct 2004 12:16 PM
    Due:     Fri, 15 Oct 2004 12:00 AM

Description:
WSM needs to support declarative usage of controls -- in other words, it needs to be a Java control client.  This means supporting auto-initialization of control type fields annotated with @Control, and hooking up of event handler methods annotated with @EventHandler.

High level steps needed to make this happen:

1) Ensure the WSM build process passes WMS sources through apt, and that the ControlClientAnnotationProcessor in controls.jar is registered with apt during that process.  For each WSM file Foo.java that uses controls, a corresponding FooClientInitializer.class should be generated by this build process.

2) When an instance of a WSM class that uses controls is instantiated, the corresponding initializer class should be loaded and its initialize method executed.  See org.apache.beehive.controls.runtime.bean.ControlBean's ensureControl() method for details on how this can be done.




---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira