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/07 04:54:51 UTC
[jira] Created: (BEEHIVE-7) Integrate declarative controls support into WSM
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
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: Unassigned
Priority: Major
Project: Beehive
Components:
Web Services (181)
Fix Fors:
TBD
Versions:
TBD
Assignee:
Reporter: Kenneth Tam
Created: Wed, 6 Oct 2004 7:52 PM
Updated: Wed, 6 Oct 2004 7:52 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
[jira] Commented: (BEEHIVE-7) Integrate declarative controls support into WSM
Posted by be...@incubator.apache.org.
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
[jira] Resolved: (BEEHIVE-7) Integrate declarative controls support into WSM
Posted by be...@incubator.apache.org.
Message:
The following issue has been resolved as FIXED.
Resolver: Michael Merz
Date: Thu, 14 Oct 2004 12:12 PM
Rev 54794.
Controls are now enabled for jws-files, i.e. control annotations in jws-files get picked up by apt.
The AnnotatedAxis webapp uses ...servlet.ControlFilter to get a context. The filter is configured for *.jws files.
---------------------------------------------------------------------
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:12 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
[jira] Closed: (BEEHIVE-7) Integrate declarative controls support into WSM
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-7?page=all ]
Jeremiah Johnson closed BEEHIVE-7:
----------------------------------
Assign To: Jeremiah Johnson (was: Michael Merz)
Declarative usages of Controls is available in JWS. There are a couple samples and DRTs and has been documented that APT needs to run on the .JWS. There are some DRTs for EventHandler, but I didn't see any samples in JWS outside of the DRTs. I wrote my own sample and verified that events are getting called in the JWS as expected.
> Integrate declarative controls support into WSM
> -----------------------------------------------
>
> Key: BEEHIVE-7
> URL: http://issues.apache.org/jira/browse/BEEHIVE-7
> Project: Beehive
> Type: Task
> Components: Web Services (181)
> Versions: V1Alpha
> Reporter: Kenneth Tam
> Assignee: Jeremiah Johnson
> Fix For: V1Alpha
>
> 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.
--
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