RE: html-el oddities

2005-02-25 Thread Trevor Hill
Finally solved my own problem here:

My application server (JRun 4) does not appear to be compliant with the Servlet 
2.3 spec.  It is mostly compliant, but seems to be broken in a few subtle ways, 
one of which manifests itself in struts-el dying a horrible death if you try to 
use it on JRun 4.

I didn't write this macromedia forums post, but it accurately describes the 
problem and the workaround, for those brave enough to use JRun as their J2EE 
server.

http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=68threadid=958539enterthread=y

Thanks to all who assisted,

--Trevor

-Original Message-
From: Trevor Hill 
Sent: February 23, 2005 4:45 PM
To: Struts Users Mailing List
Subject: RE: html-el oddities


Forgive me for coming off as incredibly dense here:

I'm not sure what a BeanInfo class is or how it fits into the whole 
struts-el-action-form arrangement of things, so I'm not sure where to go from 
here.  I have verified that my taglibs are correct and in place, that the 
struts and struts-el JARs are in the WEB-INF/lib folder, and that the taglib 
references at the top of my JSP pages map to the correct URIs in the web.xml 
file.

Do you mean that I should run a debugger through my JSP page? I don't think I 
have the ability to do that in Eclipse.

Thanks and apologies for cluelessness,

--Trevor


