RE: fmt:bundle
After upgrading to the current version, It works as expected. I guess this is just one of those technoloiges i have taken for granted. Thanks for assisting. -Original Message- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 22, 2005 6:09 PM To: Tag Libraries Users List Subject: RE: fmt:bundle Well, I am still using 1.0.2. I will upgrade ans see if it changes. Thanks for the help -Original Message- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 22, 2005 5:11 PM To: Tag Libraries Users List Subject: Re: fmt:bundle On 11/22/05, Ray Madigan [EMAIL PROTECTED] wrote: snip Displays FOO???Bar??? The first bundle is set but the second one doesn't snap/ I was intrigued and I had to try this. Works correctly for me, I get: FOO BAR Tried on JSTL 1.1, Tomcat 5.0.28. So it turns out we *still* don't have enough information, we're missing something. -Rahul -Original Message- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Sunday, November 20, 2005 8:54 PM To: Tag Libraries Users List Subject: Re: fmt:bundle On 11/16/05, Ray Madigan [EMAIL PROTECTED] wrote: I was wondering if anyone could shed some light on a problem I am having! I have a page that needs to get a resource bundle based on a string passed into the page. It is kinda like this: snip/ Ray - Sorry, I'm not sure based on the information in this email. But, I'm quite positive this is not a JSTL issue. If you think it is, please post the smallest reproducible test case. -Rahul !-- array holds the list of the reference names for the resource bundle -- c:forEach var='foo' items='${array}' fmt:bundle basename='common' !-- find resource name and store it in attribute bar -- fmt:message key='${foo}' var='bar'/ /fmt:bundle !-- iterate through the list of elements -- c:forEach var='map' items='${elements}' fmt:bundle basename='${bar}' !-- find the property in the bar reference resource -- fmt:message key='${map}'/ /fmt:bundle /forEach /forEach -Original Message- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 16, 2005 12:37 AM To: Taglibs-User Subject: fmt:bundle I was wondering if anyone could shed some light on a problem I am having! I have a pafe that needs to get a resource bundle based on a string passed into the page. It is kinda like this: fmt:bundle basename='common'/ fmt:message key='${foo}' var='bar'/ /fmt:bundle c:forEach var='bar' items='barMap' fmt:bundle basename='bar.key' fmt:message key='${bar.value}'/ /fmt:bundle /forEach Things work well for the first fmt:bundle ant the first fmt:bundle in the c:forEach. The second fmt:message acts like it con't find the resource in the bundle. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: fmt:bundle
I have two bundle files foo_en.properties Foo=FOO bar_en.properties Bar=BAR In my jsp I have html head fmt:setLocale value='en'/ /head body table trtd fmt:bundle basename='foo' fmt:message key='Foo'/ /fmt:bundle /td td fmt:bundle basename='bar' fmt:message key='Bar'/ /fmt:bundle /td /tr /table /body /html Displays FOO???Bar??? The first bundle is set but the second one doesn't -Original Message- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Sunday, November 20, 2005 8:54 PM To: Tag Libraries Users List Subject: Re: fmt:bundle On 11/16/05, Ray Madigan [EMAIL PROTECTED] wrote: I was wondering if anyone could shed some light on a problem I am having! I have a page that needs to get a resource bundle based on a string passed into the page. It is kinda like this: snip/ Ray - Sorry, I'm not sure based on the information in this email. But, I'm quite positive this is not a JSTL issue. If you think it is, please post the smallest reproducible test case. -Rahul !-- array holds the list of the reference names for the resource bundle -- c:forEach var='foo' items='${array}' fmt:bundle basename='common' !-- find resource name and store it in attribute bar -- fmt:message key='${foo}' var='bar'/ /fmt:bundle !-- iterate through the list of elements -- c:forEach var='map' items='${elements}' fmt:bundle basename='${bar}' !-- find the property in the bar reference resource -- fmt:message key='${map}'/ /fmt:bundle /forEach /forEach -Original Message- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 16, 2005 12:37 AM To: Taglibs-User Subject: fmt:bundle I was wondering if anyone could shed some light on a problem I am having! I have a pafe that needs to get a resource bundle based on a string passed into the page. It is kinda like this: fmt:bundle basename='common'/ fmt:message key='${foo}' var='bar'/ /fmt:bundle c:forEach var='bar' items='barMap' fmt:bundle basename='bar.key' fmt:message key='${bar.value}'/ /fmt:bundle /forEach Things work well for the first fmt:bundle ant the first fmt:bundle in the c:forEach. The second fmt:message acts like it con't find the resource in the bundle. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fmt:bundle
On 11/22/05, Ray Madigan [EMAIL PROTECTED] wrote: snip Displays FOO???Bar??? The first bundle is set but the second one doesn't snap/ I was intrigued and I had to try this. Works correctly for me, I get: FOO BAR Tried on JSTL 1.1, Tomcat 5.0.28. So it turns out we *still* don't have enough information, we're missing something. -Rahul -Original Message- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Sunday, November 20, 2005 8:54 PM To: Tag Libraries Users List Subject: Re: fmt:bundle On 11/16/05, Ray Madigan [EMAIL PROTECTED] wrote: I was wondering if anyone could shed some light on a problem I am having! I have a page that needs to get a resource bundle based on a string passed into the page. It is kinda like this: snip/ Ray - Sorry, I'm not sure based on the information in this email. But, I'm quite positive this is not a JSTL issue. If you think it is, please post the smallest reproducible test case. -Rahul !-- array holds the list of the reference names for the resource bundle -- c:forEach var='foo' items='${array}' fmt:bundle basename='common' !-- find resource name and store it in attribute bar -- fmt:message key='${foo}' var='bar'/ /fmt:bundle !-- iterate through the list of elements -- c:forEach var='map' items='${elements}' fmt:bundle basename='${bar}' !-- find the property in the bar reference resource -- fmt:message key='${map}'/ /fmt:bundle /forEach /forEach -Original Message- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 16, 2005 12:37 AM To: Taglibs-User Subject: fmt:bundle I was wondering if anyone could shed some light on a problem I am having! I have a pafe that needs to get a resource bundle based on a string passed into the page. It is kinda like this: fmt:bundle basename='common'/ fmt:message key='${foo}' var='bar'/ /fmt:bundle c:forEach var='bar' items='barMap' fmt:bundle basename='bar.key' fmt:message key='${bar.value}'/ /fmt:bundle /forEach Things work well for the first fmt:bundle ant the first fmt:bundle in the c:forEach. The second fmt:message acts like it con't find the resource in the bundle. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: fmt:bundle
Well, I am still using 1.0.2. I will upgrade ans see if it changes. Thanks for the help -Original Message- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 22, 2005 5:11 PM To: Tag Libraries Users List Subject: Re: fmt:bundle On 11/22/05, Ray Madigan [EMAIL PROTECTED] wrote: snip Displays FOO???Bar??? The first bundle is set but the second one doesn't snap/ I was intrigued and I had to try this. Works correctly for me, I get: FOO BAR Tried on JSTL 1.1, Tomcat 5.0.28. So it turns out we *still* don't have enough information, we're missing something. -Rahul -Original Message- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Sunday, November 20, 2005 8:54 PM To: Tag Libraries Users List Subject: Re: fmt:bundle On 11/16/05, Ray Madigan [EMAIL PROTECTED] wrote: I was wondering if anyone could shed some light on a problem I am having! I have a page that needs to get a resource bundle based on a string passed into the page. It is kinda like this: snip/ Ray - Sorry, I'm not sure based on the information in this email. But, I'm quite positive this is not a JSTL issue. If you think it is, please post the smallest reproducible test case. -Rahul !-- array holds the list of the reference names for the resource bundle -- c:forEach var='foo' items='${array}' fmt:bundle basename='common' !-- find resource name and store it in attribute bar -- fmt:message key='${foo}' var='bar'/ /fmt:bundle !-- iterate through the list of elements -- c:forEach var='map' items='${elements}' fmt:bundle basename='${bar}' !-- find the property in the bar reference resource -- fmt:message key='${map}'/ /fmt:bundle /forEach /forEach -Original Message- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 16, 2005 12:37 AM To: Taglibs-User Subject: fmt:bundle I was wondering if anyone could shed some light on a problem I am having! I have a pafe that needs to get a resource bundle based on a string passed into the page. It is kinda like this: fmt:bundle basename='common'/ fmt:message key='${foo}' var='bar'/ /fmt:bundle c:forEach var='bar' items='barMap' fmt:bundle basename='bar.key' fmt:message key='${bar.value}'/ /fmt:bundle /forEach Things work well for the first fmt:bundle ant the first fmt:bundle in the c:forEach. The second fmt:message acts like it con't find the resource in the bundle. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fmt:bundle
On 11/16/05, Ray Madigan [EMAIL PROTECTED] wrote: I was wondering if anyone could shed some light on a problem I am having! I have a page that needs to get a resource bundle based on a string passed into the page. It is kinda like this: snip/ Ray - Sorry, I'm not sure based on the information in this email. But, I'm quite positive this is not a JSTL issue. If you think it is, please post the smallest reproducible test case. -Rahul !-- array holds the list of the reference names for the resource bundle -- c:forEach var='foo' items='${array}' fmt:bundle basename='common' !-- find resource name and store it in attribute bar -- fmt:message key='${foo}' var='bar'/ /fmt:bundle !-- iterate through the list of elements -- c:forEach var='map' items='${elements}' fmt:bundle basename='${bar}' !-- find the property in the bar reference resource -- fmt:message key='${map}'/ /fmt:bundle /forEach /forEach -Original Message- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 16, 2005 12:37 AM To: Taglibs-User Subject: fmt:bundle I was wondering if anyone could shed some light on a problem I am having! I have a pafe that needs to get a resource bundle based on a string passed into the page. It is kinda like this: fmt:bundle basename='common'/ fmt:message key='${foo}' var='bar'/ /fmt:bundle c:forEach var='bar' items='barMap' fmt:bundle basename='bar.key' fmt:message key='${bar.value}'/ /fmt:bundle /forEach Things work well for the first fmt:bundle ant the first fmt:bundle in the c:forEach. The second fmt:message acts like it con't find the resource in the bundle. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fmt:bundle scope problem
Sorry, my [EMAIL PROTECTED] provider reset my webmail to HTML composition. Let me try again: I'm using JSTL 1.1 on Tomcat 5.0, and fmt:bundle is changing the bundle for the entire page, not just for fmt:message tags in its body. My web.xml: !-- fallback language is english -- context-param param-namejavax.servlet.jsp.jstl.fmt.fallbackLocale/param-name param-valueen/param-value /context-param !-- message file prefix is directory -- context-param param-namejavax.servlet.jsp.jstl.fmt.localizationContext/param-name param-valuedirectory/param-value /context-param The offending snippet of JSP: span class=listing-meta-info %-- BUGBUG fmt:bundle is setting bundle for page scope, not tag scope --% span class=definition title=fmt:bundle basename=glossaryfmt:message key=${website.siteType}//fmt:bundle fmt:message key=${website.siteType}/ /span /span The same text appears in the title and between the spans, even if I enclose the second fmt:message in its own fmt:bundle with a different basename in order to work-around this problem. I'm guessing this is a problem with tag reuse. Can anyone reproduce this, point me to a bug report, or suggest a work-around? Thanks, Rick DeBay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fmt:bundle scope problem
There are some typos in your example, are they just c/p errors? I think the span should look like: span class=definition title=fmt:bundle basename=glossaryfmt:message key=${website.siteType}//fmt:bundle fmt:message key=${website.siteType}/ /span Otherwise, if you think it's a pooling bug, you can turn it off in $CATALINA_HOME/conf/web.xml. Look for: servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class ... /servlet and add the following init param: init-param param-nameenablePooling/param-name param-valuefalse/param-value /init-param Quoting [EMAIL PROTECTED]: Sorry, my [EMAIL PROTECTED] provider reset my webmail to HTML composition. Let me try again: I'm using JSTL 1.1 on Tomcat 5.0, and fmt:bundle is changing the bundle for the entire page, not just for fmt:message tags in its body. My web.xml: !-- fallback language is english -- context-param param-namejavax.servlet.jsp.jstl.fmt.fallbackLocale/param-name param-valueen/param-value /context-param !-- message file prefix is directory -- context-param param-namejavax.servlet.jsp.jstl.fmt.localizationContext/param-name param-valuedirectory/param-value /context-param The offending snippet of JSP: span class=listing-meta-info %-- BUGBUG fmt:bundle is setting bundle for page scope, not tag scope --% span class=definition title=fmt:bundle basename=glossaryfmt:message key=${website.siteType}//fmt:bundle fmt:message key=${website.siteType}/ /span /span The same text appears in the title and between the spans, even if I enclose the second fmt:message in its own fmt:bundle with a different basename in order to work-around this problem. I'm guessing this is a problem with tag reuse. Can anyone reproduce this, point me to a bug report, or suggest a work-around? Thanks, Rick DeBay -- Kris Schneider mailto:[EMAIL PROTECTED] D.O.Tech http://www.dotech.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fmt:bundle scope problem
They're not typos, it's iPowerWeb mucking with my email. OK, it works now. I suppose I should submit a bug report? Any pointers besides use common sense? Thanks, Rick DeBay On Thu, 29 Jan 2004 14:42 , Kris Schneider [EMAIL PROTECTED] sent: There are some typos in your example, are they just c/p errors? I think the span should look like: title= key=${website.siteType}/ Otherwise, if you think it's a pooling bug, you can turn it off in $CATALINA_HOME/conf/web.xml. Look for: jsp org.apache.jasper.servlet.JspServlet ... and add the following init param: enablePooling false Quoting [EMAIL PROTECTED]: Sorry, my [EMAIL PROTECTED] provider reset my webmail to HTML composition. Let me try again: I'm using JSTL 1.1 on Tomcat 5.0, and fmt:bundle is changing the bundle for the entire page, not just for fmt:message tags in its body. My web.xml: javax.servlet.jsp.jstl.fmt.fallbackLocale en javax.servlet.jsp.jstl.fmt.localizationContext directory The offending snippet of JSP: --% basename=glossary key=${website.siteType}/ The same text appears in the title and between the spans, even if I enclose the second fmt:message in its own fmt:bundle with a different basename in order to work-around this problem. I'm guessing this is a problem with tag reuse. Can anyone reproduce this, point me to a bug report, or suggest a work-around? Thanks, Rick DeBay -- Kris Schneider [EMAIL PROTECTED]','','','')[EMAIL PROTECTED] D.O.Tech http://www.dotech.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]