<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 9/14/16 1:18 PM, Brent Putman wrote:<br>
</div>
<blockquote
cite="mid:12d00d31-b183-0b90-c8ce-f58c2f5c965b@georgetown.edu"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 9/14/16 1:11 PM, Brent Putman
wrote:<br>
</div>
<blockquote
cite="mid:61661301-0e99-322b-f11d-37a05042d8f0@georgetown.edu"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p><br>
</p>
<br>
Ah. That was the other thing I was meaning to ask and/or look
into re: the c: namespace usage of param names. When I first saw
that, I was mildly surprised that that even worked. I always
kind of thought that ctor and method parameter *names* weren't
included in the byte code by default. You only got them with
debug turned on. That may not be correct at all. However, I
wonder if the c:name ctor stuff still works if debug is turned
off. If not, then that's another reason why that seems unwise
to me personally.<br>
</blockquote>
<br>
Some quick googling from multiple sources seems to confirm the
above. You only get ctor param names with debug=true and so the
Spring c:name stuff only works with debug turned on.<br>
</blockquote>
<br>
<br>
Off-topic, but this is also apparently true for other Spring things,
like MVC @RequestParam. The annotation name/value for the request
param is only optional (i.e. taken from the method param name) if
compiled with debug. In hindsight this is completely obvious, but I
never thought about it before. <br>
<br>
OTOH, I use that all the time in MVC in my local projects, and I'm
pretty sure do *not* have debug explicitly set anwhere. So, hmmm.
Maybe Maven is defaulting something somewhere.<br>
<br>
</body>
</html>