<div class="gmail_quote">On Sun, Sep 6, 2009 at 9:46 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Why don't we specify that only bundled resources are required to be supported, and that a container may portably support installed libraries?<br></blockquote><div><br>That's precisely what I had in mind.<br> </div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Mojarra and other implementations would be able to provide this support via a vendor specific SPI.</blockquote><div><br>Should the SPI be part of the spec or something the implementation provides? Perhaps Mojarra can introduce an SPI that we later promote in an MR?<br>
<br>-Dan<br><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://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br>