Re: DynaActionForm question

[Mark Lowe]

Nice...

So the attribute attribute lets you override the the attribute name 
when the setAttribute method is called, rather than using the default 
form name.

Thanks Mark

On 3 Jan 2004, at 14:13, Matthias Wessendorf wrote:

hi,

attribute:
Name of the request-scope or session-scope attribute that
is used to access our ActionForm bean, if it is other than
the bean's specified "name". Optional if "name" is specified,
else not valid.
if you have something like this:


and:

 

your FormBean "form" of type:DynaValidatorForm
is named as "foo"
request.getAttribute("foo");
or
request.getSession().getAttribute("foo");
greetings
matthias
-Original Message-
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 03, 2004 2:05 PM
To: Struts Users Mailing List
Subject: Re: DynaActionForm question
Not sure if its deprecated but i always use



rather than attribute which i don't know anything about.

Cheers Mark

On 2 Jan 2004, at 20:44, Sifuentes, Ben wrote:

I have been trying to do the following:

type="com.mckesson.eig.actions.search.patient.SearchForm">
			type="java.util.ArrayList"/>

type="java.lang.String"/>







type="java.lang.String"/>
			type="java.lang.String"/>
			type="java.lang.String"/>






   
  

  


type="com.mckesson.eig.common.presentation.properties.WindowPopupProper
ties"
/>


attribute="searchForm"
scope="session"
validate="false">

	Based on the following struts documentation this should have
worked?

  


When the /editRegistration action is invoked, a registrationForm
is
created and added to the request, but its validate method is not
called. The
default value of the validate attribute is true, so if you do not want

an
action to trigger form validation, you need to remember to add this
attribute and set it to false.
	So now when I print off the session values when the action is
fired
these attributes are the only ones that exists:

	[02 Jan 2004 13:40:58,699] [RemoteParameterAction] Scope:
session
	[02 Jan 2004 13:40:58,699] [RemoteParameterAction] searchForm
must be
null in session
[02 Jan 2004 13:40:58,709] [RemoteParameterAction] name:
SWIM_USER
[02 Jan 2004 13:40:58,779] [RemoteParameterAction] name:
SWIM_FACILITY
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] name:
SESSION_MANAGER
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] name:
SWIM_MRN
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] name:
org.apache.struts.action.LOCALE
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] Our Form is
null
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] Controller
contains Mrn: [032599]
I was expecting to see a searchForm in the session based on the
documentation also that the form would not be null that was passed to
execute.
	-Ben



-
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: DynaActionForm question

[Matthias Wessendorf]

hi,

attribute:   
Name of the request-scope or session-scope attribute that
is used to access our ActionForm bean, if it is other than
the bean's specified "name". Optional if "name" is specified,
else not valid.

if you have something like this:



and:

 


your FormBean "form" of type:DynaValidatorForm
is named as "foo" 
request.getAttribute("foo");
or
request.getSession().getAttribute("foo");

greetings 
matthias


