[ajug-members] <html:select> inside<logic:iterate>
shyam mohan srivastava
smsrivastava77 at rediffmail.com
Wed Jun 16 06:48:12 EDT 2004
An HTML attachment was scrubbed...
URL: http://www.ajug.org/pipermail/ajug-members/attachments/20040616/6ceab030/attachment.html
-------------- next part --------------
hello All
I am doing struts . I am facing one problem with <html:select> inside <logic:iterate>. I want to post multiple select value of select list which is inside the <logic:iterate>.
JSP Page:->
<logic:iterate id="edit_doc" name="edit" >
<html:select property="pk_login_type" name="edit_doc" multiple="true" size="2" >
<html:options collection="docs_select" labelProperty="var_login_type" property="pk_login_type_id" />
</html:select>
</logic:iterate)
Action Form Class:->when i load this page
public void setEdit(Vector edit){
this.edit=edit;
}
public Vector getEdit(){
return edit;
}
Action Form Class:->when i post this page then bean form of other page
public void setEdit(Vector edit){
this.edit=edit;
}
public Vector getEdit(){
return edit;
}
Action Class for reterive value
Vector edit=EdSuppUpdate.getEdit();
Iterator iter = edit.iterator();
while(iter.hasNext())
{
String[] ashwani=(String[])iter.next();
for(int k=0;k<ashwani.length;k++)
{
System.out.println("ashwani ==>"+ashwani[k]);
}
}
It does not print. I think i am not doing right.
please help me soon.
thanks in advanced.
shyam
On Wed, 16 Jun 2004 Rob Kischuk wrote :
>We have been using Quartz in production now for 8-10 months now. Much like you describe, we are using it for nightly maintenance - transfer of data between systems, triggering events in our workflow systems, and flagging of exception conditions. We're using the CronTrigger style of trigger, which lets you use full cron expressions to trigger your task. We are using JBoss' version of a startup task, an MBean, to configure the SchedulerFactory.
>
>Our experience has been seamless. It has been so reliable that, quite honestly, I don't even remember that we use Quartz. I just know that the maintenance tasks will run. Our failures have been due to our mistakes, never anything we could track back to Quartz. It's one of those simple little frameworks that you can incorporate into your systems and it will _just_ _work_, at least from our experience.
>
>To give you an idea, this is our code that configures the scheduler:
>
> SchedulerFactory factory = new StdSchedulerFactory();
> sched = factory.getScheduler();
> sched.start();
> CronTrigger trig = new CronTrigger("Daily trigger", Scheduler.DEFAULT_GROUP);
> trig.setCronExpression("0 0 2 * * ?");
> JobDetail jobDetail = new JobDetail("maintenanceJob",
> Scheduler.DEFAULT_GROUP,
> this.getClass());
> sched.scheduleJob( jobDetail,trig);
>
>All that's required is that the class specified in the JobDetail constructor implements the org.quartz.Job interface, which requires an execute(JobContext) method. Fairly clean, not too intrusive.
>
>-Rob
>
>Jason Chambers wrote:
>
>>I am considering using OpenSymphony Quartz as a replacement for cron. The jobs I need to run are data maintenance, purging, reconciliation and export type stuff. Today it is a hodge-podge of Java, Pro*C, Korn-shell, Perl, C and so on all driven by cron. I want to retire all of this crap and standardize on Java.
>>
>>What are your experiences of using Quartz?
>>_______________________________________________
>>ajug-members mailing list
>>ajug-members at ajug.org
>>http://www.ajug.org/mailman/listinfo/ajug-members
>
>
>_______________________________________________
>ajug-members mailing list
>ajug-members at ajug.org
>http://www.ajug.org/mailman/listinfo/ajug-members
More information about the ajug-members
mailing list