Bill,
>pass information from the browser to the Action. You shouldn't use
>ActionForms to pass arbitrary data from java code to JSP code, except
>for pre-populating form fields.)
Could you please explain with example for this?
I'm not sure what "pass arbitrary data from java code to JSP code" means?
>Regarding struts-config.xml: in OzStruts, it's too bad that you have to
>register OzPage (ActionForm) and register Listener (Action) separately.
>Conceptually, they are the same thing, right? I just want to say
No, Page registration and listener registration is different.
And I don't think it's so bad, becasue I didn't change anything from Struts.
Page registration is Form registration.
<form-bean name="AddVendorPage" type="foo.bar.AddVendorPage"/>
Listener registration is action definition.
<action path="/blah/blah/addVendor"
name="AddVendorPage"
This is exactly the same as we have now.
This means on "/blah/blah/addVendor.do"
AddVendorPage.addVendor will be invoked in OzStruts.
The main idea is not changing any existing configuration,
and I just want to use proven part as it is.
If I need to modify it, I'd better to go to new frameworks, JSF, Tapestry,
ECHO...
>something like this:
>
><ozPage
> input="/webpage/ozstruts/vendor/addVendor.jsp"
>
>type="net.sourceforge.optionzero.ozstruts.sample.webapp.ozstruts.vendor.AddVendorPage">
> <forward name="VendorDetailPage"
>path="/webpage/ozstruts/vendor/vendorDetail.jsp"/>
> <forward name="AddVendorPage"
>path="/webpage/ozstruts/vendor/addVendor.jsp"/>
></ozPage>
>
I guess this defines corresponding JSP as input,
and defines possible transition pages from it.
But we need to use this in action mapping, but how?
I'm sorry it's little difficult to me.
Anyway, thanks so much for your feedback.
Tak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
