<div dir="ltr">Hi Tobias,<div><br></div><div><div>> This is a critical bug in SJC which I will work on resolving today if</div><div>> possible.</div></div><div><br></div><div>Latest released versions of the SciJava software stack now have this bug fixed.</div>
<div><br></div><div>You can get the needed component versions by using pom-imagej 2.49 as parent.</div><div><br></div><div>Regards,</div><div>Curtis</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 22, 2014 at 11:51 AM, Curtis Rueden <span dir="ltr"><<a href="mailto:ctrueden@wisc.edu" target="_blank">ctrueden@wisc.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Tobias,<div><br></div><div><div class=""><div>> I imagine that in many cases it would be helpful to somehow produce an</div>
<div>> explicit list of transitive (runtime) dependencies at compile time.</div><div>> But this is probably not possible because these dependencies are</div>
<div>> specified as interfaces and there is no way of knowing beforehand the</div><div>> dependencies of the implementing class that will be used at runtime.</div><div><br></div></div><div>Actually, you can do it either way. If you ask for an interface, it adds all concrete service plugins that implement that interface. If you ask for a concrete class, you get that concrete class only. But it is true that whenever you ask for an interface, you will also transitively bring in all dependencies of all implementing classes.</div>
<div class="">
<div><br></div><div>> In the present case it is even worse, because, if I understand</div><div>> correctly, simply put the problem was not a missing dependency is</div><div>> missing but additional stuff being present?</div>
</div></div><div><br></div><div>Right. There was an additional AppEventService that had a dependency on the most problematic and limited ImageJ service: the DefaultLegacyService.</div><div><br></div><div>Another way I plan to (eventually!) mitigate that is to make the DefaultLegacyService less crabby: I want it to be possible to have more than one, that simply ends up referencing the same instance of ImageJ 1.x. This shouldn't be too hard to do but haven't had to time explore that yet. This would "paper over" the problem you had in that you wouldn't have received an exception, but still would have brought in a whole bunch of unneeded service dependencies for the purposes of ImgOpener.</div>
<div><br></div><div>The real fix here is to retool the AppEvent API as described here:</div><div><a href="https://github.com/scijava/scijava-common/commit/852f05cf1dbfb3ce99ccd416fee64573a0692764" target="_blank">https://github.com/scijava/scijava-common/commit/852f05cf1dbfb3ce99ccd416fee64573a0692764</a><br>
</div><div><br></div><div>This is a critical bug in SJC which I will work on resolving today if possible.</div><div><br>Regards,</div><div>Curtis</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Fri, Aug 22, 2014 at 11:45 AM, Tobias Pietzsch <span dir="ltr"><<a href="mailto:pietzsch@mpi-cbg.de" target="_blank">pietzsch@mpi-cbg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Hi Curtis,<div><br><div><div><div><div>On 22 Aug 2014, at 16:51, Curtis Rueden <<a href="mailto:ctrueden@wisc.edu" target="_blank">ctrueden@wisc.edu</a>> wrote:</div><br><blockquote type="cite">
<div dir="ltr">Hi Tobias,<div><br></div><div><div>> Except now all dependencies are not there anymore because now there</div><div>> are non-obvious (to me) implicit runtime dependencies.</div><div>></div><div>
> I find this unfortunate.</div></div><div><br></div><div>I agree that this is a two-edged sword. We have more types of plugins now, which can alter the runtime behavior in more ways, so of course it becomes possible for ill-behaved plugins to bring down the system.</div>
<div><br></div><div>This is already true in ImageJ 1.x though, because it is extensible at runtime: any plugin class could have a static initializer block that hoses up the JVM however it can imagine. It is just easier to do now.</div>
<div><br></div><div>IMO, it would not be worth it to eliminate these powerful extension points just because of this possibility. The flexibility gained outweighs any disadvantages.</div></div></blockquote><div><br></div>
</div><div>I agree that it is very powerful and I’m not proposing to eliminate it.</div><div><br></div><div>I’m happy that my problem is just a quirk and that I will be able to continue just calling new ImgOpener(), in blissfull ignorance of what is going on behind the scenes.</div>
<div><br><blockquote type="cite"><div dir="ltr"><div>We have already taken great pains to mitigate the issue with services in the context: when you create a new ImgOpener without specifying an SJC context, it uses _only_ relevant service types: things that implement the SciJavaService and SCIFIOService interfaces. In other words: _not_ ImageJServices or other service types. The reason LegacyService is being (erroneously!) pulled in here is due to a bug in the design of the SJC AppEventService, as I said. I introduced a "LegacyAppEventService" which is a SciJavaService but depends on the ImageJ LegacyService. Hence, any Context that asks for SciJavaServices now pulls in a DefaultLegacyService whenever the LegacyAppEventService is on the classpath. The fix is to stop doing that.</div>
<div><br></div><div>Anyway, if it still bothers you that any ol' developer can add something to the classpath which hoses up your programs, then you can stop it: create a more carefully controlled SJC Context and pass that to the ImgOpener. Alternately, we could change ImgOpener to be even more conservative in which services it uses. Of course, there are downsides there: any additional file format plugins, codec plugins, etc., might not be work properly if they do not have access to the services they need.</div>
<div><br></div><div>I am very open to ideas for mitigating the extensibility issues here.</div></div></blockquote><div><br></div></div><div>I currently have only limited knowledge of the workings of scijava-common so I admit that I have no ideas here.</div>
<div><br></div><div>I imagine that in many cases it would be helpful to somehow produce an explicit list of transitive (runtime) dependencies at compile time. But this is probably not possible because these dependencies are specified as interfaces and there is no way of knowing beforehand the dependencies of the implementing class that will be used at runtime.</div>
<div>In the present case it is even worse, because, if I understand correctly, simply put the problem was not a missing dependency is missing but additional stuff being present?</div><div><br></div><div>best regards,</div>
<div>Tobias</div><div><div><br><blockquote type="cite"><div dir="ltr"><div><br></div><div>Regards,</div><div>Curtis</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 22, 2014 at 9:35 AM, Tobias Pietzsch <span dir="ltr"><<a href="mailto:pietzsch@mpi-cbg.de" target="_blank">pietzsch@mpi-cbg.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Johannes,<div><div><br></div><div>On 22 Aug 2014, at 09:04, Johannes Schindelin <<a href="mailto:Johannes.Schindelin@gmx.de" target="_blank">Johannes.Schindelin@gmx.de</a>> wrote:</div>
</div><div><div><br><blockquote type="cite"><div>Hi Tobias,<br><br>On Fri, 22 Aug 2014, Tobias Pietzsch wrote:<br><br><blockquote type="cite">Currently<br>new io.scif.img.ImgOpener();<br>fails with<br>java.lang.IllegalArgumentException: Invalid service: net.imagej.legacy.LegacyAppEventService<br>
</blockquote><br>Yep, the explanation is very easy:<br><br></div><blockquote type="cite"><div>[...]<br>Caused by: java.lang.UnsupportedOperationException: Cannot instantiate more than one DefaultLegacyService<br>
</div>[…]<br></blockquote></blockquote><div><br></div><div>I missed that...</div><div><br><blockquote type="cite"><br>There is already a context, including a legacy service. Unfortunately, the<br>best way to get at this context from an *ImageJ 1.x plugin* that I could<br>
come up with is:<br><br><span style="white-space:pre-wrap"> </span>import org.scijava.Context;<br><br><span style="white-space:pre-wrap"> </span>...<br><br><span style="white-space:pre-wrap"> </span>final Context context = (Context)<br>
<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>IJ.runPlugIn(Context.class.getName(), "");<br><span style="white-space:pre-wrap"> </span>final ImgOpener opener = new ImgOpener(context);<br>
<br>(There is no way to make that more convenient without letting SCIFIO<br>depend on ImageJ 1.x, which is of course a big no-no).<br></blockquote><div><br></div></div><div><div>The problem with this solution you suggested is that it does not work in Eclipse:</div>
<div><div style="margin:0px;font-size:11px;font-family:Monaco;color:rgb(255,38,0)">Exception in thread "main" <span style="text-decoration:underline;color:#0433ff">java.lang.IllegalArgumentException</span>: Invalid service: net.imagej.legacy.DefaultLegacyService</div>
</div><div><br></div></div><div>As much as I understand the need for the runtime service discovery used by the scijava stack, there are certainly downsides to it.</div><div>My feeling is that in some ways it undermines the advantages that we have gained by switching to maven.</div>
<div>I can import a maven project into my Eclipse, and all the dependencies are there, explicitly and automatically, which is really very convenient.</div><div>Except now all dependencies are not there anymore because now there are non-obvious (to me) implicit runtime dependencies.</div>
<div>I find this unfortunate.</div><div><br></div><div>That being said, I found a solution that works for now, both in Eclipse and in Fiji</div><div> final ImgOpener opener = new ImgOpener( new Context( SCIFIOService.class, AppService.class, StatusService.class ) );</div>
<div><div>This avoids requiring the net.imagej.legacy.LegacyAppEventService.</div><div>It seems to work, but I’m not sure: Are there any downsides to that?</div><div><br></div><div>best regards,</div><div>Tobias</div><div>
<br></div></div><div><blockquote type="cite"><br>Of course, you could also turn your plugin into an ImageJ2 plugin -- which<br>is handled properly in Fiji thanks to Fiji Just Being ImageJ2 -- and then<br>it would become as easy as:<br>
<br><span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>@Parameter<br><span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>private IOService io;<br><br><span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>...<br>
<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>// use the IOService (which lets SCIFIO handle<br><span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>// things) to open your dataset<br>
<br>Ciao,<br>Johannes<br><br>-- <br>-- <br>Please avoid top-posting, and please make sure to reply-to-all!<br><br>Mailing list web interface: <a href="http://groups.google.com/group/fiji-devel" target="_blank">http://groups.google.com/group/fiji-devel</a><br>
<br>--- <br>You received this message because you are subscribed to the Google Groups "Fiji-devel" group.<br>To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:fiji-devel+unsubscribe@googlegroups.com" target="_blank">fiji-devel+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/optout</a>.<br></blockquote></div></div><br></div></div></blockquote></div><br></div>
</blockquote></div></div></div><br></div></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>