Re: Maven - No template found for component Main

2016-09-05 Thread Gino Pacitti
+1 > On 4 Sep 2016, at 23:21, Theodore Petrosky wrote: > > JMHO but I think we should keep the money in the association, and we should > promote the Kickstarter project. > > Put out an email every week to get everyone’s attention to sign up and put in > some money. I’m ready! > > > > >> On

Re: Deadlocks, editing context locking and network tasks

2016-09-05 Thread Samuel Pelletier
Mark, I discover some useful classes in the er.extensions.concurrency package inside ERExtensions. Bases on these my current pattern for background tasks is this: ERXApplication._startRequest(); ec = ERXEC.newEditingContext(parentObjectStore); try { do the job without worrying about loc

Re: Deadlocks, editing context locking and network tasks

2016-09-05 Thread Mark Wardle
Dear René, Thank you. This is really helpful. I hadn’t spotted the screencast and will check it out. Mark > On 5 Sep 2016, at 09:34, René Bock wrote: > > Hi Mark > >> Am 03.09.2016 um 22:36 schrieb Mark Wardle : >> >> Dear all, >> >> I’m debugging a deadlock and realise that I probably nee

Re: Maven - No template found for component Main

2016-09-05 Thread Mark Wardle
Hugi, Thank you. It works! Mark > On 4 Sep 2016, at 23:16, Hugi Thordarson wrote: > > You probably need to open the Eclipse .project-file in your project and add: > > org.maven.ide.eclipse.maven2Nature > > …as a project nature (inside the “natures"-tag). > > WebObjects uses this identifier t

Re: Maven - No template found for component Main

2016-09-05 Thread Hugi Thordarson
Oh come on, Theodore—you just cost me a thousand bucks! :) But seriously, I agree the community should hold on to its funds for the conferences. I’m not sure Maven by itself is a large enough subject to warrant a Kickstarter, but I’ve been wanting to do a more complete “Modern WebObjects” proje

Re: Deadlocks, editing context locking and network tasks

2016-09-05 Thread René Bock
Hi Mark > Am 03.09.2016 um 22:36 schrieb Mark Wardle : > > Dear all, > > I’m debugging a deadlock and realise that I probably need to re-design some > of my code logic. > > Am I right in saying… > > 1. For a background thread, it is appropriate to create a new editing context > (ERXEC.newEdi