lost URL parameters with s:param tag

2010-07-20 Thread Emi Lu

Good morning,

It seems that s:param does not work well when more than one s:param is 
assigned.


s:url id=url_help namespace=/Action/Global action=ProcessHelp
   s:param name=helpTitle  value=example1 /
   s:param name=help_text_name value=contents /
/s:url


The second help_text_name is never called. How come? Found one line 
bug report lost URL parameters with s:param tag (bug 1938) at 
http://readlist.com/lists/struts.apache.org/user/9/47016.html


Does someone know whether the bug has been fixed?

Thanks a lot!
--
Lu Ying

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Emi Lu

On 07/20/2010 11:48 AM, Emi Lu wrote:

Good morning,

It seems that s:param does not work well when more than one s:param is
assigned.

s:url id=url_help namespace=/Action/Global action=ProcessHelp
s:param name=helpTitle value=example1 /
s:param name=help_text_name value=contents /
/s:url


The second help_text_name is never called. How come? Found one line
bug report lost URL parameters with s:param tag (bug 1938) at
http://readlist.com/lists/struts.apache.org/user/9/47016.html

Does someone know whether the bug has been fixed?


Another bug link:
https://issues.apache.org/jira/browse/WW-1938

Does someone has the fix version?

Thanks,
--
Lu Ying

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Brian Thompson
We ran into the same problem with our Struts apps; we ended up using
c:url from the JSTL core taglib instead.

-Brian



On Tue, Jul 20, 2010 at 10:58 AM, Emi Lu em...@encs.concordia.ca wrote:
 On 07/20/2010 11:48 AM, Emi Lu wrote:

 Good morning,

 It seems that s:param does not work well when more than one s:param is
 assigned.

 s:url id=url_help namespace=/Action/Global action=ProcessHelp
 s:param name=helpTitle value=example1 /
 s:param name=help_text_name value=contents /
 /s:url


 The second help_text_name is never called. How come? Found one line
 bug report lost URL parameters with s:param tag (bug 1938) at
 http://readlist.com/lists/struts.apache.org/user/9/47016.html

 Does someone know whether the bug has been fixed?

 Another bug link:
 https://issues.apache.org/jira/browse/WW-1938

 Does someone has the fix version?

 Thanks,
 --
 Lu Ying

 -
 To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
 For additional commands, e-mail: user-h...@struts.apache.org



-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Dale Newfield

On 7/20/10 11:48 AM, Emi Lu wrote:

It seems that s:param does not work well when more than one s:param is
assigned.


I use multiple param tags inside url tags all over the place.  It does 
work.  I would suggest running your application inside a debugger to 
find out what exactly is not working for you.  One thing I would suggest 
is eliminating ambiguities -- value fields (for example) are going to be 
interpreted as OGNL, so if you want the ognl expression contents, then 
value=%{contents} and if you want the string contents, then 
value=%{'contents'}.


-Dale

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Emi Lu

On 07/20/2010 01:39 PM, Dale Newfield wrote:

On 7/20/10 11:48 AM, Emi Lu wrote:

It seems that s:param does not work well when more than one s:param is
assigned.


I use multiple param tags inside url tags all over the place. It does
work. I would suggest running your application inside a debugger to find
out what exactly is not working for you. One thing I would suggest is
eliminating ambiguities -- value fields (for example) are going to be
interpreted as OGNL, so if you want the ognl expression contents, then
value=%{contents} and if you want the string contents, then
value=%{'contents'}.


Thank you for all your inputs!

Conclusion:
=
(1) workable version:
s:param name=helpTitle  value=%{getText('example1')} /
s:param name=helpText   value=%{getText('example2')} /

(2) this way, it does not work:
s:param name=helpTitle  value=example1 /
s:param name=helpText   value=example2 /

Frankly, I do *not* like way(1) since %{getText('example2')} is a very 
long paragraph. I prefer to transfer key property and retrieve text in 
Action Class.


Anyhow, it seems that this is the current solution I could find for now.

If you have better ideas, please let me know.

Thanks a lot!

--
Lu Ying

Note:
attribute.property
=
example1=Title info
example2=.. a very long paragraph ...

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Lukasz Lenart
2010/7/20 Emi Lu em...@encs.concordia.ca:
 s:param name=helpTitle      value=%{getText('example1')} /
 s:param name=helpText       value=%{getText('example2')} /

