OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-markup message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [wsrp-markup] [wsrp][markup] Minutes for 7/10/02 conference call


Chris,
   Sorry I missed the call this week.  Can you explain why:
 JSR 168 has the notion of action URLs and render URLs.  An action URL causes an entity to execute its process phase.  By allowing two types of actions the entity can bypass the action phase and allow for the render phase to receive the action parameters.  There is probably nothing that needs to be added to the WSRP protocol to address this.  The producer container will be able to handle this transparently.
 
   How does the container/portal determine whether to call the action method vs. the render method if there isn't an indication in the originating URL?  I.e. how is this handled transparently?  Are we expecting the JSR to encode this information in "query string" parameters - hence its opaque to us?
      -Mike-
 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC