- From: Arthur Ryman <ryman@ca.ibm.com>
- Date: Thu, 19 Jan 2006 12:56:13 -0500
- To: Amelia A Lewis <alewis@tibco.com>
- Cc: www-ws-desc@w3.org, www-ws-desc-request@w3.org
- Message-ID: <OFC98AE5D5.A0EE5685-ON852570FB.0061438D-852570FB.00628507@ca.ibm.com>
Amy, Thx. I'll add this to Part 1. Arthur Ryman, IBM Software Group, Rational Division blog: http://ryman.eclipsedevelopersjournal.com/ phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063, text: 4169395063@fido.ca Amelia A Lewis <alewis@tibco.com> Sent by: www-ws-desc-request@w3.org 01/18/2006 01:36 PM To www-ws-desc@w3.org cc Subject action item: warning to extensions authors In fulfillment of my action item, the following text is suggested as the final paragraph of section 6.3 (editor's copy) of part 1. <note><p> Authors of extensibility elements which may manifest as properties of the <comp>Description</comp> component should be alert to the impact of imports on their extensions, or their extensions on imports. It is not possible, within the component model, to define extensions which have an effective scope equal to the scope of a containing file. Extensions which modify the behavior of the components contained in a description may therefore unexpectedly modify the behavior of components in imported descriptions as well, unless proper care is taken. Users of such extension elements should also be aware of the potential pitfalls. </p></note> Amy! -- Amelia A. Lewis Senior Architect TIBCO/Extensibility, Inc. alewis@tibco.com
Received on Thursday, 19 January 2006 17:56:25 UTC