You'll need a property on each instance to indicate its owner. You can
then use a disabled() or hidden() methods to make the object read-only or
to hide it completely.
There were a couple of pages on the Isis website about this, I've just
updated them with examples for this use case [1],[2]
HTH
Hi,
This is somehow related to the tickets about SMS [1], mail [2] and twitter
[3] notifications.
Yet another way for notification.
1. https://issues.apache.org/jira/browse/ISIS-182
2. https://issues.apache.org/jira/browse/ISIS-171
3. https://issues.apache.org/jira/browse/ISIS-183
Martin
That's a good point, Martin.
I guess I should elaborate a little more...
- it's relatively easy for us to write a domain service that will send out
an SMS, mail or twitter message. We haven't done written any of these, but
it's just a matter of wrapping the API in a domain service that then
Tnx Dan!!
You'll need a property on each instance to indicate its owner. You can
then use a disabled() or hidden() methods to make the object read-only or
to hide it completely.
There were a couple of pages on the Isis website about this, I've just
updated them with examples for this use
Hi Dan,
This is working fine!!
Maybe it is worthwhile to mention in the documentation�that the
getUser().hasRole(..) now needs isisModuleSecurityRealm:ROLE-HERE as an
argument instead of just ROLE-HERE?
Greetz, Johan
You'll need a property on each instance to indicate its owner.
You can also use a regex: getUser().hasRole(.*YOUR_ROLE) if I'm correct.
Cheers,
Jeroen
On 23 Oct 2014 17:00, johandoornen...@filternet.nl wrote:
Hi Dan,
This is working fine!!
Maybe it is worthwhile to mention in the documentation that the
getUser().hasRole(..) now needs
