Nope, doesn't do multi-part forms as yet. But, you can just configure it to not have a form and then use one of the many multi-part libraries (in otherwords, it doesn't prevent you, I hope). It would be nice though to be able to say, "And this controller takes a submitted file which should go here."
I didn't go the <param> route because I didn't know about it when I started, and by the time I was done, it was so easy to do JDOM that it ended up being about the same. I personally like knowing that something has a form clearly. Also, I'm using a SingletonController, so this is expected behavior since the JDOM element is passed to the .init method for you to examine. Actually, I think you would handle your parameters in the same way I'm doing the <form> tags with a SingletonController.
Zed
On Tuesday, January 7, 2003, at 05:13 AM, Aapo Laakkonen wrote:
Does it work with multipart forms?I also managed to write a fairly complete base controller which integrates with FormProc to give you semi-automated form validation.
I did build yesterday something similar, althought I used more
lightweight approach. I did not introduce any new tags, as what I can
see you did. I just used controller parameters, eg.:
<controller ...>
<param name="form" value="loginForm" />
<!--
or maybe
<param name="extendedForm" value="loginForm" />
-->
</controller>
Then I just build a few abstract classes. I use only the validation part
of the FormProc.
I'm thinking about implemeting something similar for Authorization:
<controller ...>
<param name="rolesRequired" value="manager publisher" />
</controller>
This is my approach... maybe you did it better, but this works fine for
me.
----- Zed A. Shaw http://www.zedshaw.com/
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com [INVALID FOOTER]