It's the expected behavior as you don't have these properties in your
action. You're looking throughout message resources and not for
action's variable.


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia 2010 http://javarsovia.pl

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Chris Pratt
Are you intending for these values to come from your application resource
bundle?  That's where getText() gets it's values from.  I believe it it
doesn't find anything it just returns whatever is passed to is, which might
be why you're seeing what I expect you are expecting.

If you are actually trying to test this out with static values (or use
static values), try this instead (note the embedded single quotes within the
double quoted, maybe cutting-n-pasting would work best)

s:param name=helpTitle  value='example1'/
s:param name=helpText value='example2'/

  (*Chris*)

On Tue, Jul 20, 2010 at 12:20 PM, Emi Lu em...@encs.concordia.ca wrote:

 On 07/20/2010 01:39 PM, Dale Newfield wrote:

 On 7/20/10 11:48 AM, Emi Lu wrote:

 It seems that s:param does not work well when more than one s:param is
 assigned.


 I use multiple param tags inside url tags all over the place. It does
 work. I would suggest running your application inside a debugger to find
 out what exactly is not working for you. One thing I would suggest is
 eliminating ambiguities -- value fields (for example) are going to be
 interpreted as OGNL, so if you want the ognl expression contents, then
 value=%{contents} and if you want the string contents, then
 value=%{'contents'}.


 Thank you for all your inputs!

 Conclusion:
 =
 (1) workable version:
 s:param name=helpTitle  value=%{getText('example1')} /
 s:param name=helpText   value=%{getText('example2')} /

 (2) this way, it does not work:

 s:param name=helpTitle  value=example1 /
 s:param name=helpText   value=example2 /

 Frankly, I do *not* like way(1) since %{getText('example2')} is a very
 long paragraph. I prefer to transfer key property and retrieve text in
 Action Class.

 Anyhow, it seems that this is the current solution I could find for now.

 If you have better ideas, please let me know.


 Thanks a lot!

 --
 Lu Ying

 Note:
 attribute.property
 =
 example1=Title info
 example2=.. a very long paragraph ...


 -
 To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
 For additional commands, e-mail: user-h...@struts.apache.org




Re: lost URL parameters with s:param tag

2010-07-20 Thread Emi Lu



Are you intending for these values to come from your application resource
bundle?  That's where getText() gets it's values from.  I believe it it
doesn't find anything it just returns whatever is passed to is, which might
be why you're seeing what I expect you are expecting.

If you are actually trying to test this out with static values (or use
static values), try this instead (note the embedded single quotes within the
double quoted, maybe cutting-n-pasting would work best)

s:param name=helpTitle  value='example1'/
s:param name=helpText value='example2'/


All right, I found the trick.

Workable solution:

s:param name=helpTitle  value=%{'example1'}/
s:param name=helpText   value=%{'example2'}/

Thank you for all your help! Very helpful!

--
Lu Ying





On Tue, Jul 20, 2010 at 12:20 PM, Emi Luem...@encs.concordia.ca  wrote:


On 07/20/2010 01:39 PM, Dale Newfield wrote:


On 7/20/10 11:48 AM, Emi Lu wrote:


It seems that s:param does not work well when more than one s:param is
assigned.



I use multiple param tags inside url tags all over the place. It does
work. I would suggest running your application inside a debugger to find
out what exactly is not working for you. One thing I would suggest is
eliminating ambiguities -- value fields (for example) are going to be
interpreted as OGNL, so if you want the ognl expression contents, then
value=%{contents} and if you want the string contents, then
value=%{'contents'}.



Thank you for all your inputs!

Conclusion:
=
(1) workable version:
s:param name=helpTitle  value=%{getText('example1')} /
s:param name=helpText   value=%{getText('example2')} /

(2) this way, it does not work:

s:param name=helpTitle  value=example1 /
s:param name=helpText   value=example2 /

Frankly, I do *not* like way(1) since %{getText('example2')} is a very
long paragraph. I prefer to transfer key property and retrieve text in
Action Class.

Anyhow, it seems that this is the current solution I could find for now.

If you have better ideas, please let me know.


