anonymous wrote : As you pointed out, specifying the validation in the PDL is
preferable to performing validation in the UI. I would recommend that the jpdl
schema be enhanced to support more validation. enhancing the schema is not
that difficult, creating the code behind it is.
If it is done
I also don't see the point of requiring a value but allowing it to be an empty
string. The point of requiring a value is so that you obtain the required user
input. In addition, sometimes you need to verify that the non-empty value meets
additional validation requirements (such as being a valid
I can't think of a case where I'd want empty string to be a valid value. Is
there some use-case I'm not thinking of?
It seems like it would be a pretty good usability increase to consider empty
strings as invalid.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtop
JSF posts an empty value in many cases. So the required attribute IS enforced
(the required attribute is in the pd), only with an empty value!!!.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070421#4070421
Reply to the post :
http://www.jboss.com/index.ht
One of the reasons I'm using the JSF form validation is that the "required"
attribute isn't enforced in the process definition, e.g. :
|
|
|
|
|
|
|
|
|
|
|
|
You can open the corresponding form for this node in the jbpm
difficult... Since in this case the process does validation to (as it should,
never trust the UI). you can do conditional required here with e.g. a EL with
reference to the transition name. Difficult , but it could be done. Doing this
on the process level is more difficult. I therefore started a
Maybe required=true is inappropriate here, since it isn't actually required by
all transitions.
Can you set the required=false, then do transition specific validation?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069756#4069756
Reply to the post :
http://
that is because there is not only validation on the form (with the
required=true) but also in the PD. That validation cannot be bypassed.
Please file a jira issue with this request. It might be picked up, it might not
be.
View the original post :
http://www.jboss.com/index.html?module=bb&op=v
Can you see the transition from the validator? That's the only (bad) solution I
found right now.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069506#4069506
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069506
_
