Здравей Борис!
You can also take a look at
https://github.com/isisaddons/isis-app-kitchensink/tree/master/dom/src/main/java/org/isisaddons/app/kitchensink/dom/hierarchy
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Dec 15, 2014 at 8:20 PM, Boris Toninski
Hi Jeroen,
thanks a lot for the quick reply. I will start looking at Estatio as you have
suggested.
From: Jeroen van der Wal
Sent: Monday, December 15, 2014 7:52 PM
To: users
Subject: Re: Is Apache ISIS suitable for hierarchical data administration
Hi B
Hi Boris,
Welcome on the mailing list!
The first possibility you describe is a typical scenario for an Apache Isis
application. In Estatio we have hierarchical patterns everywhere, you can
start investigating Property->Unit in the asset module.
Lease->LeaseItem->LeaseTerm [2] is also interesting.
We have to implement an admin web site for entering / editing our static
data in the DB. The data is hierarchical. Lets take a company example.
We will have Company entity (DB table), the company will have children
entities - Department, it will again have children - Employee, and again
it will
OK, if you're using the simpleapp archetype then that does have security
enabled, just using the shiro.ini file ie our "sven" user etc.
But that doesn't include the "initialization" user.
So I guess the fix is the archetype should include those permissions, and
we should document the existenc
I've not enabled anything related to security.
Just downloaded the simple archetype 3-4 weeks ago.
Are there any steps to follow?
Thanks,
Oscar
> El 15/12/2014, a las 11:15, Dan Haywood
> escribió:
>
> Have you enabled security also? The exception stack trace includes:
>
> org.apache.i
On 13 December 2014 at 13:17, Martin Grigorov wrote:
>
> There is a Markdown broken link at the middle of the page content:
>
> ...
> I just committed a change in the .md file but I still don't see the change
> at
>
> http://isis.apache.org/more-advanced-topics/How-to-suppress-contributions.html
>
Have you enabled security also? The exception stack trace includes:
org.apache.isis.applib.services.wrapper.HiddenException: Reason: Not
authorized to view. Identifier: com.tellmegen.domain.model.Account#name()
Initialization is performed using a "special" user (I think it's called
"initializati
Hi to all.
I've started some work using the latest snapshot.
I was used to invoke all setters inside a
wrapperFactory.wrap(domainObject).setXXX() in order to always force execution
of domain logic placed inside the validateXXX, hiddenXXX, disabledXXX,
modifyXXX, clearXXX, etc. methods.
But on
