[wsrp-wsia] Issue #21: More verbiage for initEnvironment()

[Rich Thompson <richt2@us.ibm.com>]

This is one of those catch-22s ... the process we established says the
editors should put things in the spec after they are resolved, but these
editorial type usually want to see it in the spec before it goes to
resolved. Current language is:

  If  the  Producer's  metadata has set the doInitEnvironment flag to true,
  then  the  Consumer  MUST  invoke  initEnvironment() once for the groupID
  prior  to invoking getMarkup() for this End-User for any entity using the
  same  groupID.  The  Consumer  MAY invoke initEnvironment() concurrently,
  each with a different groupID, for the interactions with the End-User. If
  at     any     time    the    Producer    throws    a    fault    message
  ("WSRP.Interface.InvalidEnvironment") indicating the environment for this
  groupID with this End-User has been invalidated at the Producer, then the
  Consumer  MUST again invoke initEnvironment() for this groupID and SHOULD
  then reprocess the invocation that caused the fault message to be thrown.

This fault message is in the table in section 14. That section briefly
discusses that WSDL fault codes are strings with '.' delimited hierarchies
for the messages. All of ours start with 'WSRP', currently there are two
second level strings ('Security' and 'Interface').



                                                                                                                  
                      Michael Freedman                                                                            
                      <Michael.Freedman@        To:       wsrp-wsia <wsrp-wsia@lists.oasis-open.org>              
                      oracle.com>               cc:                                                               
                                                Subject:  [wsrp-wsia] re: Issues for 10/7                         
                      10/15/2002 06:53                                                                            
                      PM                                                                                          
                                                                                                                  
                                                                                                                  



There are few issues this week that have been marked to move from
tentative to resolved that I don't think are ready yet.  Here are the
comments for those issues:

Issue #21: More verbiage for initEnvironment().
   Though draft .7 adds more words to clarify this it still has a
placeholder for defining the fault that indicates the inited environment
has expired.  Is there another issue open to address this?  If not
should we leave this issue open until the verbiage is complete?

    -Mike-







----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>