<div class="gmail_quote">On Wed, Mar 24, 2010 at 3:38 AM, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
But how do you solve that in SE? Or even in a web environment, more and more web environment are getting away from the servlet API imposed constraint.</blockquote><div><br></div><div>Sigh. And that's why this problem is more difficult than it has to be. Because we can't even handle the 80-90% case.</div>
<div><br></div><div>But you did get me thinking. Maybe the way to address the problem is to see this more as an integration concern for the SPI. So if I'm running in a servlet environment (whether it be a servlet container or Java EE), then I'm providing an implementation that standardizes on the servlet context. But we can define other mappings for other known environments, or unknown environments can supply the SPI impl.</div>
<div><br></div><div>Btw, it's not like JNDI is all that portable to SE either ;)</div><div><br></div><div>-Dan</div><div><br></div></div>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>