-Original Message-
From: Karr, David [mailto:[EMAIL PROTECTED]
Sent: February 16, 2005 3:16 PM
To: Struts Users Mailing List
Subject: RE: html-el oddities


I suggest you set this up so you can step through this in your debugger.

My theory is that somehow the association with the BeanInfo class is not
happening.  That would cause the symptom you're seeing, but I don't know
how it could get into that state.

 -Original Message-
 From: Trevor Hill [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, February 15, 2005 8:11 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 Thanks -- your option (2) seems to be working fairly well for 
 me now.  I still have to see if struts will accept the faked 
 up input tag and stick the data into the form bean, but I 
 don't see any reason why that shouldn't work.
 
 I wonder why (1) wouldn't work for me though -- it gave me 
 the same result as the JSTL tag did. (It iterated fine but 
 would just print out ${cur.prdNumber} rather than the actual vaule)
 
 It seems odd that the EL tag does everything except actually 
 do the EL-evaulation.
 
 --Trevor
 
 -Original Message-
 From: Woodchuck [mailto:[EMAIL PROTECTED]
 Sent: February 15, 2005 10:31 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 i can think of 2 things you can try:
 
 
 1) use logic:iterate instead of c:forEach
 
 i have found that jstl-scoped objects do not always work well 
 with struts tags
 
 
 2) simply don't use the html-el:text tag
 
 you can achieve the same result with:
 
 input type=text name=quantity(c:out 
 value='${cur.PrdNumber}'/) maxlength=5 size=3 value=
 
 
 hth,
 woodchuck
 
 
 --- Trevor Hill [EMAIL PROTECTED] wrote:
 
  To try and attack this question from another angle, is there any 
  reason that this wouldn't work (or would work differently) in
  Struts(-el) 1.1 as opposed to 1.2.x?  I'm limited to using 
 1.1 only, 
  but cannot find any old 1.1 documentation to work from.
  
  Thanks,
  --Trevor
  
  -Original Message-
  From: Trevor Hill
  Sent: February 14, 2005 8:33 AM
  To: Struts Users Mailing List
  Subject: RE: html-el oddities
  
  
  As I said in my original question, I had tried 
 'cur.prdNumber' and had 
  the same result, and so had tried shoving the value of 
 cur.prdNumber 
  into a page-scoped variable named 'curPrdNumber', with the 
 exact same 
  less-than-spectacular results.
  
  So I guess I'm still stuck, but thanks.
  
  -Original Message-
  From: Jason Lea [mailto:[EMAIL PROTECTED]
  Sent: February 11, 2005 4:54 PM
  To: Struts Users Mailing List
  Subject: Re: html-el oddities
  
  
  I think you are missing a dot :)  cur.PrdNumber not curPrdNumber
  
  Try:
  
  input type=text name=quantity(${cur.PrdNumber}) maxlength=5
  size=3 value=/td
  
  
  
  
  
  
  Trevor Hill wrote:
  
  I'm having an interesting issue.  I have a form in which the only
  input is a bunch of text boxes which correspond to quantities of 
  products.  The associated form thus consists of just a HashMap.  My 
  JSP page is as follows:
  ... header stuff ...
  
  tr
 thProduct/th
 thProduct Number/th
 thPrice/th
 thQuantity to add/th
  /tr
  
  c:forEach items=${priceList} var=cur
  c:set scope=page var=curPrdNumber value=${cur.prdNumber}/
  
  tr
 tdc:out value=${cur.itemName}//td
 tdc:out value=${cur.prdNumber}//td
 tdfmt:formatNumber type=currency
  currencyCode=${cur.currencyCode} value=${cur.price}//td
  
 td style=text-align:righthtml-el:text
  property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
  /tr
  
  ... submit button, close form

RE: html-el oddities

2005-02-23 Thread Trevor Hill
Forgive me for coming off as incredibly dense here:

I'm not sure what a BeanInfo class is or how it fits into the whole 
struts-el-action-form arrangement of things, so I'm not sure where to go from 
here.  I have verified that my taglibs are correct and in place, that the 
struts and struts-el JARs are in the WEB-INF/lib folder, and that the taglib 
references at the top of my JSP pages map to the correct URIs in the web.xml 
file.

Do you mean that I should run a debugger through my JSP page? I don't think I 
have the ability to do that in Eclipse.

Thanks and apologies for cluelessness,

--Trevor


-Original Message-
From: Karr, David [mailto:[EMAIL PROTECTED]
Sent: February 16, 2005 3:16 PM
To: Struts Users Mailing List
Subject: RE: html-el oddities


I suggest you set this up so you can step through this in your debugger.

My theory is that somehow the association with the BeanInfo class is not
happening.  That would cause the symptom you're seeing, but I don't know
how it could get into that state.

 -Original Message-
 From: Trevor Hill [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, February 15, 2005 8:11 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 Thanks -- your option (2) seems to be working fairly well for 
 me now.  I still have to see if struts will accept the faked 
 up input tag and stick the data into the form bean, but I 
 don't see any reason why that shouldn't work.
 
 I wonder why (1) wouldn't work for me though -- it gave me 
 the same result as the JSTL tag did. (It iterated fine but 
 would just print out ${cur.prdNumber} rather than the actual vaule)
 
 It seems odd that the EL tag does everything except actually 
 do the EL-evaulation.
 
 --Trevor
 
 -Original Message-
 From: Woodchuck [mailto:[EMAIL PROTECTED]
 Sent: February 15, 2005 10:31 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 i can think of 2 things you can try:
 
 
 1) use logic:iterate instead of c:forEach
 
 i have found that jstl-scoped objects do not always work well 
 with struts tags
 
 
 2) simply don't use the html-el:text tag
 
 you can achieve the same result with:
 
 input type=text name=quantity(c:out 
 value='${cur.PrdNumber}'/) maxlength=5 size=3 value=
 
 
 hth,
 woodchuck
 
 
 --- Trevor Hill [EMAIL PROTECTED] wrote:
 
  To try and attack this question from another angle, is there any 
  reason that this wouldn't work (or would work differently) in
  Struts(-el) 1.1 as opposed to 1.2.x?  I'm limited to using 
 1.1 only, 
  but cannot find any old 1.1 documentation to work from.
  
  Thanks,
  --Trevor
  
  -Original Message-
  From: Trevor Hill
  Sent: February 14, 2005 8:33 AM
  To: Struts Users Mailing List
  Subject: RE: html-el oddities
  
  
  As I said in my original question, I had tried 
 'cur.prdNumber' and had 
  the same result, and so had tried shoving the value of 
 cur.prdNumber 
  into a page-scoped variable named 'curPrdNumber', with the 
 exact same 
  less-than-spectacular results.
  
  So I guess I'm still stuck, but thanks.
  
  -Original Message-
  From: Jason Lea [mailto:[EMAIL PROTECTED]
  Sent: February 11, 2005 4:54 PM
  To: Struts Users Mailing List
  Subject: Re: html-el oddities
  
  
  I think you are missing a dot :)  cur.PrdNumber not curPrdNumber
  
  Try:
  
  input type=text name=quantity(${cur.PrdNumber}) maxlength=5
  size=3 value=/td
  
  
  
  
  
  
  Trevor Hill wrote:
  
  I'm having an interesting issue.  I have a form in which the only
  input is a bunch of text boxes which correspond to quantities of 
  products.  The associated form thus consists of just a HashMap.  My 
  JSP page is as follows:
  ... header stuff ...
  
  tr
 thProduct/th
 thProduct Number/th
 thPrice/th
 thQuantity to add/th
  /tr
  
  c:forEach items=${priceList} var=cur
  c:set scope=page var=curPrdNumber value=${cur.prdNumber}/
  
  tr
 tdc:out value=${cur.itemName}//td
 tdc:out value=${cur.prdNumber}//td
 tdfmt:formatNumber type=currency
  currencyCode=${cur.currencyCode} value=${cur.price}//td
  
 td style=text-align:righthtml-el:text
  property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
  /tr
  
  ... submit button, close form, etc
  
  
  
  However, the output of the last TD is:
  
  input type=text name=quantity(${curPrdNumber}) maxlength=5
  size=3 value=/td
  
  which is correct except for that whole not interpreting the EL
  expression bit.
  
  I've tried using a page-scoped temporary variable (as above), I've
  tried directly referencing ${cur.prdNumber} in the 
 html-el:text tag, 
  I've checked all my TLDs and the struts-el.jar files to 
 ensure they're 
  in the correct place and checked the web.xml file to make 
 sure all the 
  TLDs are mentioned.  There are no error messages in my 
 application's 
  log or my application server's log that would suggest some class or 
  configuration file being out of whack.
  
  All my other taglibs (normal

RE: html-el oddities

2005-02-16 Thread Karr, David
I suggest you set this up so you can step through this in your debugger.

My theory is that somehow the association with the BeanInfo class is not
happening.  That would cause the symptom you're seeing, but I don't know
how it could get into that state.

 -Original Message-
 From: Trevor Hill [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, February 15, 2005 8:11 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 Thanks -- your option (2) seems to be working fairly well for 
 me now.  I still have to see if struts will accept the faked 
 up input tag and stick the data into the form bean, but I 
 don't see any reason why that shouldn't work.
 
 I wonder why (1) wouldn't work for me though -- it gave me 
 the same result as the JSTL tag did. (It iterated fine but 
 would just print out ${cur.prdNumber} rather than the actual vaule)
 
 It seems odd that the EL tag does everything except actually 
 do the EL-evaulation.
 
 --Trevor
 
 -Original Message-
 From: Woodchuck [mailto:[EMAIL PROTECTED]
 Sent: February 15, 2005 10:31 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 i can think of 2 things you can try:
 
 
 1) use logic:iterate instead of c:forEach
 
 i have found that jstl-scoped objects do not always work well 
 with struts tags
 
 
 2) simply don't use the html-el:text tag
 
 you can achieve the same result with:
 
 input type=text name=quantity(c:out 
 value='${cur.PrdNumber}'/) maxlength=5 size=3 value=
 
 
 hth,
 woodchuck
 
 
 --- Trevor Hill [EMAIL PROTECTED] wrote:
 
  To try and attack this question from another angle, is there any 
  reason that this wouldn't work (or would work differently) in
  Struts(-el) 1.1 as opposed to 1.2.x?  I'm limited to using 
 1.1 only, 
  but cannot find any old 1.1 documentation to work from.
  
  Thanks,
  --Trevor
  
  -Original Message-
  From: Trevor Hill
  Sent: February 14, 2005 8:33 AM
  To: Struts Users Mailing List
  Subject: RE: html-el oddities
  
  
  As I said in my original question, I had tried 
 'cur.prdNumber' and had 
  the same result, and so had tried shoving the value of 
 cur.prdNumber 
  into a page-scoped variable named 'curPrdNumber', with the 
 exact same 
  less-than-spectacular results.
  
  So I guess I'm still stuck, but thanks.
  
  -Original Message-
  From: Jason Lea [mailto:[EMAIL PROTECTED]
  Sent: February 11, 2005 4:54 PM
  To: Struts Users Mailing List
  Subject: Re: html-el oddities
  
  
  I think you are missing a dot :)  cur.PrdNumber not curPrdNumber
  
  Try:
  
  input type=text name=quantity(${cur.PrdNumber}) maxlength=5
  size=3 value=/td
  
  
  
  
  
  
  Trevor Hill wrote:
  
  I'm having an interesting issue.  I have a form in which the only
  input is a bunch of text boxes which correspond to quantities of 
  products.  The associated form thus consists of just a HashMap.  My 
  JSP page is as follows:
  ... header stuff ...
  
  tr
 thProduct/th
 thProduct Number/th
 thPrice/th
 thQuantity to add/th
  /tr
  
  c:forEach items=${priceList} var=cur
  c:set scope=page var=curPrdNumber value=${cur.prdNumber}/
  
  tr
 tdc:out value=${cur.itemName}//td
 tdc:out value=${cur.prdNumber}//td
 tdfmt:formatNumber type=currency
  currencyCode=${cur.currencyCode} value=${cur.price}//td
  
 td style=text-align:righthtml-el:text
  property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
  /tr
  
  ... submit button, close form, etc
  
  
  
  However, the output of the last TD is:
  
  input type=text name=quantity(${curPrdNumber}) maxlength=5
  size=3 value=/td
  
  which is correct except for that whole not interpreting the EL
  expression bit.
  
  I've tried using a page-scoped temporary variable (as above), I've
  tried directly referencing ${cur.prdNumber} in the 
 html-el:text tag, 
  I've checked all my TLDs and the struts-el.jar files to 
 ensure they're 
  in the correct place and checked the web.xml file to make 
 sure all the 
  TLDs are mentioned.  There are no error messages in my 
 application's 
  log or my application server's log that would suggest some class or 
  configuration file being out of whack.
  
  All my other taglibs (normal struts tags and jstl tags) are working
  just fine, and the html-el tag /seems/ to work fine from a Struts 
  standpoint in that it makes an input type=text just like it 
  should, but no el-evaluation.  This problem doesn't appear to be 
  specific to the mapped property quantity, as I can try 
 other html-el 
  tags that directly refer to either ${curPrdNumber} or 
  {$cur.prdNumber}, and I get the same result -- no evaluation.
  
  Am I missing something glaringly obvious?
  
  Thanks,
  --Trevor
  
  
  
 
 -
  This transmission (including any attachments) may contain
  confidential information, privileged material (including material 
  protected by the solicitor-client or other applicable

RE: html-el oddities

2005-02-15 Thread Trevor Hill
To try and attack this question from another angle, is there any reason that 
this wouldn't work (or would work differently) in Struts(-el) 1.1 as opposed to 
1.2.x?  I'm limited to using 1.1 only, but cannot find any old 1.1 
documentation to work from.

Thanks,
--Trevor 

-Original Message-
From: Trevor Hill 
Sent: February 14, 2005 8:33 AM
To: Struts Users Mailing List
Subject: RE: html-el oddities


As I said in my original question, I had tried 'cur.prdNumber' and had the same 
result, and so had tried shoving the value of cur.prdNumber into a page-scoped 
variable named 'curPrdNumber', with the exact same less-than-spectacular 
results.

So I guess I'm still stuck, but thanks.

-Original Message-
From: Jason Lea [mailto:[EMAIL PROTECTED]
Sent: February 11, 2005 4:54 PM
To: Struts Users Mailing List
Subject: Re: html-el oddities


I think you are missing a dot :)  cur.PrdNumber not curPrdNumber

Try:

input type=text name=quantity(${cur.PrdNumber}) maxlength=5 
size=3 value=/td






Trevor Hill wrote:

I'm having an interesting issue.  I have a form in which the only input is a 
bunch of text boxes which correspond to quantities of products.  The 
associated form thus consists of just a HashMap.  My JSP page is as follows:
... header stuff ...

tr
   thProduct/th
   thProduct Number/th
   thPrice/th
   thQuantity to add/th
/tr

c:forEach items=${priceList} var=cur
c:set scope=page var=curPrdNumber value=${cur.prdNumber}/

tr
   tdc:out value=${cur.itemName}//td
   tdc:out value=${cur.prdNumber}//td
   tdfmt:formatNumber type=currency 
 currencyCode=${cur.currencyCode} value=${cur.price}//td

   td style=text-align:righthtml-el:text 
 property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
/tr

... submit button, close form, etc



However, the output of the last TD is: 

input type=text name=quantity(${curPrdNumber}) maxlength=5 size=3 
value=/td

which is correct except for that whole not interpreting the EL expression 
bit.

I've tried using a page-scoped temporary variable (as above), I've tried 
directly referencing ${cur.prdNumber} in the html-el:text tag, I've checked 
all my TLDs and the struts-el.jar files to ensure they're in the correct place 
and checked the web.xml file to make sure all the TLDs are mentioned.  There 
are no error messages in my application's log or my application server's log 
that would suggest some class or configuration file being out of whack.

All my other taglibs (normal struts tags and jstl tags) are working just fine, 
and the html-el tag /seems/ to work fine from a Struts standpoint in that it 
makes an input type=text just like it should, but no el-evaluation.  This 
problem doesn't appear to be specific to the mapped property quantity, as I 
can try other html-el tags that directly refer to either ${curPrdNumber} or 
{$cur.prdNumber}, and I get the same result -- no evaluation.

Am I missing something glaringly obvious?

Thanks,
--Trevor



-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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


  


-- 
Jason Lea




-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 2005.02.10




-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.



-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone

RE: html-el oddities

2005-02-15 Thread Woodchuck
i can think of 2 things you can try:


1) use logic:iterate instead of c:forEach

i have found that jstl-scoped objects do not always work well with
struts tags


2) simply don't use the html-el:text tag

you can achieve the same result with:

input type=text name=quantity(c:out value='${cur.PrdNumber}'/)
maxlength=5 size=3 value=


hth,
woodchuck


--- Trevor Hill [EMAIL PROTECTED] wrote:

 To try and attack this question from another angle, is there any
 reason that this wouldn't work (or would work differently) in
 Struts(-el) 1.1 as opposed to 1.2.x?  I'm limited to using 1.1 only,
 but cannot find any old 1.1 documentation to work from.
 
 Thanks,
 --Trevor 
 
 -Original Message-
 From: Trevor Hill 
 Sent: February 14, 2005 8:33 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 As I said in my original question, I had tried 'cur.prdNumber' and
 had the same result, and so had tried shoving the value of
 cur.prdNumber into a page-scoped variable named 'curPrdNumber', with
 the exact same less-than-spectacular results.
 
 So I guess I'm still stuck, but thanks.
 
 -Original Message-
 From: Jason Lea [mailto:[EMAIL PROTECTED]
 Sent: February 11, 2005 4:54 PM
 To: Struts Users Mailing List
 Subject: Re: html-el oddities
 
 
 I think you are missing a dot :)  cur.PrdNumber not curPrdNumber
 
 Try:
 
 input type=text name=quantity(${cur.PrdNumber}) maxlength=5 
 size=3 value=/td
 
 
 
 
 
 
 Trevor Hill wrote:
 
 I'm having an interesting issue.  I have a form in which the only
 input is a bunch of text boxes which correspond to quantities of
 products.  The associated form thus consists of just a HashMap.  My
 JSP page is as follows:
 ... header stuff ...
 
 tr
  thProduct/th
  thProduct Number/th
  thPrice/th
  thQuantity to add/th
 /tr
 
 c:forEach items=${priceList} var=cur
 c:set scope=page var=curPrdNumber value=${cur.prdNumber}/
 
 tr
  tdc:out value=${cur.itemName}//td
  tdc:out value=${cur.prdNumber}//td
  tdfmt:formatNumber type=currency
 currencyCode=${cur.currencyCode} value=${cur.price}//td
 
  td style=text-align:righthtml-el:text
 property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
 /tr
 
 ... submit button, close form, etc
 
 
 
 However, the output of the last TD is: 
 
 input type=text name=quantity(${curPrdNumber}) maxlength=5
 size=3 value=/td
 
 which is correct except for that whole not interpreting the EL
 expression bit.
 
 I've tried using a page-scoped temporary variable (as above), I've
 tried directly referencing ${cur.prdNumber} in the html-el:text tag,
 I've checked all my TLDs and the struts-el.jar files to ensure
 they're in the correct place and checked the web.xml file to make
 sure all the TLDs are mentioned.  There are no error messages in my
 application's log or my application server's log that would suggest
 some class or configuration file being out of whack.
 
 All my other taglibs (normal struts tags and jstl tags) are working
 just fine, and the html-el tag /seems/ to work fine from a Struts
 standpoint in that it makes an input type=text just like it
 should, but no el-evaluation.  This problem doesn't appear to be
 specific to the mapped property quantity, as I can try other
 html-el tags that directly refer to either ${curPrdNumber} or
 {$cur.prdNumber}, and I get the same result -- no evaluation.
 
 Am I missing something glaringly obvious?
 
 Thanks,
 --Trevor
 
 
 

-
 This transmission (including any attachments) may contain
 confidential information, privileged material (including material
 protected by the solicitor-client or other applicable privileges), or
 constitute non-public information. Any use of this information by
 anyone other than the intended recipient is prohibited. If you have
 received this transmission in error, please immediately reply to the
 sender and delete this information from your system. Use,
 dissemination, distribution, or reproduction of this transmission by
 unintended recipients is not authorized and may be unlawful.
 

-
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
   
 
 
 -- 
 Jason Lea
 
 
 
 
 -- 
 No virus found in this outgoing message.
 Checked by AVG Anti-Virus.
 Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 2005.02.10
 
 
 
 
 -
 This transmission (including any attachments) may contain
 confidential information, privileged material (including material
 protected by the solicitor-client or other applicable privileges), or
 constitute non-public information. Any use of this information by
 anyone other than the intended recipient is prohibited. If you have
 received this transmission in error, please immediately reply to the
 sender and delete this information from your

Re: html-el oddities

2005-02-15 Thread Wendy Smoak
From: Trevor Hill [EMAIL PROTECTED]
 I'm limited to using 1.1 only, but cannot find any old 1.1 documentation
to work from.

There should be a 'struts-documentation.war' contained in the 1.1
distribution.  That will have docs that match what's in 1.1, as opposed to
the more current ones on the website.

-- 
Wendy Smoak


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



RE: html-el oddities

2005-02-15 Thread Trevor Hill
Thanks -- your option (2) seems to be working fairly well for me now.  I still 
have to see if struts will accept the faked up input tag and stick the data 
into the form bean, but I don't see any reason why that shouldn't work.

I wonder why (1) wouldn't work for me though -- it gave me the same result as 
the JSTL tag did. (It iterated fine but would just print out ${cur.prdNumber} 
rather than the actual vaule)

It seems odd that the EL tag does everything except actually do the 
EL-evaulation.

--Trevor

-Original Message-
From: Woodchuck [mailto:[EMAIL PROTECTED]
Sent: February 15, 2005 10:31 AM
To: Struts Users Mailing List
Subject: RE: html-el oddities


i can think of 2 things you can try:


1) use logic:iterate instead of c:forEach

i have found that jstl-scoped objects do not always work well with
struts tags


2) simply don't use the html-el:text tag

you can achieve the same result with:

input type=text name=quantity(c:out value='${cur.PrdNumber}'/)
maxlength=5 size=3 value=


hth,
woodchuck


--- Trevor Hill [EMAIL PROTECTED] wrote:

 To try and attack this question from another angle, is there any
 reason that this wouldn't work (or would work differently) in
 Struts(-el) 1.1 as opposed to 1.2.x?  I'm limited to using 1.1 only,
 but cannot find any old 1.1 documentation to work from.
 
 Thanks,
 --Trevor 
 
 -Original Message-
 From: Trevor Hill 
 Sent: February 14, 2005 8:33 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 As I said in my original question, I had tried 'cur.prdNumber' and
 had the same result, and so had tried shoving the value of
 cur.prdNumber into a page-scoped variable named 'curPrdNumber', with
 the exact same less-than-spectacular results.
 
 So I guess I'm still stuck, but thanks.
 
 -Original Message-
 From: Jason Lea [mailto:[EMAIL PROTECTED]
 Sent: February 11, 2005 4:54 PM
 To: Struts Users Mailing List
 Subject: Re: html-el oddities
 
 
 I think you are missing a dot :)  cur.PrdNumber not curPrdNumber
 
 Try:
 
 input type=text name=quantity(${cur.PrdNumber}) maxlength=5 
 size=3 value=/td
 
 
 
 
 
 
 Trevor Hill wrote:
 
 I'm having an interesting issue.  I have a form in which the only
 input is a bunch of text boxes which correspond to quantities of
 products.  The associated form thus consists of just a HashMap.  My
 JSP page is as follows:
 ... header stuff ...
 
 tr
  thProduct/th
  thProduct Number/th
  thPrice/th
  thQuantity to add/th
 /tr
 
 c:forEach items=${priceList} var=cur
 c:set scope=page var=curPrdNumber value=${cur.prdNumber}/
 
 tr
  tdc:out value=${cur.itemName}//td
  tdc:out value=${cur.prdNumber}//td
  tdfmt:formatNumber type=currency
 currencyCode=${cur.currencyCode} value=${cur.price}//td
 
  td style=text-align:righthtml-el:text
 property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
 /tr
 
 ... submit button, close form, etc
 
 
 
 However, the output of the last TD is: 
 
 input type=text name=quantity(${curPrdNumber}) maxlength=5
 size=3 value=/td
 
 which is correct except for that whole not interpreting the EL
 expression bit.
 
 I've tried using a page-scoped temporary variable (as above), I've
 tried directly referencing ${cur.prdNumber} in the html-el:text tag,
 I've checked all my TLDs and the struts-el.jar files to ensure
 they're in the correct place and checked the web.xml file to make
 sure all the TLDs are mentioned.  There are no error messages in my
 application's log or my application server's log that would suggest
 some class or configuration file being out of whack.
 
 All my other taglibs (normal struts tags and jstl tags) are working
 just fine, and the html-el tag /seems/ to work fine from a Struts
 standpoint in that it makes an input type=text just like it
 should, but no el-evaluation.  This problem doesn't appear to be
 specific to the mapped property quantity, as I can try other
 html-el tags that directly refer to either ${curPrdNumber} or
 {$cur.prdNumber}, and I get the same result -- no evaluation.
 
 Am I missing something glaringly obvious?
 
 Thanks,
 --Trevor
 
 
 

-
 This transmission (including any attachments) may contain
 confidential information, privileged material (including material
 protected by the solicitor-client or other applicable privileges), or
 constitute non-public information. Any use of this information by
 anyone other than the intended recipient is prohibited. If you have
 received this transmission in error, please immediately reply to the
 sender and delete this information from your system. Use,
 dissemination, distribution, or reproduction of this transmission by
 unintended recipients is not authorized and may be unlawful.
 

-
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
   
 
 
 -- 
 Jason Lea

RE: html-el oddities

2005-02-15 Thread Woodchuck
that is odd.

make sure your tag definition is pointing to the EL tld, you may have
updated the tag handle but not the tld reference?


--- Trevor Hill [EMAIL PROTECTED] wrote:

 Thanks -- your option (2) seems to be working fairly well for me now.
  I still have to see if struts will accept the faked up input tag and
 stick the data into the form bean, but I don't see any reason why
 that shouldn't work.
 
 I wonder why (1) wouldn't work for me though -- it gave me the same
 result as the JSTL tag did. (It iterated fine but would just print
 out ${cur.prdNumber} rather than the actual vaule)
 
 It seems odd that the EL tag does everything except actually do the
 EL-evaulation.
 
 --Trevor
 
 -Original Message-
 From: Woodchuck [mailto:[EMAIL PROTECTED]
 Sent: February 15, 2005 10:31 AM
 To: Struts Users Mailing List
 Subject: RE: html-el oddities
 
 
 i can think of 2 things you can try:
 
 
 1) use logic:iterate instead of c:forEach
 
 i have found that jstl-scoped objects do not always work well with
 struts tags
 
 
 2) simply don't use the html-el:text tag
 
 you can achieve the same result with:
 
 input type=text name=quantity(c:out value='${cur.PrdNumber}'/)
 maxlength=5 size=3 value=
 
 
 hth,
 woodchuck
 
 
 --- Trevor Hill [EMAIL PROTECTED] wrote:
 
  To try and attack this question from another angle, is there any
  reason that this wouldn't work (or would work differently) in
  Struts(-el) 1.1 as opposed to 1.2.x?  I'm limited to using 1.1
 only,
  but cannot find any old 1.1 documentation to work from.
  
  Thanks,
  --Trevor 
  
  -Original Message-
  From: Trevor Hill 
  Sent: February 14, 2005 8:33 AM
  To: Struts Users Mailing List
  Subject: RE: html-el oddities
  
  
  As I said in my original question, I had tried 'cur.prdNumber' and
  had the same result, and so had tried shoving the value of
  cur.prdNumber into a page-scoped variable named 'curPrdNumber',
 with
  the exact same less-than-spectacular results.
  
  So I guess I'm still stuck, but thanks.
  
  -Original Message-
  From: Jason Lea [mailto:[EMAIL PROTECTED]
  Sent: February 11, 2005 4:54 PM
  To: Struts Users Mailing List
  Subject: Re: html-el oddities
  
  
  I think you are missing a dot :)  cur.PrdNumber not curPrdNumber
  
  Try:
  
  input type=text name=quantity(${cur.PrdNumber}) maxlength=5 
  size=3 value=/td
  
  
  
  
  
  
  Trevor Hill wrote:
  
  I'm having an interesting issue.  I have a form in which the only
  input is a bunch of text boxes which correspond to quantities of
  products.  The associated form thus consists of just a HashMap.  My
  JSP page is as follows:
  ... header stuff ...
  
  tr
 thProduct/th
 thProduct Number/th
 thPrice/th
 thQuantity to add/th
  /tr
  
  c:forEach items=${priceList} var=cur
  c:set scope=page var=curPrdNumber value=${cur.prdNumber}/
  
  tr
 tdc:out value=${cur.itemName}//td
 tdc:out value=${cur.prdNumber}//td
 tdfmt:formatNumber type=currency
  currencyCode=${cur.currencyCode} value=${cur.price}//td
  
 td style=text-align:righthtml-el:text
  property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
  /tr
  
  ... submit button, close form, etc
  
  
  
  However, the output of the last TD is: 
  
  input type=text name=quantity(${curPrdNumber}) maxlength=5
  size=3 value=/td
  
  which is correct except for that whole not interpreting the EL
  expression bit.
  
  I've tried using a page-scoped temporary variable (as above), I've
  tried directly referencing ${cur.prdNumber} in the html-el:text
 tag,
  I've checked all my TLDs and the struts-el.jar files to ensure
  they're in the correct place and checked the web.xml file to make
  sure all the TLDs are mentioned.  There are no error messages in my
  application's log or my application server's log that would suggest
  some class or configuration file being out of whack.
  
  All my other taglibs (normal struts tags and jstl tags) are
 working
  just fine, and the html-el tag /seems/ to work fine from a Struts
  standpoint in that it makes an input type=text just like it
  should, but no el-evaluation.  This problem doesn't appear to be
  specific to the mapped property quantity, as I can try other
  html-el tags that directly refer to either ${curPrdNumber} or
  {$cur.prdNumber}, and I get the same result -- no evaluation.
  
  Am I missing something glaringly obvious?
  
  Thanks,
  --Trevor
  
  
  
 

