RE: Problems with optionsCollection tag and Weblogic 6.1

2002-03-26 Thread Arnaud Heritier

It's done Marcelo

===>

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7485>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7485

Bad release of tag html:optionsCollection

   Summary: Bad release of tag html:optionsCollection
   Product: Struts
   Version: 1.1 Beta 1
  Platform: All
   URL: http://www.mail-archive.com/struts-
user%40jakarta.apache.org/msg26926.html
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Custom Tags
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The use of the optionsCollection tag with Weblogic produces errors.
The problem should be in the release method.

OptionsCollectionTag is initialized with :

protected String label = "label";
protected String name = Constants.BEAN_KEY;
protected String property = null;
private String style = null;
private String styleClass = null;
protected String value = "value";

but the release method defines :

label = null;
name = null;
property = null;
style = null;
styleClass = null;
value = null;

so label, name and value don't have their default values.



> -Message d'origine-
> De:   Marcelo Vanzin [SMTP:[EMAIL PROTECTED]]
> Date: mardi 26 mars 2002 16:05
> A:    Struts Users Mailing List
> Objet:        Re: Problems with optionsCollection tag and Weblogic 6.1
> 
> Arnaud Heritier wrote:
> > but the release method defines :
> > 
> > label = null;
> > name = null;
> > property = null;
> > style = null;
> > styleClass = null;
> > value = null;
> 
>   Hmmm, I guess this is something that needs to be fixed. :-) I think I 
> missed this in the code...
> 
> > Do you used the name and value attributes in the tag 
> 
>   I use "property" but not "name", so when the name is set to "null" I am 
> screwed... thanks for the help!!!
> 
>   Have you warned the taglib developers about it? (I'll be building Struts 
> 1.1b with this fix for internal use.)
> 
> -- 
> []'s
> Marcelo Vanzin
> Touch Tecnologia
> [EMAIL PROTECTED]
> "Life is too short to drink cheap beer"
> 
> 
> --
> 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]>




Re: Problems with optionsCollection tag and Weblogic 6.1

2002-03-26 Thread Marcelo Vanzin

Arnaud Heritier wrote:
> but the release method defines :
> 
> label = null;
> name = null;
> property = null;
> style = null;
> styleClass = null;
> value = null;

Hmmm, I guess this is something that needs to be fixed. :-) I think I 
missed this in the code...

> Do you used the name and value attributes in the tag 

I use "property" but not "name", so when the name is set to "null" I am 
screwed... thanks for the help!!!

Have you warned the taglib developers about it? (I'll be building Struts 
1.1b with this fix for internal use.)

-- 
[]'s
Marcelo Vanzin
Touch Tecnologia
[EMAIL PROTECTED]
"Life is too short to drink cheap beer"


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




RE: Problems with optionsCollection tag and Weblogic 6.1

2002-03-26 Thread Arnaud Heritier

I don't know if it is the source of the problem but in struts 1.1 B1 the code of 
OptionsCollectionTag is initialized with :

protected String label = "label";
protected String name = Constants.BEAN_KEY;
protected String property = null;
private String style = null;
private String styleClass = null;
protected String value = "value";

but the release method defines :

label = null;
name = null;
property = null;
style = null;
styleClass = null;
value = null;

so label, name and value don't have their default values.

it can produce the error.


Do you used the name and value attributes in the tag 


Arnaud 

> -Message d'origine-
> De:   Arnaud Heritier [SMTP:[EMAIL PROTECTED]]
> Date: mardi 26 mars 2002 15:42
> A:'Struts Users Mailing List'
> Objet:    RE: Problems with optionsCollection tag and Weblogic 6.1
> 
> I didn't watch the code but the difference between tomcat and weblogic is that 
>weblogic reuse the taglibraries in the same page.
> Tomcat create a new TagClass for each tag instance while Weblogic reuse the first 
>instance and call the release method.
> 
> This method should reinit all default values in the release method.
> I'm using struts 1.0.2 with WLS 6.1 SP2 and i don't have any problem.
> But I know that there's a lot of bug in WLS 6.1.
> 
> arnaud
> 
> > -Message d'origine-
> > De: Marcelo Vanzin [SMTP:[EMAIL PROTECTED]]
> > Date:   mardi 26 mars 2002 15:32
> > A:  Struts Users
> > Objet:  Problems with optionsCollection tag and Weblogic 6.1
> > 
> > 
> > Hello there,
> > 
> > I've started to use Struts 1.1, and one of the things I was testing was 
> > the "html:optionsCollection" tag, to replace one we coded here (based on 
> > html:options) that did the same thing.
> > 
> > Everything worked fine when testing in Tomcat, but when running our JSPs 
> > in Weblogic (6.1 sp1) something realy strange happens.
> > 
> > The first time the tag is called, it works fine. But if you call it a 
> > second time in the same page, it fails with an exception:
> > 
> > javax.servlet.jsp.JspException: Cannot find bean null in scope null
> > at org.apache.struts.util.RequestUtils.lookup(RequestUtils.java:692)
> > at 
> > 
>org.apache.struts.taglib.html.OptionsCollectionTag.doStartTag(OptionsCollectionTag.java:217)
> > 
> > I have a page with 4 calls to this tag, and it always fails in the second 
> > call. If I comment the 1st one, then it will fail on the 3rd (and the 
> > one that previously caused the exception will render fine).
> > 
> > I've taken a look at the tag code, and it does not seem to have anything 
> > unusual, so I think this is an issue with Weblogic.
> > 
> > Has anyone seen this behaviour, and has some idea of a workaround?
> > 
> > (We're struggling to install sp2 now, maybe when we manage to install it 
> > this bug may be fixed, who knows...)
> > 
> > -- 
> > []'s
> > Marcelo Vanzin
> > Touch Tecnologia
> > [EMAIL PROTECTED]
> > "Life is too short to drink cheap beer"
> > 
> > 
> > --
> > 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]>