Thanks a lot!

--
Lu Ying

Note:
attribute.property
=
example1=Title info
example2=.. a very long paragraph ...


-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org







-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Johannes Geppert

does it work when you define it this way?

s:url id=url_help namespace=/Action/Global action=ProcessHelp 
s:param name=helpTitleexample1
s:param name=help_text_namecontents
/s:url 

Johannes


luy wrote:
 
 Good morning,
 
 It seems that s:param does not work well when more than one s:param is 
 assigned.
 
 s:url id=url_help namespace=/Action/Global action=ProcessHelp
 s:param name=helpTitle  value=example1 /
 s:param name=help_text_name value=contents /
 /s:url
 
 
 The second help_text_name is never called. How come? Found one line 
 bug report lost URL parameters with s:param tag (bug 1938) at 
 http://readlist.com/lists/struts.apache.org/user/9/47016.html
 
 Does someone know whether the bug has been fixed?
 
 Thanks a lot!
 --
 Lu Ying
 
 -
 To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
 For additional commands, e-mail: user-h...@struts.apache.org
 
 
 


-
---
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep

-- 
View this message in context: 
http://old.nabble.com/lost-URL-parameters-with-%3Cs%3Aparam%3E-tag-tp29216501p29216887.html
Sent from the Struts - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: lost URL parameters with s:param tag

2010-07-20 Thread Chris Pratt
Not unless you sprinkle a couple of /s:param's in there as well.
  (*Chris*)

On Tue, Jul 20, 2010 at 1:08 PM, Johannes Geppert jo...@web.de wrote:


 does it work when you define it this way?

 s:url id=url_help namespace=/Action/Global action=ProcessHelp
 s:param name=helpTitleexample1
s:param name=help_text_namecontents
 /s:url

 Johannes


 luy wrote:
 
  Good morning,
 
  It seems that s:param does not work well when more than one s:param is
  assigned.
 
  s:url id=url_help namespace=/Action/Global action=ProcessHelp
  s:param name=helpTitle  value=example1 /
  s:param name=help_text_name value=contents /
  /s:url
 
 
  The second help_text_name is never called. How come? Found one line
  bug report lost URL parameters with s:param tag (bug 1938) at
  http://readlist.com/lists/struts.apache.org/user/9/47016.html
 
  Does someone know whether the bug has been fixed?
 
  Thanks a lot!
  --
  Lu Ying
 
  -
  To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
  For additional commands, e-mail: user-h...@struts.apache.org
 
 
 


 -
 ---
 web: http://www.jgeppert.com
 twitter: http://twitter.com/jogep

 --
 View this message in context:
 http://old.nabble.com/lost-URL-parameters-with-%3Cs%3Aparam%3E-tag-tp29216501p29216887.html
 Sent from the Struts - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
 For additional commands, e-mail: user-h...@struts.apache.org




Re: Struts 2 - lost URL parameters with s:param tag (bug 1938)

2007-08-28 Thread Laurie Harper

Riccardo Mollame wrote:

Does anybody know about any fix or workaround to the
mentioned bug?


Did you see James Holmes' comment? [1] By the sound of it, there's no 
problem with the s:url tag itself, it's a question of how you 
subsequently use the value it produces. How are you using it?


L.


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



Re: Struts 2 - lost URL parameters with s:param tag (bug 1938)

2007-08-28 Thread Laurie Harper

[edit: include the URL for James' post]

Riccardo Mollame wrote:

Does anybody know about any fix or workaround to the
mentioned bug?


Did you see James Holmes' comment? [1] By the sound of it, there's no
problem with the s:url tag itself, it's a question of how you
subsequently use the value it produces. How are you using it?

L.

https://issues.apache.org/struts/browse/WW-1938#action_41635


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



Struts 2 - lost URL parameters with s:param tag (bug 1938)

2007-08-27 Thread Riccardo Mollame
Does anybody know about any fix or workaround to the
mentioned bug?

For the record, it's the bug emerging when the s:url
contains more than one s:param tag, in which case
strange things happen (e.g. only one parameter is
actually retrievable in the target action, the others
producing the infamous nullPointerException)

All my best to everyone.


  ___ 
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: 
http://it.docs.yahoo.com/nowyoucan.html

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