-
  This transmission (including any attachments) may contain
  confidential information, privileged material (including material
  protected by the solicitor-client or other applicable privileges),
 or
  constitute non-public information. Any use of this information by
  anyone other than the intended recipient is prohibited. If you have
  received this transmission in error, please immediately reply to
 the
  sender and delete this information from your system. Use

RE: html-el oddities

2005-02-14 Thread Trevor Hill
As I said in my original question, I had tried 'cur.prdNumber' and had the same 
result, and so had tried shoving the value of cur.prdNumber into a page-scoped 
variable named 'curPrdNumber', with the exact same less-than-spectacular 
results.

So I guess I'm still stuck, but thanks.

-Original Message-
From: Jason Lea [mailto:[EMAIL PROTECTED]
Sent: February 11, 2005 4:54 PM
To: Struts Users Mailing List
Subject: Re: html-el oddities


I think you are missing a dot :)  cur.PrdNumber not curPrdNumber

Try:

input type=text name=quantity(${cur.PrdNumber}) maxlength=5 
size=3 value=/td






Trevor Hill wrote:

I'm having an interesting issue.  I have a form in which the only input is a 
bunch of text boxes which correspond to quantities of products.  The 
associated form thus consists of just a HashMap.  My JSP page is as follows:
... header stuff ...

