isis-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Meyer - KMZ" <>
Subject Re: Some questions
Date Thu, 21 Nov 2013 19:39:32 GMT

> > In no particular order:
> > a) how well does it work on EE6+ servers
> very well, thank you!


I was aked if the wars can be deployed into non-Tomcat installations.
> > and how much of EE
> > infrastructure can it leverage? (see next questions)
> >
> Since Isis is a framework that provides a container for domain objects, the
> user's code is substantially hidden from JEE.  So the question really is to
> what extent could one expose these services.

I think this question was from the other perspective: Can the 
user-written domain classes access services provided by the EE 
server? (i.e. can the "developer" access more than what is provided 
by Isis). [I don't know what these could be, personally].

> > d) could user use JPA instead of JDO?
> > [The Isis DN objectstore currently has a JDO implementation. One
> > would have to write a JPA equivalent?]
> >
> Not currently.  DN does support JPA syntax, so I imagine the changes would
> be pretty simple.
> Supporting a different JPA implementaition would be much more work...
>  Note: we cannot ever support Hibernate because of its license (LGPL); that
> basically leaves OpenJPA.

To clarify, a user could add Hibernate into their own extension, but it 
could never be added to the Apache Isis codebase on

> > f) What about client-side validation?
> >
> >
> What's the client in this context... presumably the browser/Javascript?
> It would be possible, if using the Wicket viewer, to write some custom
> Javascript, and have it call back into the Restful Objects viewer to
> perform validation.  Otherwise, we are leveraging the capabilities of the
> Wicket framework.  That does quite a lot in this space.  Isis' Wicket
> viewer has a pluggable architecture for its components, so writing cleverer
> widgets is certainly do-able.

On further questioning, the asker of this question was after reducing 
the number of queries to the server - so the idea of AJAX calls back 
to the RO viewer is not ideal. He'd want scripts that do the validation 
on the client without additional calls back to the server.

I can imagine a system whereby validation scripts get served to the 
client. Can they be introspected from the validateXXX methods? That 
would be interesting!

> > General feedback: The guys asking all seemed to working on or for
> > Redhat (JBoss) and related. They seemed surprised that Isis adopted
> > JDO over JPA, with comments along the lines of "but JDO is dead
> > already".
> I doubt that Andy Jefferson would agree. But yes, it is the betamax to
> JPA's vhs.  Note: it's also more capable, eg supporting NoSQL stores as
> well as RDBMS [2]

Interesting! Are you offering to push this analogy to the next level: 
betamax was also the better technology over VHS.. is JDO somehow 
better than JPA? (apart from the extra NoSQL functionality).

> > Otherwise, the general consensus was positive, since Isis
> > handles all that one could want, if one wanted everything to be
> > provided by a single framework.
> >
> >
> Nice to hear!
> Thanks for doing this talk, Kevin.

I quite enjoy giving these talks.. I do quite like the Isis Framework ;)

- Kevin

View raw message