On 20 August 2013 07:01, Hugo van Elk <hugo.van....@gmail.com> wrote:
> Hi Dan! > > Perhaps something more, but nothing is fixed yet. I think the concept of > ISIS is great. > Good to hear. And welcome to the list, Hugo. > > Right now I have the following goals: > > - give an API design workshop - I want to have a demo of hateoas. I can > build that in ISIS of spring-hateoas. I like the idea of using the > browser > as a generic client (illustration of discoverability). > > I presume this is the RO viewer? My preferred Chrome plugins are json-view (extension) and REST Console (app), but I guess there are many equivalents. > - prototype - next week we start a greenfield project. I would like to > be able to quickly prototype our insights. > > I predict you'll have a lot of fun! > - production code - perhaps this prototype can be used as a starting > point for production code But that depends on how the team reacts. We > already decided to go for JPA with Hibernate impl and wicket front end. > > Thanks for showing interest! > > As a heads-up, at the moment we don't support the JPA API, only the JDO API. That's because the latter gives us more reach (eg NOSQL support), as well as for Google App Engine. So if you did want to take your app through to production with Isis, right now you would need to switch to JDO. Obviously that rules out Hibernate. Oscar (our newest committer) is currently working on a project where they did decide to adopt Isis for their production framework. That means they had to port their existing JPA entities to JDO. My understanding is that it wasn't too difficult. If you are just getting started with Isis, though, then the "safe" path is to do as you describe, just to use it for prototyping, and then take your pojos and deploy on some other, more familiar, production runtime. With care, it would be possible for your pojos to be usable without change in both Isis (as a prototyping platform) and in your produciton platform. If you do go this route, then you'll need to figure out for yourself how production runtime interacts with the domain objects; obviously it isn't going to understand any Isis-specific metadata such as @MemberOrder. But you could easily teach it about our hideXxx(), disableXxx() and validateXxx() supporting methods. We also have a ticket raised [1] for Isis to support the JSR-349 annotations. So if you stick to using those - and we were to implement that ticket - then porting to a Hibernate impl (which is gonna intrinsically understand those annotations) would ease things substantially. Hope that's of use Dan > With kind regards > > Hugo > > > [1] https://issues.apache.org/jira/browse/ISIS-491 > > > > > On Tue, Aug 20, 2013 at 12:04 AM, Dan Haywood > <d...@haywood-associates.co.uk>wrote: > > > On 19 August 2013 20:48, Weston Myers <weston.my...@infusionsoft.com> > > wrote: > > > > > > > > We got the image working as blob but we had to copy the application > > > example from example/application/quickstart_wicket_restful_jdo. > > > > > > That's the correct thing to do. > > > > > > > > > We could not get the 1.0.3 or the 1.0.4 archetypes to build. The tests > > > failed for all of them and, after disabling the tests, they still > failed > > > to build. > > > > > > > Yeah, I should have said explicitly... I only update the archetypes when > > about to do a release (we reverse engineer the > > example/application/quickstart_wrj, as per [1]). So at any given moment > > the archetypes in trunk are almost certainly broken. > > > > > > > > > > Thank you, > > > Weston Myers > > > > > > > > You're welcome. In what capacity are you looking at Isis ... just > > prototyping, or perhaps something more? > > > > Cheers > > Dan > > > > > > [1] http://isis.apache.org/contributors/recreating-an-archetype.html > > > > > > > > > > > > >
