<div dir="ltr">Maybe I should have the callJavaCompileCommand method call the flex compiler<div>in a new thread?? </div><div><br></div><div><br><br><div class="gmail_quote">On Thu, Sep 4, 2008 at 8:43 PM, Henry Minsky <span dir="ltr"><<a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com</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"><div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div><br></div><div><div>2)</div>
<div>+ exitval = flex2.compiler.util.ThreadLocalToolkit.errorCount();</div><div>Couldn't find any doc for ThreadLocalToolkit. Are the errors additive,</div><div>or will they be reset to 0 on each call into the compiler? (i.e. I'm</div>
<div>worried about an error being 'sticky' to the next compile - I guess</div><div>it would only result in a stray FAIL println to the error console).</div><div></div></div></div></blockquote><div><br></div></div>
<div>The ThreadLocalToolkit class has a flex Logger object, which is stored within a ThreadLocal</div>
<div>object, which is a Java thing that creates local vars which are unique to a thread. The Logger object</div><div>holds the error count. So as long as each compile is done in a new thread, the error count</div><div>will get reset. Now, the question is whether each compile actually does happen in a new thread. I </div>
<div>bet Tomcat has some kind of a thread pool, so I wonder if this is going to cause confusion</div><div>at some point. </div><div><br></div><div><br></div><div><br></div><div> </div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Henry Minsky<br>Software Architect<br><a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com</a><br><br><br>
</div></div>