David,
No, I have not seen this behaviour before. I tried to reproduce it in my
app, by pasting your enctype="multipart/form-data" attribute into my
form. However, I still got generated action attributes with a .faces
extension.
I did, however, run into crippling problems in my application once I
added this attribute. After browsing to the page with this form on it,
clicking any button on that page resulted in the following exception:
java.lang.NoClassDefFoundError:
org/apache/commons/io/output/DeferredFileOutputStream
I don't normally have an enctype attribute set on my forms, and they
work great without one. I notice that when I don't set this attribute,
the generated forms have enctype="application/x-www-form-urlencoded".
I don't know if this attribute has anything to do with your problem
(since I wasn't able to reproduce it) but perhaps it's worth looking at.
Is that there to ensure compatibility with some other technology you are
using?
Also, what versions of the jars are you using?
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
David Delbecq wrote:
In one of my webapps, i have a very strange behaviour for myfaces form tag.
When i put in <webapp>/jsp/test-jsf.jsp the the form tag:
<h:form id="instanciate" enctype="multipart/form-data">
.....
</h:form>
and i point my browser to
<webapp>/jsp/test-jsf.faces i see myfaces has rendered the form tag
like this
<form id="instanciate" name="instanciate" method="post"
action="/shark-DemoSite/jsp/test-jsf.jsp" enctype="multipart/form-data">
As you see, form action points to a jsp instead of a .faces, I have
never had this behaviour before in another app, has anyone already
experienced this and can suggest me where to look at?
Thanks
David Delbecq
Royal Meteorological Institute of Belgium