-Original Message-
From: Mark Lowe [mailto:[EMAIL PROTECTED] 
Sent: Saturday, January 03, 2004 2:05 PM
To: Struts Users Mailing List
Subject: Re: DynaActionForm question


Not sure if its deprecated but i always use

 I have been trying to do the following:
>  name="searchForm"
>
type="com.mckesson.eig.actions.search.patient.SearchForm">
>   
>type="java.util.ArrayList"/>
>   
>type="java.lang.String"/>
>type="java.lang.String"/>
>type="java.lang.String"/>
>type="java.lang.String"/>
>type="java.lang.String"/>
>type="java.lang.String"/>
>type="java.lang.String"/>
>   
>   
>   
>type="java.lang.String"/>
>type="java.lang.String"/>
>type="java.util.ArrayList"
> className="com.mckesson.eig.common.struts.NullInitialPropertyConfig"/>
>type="java.lang.String"/>
>type="java.lang.String"/>
>type="java.lang.Integer"/>
>type="java.util.ArrayList"/>  
>type="java.lang.String"/> 
>type="java.lang.String[]"/>   
>type="java.lang.String"/> 
>type="java.lang.String"/>
>   
type="com.mckesson.eig.common.presentation.properties.WindowPopupProper 
> ties"
> />
>   
>
>  path="/remoteParam"
>   
> type="com.mckesson.eig.actions.RemoteParameterAction">
>   attribute="searchForm"
>   scope="session"
>   validate="false">
>   
>
>
>   Based on the following struts documentation this should have
worked?
>
>  
> type="org.apache.struts.webapp.example.EditRegistrationAction"
>attribute="registrationForm"
>scope="request"
>validate="false">
> 
>   
>   
>   When the /editRegistration action is invoked, a registrationForm
is 
> created and added to the request, but its validate method is not
> called. The
> default value of the validate attribute is true, so if you do not want

> an
> action to trigger form validation, you need to remember to add this
> attribute and set it to false.
>
>   So now when I print off the session values when the action is
fired 
> these attributes are the only ones that exists:
>
>   [02 Jan 2004 13:40:58,699] [RemoteParameterAction] Scope:
session
>   [02 Jan 2004 13:40:58,699] [RemoteParameterAction] searchForm
must be 
> null in session
>   [02 Jan 2004 13:40:58,709] [RemoteParameterAction] name:
SWIM_USER
>   [02 Jan 2004 13:40:58,779] [RemoteParameterAction] name: 
> SWIM_FACILITY
>   [02 Jan 2004 13:40:58,789] [RemoteParameterAction] name: 
> SESSION_MANAGER
>   [02 Jan 2004 13:40:58,789] [RemoteParameterAction] name:
SWIM_MRN
>   [02 Jan 2004 13:40:58,789] [RemoteParameterAction] name: 
> org.apache.struts.action.LOCALE
>   [02 Jan 2004 13:40:58,789] [RemoteParameterAction] Our Form is 
> null
>   [02 Jan 2004 13:40:58,789] [RemoteParameterAction] Controller 
> contains Mrn: [032599]
>
>
>   I was expecting to see a searchForm in the session based on the 
> documentation also that the form would not be null that was passed to 
> execute.
>
>
>   -Ben
>
>
>
>
> -
> 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: DynaActionForm question

[Mark Lowe]

Not sure if its deprecated but i always use



rather than attribute which i don't know anything about.

Cheers Mark

On 2 Jan 2004, at 20:44, Sifuentes, Ben wrote:

I have been trying to do the following:
	
		name="searchForm"
		type="com.mckesson.eig.actions.search.patient.SearchForm">
			
type="java.util.ArrayList"/>
			
type="java.util.ArrayList"/>
			
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
			
			
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
type="java.util.ArrayList"
className="com.mckesson.eig.common.struts.NullInitialPropertyConfig"/>
			
type="java.lang.String"/>
			
type="java.lang.String"/>
			
type="java.lang.Integer"/>
			
type="java.util.ArrayList"/>			
			
type="java.lang.String"/>		
			
type="java.lang.String[]"/>			
			
type="java.lang.String"/>			
			
type="java.lang.String"/>
			
type="com.mckesson.eig.common.presentation.properties.WindowPopupProper 
ties"
/>
	


attribute="searchForm"
scope="session"
validate="false">

	Based on the following struts documentation this should have worked?

	
	
type="org.apache.struts.webapp.example.EditRegistrationAction"
	 attribute="registrationForm"
	 scope="request"
	 validate="false">
	  
	
	
	When the /editRegistration action is invoked, a registrationForm is
created and added to the request, but its validate method is not  
called. The
default value of the validate attribute is true, so if you do not want  
an
action to trigger form validation, you need to remember to add this
attribute and set it to false.

So now when I print off the session values when the action is fired
these attributes are the only ones that exists:
[02 Jan 2004 13:40:58,699] [RemoteParameterAction] Scope: session
[02 Jan 2004 13:40:58,699] [RemoteParameterAction] searchForm must
be null in session
[02 Jan 2004 13:40:58,709] [RemoteParameterAction] name: SWIM_USER
[02 Jan 2004 13:40:58,779] [RemoteParameterAction] name:
SWIM_FACILITY
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] name:
SESSION_MANAGER
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] name: SWIM_MRN
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] name:
org.apache.struts.action.LOCALE
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] Our Form is
null
[02 Jan 2004 13:40:58,789] [RemoteParameterAction] Controller
contains Mrn: [032599]
I was expecting to see a searchForm in the session based on the
documentation also that the form would not be null that was passed to
execute.
	-Ben



-
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: DynaActionForm question

[Gemes Tibor]

2003. január 21. 15:35 dátummal [EMAIL PROTECTED] ezt írtad:
> Is it possible to instantiate an instance of DynaActionForm before I
> populate the page?

Yes, for an example in your prepopulating action. Create an action which 
collects the data and populates your form. And assign the same actionform to 
this action. 

Hth

Tib

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

RE: DynaActionForm question

[pqin]

Is it possible to instantiate an instance of DynaActionForm before I
populate the page?

Regards,
 
 
PQ
 
"This Guy Thinks He Knows Everything"
"This Guy Thinks He Knows What He Is Doing"