tr
   thProduct/th
   thProduct Number/th
   thPrice/th
   thQuantity to add/th
/tr

c:forEach items=${priceList} var=cur
c:set scope=page var=curPrdNumber value=${cur.prdNumber}/

tr
   tdc:out value=${cur.itemName}//td
   tdc:out value=${cur.prdNumber}//td
   tdfmt:formatNumber type=currency 
 currencyCode=${cur.currencyCode} value=${cur.price}//td

   td style=text-align:righthtml-el:text 
 property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
/tr

... submit button, close form, etc



However, the output of the last TD is: 

input type=text name=quantity(${curPrdNumber}) maxlength=5 size=3 
value=/td

which is correct except for that whole not interpreting the EL expression 
bit.

I've tried using a page-scoped temporary variable (as above), I've tried 
directly referencing ${cur.prdNumber} in the html-el:text tag, I've checked 
all my TLDs and the struts-el.jar files to ensure they're in the correct place 
and checked the web.xml file to make sure all the TLDs are mentioned.  There 
are no error messages in my application's log or my application server's log 
that would suggest some class or configuration file being out of whack.

All my other taglibs (normal struts tags and jstl tags) are working just fine, 
and the html-el tag /seems/ to work fine from a Struts standpoint in that it 
makes an input type=text just like it should, but no el-evaluation.  This 
problem doesn't appear to be specific to the mapped property quantity, as I 
can try other html-el tags that directly refer to either ${curPrdNumber} or 
{$cur.prdNumber}, and I get the same result -- no evaluation.