RE: Problems with optionsCollection tag and Weblogic 6.1

2002-03-26 Thread Arnaud Heritier

I didn't watch the code but the difference between tomcat and weblogic is that 
weblogic reuse the taglibraries in the same page.
Tomcat create a new TagClass for each tag instance while Weblogic reuse the first 
instance and call the release method.

This method should reinit all default values in the release method.
I'm using struts 1.0.2 with WLS 6.1 SP2 and i don't have any problem.
But I know that there's a lot of bug in WLS 6.1.

arnaud

> -Message d'origine-
> De:   Marcelo Vanzin [SMTP:[EMAIL PROTECTED]]
> Date: mardi 26 mars 2002 15:32
> A:Struts Users
> Objet:        Problems with optionsCollection tag and Weblogic 6.1
> 
> 
>   Hello there,
> 
>   I've started to use Struts 1.1, and one of the things I was testing was 
> the "html:optionsCollection" tag, to replace one we coded here (based on 
> html:options) that did the same thing.
> 
>   Everything worked fine when testing in Tomcat, but when running our JSPs 
> in Weblogic (6.1 sp1) something realy strange happens.
> 
>   The first time the tag is called, it works fine. But if you call it a 
> second time in the same page, it fails with an exception:
> 
> javax.servlet.jsp.JspException: Cannot find bean null in scope null
> at org.apache.struts.util.RequestUtils.lookup(RequestUtils.java:692)
> at 
> 
>org.apache.struts.taglib.html.OptionsCollectionTag.doStartTag(OptionsCollectionTag.java:217)
> 
>   I have a page with 4 calls to this tag, and it always fails in the second 
> call. If I comment the 1st one, then it will fail on the 3rd (and the 
> one that previously caused the exception will render fine).
> 
>   I've taken a look at the tag code, and it does not seem to have anything 
> unusual, so I think this is an issue with Weblogic.
> 
>   Has anyone seen this behaviour, and has some idea of a workaround?
> 
>   (We're struggling to install sp2 now, maybe when we manage to install it 
> this bug may be fixed, who knows...)
> 
> -- 
> []'s
> Marcelo Vanzin
> Touch Tecnologia
> [EMAIL PROTECTED]
> "Life is too short to drink cheap beer"
> 
> 
> --
> 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]>




Problems with optionsCollection tag and Weblogic 6.1

2002-03-26 Thread Marcelo Vanzin


Hello there,

I've started to use Struts 1.1, and one of the things I was testing was 
the "html:optionsCollection" tag, to replace one we coded here (based on 
html:options) that did the same thing.

Everything worked fine when testing in Tomcat, but when running our JSPs 
in Weblogic (6.1 sp1) something realy strange happens.

The first time the tag is called, it works fine. But if you call it a 
second time in the same page, it fails with an exception:

javax.servlet.jsp.JspException: Cannot find bean null in scope null
at org.apache.struts.util.RequestUtils.lookup(RequestUtils.java:692)
at 
org.apache.struts.taglib.html.OptionsCollectionTag.doStartTag(OptionsCollectionTag.java:217)

I have a page with 4 calls to this tag, and it always fails in the second 
call. If I comment the 1st one, then it will fail on the 3rd (and the 
one that previously caused the exception will render fine).

I've taken a look at the tag code, and it does not seem to have anything 
unusual, so I think this is an issue with Weblogic.

Has anyone seen this behaviour, and has some idea of a workaround?

(We're struggling to install sp2 now, maybe when we manage to install it 
this bug may be fixed, who knows...)

-- 
[]'s
Marcelo Vanzin
Touch Tecnologia
[EMAIL PROTECTED]
"Life is too short to drink cheap beer"


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