-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] 
Sent: January 20, 2003 7:58 PM
To: Struts Users Mailing List
Subject: Re: DynaActionForm question



On Mon, 20 Jan 2003, Giri Alwar wrote:

>
> I have a question for the folks in general. What is the main reason for
> using the DynaActionForm class (as opposed to writing your own
ActionForm)?

That's it in a nutshell :-).  Having to write fewer classes is goodness.

> While you don't have to write your own class with DynaActionForm, aren't
you
> restricting yourself to using Struts taglibs (especially the bean
taglibs?).

You're certainly dependent on commons-beanutils.

> What if you want to use JSTL now or sometime in the future?

If you look closely at the public API for DynaActionForm, you'll see the
getMap() method.  This returns the name/value map for the properties of
the DynaBean, and makes it pretty easy to use JSTL with DynaActionForm
beans.  For example, the following are essentially equivalent:

  

  

if "customer" points at a DynaActionForm bean.

> With the IDE's
> that we all use today, creating an ActionForm class with getter/setter
> methods is a breeze. Hence, what do you truly gain by using
DynaActionForm?

Not everyone has (or likes) an IDE.

> Giri


Craig


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

Re: DynaActionForm question

[Craig R. McClanahan]

On Mon, 20 Jan 2003, Giri Alwar wrote:

>
> I have a question for the folks in general. What is the main reason for
> using the DynaActionForm class (as opposed to writing your own ActionForm)?

That's it in a nutshell :-).  Having to write fewer classes is goodness.

> While you don't have to write your own class with DynaActionForm, aren't you
> restricting yourself to using Struts taglibs (especially the bean taglibs?).

You're certainly dependent on commons-beanutils.

> What if you want to use JSTL now or sometime in the future?

If you look closely at the public API for DynaActionForm, you'll see the
getMap() method.  This returns the name/value map for the properties of
the DynaBean, and makes it pretty easy to use JSTL with DynaActionForm
beans.  For example, the following are essentially equivalent:

  

  

if "customer" points at a DynaActionForm bean.

> With the IDE's
> that we all use today, creating an ActionForm class with getter/setter
> methods is a breeze. Hence, what do you truly gain by using DynaActionForm?

Not everyone has (or likes) an IDE.

> Giri


Craig


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

RE: DynaActionForm question

[James Turner]

> From: Giri Alwar [mailto:[EMAIL PROTECTED]] 
> Subject: Re: DynaActionForm question

> The DynaActionForm differs from the ActionForm in one 
> critical way: the ActionForm class is a real Javabean with 
> getter/setters for your properties. Hence it can be used with 
> other third party taglibs such as JSTL etc. The 
> DynaActionForm does not have getters/setters for your 
> properties. The only reason it works with Struts taglibs is 
> because Struts taglibs recognize the DynaActionForm as 
> something unique and process it differently.

Actually, DynaActionForm works just fine with JSTL, because it
implements a .map getter, so where in a non-DynaForm JSTL you might say:

value="${bean.property}"

You can say

value="${bean.map.property}" using a DynaForm

> I have a question for the folks in general. What is the main 
> reason for using the DynaActionForm class (as opposed to 
> writing your own ActionForm)? While you don't have to write 
> your own class with DynaActionForm, aren't you restricting 
> yourself to using Struts taglibs (especially the bean 
> taglibs?). What if you want to use JSTL now or sometime in 
> the future? With the IDE's that we all use today, creating an 
> ActionForm class with getter/setter methods is a breeze. 
> Hence, what do you truly gain by using DynaActionForm? Giri

As mentioned, you can use DynaForms with JSTL just fine, and even with
modern IDEs, not having to write and maintain a class per form is a
major win for me.

James Turner
Owner & Manager, Black Bear Software, LLC
[EMAIL PROTECTED]

Author: 
MySQL & JSP Web Applications: 
Data Driven Programming Using Tomcat and MySQL
ISBN 0672323095; SAMS, 2002

Co-Author: 
Struts Kick Start
ISBN 0672324725; SAMS, 2002

Forthcoming:
Java Server Faces Kick Start 
SAMS, Fall 2003





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

Re: DynaActionForm question

[Giri Alwar]

The DynaActionForm differs from the ActionForm in one critical way: the
ActionForm class is a real Javabean with getter/setters for your properties.
Hence it can be used with other third party taglibs such as JSTL etc. The
DynaActionForm does not have getters/setters for your properties. The only
reason it works with Struts taglibs is because Struts taglibs recognize the
DynaActionForm as something unique and process it differently.