Am I missing something glaringly obvious?

Thanks,
--Trevor



-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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


  


-- 
Jason Lea




-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 2005.02.10




-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



html-el oddities

2005-02-11 Thread Trevor Hill
I'm having an interesting issue.  I have a form in which the only input is a 
bunch of text boxes which correspond to quantities of products.  The associated 
form thus consists of just a HashMap.  My JSP page is as follows:
... header stuff ...

tr
thProduct/th
thProduct Number/th
thPrice/th
thQuantity to add/th
/tr

c:forEach items=${priceList} var=cur
c:set scope=page var=curPrdNumber value=${cur.prdNumber}/

tr
tdc:out value=${cur.itemName}//td
tdc:out value=${cur.prdNumber}//td
tdfmt:formatNumber type=currency 
currencyCode=${cur.currencyCode} value=${cur.price}//td

td style=text-align:righthtml-el:text 
property=quantity(${curPrdNumber}) size=3 maxlength=5 //td
/tr

... submit button, close form, etc



However, the output of the last TD is: 

input type=text name=quantity(${curPrdNumber}) maxlength=5 size=3 
value=/td

which is correct except for that whole not interpreting the EL expression bit.

I've tried using a page-scoped temporary variable (as above), I've tried 
directly referencing ${cur.prdNumber} in the html-el:text tag, I've checked all 
my TLDs and the struts-el.jar files to ensure they're in the correct place and 
checked the web.xml file to make sure all the TLDs are mentioned.  There are no 
error messages in my application's log or my application server's log that 
would suggest some class or configuration file being out of whack.

All my other taglibs (normal struts tags and jstl tags) are working just fine, 
and the html-el tag /seems/ to work fine from a Struts standpoint in that it 
makes an input type=text just like it should, but no el-evaluation.  This 
problem doesn't appear to be specific to the mapped property quantity, as I 
can try other html-el tags that directly refer to either ${curPrdNumber} or 
{$cur.prdNumber}, and I get the same result -- no evaluation.

Am I missing something glaringly obvious?

Thanks,
--Trevor



-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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