<br><br><div class="gmail_quote">On Mon, Apr 13, 2009 at 5:34 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.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;">
<br><br><div class="gmail_quote"><div class="im">On Mon, Apr 13, 2009 at 1:45 PM, Kito Mann <span dir="ltr"><<a href="mailto:kito.mann@virtua.com" target="_blank">kito.mann@virtua.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;">
<br><div class="gmail_quote"><div>On Fri, Mar 20, 2009 at 5:05 PM, Kito Mann <span dir="ltr"><<a href="mailto:kito.mann@virtua.com" target="_blank">kito.mann@virtua.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;">
That's what I was afraid of :-). What about automatically reloading configuration -- did I miss that in the spec?</blockquote></div><div><br>Anyone have an answer for this one? </div></div></blockquote></div><div><br>
I would hope that in the development stage that this is going to be available in implementations. I'm trying to think why it needs to be defined in the spec. Does it need to be?</div></div></blockquote><div><br>Not necessarily. It's just frustrating that none of the deployment features can be adequately defined in the spec (i.e. Groovy, and reloading artifacts). The JSR says:<br>
<br>Eliminate the "deployment step". All the artifacts that comprise a JSF
application can be modified while the application is running. This will
bring the responsiveness people have been used to with iterative JSP
development to the JSF developer. One design idea for this is to allow
JSF artifacts to be authored in Script.<br><br>As far as I can tell, the only parts of this we've actually covered are (1) reloading of VDL pages, and (2) allowing components to be authored in Script. So, an implementation can only support (1) and (2), and consequently still require restarts for changes to faces-config.xml or other artifacts (such as managed beans). That's not much better than JSF 1.2. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><br>
<br>-Dan</div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan" target="_blank">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>
</blockquote></div><br>