On 11/07/2018 22:56, [email protected] wrote:
I want to set up some common metadata that a suite of services
implemented in SWP can access.
I have a superclass of services, and in the header I can use a named
graph to persist information - because AFAICT it appears that named
graphs are the only mechanism for sharing context outside nested
elements?
Is there another way - perhaps to tap into what is obviously available
for parameters passed to the SWP which are available anywhere ?
Maybe http://uispin.org/ui.html#setContext or
http://uispin.org/ui.html#param
Secondly - is there any way to access metadata that identifies the SWP
service being called? I need to do this in a header, or some other way
to have the superclass access this information and pass it in a
standard way to activity loggers in each specialised service,
?thisNode and ?thisParent dont seem to work.
ui:param("_viewClass") should give you the physical starting point
assuming the service is called using _viewClass=...
I don't see any other standard way of finding the root entry point. You
could modify you root services so that they set some context variable
using ui:setContext, and the elements downstream can query that value
using ui:contextValue().
Finally - it seems if i subclass a service then the headerIncludes
from the parent is still run - which is what I want - but is there any
guarantee or way to force it to be included first?
Yes, inherited headIncludes will be executed first.
Holger
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
