As far as I am concerned this is the case. I am mentored by Jeroen, so I assume he’ll teach me the conventions of proper ISIS usage ;-)
Sander On 25 Jul 2014, at 11:19, Dan Haywood <[email protected]> wrote: > Very good. > > As a suggestion (perhaps you did this already), I would wrap this > functionality into a domain service so that it can be unit tested > independently, and then inject it into other entities/services. In general > anything that "touches" the outside world should be in a domain service. > > Cheers > Dan > > > > On 25 July 2014 09:41, Sander Ginn <[email protected]> wrote: > >> Hi Dan, >> >> It is indeed an ISIS application. The symlink is needed as we have a >> central storage point for files on a server. >> Fortunately I have figured the issue out. As it turns out it wasn’t a >> permissions issue but I was passing the parameters in an incorrect way. >> >> Sander >> >> On 24 Jul 2014, at 17:38, Dan Haywood <[email protected]> >> wrote: >> >>> Hi Sander, >>> >>> Is this within an Apache Isis application? I'm trying to guess why you >>> would want to create a symlink? >>> >>> Dan >>> >>> >>> >>> On 24 July 2014 13:48, Sander Ginn <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I wish to use Runtime.exec() to create a symbolic link. The link fails >> to >>>> create and I have a feeling it has to do with insufficient rights for >> the >>>> runtime. >>>> How can I log the stack trace of possible exceptions? >>>> >>>> Kind regards >>>> Sander Ginn >> >>
