Today I had the problem that one of my webservice methods always threw this - not very telling - exception:
javax.xml.ws.WebServiceException: No Content-type in the header!
After some Google research I found out that there's the following flag, which enables extended logging for java webservice calls. This system environment setting must present when Tomcat (or any other webserver) is starting:
-Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
Using the output I quickly found the problematic piece of code.
Dienstag, 19. Juli 2011
Mittwoch, 10. März 2010
More about required="true" and partialSubmit
After some research in the iceFaces forums I found out that partialSubmit by design disables all required=true settings on all the form's fields but the current one.
The question remains why required=true does not come back on subsequent form submits....
The question remains why required=true does not come back on subsequent form submits....
ICEFaces validation and required="true"
Today I found out the following about ICEFaces 1.8.2 validation:
Thanks for comments and work arounds or clarifications.
- required="true" does not work whenever a partial submit is sent (e.g. by an user selecting a date with an ice:selectInputDate)
- as a consequence empty fields which have required="true" set just don't throw an validation error
- other validators trigger correctly
- this behaviour is even more problematic because in subsequent form submits (partial or complete ones) the required="true" behaviour does not come back, so it's possible to send the form without filling out the fields which are marked as required="true"
Thanks for comments and work arounds or clarifications.
Abonnieren
Kommentare (Atom)