[Esml-users] RE: esml-users Digest, Vol 2, Issue 3
Schulte, Mark D
mark.d.schulte at boeing.com
Mon May 17 07:55:43 CDT 2004
Even without the Teknowledge plug-in, the information concerning events
can be discerned from the original model since that information is
captured in the documentation field associated with the component
(class, <abstract component> or <concrete component>). So for example,
if you look at the BM1__CyclicDeviceComponent, you can view its
documentation field in Rose and see it has an entry for Events
Consummable = INTERVAL_TIMEOUT and events supplied = ANY. So all
instances of this component type can only consume the one event type
listed but depending on the particular instance, any type of event would
be legal to publish. The EventSink and EventSupplier classes being
referred to provide the mechanisms for publishing and subscribing to
events, but since Rose classes define the component type information and
not the instance level model, this is just providing a mechanism for the
events to be handled rather than specifying specific events at that
point.
-----Original Message-----
From: esml-users-request at list.isis.vanderbilt.edu
[mailto:esml-users-request at list.isis.vanderbilt.edu]
Sent: Thursday, May 13, 2004 12:00 PM
To: esml-users at list.isis.vanderbilt.edu
Subject: esml-users Digest, Vol 2, Issue 3
Send esml-users mailing list submissions to
esml-users at list.isis.vanderbilt.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
or, via email, send a message with subject or body 'help' to
esml-users-request at list.isis.vanderbilt.edu
You can reach the person managing the list at
esml-users-owner at list.isis.vanderbilt.edu
When replying, please edit your Subject line so it is more specific than
"Re: Contents of esml-users digest..."
Today's Topics:
1. RE: Re: RE Esml-users Event ports with null event refs
(Jesse Greenwald)
2. RE: Re: RE Esml-users Event ports with null event refs
(Sandeep Neema)
3. RE: Re: RE Esml-users Event ports with null event refs
(Jesse Greenwald)
4. RE: Re: RE Esml-users Event ports with null event refs
(Sandeep Neema)
----------------------------------------------------------------------
Message: 1
Date: Wed, 12 May 2004 12:32:29 -0500
From: Jesse Greenwald <jesse at cis.ksu.edu>
Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null
event refs
To: "A list for ESML users to share thoughts and discuss bugs and
fixes." <esml-users at list.isis.vanderbilt.edu>
Message-ID: <1084383149.840.13.camel at localhost>
Content-Type: text/plain; charset=iso-8859-1
Hi Sandeep,
On Tue, 2004-05-11 at 22:57, Sandeep Neema wrote:
> Jesse,
> The specific events to publish are often instance-specific decision
> i.e. a Component user can customize the specific event-types published
> by a component when instantiating a component in the system. This is
> the reason why these event references are 'null'. In fact this
> information (i.e. null event-types) is coming from the PRISM interface
> of Rational Rose, where some publish/subscribe ports of components are
> typed with 'ANY Event'.
Is the Rational Rose model that you are talking about the one that is
included with the OEP releases from Boeing? I've looked at the Rose
model that comes with the 3.0 release of the OEP and I don't see what
you are referring too. In the model I'm look at, most of the components
simply use the abstract BM__EventSink (of which there is only one
implementation - BM__UpdateEventSinkAdapter_T) for consuming events and
the UUEventSupplier for publishing events. Is there some attribute or
association that I'm missing?
Thanks,
Jesse
------------------------------
Message: 2
Date: Wed, 12 May 2004 13:51:15 -0500
From: "Sandeep Neema" <sandeep at isis.vanderbilt.edu>
Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null
event refs
To: "esml-users" <esml-users at list.isis.vanderbilt.edu>
Message-ID:
<029DBE7A1D95BF4A860FE19EA15FA533C02393 at isis.Vanderbilt.Edu>
Content-Type: text/plain; charset="us-ascii"
Jesse,
These are the ACL properties that I am referring to. I believe that you
need the Teknowledge plug-in to look at/or edit those attributes in
Rose. The Teknowlege plug-in generates the PRISM xml file that is used
to seed the ESML model.
Here is an XML generated with that plugin.
Thanks
Sandeep
--
Sandeep Neema
Research Scientist,
Institute of Software Integrated Systems, Vanderbilt University
Phone: 615-343-9996
Email: sandeep.k.neema at vanderbilt.edu
-----Original Message-----
From: Jesse Greenwald [mailto:jesse at cis.ksu.edu]
Sent: Wednesday, May 12, 2004 12:32 PM
To: esml-users
Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null event
refs
Hi Sandeep,
On Tue, 2004-05-11 at 22:57, Sandeep Neema wrote:
> Jesse,
> The specific events to publish are often instance-specific decision
i.e.
> a Component user can customize the specific event-types published by a
> component when instantiating a component in the system. This is the
> reason why these event references are 'null'. In fact this information
> (i.e. null event-types) is coming from the PRISM interface of Rational
> Rose, where some publish/subscribe ports of components are typed with
> 'ANY Event'.
Is the Rational Rose model that you are talking about the one that is
included with the OEP releases from Boeing? I've looked at the Rose
model that comes with the 3.0 release of the OEP and I don't see what
you are referring too. In the model I'm look at, most of the components
simply use the abstract BM__EventSink (of which there is only one
implementation - BM__UpdateEventSinkAdapter_T) for consuming events and
the UUEventSupplier for publishing events. Is there some attribute or
association that I'm missing?
Thanks,
Jesse
_______________________________________________
esml-users mailing list
esml-users at list.isis.vanderbilt.edu
http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OEP_B3.0-ACL.xml
Type: text/xml
Size: 86946 bytes
Desc: OEP_B3.0-ACL.xml
Url :
http://list.isis.vanderbilt.edu/pipermail/esml-users/attachments/2004051
2/e6baf27c/OEP_B3.0-ACL-0001.xml
------------------------------
Message: 3
Date: Thu, 13 May 2004 11:23:17 -0500
From: Jesse Greenwald <jesse at cis.ksu.edu>
Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null
event refs
To: "A list for ESML users to share thoughts and discuss bugs and
fixes." <esml-users at list.isis.vanderbilt.edu>
Message-ID: <1084465397.852.114.camel at localhost>
Content-Type: text/plain; charset=iso-8859-1
Hi Sandeep,
After looking at OEP Rose model and the XML ESCM export, I think there
are some problems with the model. For instance, there three different
event types for timeouts (Interval Timeout, INTERVAL_TIMEOUT,
INTERVAL_TIMEOUT). Shouldn't these all be the same? There should also
be an event type for data available events since this is the other event
type that is used in the system. Instead, there is no data available
event and components are being specified as just publishing ANY. But,
this would seem to imply that the components are publishing timeout
events, but only timers should be publishing timeout events.
I'm going to go ahead and ping the Boeing folk and see what they say
about the model.
Thanks a bunch for help,
Jesse
On Wed, 2004-05-12 at 13:51, Sandeep Neema wrote:
> Jesse,
> These are the ACL properties that I am referring to. I believe that
> you need the Teknowledge plug-in to look at/or edit those attributes
> in Rose. The Teknowlege plug-in generates the PRISM xml file that is
> used to seed the ESML model.
>
> Here is an XML generated with that plugin.
>
> Thanks
> Sandeep
>
>
> --
> Sandeep Neema
> Research Scientist,
> Institute of Software Integrated Systems, Vanderbilt University
> Phone: 615-343-9996
> Email: sandeep.k.neema at vanderbilt.edu
>
> -----Original Message-----
> From: Jesse Greenwald [mailto:jesse at cis.ksu.edu]
> Sent: Wednesday, May 12, 2004 12:32 PM
> To: esml-users
> Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null
event
> refs
>
> Hi Sandeep,
>
> On Tue, 2004-05-11 at 22:57, Sandeep Neema wrote:
> > Jesse,
> > The specific events to publish are often instance-specific decision
> i.e.
> > a Component user can customize the specific event-types published by
> > a component when instantiating a component in the system. This is
> > the reason why these event references are 'null'. In fact this
> > information (i.e. null event-types) is coming from the PRISM
> > interface of Rational Rose, where some publish/subscribe ports of
> > components are typed with 'ANY Event'.
>
> Is the Rational Rose model that you are talking about the one that is
> included with the OEP releases from Boeing? I've looked at the Rose
> model that comes with the 3.0 release of the OEP and I don't see what
> you are referring too. In the model I'm look at, most of the
> components simply use the abstract BM__EventSink (of which there is
> only one implementation - BM__UpdateEventSinkAdapter_T) for consuming
> events and the UUEventSupplier for publishing events. Is there some
> attribute or association that I'm missing?
>
> Thanks,
> Jesse
>
> _______________________________________________
> esml-users mailing list
> esml-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
>
> ______________________________________________________________________
> _______________________________________________
> esml-users mailing list
> esml-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
------------------------------
Message: 4
Date: Thu, 13 May 2004 11:41:22 -0500
From: "Sandeep Neema" <sandeep at isis.vanderbilt.edu>
Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null
event refs
To: "esml-users" <esml-users at list.isis.vanderbilt.edu>
Cc: "Noll, Dennis D" <dennis.d.noll at boeing.com>
Message-ID:
<029DBE7A1D95BF4A860FE19EA15FA533C02419 at isis.Vanderbilt.Edu>
Content-Type: text/plain; charset="us-ascii"
Jesse,
Yes, the 'Interval Timeout', and 'INTERVAL_TIMEOUT', and so on should be
the same. These are user modeling errors i.e. when somebody is editing
the ACL properties the mistakes are made. However, the 'ANY' simply
indicates that the component can publish any event that it is configured
to publish during thru the models. There is nothing magical about the
DATA_AVAILABLE event as far as the component types are concerned, and
that's why it is not there in the component type models. The
DATA_AVAILABLE event is a scenario specific artifact that is modeled in
the scenario models, and the component instances are appropriately bound
to that particular event type. The 'INTERVAL_TIMEOUT' on the other hand
has special semantics and is an event that could/should be published by
the Timer component (which is not a real component) only.
In any case these questions are best answered by the Boeing folks (I am
cc'ing Dennis and Mark on this)
Thanks,
Sandeep
--
Sandeep Neema
Research Scientist,
Institute of Software Integrated Systems, Vanderbilt University
Phone: 615-343-9996
Email: sandeep.k.neema at vanderbilt.edu
-----Original Message-----
From: Jesse Greenwald [mailto:jesse at cis.ksu.edu]
Sent: Thursday, May 13, 2004 11:23 AM
To: esml-users
Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null event
refs
Hi Sandeep,
After looking at OEP Rose model and the XML ESCM export, I think there
are some problems with the model. For instance, there three different
event types for timeouts (Interval Timeout, INTERVAL_TIMEOUT,
INTERVAL_TIMEOUT). Shouldn't these all be the same? There should also
be an event type for data available events since this is the other event
type that is used in the system. Instead, there is no data available
event and components are being specified as just publishing ANY. But,
this would seem to imply that the components are publishing timeout
events, but only timers should be publishing timeout events.
I'm going to go ahead and ping the Boeing folk and see what they say
about the model.
Thanks a bunch for help,
Jesse
On Wed, 2004-05-12 at 13:51, Sandeep Neema wrote:
> Jesse,
> These are the ACL properties that I am referring to. I believe that
you
> need the Teknowledge plug-in to look at/or edit those attributes in
> Rose. The Teknowlege plug-in generates the PRISM xml file that is used
> to seed the ESML model.
>
> Here is an XML generated with that plugin.
>
> Thanks
> Sandeep
>
>
> --
> Sandeep Neema
> Research Scientist,
> Institute of Software Integrated Systems, Vanderbilt University
> Phone: 615-343-9996
> Email: sandeep.k.neema at vanderbilt.edu
>
> -----Original Message-----
> From: Jesse Greenwald [mailto:jesse at cis.ksu.edu]
> Sent: Wednesday, May 12, 2004 12:32 PM
> To: esml-users
> Subject: RE: [Esml-users] Re: RE Esml-users Event ports with null
event
> refs
>
> Hi Sandeep,
>
> On Tue, 2004-05-11 at 22:57, Sandeep Neema wrote:
> > Jesse,
> > The specific events to publish are often instance-specific decision
> i.e.
> > a Component user can customize the specific event-types published by
a
> > component when instantiating a component in the system. This is the
> > reason why these event references are 'null'. In fact this
information
> > (i.e. null event-types) is coming from the PRISM interface of
Rational
> > Rose, where some publish/subscribe ports of components are typed
with
> > 'ANY Event'.
>
> Is the Rational Rose model that you are talking about the one that is
> included with the OEP releases from Boeing? I've looked at the Rose
> model that comes with the 3.0 release of the OEP and I don't see what
> you are referring too. In the model I'm look at, most of the
components
> simply use the abstract BM__EventSink (of which there is only one
> implementation - BM__UpdateEventSinkAdapter_T) for consuming events
and
> the UUEventSupplier for publishing events. Is there some attribute or
> association that I'm missing?
>
> Thanks,
> Jesse
>
> _______________________________________________
> esml-users mailing list
> esml-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
>
> ______________________________________________________________________
> _______________________________________________
> esml-users mailing list
> esml-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
_______________________________________________
esml-users mailing list
esml-users at list.isis.vanderbilt.edu
http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
------------------------------
_______________________________________________
esml-users mailing list
esml-users at list.isis.vanderbilt.edu
http://list.isis.vanderbilt.edu/mailman/listinfo/esml-users
End of esml-users Digest, Vol 2, Issue 3
****************************************
More information about the esml-users
mailing list