struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karr, David" <>
Subject RE: problem with bean:define tag
Date Thu, 23 Jan 2003 21:18:47 GMT
That seems like a weird name to use, but it might work.  You really
should just be executing this in the debugger so you can see exactly
what is happening.

-----Original Message-----
From: Adel [] 
Sent: Thursday, January 23, 2003 1:05 PM
Subject: Re: problem with bean:define tag

Hi again,
Thanks for your answer David. The beanName I am using is
<bean:define name="<%=Action.Mapping_KEY%>" id="path" property="path"
scope="request" toScope="page" />
This works fine with 1.1b1 but not with 1.1b3.
 Note that you will get this message if the count of "name", "value",
"body" is != 1.  The message sounds like it's saying you have more than
one of them, but in truth you could get the error if you had none of
them.  I'm going to guess that "beanName" is empty or null.

-----Original Message-----
From: Adel [] 
Sent: Thursday, January 23, 2003 10:31 AM
Subject: problem with bean:define tag


I am having a strange problem with stuts 1.1.b3 (with Weblogic 7).
Everything woks fine with struts 1.1.b1 but when I moved to the 1.1.b3
the define tag is generating an exception. The define tag that generates
the execption:

<bean:define name="<%=beanName%>" id="path" property="path"
scope="request" toScope="page" />

The generated exception :

javax.servlet.jsp.JspException: Define tag can contain only one of name
attribute, value attribute, or body content

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

View raw message