The "E" from Real Estate ... sorry. We are trying to evaluate Isis by fully implementing a subset of a SubDomain without making changes to the framework, as we are not quite confident about its internals. We are descovering some interesting things while debugging, but have not made any changes to source code.
Be sure that if we make any local changes to Apache Isis code we will release it or at least comment with you as the project's leader. Our "core business" is risk management and compliance, so we understand the concept of risk and the mitigation activity you are proposing. We would "commit" to it :-) Thanks for giving the option. We have not explored the bookmarks functionality. It's really interesting, an option we don't have on our own framework. The fact is that we are currently centered on exploring the framework and the migration costs. Our current focus is on evaluating the Domain ease of implementation, validation, testing, integrated security (we are using CAS as Single Sign-On; seems to be supported by Apache Shiro. And also Spring Security through Wavemaker, but we are quite confident we can integrate all authentication and authorization). We are also seeing a lot of value on the REST generated "API" (despite we have not focus our proof-of-concept there yet). It's not as centered on the Wickets or other presentation viewer, as we had something similar over Wavemaker (less powerful but enough for our current needs; we are also evaluating if it's worth the effort to extend it to support the Apache Isis programming model characteristics we are considering to use) . But thanks to the Wickets viewer the time needed from coding to showing the app to a business expert is REALLY shorter than the one we have with Wavemaker. So, at least, for prototyping we are planning to use it. Let's see what happens for production... I will create now the "Jira" tickets. El 14/05/2013, a las 08:34, Dan Haywood <[email protected]> escribió: > On 13 May 2013 14:06, GESCONSULTOR - Óscar Bou <[email protected]>wrote: > >> >> Nice to see there's going to be an official release this month. I >> understand they are not more often, if you were doing a lot of improvements >> due to the Statio project development. >> >> > s/Statio/Estatio.. > > Do you like the way that bookmarks now work. I should post about it, but > briefly: > > @Bookmarkable - bookmarked, in hidden panel to the left > @Bookmarkable(AS_CHILD) - will be bookmarked, but only if (one of) its > parent references is also bookmarked. > > > >> By now we will continue to prioritize to implement on Apache Isis a BC of >> our current solution in order to test it with our Domain, but those >> contributions are "annotated" :-) >> >> I couldn't quite parse what you are saying here. But if you are making > some local fixes to Isis, then please do consider raising tickets and > attaching patches. Then I can fold those changes back into Isis. > > Also, it seems that you now doing a lot of work on Isis, and that there's a > chance it may become a key dependency of your system. Any dependency > implies a risk. To offset that risk, it might make sense for you to look > to being a committer (and having a more direct influence on the framework) > in the future. If that appeals, then the first step down that road is to > start providing some contributions. > > cheers > Dan