I have a question for the folks in general. What is the main reason for
using the DynaActionForm class (as opposed to writing your own ActionForm)?
While you don't have to write your own class with DynaActionForm, aren't you
restricting yourself to using Struts taglibs (especially the bean taglibs?).
What if you want to use JSTL now or sometime in the future? With the IDE's
that we all use today, creating an ActionForm class with getter/setter
methods is a breeze. Hence, what do you truly gain by using DynaActionForm?
Giri

- Original Message -
From: "Mark Minnie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, January 19, 2003 11:04 PM
Subject: DynaActionForm question


"Struts in Action" on page 162 reads:

"You can use a DynaActionForm anywhere an ActionForm can be used.  You can
also substitute a DynaActionForm for a conventional ActionForm without
changing any of the existing Java or JSP code."

I changed a ActionForm to a DynaActionForm by using the struts-config.xml:


   
   


I thought I would not have to change my existing code in the Action java
code, but my existing code did not work.  I originally had:

String username = ((LoginForm)form).getUsername();
String password = ((LoginForm)form).getPassword();

The LoginForm was the form bean that I had created manually in java.  I
deleted the LoginForm and replaced the form bean with a DynaActionForm as
listed above.  Of course, once I no longer have a LoginForm.java file
because it is a DynaActionForm, this Action java code does not compile.

Therefore I see that I have to change my code in going from a manually coded
form bean to a DynaActionForm.

Am I missing something?

TIA

Mark


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/2002

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

Re: DynaActionForm question

[Kris Schneider]

Pedantic clarification inline

Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>:

> 
> 
> On Sun, 19 Jan 2003, Mark Minnie wrote:
> 
> > Date: Sun, 19 Jan 2003 21:04:55 -0800
> > From: Mark Minnie <[EMAIL PROTECTED]>
> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: DynaActionForm question
> >
> > "Struts in Action" on page 162 reads:
> >
> > "You can use a DynaActionForm anywhere an ActionForm can be used.  You can
> also substitute a DynaActionForm for a conventional ActionForm without
> changing any of the existing Java or JSP code."
> >
> > I changed a ActionForm to a DynaActionForm by using the
> struts-config.xml:
> >
> >  type="org.apache.struts.action.DynaActionForm" dynamic="true">
> >
> >
> > 
> >
> > I thought I would not have to change my existing code in the Action java
> code, but my existing code did not work.  I originally had:
> >
> > String username = ((LoginForm)form).getUsername();
> > String password = ((LoginForm)form).getPassword();
> >
> > The LoginForm was the form bean that I had created manually in java.  I
> deleted the LoginForm and replaced the form bean with a DynaActionForm as
> listed above.  Of course, once I no longer have a LoginForm.java file because
> it is a DynaActionForm, this Action java code does not compile.
> >
> > Therefore I see that I have to change my code in going from a manually
> coded form bean to a DynaActionForm.
> >
> > Am I missing something?
> >
> 
> I think there was an implicit assumption in the sentence you quoted, that
> you were using BeanUtils or PropertyUtils to manipulate the properties.
> If your code had actually been:
> 
>   String username = PropertyUtils.getProperty(form, "username");
>   String password = PropertyUtils.getProperty(form, "password");

PropertyUtils.getProperty returns Object
BeanUtils.getProperty returns String

> 
> then you would indeed have had to make no changes when you swtiched from a
> standard ActionForm bean to a DynaActionForm.  If you're planning on
> experimenting with such switching, you might want to think about coding
> defensively like this.
> 
> > TIA
> >
> > Mark
> 
> Craig
> 
> 
> --
> To unsubscribe, e-mail:  
> 
> For additional commands, e-mail:
> 
> 


-- 
Kris Schneider 
D.O.Tech   

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

Re: DynaActionForm question

[Craig R. McClanahan]

On Sun, 19 Jan 2003, Mark Minnie wrote:

> Date: Sun, 19 Jan 2003 21:04:55 -0800
> From: Mark Minnie <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: DynaActionForm question
>
> "Struts in Action" on page 162 reads:
>
> "You can use a DynaActionForm anywhere an ActionForm can be used.  You can also 
>substitute a DynaActionForm for a conventional ActionForm without changing any of the 
>existing Java or JSP code."
>
> I changed a ActionForm to a DynaActionForm by using the struts-config.xml:
>
> dynamic="true">
>
>
> 
>
> I thought I would not have to change my existing code in the Action java code, but 
>my existing code did not work.  I originally had:
>
> String username = ((LoginForm)form).getUsername();
> String password = ((LoginForm)form).getPassword();
>
> The LoginForm was the form bean that I had created manually in java.  I deleted the 
>LoginForm and replaced the form bean with a DynaActionForm as listed above.  Of 
>course, once I no longer have a LoginForm.java file because it is a DynaActionForm, 
>this Action java code does not compile.
>
> Therefore I see that I have to change my code in going from a manually coded form 
>bean to a DynaActionForm.
>
> Am I missing something?
>

