Re: choices / autocomplete with option to create new item

Hi All, Imho: Putting the "don't do CRUD" principle spin on this: Isn't it just a matter of allowing a "Concert" component (I call it component since it will have several objects that are associated with the primary moment-interval) instance to be "built up" until it can be "published"? All

Re: WebServer --port option not working

Just for the records: Joerg was so kind to point me to his way of running Jetty in Eclipse. >From the project's context menu, select Run As > Maven Build then enter 'jetty:run' for the input 'Goals', configure any additional properties (e.g. -Disis.appManifest) by using the 'Add' button.

Re: object level ownership / tenancy

Hi Dan, imho I don't think it is that cut and dried (but willing to learn otherwise). When a system user is also a <> with <> to <> it is appropriate to ask the domain whether the system user identified as a <> in the system is allowed to play the <> wrt the <>. The domain may have to do

Re: choices / autocomplete with option to create new item

Hi, Dan. In our case it’s a top level annotation with any params. But probably on Isis it should be part of the @Action annotation. Important here is that, despite seeming that factory methods should have always “non-idempotent” semantics, if before creating the new instance, you verify it

AW: WebServer --port option not working

Hi Kambiz, I'm using mvn -Djetty.port=9090 jetty:run and it works for me with 1.13.0 -j -Ursprüngliche Nachricht- Von: Kambiz Darabi [mailto:dar...@m-creations.com] Gesendet: Mittwoch, 28. September 2016 23:02 An: Isis Users Betreff: WebServer --port option not working Hi,

Re: choices / autocomplete with option to create new item

could you sketch a quick code example, eg with Martin's original Concert example... guess I'm being dumb, but I don't quite get it. thx Dan On 29 September 2016 at 09:20, Óscar Bou - GOVERTIS wrote: > Hi, Dan. > > In our case it’s a top level annotation with any params. > >

Re: WebServer --port option not working

Nevertheless, it sounds like I broke something in 1.13.0 ... org.apache.isis.WebServer is our own wrapper around jetty. I'll look into it. Meantime, as Jorg says, mvn jetty:run is a decent enough workaround. Thx Dan 2016-09-29 9:53 GMT+01:00 Rade, Joerg / Kuehne + Nagel / Ham GI-DP <

Re: WebServer --port option not working

Dan, thanks for looking into it. In the mean time I put a band aid on it for my colleagues whose daily dev workflow involves debugging the code by running WebServer in eclipse: https://github.com/m-creations/isis/commit/62e81169a3d014f2ae3c4220dbe504c3b44ddd6e Looks like new

Calling repository methods from a Wicket page

Hi, in one of our applications, we have a Wicket page which is mounted onto a context path and streams a video resource to the calling client, based on some page parameters. Up to now, this page uses http calls to the RO viewer to perform the domain-related validations, lookups etc. I would