Re: [Resin-interest] Unable to pass request parameter to custom taglibwith Resin 3.1.3

2007-10-10 Thread Ambar Hegde
Thanks, Mike and Mattias. Setting rtexprvalue=true solved it.

-Ambar
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mattias Jiderhamn
  Sent: Tuesday, October 09, 2007 10:11 PM
  To: General Discussion for the Resin application server
  Subject: Re: [Resin-interest] Unable to pass request parameter to custom 
taglibwith Resin 3.1.3


  Yes, Resin 3.x is much more picky about rtexprvaluetrue/rtexprvalue in 
your TLD files.
  That is most probably what you are seeing.

  Mike Wynholds wrote:

I am not sure exactly why it stopped working, but I have noticed that 
sometimes Resin, over time, becomes more and more spec-compliant.  this often 
means things that “worked” in the past, even though they were against the spec, 
stop working.



check your .tld file to make sure that the “moduleName” parameter is set to 
rtexpr=”true”.



also, you use EL to get the request parameter instead of scriptlets, like 
this:



mytaglib:loadFav moduleName=”${param.moduleName}”/



(no need for the request.getParameter(…))



..mike..






From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ambar Hegde
Sent: Tuesday, October 09, 2007 6:29 AM
To: General Discussion for the Resin application server
Subject: [Resin-interest] Unable to pass request parameter to custom 
taglibwith Resin 3.1.3



I'm having trouble trying to pass a request parameter to a custom taglib by 
setting an attribute.



The jsp looks like this:



%

String moduleName =request.getParameter(moduleName);

%



mytaglib:loadFav moduleName=%=moduleName%/



In the loadFav class, 



public void setModuleName(String moduleName) {
this.moduleName = moduleName;   

}



 public int doStartTag() throws JspException {
AppsLogger.debug(Entered LoadDefaultFavSearchTag.doStartTag(): 
+getModuleName());

}

The getModuleName method is returning the literal string %=moduleName% 
(minus quotes).



The moduleName parameter was being passed along fine when I was using Resin 
2.1.10. However I'm seeing this behaviour

in both Resin 3.1.2 and Resin 3.1.3. Is this a bug or am I doing something 
wrong?



TIA,



-Ambar








___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
  

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Unable to pass request parameter to custom taglibwith Resin 3.1.3

2007-10-09 Thread Mike Wynholds
I am not sure exactly why it stopped working, but I have noticed that
sometimes Resin, over time, becomes more and more spec-compliant.  this
often means things that worked in the past, even though they were
against the spec, stop working.

 

check your .tld file to make sure that the moduleName parameter is set
to rtexpr=true.

 

also, you use EL to get the request parameter instead of scriptlets,
like this:

 

mytaglib:loadFav moduleName=${param.moduleName}/

 

(no need for the request.getParameter(...))

 

..mike..

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ambar Hegde
Sent: Tuesday, October 09, 2007 6:29 AM
To: General Discussion for the Resin application server
Subject: [Resin-interest] Unable to pass request parameter to custom
taglibwith Resin 3.1.3

 

I'm having trouble trying to pass a request parameter to a custom taglib
by setting an attribute.

 

The jsp looks like this:

 

%

String moduleName =request.getParameter(moduleName);

%

 

mytaglib:loadFav moduleName=%=moduleName%/

 

In the loadFav class, 

 

public void setModuleName(String moduleName) {
this.moduleName = moduleName;   

}

 

 public int doStartTag() throws JspException {
AppsLogger.debug(Entered LoadDefaultFavSearchTag.doStartTag():
+getModuleName());

}

The getModuleName method is returning the literal string
%=moduleName% (minus quotes).

 

The moduleName parameter was being passed along fine when I was using
Resin 2.1.10. However I'm seeing this behaviour

in both Resin 3.1.2 and Resin 3.1.3. Is this a bug or am I doing
something wrong?

 

TIA,

 

-Ambar

 

 

 

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Unable to pass request parameter to custom taglibwith Resin 3.1.3

2007-10-09 Thread Mattias Jiderhamn
Yes, Resin 3.x is much more picky about rtexprvaluetrue/rtexprvalue
in your TLD files.
That is most probably what you are seeing.

Mike Wynholds wrote:

 I am not sure exactly why it stopped working, but I have noticed that
 sometimes Resin, over time, becomes more and more spec-compliant. 
 this often means things that “worked” in the past, even though they
 were against the spec, stop working.

  

 check your .tld file to make sure that the “moduleName” parameter is
 set to rtexpr=”true”.

  

 also, you use EL to get the request parameter instead of scriptlets,
 like this:

  

 mytaglib:loadFav moduleName=”${param.moduleName}”/

  

 (no need for the request.getParameter(…))

  

 ..mike..

  

 

 *From:* [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] *On Behalf Of *Ambar Hegde
 *Sent:* Tuesday, October 09, 2007 6:29 AM
 *To:* General Discussion for the Resin application server
 *Subject:* [Resin-interest] Unable to pass request parameter to custom
 taglibwith Resin 3.1.3

  

 I'm having trouble trying to pass a request parameter to a custom
 taglib by setting an attribute.

  

 The jsp looks like this:

  

 %

 String moduleName =request.getParameter(moduleName);

 %

  

 mytaglib:loadFav moduleName=%=moduleName%/

  

 In the loadFav class,

  

 public void setModuleName(String moduleName) {
 this.moduleName = moduleName;  

 }

  

  public int doStartTag() throws JspException {
 AppsLogger.debug(Entered
 LoadDefaultFavSearchTag.doStartTag(): +getModuleName());

 }

 The getModuleName method is returning the literal string
 %=moduleName% (minus quotes).

  

 The moduleName parameter was being passed along fine when I was using
 Resin 2.1.10. However I'm seeing this behaviour

 in both Resin 3.1.2 and Resin 3.1.3. Is this a bug or am I doing
 something wrong?

  

 TIA,

  

 -Ambar

  

  

  

 

 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest
   


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest