Hmmm. Confusing. Could not find any reading references to scope either. Can you think of any circumstances where the store could be interested in its scope?

Oliver

Stefan L�tzkendorf wrote:

Thanks Oliver,
that are good news.
Our question occurs because the Service interface has a setScope method
(instead of addScope) and all implementations are storing a single Scope
instance in a member variable, though we have not any usage of it.
Regards,
Stefan L�tzkendorf

Oliver Zeigermann wrote:

I suppose it is intended. Stores get resolved over the Uri class and will be enlisted into the current transaction only if they not already are. So, there should be no problem.

Although not completely on topic, have a look at:

http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=2117


Oliver


Stefan L�tzkendorf wrote:

Hello,

currently it is possible to map multiple scope to the same store, e.g.

  <scope match="/" store="memory" />
  <scope match="/scope1" store="xis"/>
  <scope match="/scope2" store="xis"/>
  <scope match="/scope3" store="xis"/>

Is this an intended usage, and can we rely on this while writing a store?

Thanks in advance,
Stefan L�tzkendorf






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to