Re: really weird - evaluating a comment

[Steve Widmar]

Dave:

Browsers will ignore comments of that style - jsp processors wont.
(its possible that you - or someone else -  may want HTML comment content that is the 
result of a processed custom action, er, tag)

Using jsp comment syntax will give you what you need - 
<%--  --%>

Steve
>>> [EMAIL PROTECTED] 08/12/03 07:27PM >>>
Hi;

The following line in my jsp is throwing an exception:

 

Correct me if I'm wrong - but since it's a comment - shouldn't it be left alone?

thanks - dave

RE: nested references and javascript

[Steve Widmar]

D'oh!

(as in 'Doh yeah')

no wonder it wasn't in the archives; well, it is now (or should be soon).

Thanks, James.

>>> [EMAIL PROTECTED] 10/10/02 09:27PM >>>
You can use an alternate sytax.

Example:
Number(document.forms["myForm"].elements["foo.bar"].value);
  or
Number(document.forms[0].elements["foo.bar"].value);



James Mitchell
Software Engineer/Struts Evangelist
http://www.open-tools.org 

> -Original Message-
> From: Steve Widmar [mailto:[EMAIL PROTECTED]] 
> Sent: Friday, October 11, 2002 12:22 AM
> To: [EMAIL PROTECTED] 
> Subject: nested references and javascript
> 
> 
> I've got a question about this subject that's probably obvious to 
> experienced users.
> 
> I've searched the mail archives on the subject and haven't found 
> any joy, so here's my puzzler:
> 
> I'm starting to use nested references in 1.0.2...
> for example: 
> 
> The framework is working fine, as I've got a getFoo() on the 
> named bean with a getBar() and it shows in the html form in the browser.
> 
> When i try to update existing javascript to match the new 
> nest-compliant name, it dont work :-(
> for example:  Number(document.forms[0].foo.bar.value);
> generates the following error message:  document.forms[0].foo has 
> no properties.
> 
> So the $.64 question:  ->  am i doing it wrong, or is it undoable?
> 
> I guess it's more of a 'javascript-users' issue, but i figgered 
> someone here has hit this already
> 
> (Why 1.0.2? The app's been in production for a while on 1.0.2... 
> (BTW, thanks struts-dev)).
> 
> Thanks, 
> Steve
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

nested references and javascript

[Steve Widmar]

I've got a question about this subject that's probably obvious to experienced users.

I've searched the mail archives on the subject and haven't found any joy, so here's my 
puzzler:

I'm starting to use nested references in 1.0.2...
for example: 

The framework is working fine, as I've got a getFoo() on the named bean with a 
getBar() and it shows in the html form in the browser.

When i try to update existing javascript to match the new nest-compliant name, it dont 
work :-(
for example:  Number(document.forms[0].foo.bar.value);
generates the following error message:  document.forms[0].foo has no properties.

So the $.64 question:  ->  am i doing it wrong, or is it undoable?

I guess it's more of a 'javascript-users' issue, but i figgered someone here has hit 
this already

(Why 1.0.2? The app's been in production for a while on 1.0.2... (BTW, thanks 
struts-dev)).

Thanks, 
Steve




--
To unsubscribe, e-mail:   
For additional commands, e-mail: