You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Eddie O'Neil (JIRA)" <de...@beehive.apache.org> on 2005/09/08 21:22:49 UTC
[jira] Updated: (BEEHIVE-197) @ControlExtension: conflicting samples on incubator.apache.org

     [ http://issues.apache.org/jira/browse/BEEHIVE-197?page=all ]

Eddie O'Neil updated BEEHIVE-197:
---------------------------------

    Fix Version: V1
                     (was: v1m1)
    Description: 
This is related to BEEHIVE-118, and Ken's plan on "Inheritance semantic analysis" and/or "Robust semantic analysis".

http://incubator.apache.org/beehive/controls/controlsProgramming.html#11.1+Defining+an+Extended+Interface+for+a+Control+Type

One sample:

package org.apache.beehive.controls.examples;

import org.apache.beehive.controls.api.bean.ControlExtension;

@ControlInterface
@Destination(type=JmsMessageControl.QUEUE, name="queue.orders")
public interface OrderQueue extends JmsMessageControl
{
    ...
}

While the following one:

package org.apache.beehive.controls.examples;

import org.apache.beehive.controls.api.bean.ControlExtension;

@ControlExtension
@Destination(type=JmsMessageControl.QUEUE, name="queue.orders")
public interface OrderQueue extends JmsMessageControl
{
    public class Order implements java.io.Serializable
    {
        public Order(int buyer, String list)  { buyerID = buyer; itemList  list; }
        int buyerID;
        String [ ] itemList;       
    }

    @Message (OBJECT)
    public void submitOrder(
      @Body Order order, 
      @Property ( name="DeliverBy") String deliverBy
    );
}


The confusion: user could use either @ControlInterface or @ControlExtension to declare an extended control interface.

If user could use either @ControlExtension or @ControlInterface, more doc on when to use which one would be necessary.

  was:
This is related to BEEHIVE-118, and Ken's plan on "Inheritance semantic analysis" and/or "Robust semantic analysis".

http://incubator.apache.org/beehive/controls/controlsProgramming.html#11.1+Defining+an+Extended+Interface+for+a+Control+Type

One sample:

package org.apache.beehive.controls.examples;

import org.apache.beehive.controls.api.bean.ControlExtension;

@ControlInterface
@Destination(type=JmsMessageControl.QUEUE, name="queue.orders")
public interface OrderQueue extends JmsMessageControl
{
    ...
}

While the following one:

package org.apache.beehive.controls.examples;

import org.apache.beehive.controls.api.bean.ControlExtension;

@ControlExtension
@Destination(type=JmsMessageControl.QUEUE, name="queue.orders")
public interface OrderQueue extends JmsMessageControl
{
    public class Order implements java.io.Serializable
    {
        public Order(int buyer, String list)  { buyerID = buyer; itemList  list; }
        int buyerID;
        String [ ] itemList;       
    }

    @Message (OBJECT)
    public void submitOrder(
      @Body Order order, 
      @Property ( name="DeliverBy") String deliverBy
    );
}


The confusion: user could use either @ControlInterface or @ControlExtension to declare an extended control interface.

If user could use either @ControlExtension or @ControlInterface, more doc on when to use which one would be necessary.

    Environment: 

Updating the fix version.

> @ControlExtension: conflicting samples on incubator.apache.org
> --------------------------------------------------------------
>
>          Key: BEEHIVE-197
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-197
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: v1m1, V1Beta
>     Reporter: James Song
>     Assignee: Eddie O'Neil
>     Priority: Minor
>      Fix For: V1

>
> This is related to BEEHIVE-118, and Ken's plan on "Inheritance semantic analysis" and/or "Robust semantic analysis".
> http://incubator.apache.org/beehive/controls/controlsProgramming.html#11.1+Defining+an+Extended+Interface+for+a+Control+Type
> One sample:
> package org.apache.beehive.controls.examples;
> import org.apache.beehive.controls.api.bean.ControlExtension;
> @ControlInterface
> @Destination(type=JmsMessageControl.QUEUE, name="queue.orders")
> public interface OrderQueue extends JmsMessageControl
> {
>     ...
> }
> While the following one:
> package org.apache.beehive.controls.examples;
> import org.apache.beehive.controls.api.bean.ControlExtension;
> @ControlExtension
> @Destination(type=JmsMessageControl.QUEUE, name="queue.orders")
> public interface OrderQueue extends JmsMessageControl
> {
>     public class Order implements java.io.Serializable
>     {
>         public Order(int buyer, String list)  { buyerID = buyer; itemList  list; }
>         int buyerID;
>         String [ ] itemList;       
>     }
>     @Message (OBJECT)
>     public void submitOrder(
>       @Body Order order, 
>       @Property ( name="DeliverBy") String deliverBy
>     );
> }
> The confusion: user could use either @ControlInterface or @ControlExtension to declare an extended control interface.
> If user could use either @ControlExtension or @ControlInterface, more doc on when to use which one would be necessary.

-- 
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