I think there was an implicit assumption in the sentence you quoted, that
you were using BeanUtils or PropertyUtils to manipulate the properties.
If your code had actually been:

  String username = PropertyUtils.getProperty(form, "username");
  String password = PropertyUtils.getProperty(form, "password");

then you would indeed have had to make no changes when you swtiched from a
standard ActionForm bean to a DynaActionForm.  If you're planning on
experimenting with such switching, you might want to think about coding
defensively like this.

> TIA
>
> Mark

Craig


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

RE: DynaActionForm question

[James Turner]

> From: Mark Minnie [mailto:[EMAIL PROTECTED]] 
>
> String username = ((LoginForm)form).getUsername();
> String password = ((LoginForm)form).getPassword();
> 
> The LoginForm was the form bean that I had created manually 
> in java.  I deleted the LoginForm and replaced the form bean 
> with a DynaActionForm as listed above.  Of course, once I no 
> longer have a LoginForm.java file because it is a 
> DynaActionForm, this Action java code does not compile. 
> 
> Therefore I see that I have to change my code in going from a 
> manually coded form bean to a DynaActionForm.  


Nope, one of the differences between DynaForms and conventional forms is
that Dynaforms are map-based, which means you need to rewrite those
lines as:

String username =  (String)((LoginForm)form).get("username");
String password = (String) ((LoginForm)form).get("password");

I got so sick of recasting to String that I wrote my own class which
extends DynaActionForm class and has getString helper methods in it.

James Turner
Owner & Manager, Black Bear Software, LLC
[EMAIL PROTECTED]

Author: 
MySQL & JSP Web Applications: 
Data Driven Programming Using Tomcat and MySQL
ISBN 0672323095; SAMS, 2002

Co-Author: 
Struts Kick Start
ISBN 0672324725; SAMS, 2002

Forthcoming:
Java Server Faces Kick Start 
SAMS, Fall 2003


> -Original Message-



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

RE: DynaActionForm question

[Anoop]

Hi,

Does DynaActionForm works only with struts v1.1 and later? Cause it is not
been bundled along with v1.0.2 struts.jar. Is there any alternative for this
in v1.0.2?

Thanks,
Anoop.

-Original Message-
From: Jean Pierre Pawlak [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 03, 2002 10:55 AM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: Re: DynaActionForm question


Hi,
I had also issues with this. But in fact, I use DynaActionForms and manage
the validating
from  the StrutsAction  without problem including selecting page only
validating.
Use .setPage() before .validate(...,...).
The 'struts-validator' example bundled with Struts 1.1b2 is a good starting
point.
JPP

- Original Message -
From: "Anoop" <[EMAIL PROTECTED]>
To: "'struts-user list'" <[EMAIL PROTECTED]>
Sent: Tuesday, September 03, 2002 6:52 AM
Subject: DynaActionForm question


> Hi,
>
> Do anyone has a startup example of how to use DynaActionForm instead of
> customary ActionForm bean. Would appreciate if anyone could provide with
an
> end to end working example with jsp implementation and the form beans.
And,
> which is the jar file to be used for the same. As, the standard struts jar
> doesn't have this packaged. Am using struts v1.0.2.
>
> Thanks a lot,
> Anoop.
>
>
> --
> 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: DynaActionForm question

[Jean Pierre Pawlak]

Hi,
I had also issues with this. But in fact, I use DynaActionForms and manage
the validating
from  the StrutsAction  without problem including selecting page only
validating.
Use .setPage() before .validate(...,...).
The 'struts-validator' example bundled with Struts 1.1b2 is a good starting
point.
JPP

- Original Message -
From: "Anoop" <[EMAIL PROTECTED]>
To: "'struts-user list'" <[EMAIL PROTECTED]>
Sent: Tuesday, September 03, 2002 6:52 AM
Subject: DynaActionForm question


> Hi,
>
> Do anyone has a startup example of how to use DynaActionForm instead of
> customary ActionForm bean. Would appreciate if anyone could provide with
an
> end to end working example with jsp implementation and the form beans.
And,
> which is the jar file to be used for the same. As, the standard struts jar
> doesn't have this packaged. Am using struts v1.0.2.
>
> Thanks a lot,
> Anoop.
>
>
> --
> To unsubscribe, e-mail:

> For additional commands, e-mail:

>
>



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