JSF Validation failure causes entered values to be lost

I've created a JSP that has required="true" and a requiredMessage on several elements.
If any one element on the page fails it's validation on submit(ie was left blank), when the screen is redrawn all the entered values have disappeared.
This is obviously not going to be acceptable to a user as there may have been 5 valid entries and one mistake, and they now have to retype every entry.
Can anyone suggest why the form might be being cleared like this?

I'm using reference implementation 1.2 04-b10
I've tried using an implementation of validator and it makes no difference.
It's the only example of an inline validator other than required, which seems to work ok.
I've got around the problem for now by doing the validation in the method called when the user hits submit. It's not quite right as if the 'required' validation fails they get mutliple messages showing these failures, but the codeRef validation doesn't even fire until all the other validation passes.

Similar Messages

JSF Validation failure causes input values disappear

I am using a custom validator in my application by creating a class that implements javax.faces.validator.Validator. I use this validator for some input fields. When the validation fails the values that the user has entered are lost. Is their any way that we can keep these values? These input fields are in DataTable.
- Sandeep.
Edited by: sgatl2 on Mar 24, 2010 10:41 AM

If you see the JSF lifecycle, the validation phase comes before the update values phase.
So if your custome validator fails, the model will not change.
I would suggest you try with client side validation without a page refresh/server call.

Editing a field in ALV and validating the newly entered Value

Hi Experts,
   I have an ALV report in grid display (not object oriented). My requirement is to edit a field on the output and write the validations to validate the value that was edited on the ALV output.
This can be done using object oriented coding by using the method check_changed_data. For this to happen, i need to change the entire scope of my report into object oriented, which is like reinventing the wheel.
Since my report was developed using classical ABAP, what needs to be done to get this functionality. Any suggestions are welcome.
Thanks.

in the FM 'REUSE_ALV_GRID_DISPLAY' import parameter IS_LAYOUT check out the columsn EDIT and EDIT_COLUMN. Also Use FM 'REUSE_ALV_EVENTS_GET' to get list possible event and pass a subroutine name which will be called when ever event is fired.
example:
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      i_list_type = 0
    IMPORTING
      et_events   = l_events.
READ TABLE l_events WITH KEY name = slis_ev_top_of_page
                               INTO g_event.
IF sy-subrc = 0.
    MOVE top_of_page TO g_event-form.
    APPEND g_event TO t_events.
ENDIF.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_buffer_active    = 'X'
      i_callback_program = t_repid
      is_layout          = t_layout
      it_fieldcat        = t_fieldcat[]
      i_save             = t_save
      it_events          = t_events[]
    TABLES
      t_outtab           = g_editpos1[].

Validation failure resetting the values

Hi,
when ever the validation fails on a specific text field, it is resetting the value of the field. Is there any possibility to retain the value in the text field even the validation fails.
Thanks and Regards,
S R Prasad

I created the validation rule on entity attribute and then created inputText on the user interface. If the validation fails it is resetting the value of the field to the original value (I have tested it on the data field)
Thanks and Regards,
S R Prasad

Retain all form field values after input text field validation failure

Hi,
I have a form with 1 input text field, one Command button and one h:selectManyListbox. when User enteres some values in input field and clicks on command button named Add, the value is validated. If input is invalid, then an error message appears next to the field. If input is valid, then the value is added into h:selectManyListbox. Adding to list box is done using Ajax4Jsf.
Probelm:
Let's assume user entered 3 valid values one after another and all are added into the list box. When he enters a wrong value, and error message appears. however, the entered values in list box goes away. Is there a way to retain the values even after validation failure.
Code is given below;
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%>
<%@ taglib uri="http://richfaces.org/rich" prefix="rich"%>
<%@ taglib uri="http://richfaces.org/a4j" prefix="a4j"%>
<h:panelGroup>
     <h:outputLabel for="inputEmailId1" value="Email Id: " />
     <t:inputText value="#{bean.newEmailId}" id="inputEmailId1" maxlength="100" size="40" immediate="true">
          <t:validateEmail message="Enter a valid Email Id." />
     </t:inputText>
     <t:message for="inputEmailId1" styleClass="errorStyleClass" />
</h:panelGroup>
<t:panelGroup style="text-align: left;" >
     <a4j:commandButton value="Add" styleClass="buttonsSub" action="#{bean.addSharedEmails}"
          reRender="inputEmailId1, selectedSharedEmails" />
</t:panelGroup>
<t:panelGroup style="text-align: left;">
     <h:selectManyListbox id="selectedSharedEmails" size="8" style="width:100%;" immediate="true">
          <f:selectItems value="#{bean.sharedEmails}" />
     </h:selectManyListbox>
</t:panelGroup>
Thanks in advance,

Use the attribute "binding" instead of a "value". This will remember the value. You can also make sure that you dont have anything in your constructor or class level that initialises that value to "" or null. Because if JSF is remembering your value but your initialization that gets triggered before the page loading resets it to default values then you need to change that part of the code.

User entered values are lost on EO validation.

Hi ,
Subject : user entered values are lost on EO validation.
WE have an EO which has 4 attributes all are not null (mandatory)
There is a VO based on this EO
We have added 4 more attributes using a join in EO query using expert mode.
On the page there is a Table , that has 8 columns all mapped to these 8 attributes.
The First column is an LOv that populates 4 column attributes(2 EO based and 2 added thru expert mode)
When the user submits the page, without entering rest of the two EO mandatory atributes, the EO validation is raised and the 4 fields populated by LOv are cleared.
Can you pls tell me what am i doing wrong.
thanks
Chaitanya

Observation
All the table columns that were loosing information were "MessageStyledText" and those not loosing were "MessageTextInput"
Various approaches
SO we converted the MessageStyledText columns into MessageTextInput and the data was retaining properly.
But we wanted these columns are 'ReadOnly' so when we made these columns are MessageTextInput - ReadOnly, then data was not getting popluated by the lov in these.
Working solution - The FormValue 'Glue'
We created formValues correcponding columns and populated the FVs also along with the column (both FV and column have same ViewAtt and View instance) and found that in this case the formvalues 'Glues' the VO att value with the page and does not get lost on refresh.
Strange solution but works, thought to share with all.
thanks
Chaitanya

Error «The entered value is not on the list of valid values» in the hierarchy of mss web dynpro abap

Hello Experts
The error «The entered value is not on the list of valid values» in the hierarchy of mss web dynpro abap occurs after manager’s following actions:
selected detailed Team View ;
selected hierarchy;
changed style of the hierarchy to any other (for example, the vertical);
the error occurs after attempting to do any action.
Our system is EHP7.
If someone faced with this error, please give me advice how can i resolve this problem.

Hi John,
Sorry for the delay in replying. No, we do not have the same problem if we understand you correctly.
"We have bypassed the MSS Home Page and just embedded the Detailed Team View as a standalone application in our MSS portal role" - we also made for the our customer. BUT we have error «The entered value is not on the list of valid values» in our standard system.
Regards,
Andrey

Checkbox error "The Entered Value is Not on the List of Valid Values".

Hi All,
I have a check box attribute inside a node which is bounded to a field of type CHAR 1. I have given the property and value for the attribute as follows:
Attribute Name     ZCHECK
Type assignment     Type
Type                          ZTABLE-ZCHECK
Read-only                         0
Default Value
Null Value                           0
Input Help Mode     Automatic
Determined Input Help     ZCHECK
Type of Input Help     Fixed values for domains
Formatting
Compression     Default Value
I have created an onToggle Event for it.
Now when i execute my component i do the following.
First i click on a button called 'EDIT'. Now the check box comes to edit mode. Now when i click on the checkbox i get the following error. "The Entered Value is Not on the List of Valid Values".
When i try to debug, there is no problem in the 'INIT' method. The error is throw even before going inside the onToggle Event for check box.
Please explain how to over come this.

Hi,
Check your field ZTABLE-ZCHECK, if it is of type CHAR1 then only possible values for checkbox should be 'X' and ' '.
May be your domain has some other values in Fixed Value List.
its better to bind checkbox with attribute of type boolean
Also, the input help for attribute bound to checkbox doesn't makes any logic.
Regards
Manas Dua
Edited by: Manas Dua on Feb 26, 2010 3:11 PM

Switching dynamic tabs causes loss of entered values

I am running into a fundamental issue with dynamic tabs.
When the user has multiple tabs open, and he is busy entering values in one tab, and then switches to another tab without saving the values in the first tab, the entered values in the first tab are lost when the user triggers at least one http request in the new tab. If the user switches to the new tab, does not do anything and returns immediately to the first tab, the entered values are still there. I understand that the JSF model update phase is skipped when switching tabs because immediate="true". But the apply request values phase is still performed, so the UI components should still have the submitted value. Somehow, these values get lost when a subsequent request is send while those UI components are no longer visible. I tried changing the rendered property of the regions in the page template to "visible" so the UI components are kept in the component tree, but that didn't help.
Th idea of temporarily switching to another task, similar to switching browser tabs, is undermined with this behavior because end users don't like it when some of their work is lost.
Does anybody know a solution for this problem?
Thanks,
Steven.

I think you need to use static instead of dynamic regions that way you can keep the region modification across all the tabs. The visible property on the regions some how its not working for me so I am surronding each region with PageGroupLayout and setting the visible property to it and set rendered property to region. The visible property and rendered property condition can be controlled by the tab action.

Set_Block_Property invoke has caused the earlier enter value get disappear

Hi all,
I got a simple field which set to let user to enter a value and from the entered value user will need to press the button to search for the next display value. I have set when_button_pressed with set_block_property
go_block('ot_mat_iss_head');
Set_Block_Property('OT_MAT_ISS_HEAD', default_WHERE, 'MIH_NO = '''|| :OT_MAT_ISS_HEAD.MIH_NO1 ||''' ');
go_block('OT_MAT_ISS_HEAD');
execute_query;
the above query work fine where I got the next field display with value that what I want. However, the first column that ask user to enter the value was get disappeared. How come ? How to get it display in this case ?
Thanks.
Regards,
Lim

The first column where I ask user to enter value was in the same block with the second column that display the value. Immediately, the second value get display the first value get disappeared after press on the button.This is expected. Because your non-base table item is part of the block you are querying, when you call EXECUTE_QUERY, it clears the block (including any non-base table items) and queries the selected record.
If you want the search value to continue to be displayed in your non-base table item, then move the non-base table item to a Control block (non-base table block). Then the EXECUTE_QUERY will not affect the value of the item.
OT_MAT_ISS_HEAD.MIH_NO1 is a non db field. If I changed to DB field when I execute the button, system will prompt to ask me whether want to save my record.Again, this is expected because Forms recognizes that you have changed a record displayed in your table. Therefore, Forms will ask you if you want to save your changes. If you want to continue to display the searched value in your non-base table item, move it to a Control block.
Craig...

Validation of column fields while entering values in editable ALV

Hi,
I am currently working on a ALV,I have to validate the editable field of ALV,while entering values.SO if there is a field Item number,the range should be between M01-M99,and user should not take any value other than the F4 help assigned to the field.Can all this calculation be done using a FM & Not OOPs process for making ALV.
Please advice.
Thanks.

>
p317980 wrote:
> REF_TABNAME LIKE DD03P-TABNAME,
> Will the field just pick values from the F4 & not any random value entered by user?
>>yes.
> if these values entered at runtime need to be saved into a Ztable,will I have to use Classes for defining my ALV?
>>write some code to check if the entry exists.. if not then update the Ztable..
>>select single field from table. if sy-subrc eq 0. fine else. update ztable.if.

Dynamic values for JSF selectOneMenu using javascrpt. JSF validation error.

Hi,
Im using Myfaces 1.2 (tomahawk) . I have a very bulky page having lot of drop down menus. It has a datatable containing four drop downs in a row and the datatable has close to 40 rows (with pagination) . Each of the drop downs have close to 100 items . This makes the page size very huge and not suitable for an internet application.
Im thinking of a way to have the drop downs populated using javascript in body onload event so that the page size reduces drastically. I have defined a selectOneMenu without selectItems. So before page load there will be no items in the drop down. The body onLoad method populates the drop downs and the page gets rendered as expected. All the javascript events related to these drop downs works fine. When page is submitted i want the selected value in the bean variable.
But when the page gets submitted im getting the error
Validation Error: Value is not valid
Can someone let me know the reason behind this and a way to solve this problem . Its really URGENT...
Please help....
Thanks,
Swami.

JSFdeveloper wrote:
Validation Error: Value is not valid During validations phase, the submitted value of UISelectOne/UISelectMany will be tested against the current SelectItems. If it is not covered by the SelectItems, you will get this error.
Its really URGENT...This is your own problem, not our problem. This way you're only trying to move the problem/pressure to us and pushing us to respond soon. This is considered very rude in terms of netiquette. Next time you do so, I have no problem adding you to my ignore list. [Just ask questions the smart way|http://catb.org/esr/faqs/smart-questions.html].

Bug with validation or rendering after validation failure (?)

Can anyone confirm the behaviour on other J2EE containers that I will describe below ?
h2. Environment:
JBoss 7.1.1 (Brontes)
JDK 1.7.0_06 32-bit
Win7 64-bit
17:40:44,365 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-13) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401)Below is the very simple test case:
h2. 1) A very simple request-scoped bean:
package test;
import java.io.Serializable;
import javax.faces.bean.ManagedBean;
import javax.faces.bean.RequestScoped;
import javax.validation.constraints.NotNull;
@ManagedBean
@RequestScoped
public class RequestBean implements Serializable {
     private static final long serialVersionUID = 1L;
     @NotNull(message="Input 1 is required")
     private String input1;
     @NotNull(message="Input 2 is required")
     private String input2;
     public String getInput1() {
          return input1;
     public String getInput2() {
          return input2;
     public void setInput1(String input1) {
          this.input1 = input1;
     public void setInput2(String input2) {
          this.input2 = input2;
}h2. 2) A very simple test.xhtml page:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:h="http://java.sun.com/jsf/html"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:ui="http://java.sun.com/jsf/facelets">
<h:head></h:head>
<body>
<h:form>
       <h:panelGrid columns="2">
           Input 1: <h:inputText value="#{requestBean.input1}" />
           Input 2: <h:inputText value="#{requestBean.input2}" />
           <h:commandButton id="submit" value="Submit"/><br/>
           <h:messages/><br/>
       </h:panelGrid>
</h:form>
</body>
</html>h2. 3. web.xml contents:
<?xml version="1.0"?>
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<display-name>test</display-name>
<context-param>
<param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>

<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.faces</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
</web-app>h2. 4. faces-config.xml contents:
<?xml version="1.0" encoding="UTF-8"?>
<faces-config
    xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_1.xsd"
     version="2.1">
</faces-config>h2. 5. Contents of WEB-INF/lib:
salvojo@AAS-AUD20901BL /cygdrive/c/jboss-as-7.1.1.Final/standalone
$ ls -alt deployments/test.war/WEB-INF/lib/
total 1384
drwx------+ 1 Administrators Domain Users      0 Nov 2 17:40 ..
drwx------+ 1 Administrators Domain Users      0 Nov 2 16:56 .
-rwx------+ 1 Administrators Domain Users 393259 Nov 2 16:56 standard.jar
-rwx------+ 1 Administrators Domain Users 21029 Nov 2 16:56 jstl.jar
-rwx------+ 1 Administrators Domain Users 38015 Nov 2 16:56 commons-logging.jar
-rwx------+ 1 Administrators Domain Users 139966 Nov 2 16:56 commons-digester.jar
-rwx------+ 1 Administrators Domain Users 559366 Nov 2 16:56 commons-collections.jar
-rwx------+ 1 Administrators Domain Users 188671 Nov 2 16:56 commons-beanutils.jar
-rwx------+ 1 Administrators Domain Users 48742 Nov 2 16:56 common-annotations.jarh2. 6. The test case
h4. 6.1 Open the test.jsf page with your browser
h4. 6.2 Click on Submit WITHOUT specifying any values for both Input1 and Input2.
Expected behaviour: Messages displayed that both input fields are required.
Actual: As expected
h4. 6.3 Supply values for both Input1 and Input2, then click Submit
Expected behaviour: No validation messages displayed. Entered values remain in the input field
Actual: As expected
h4. 6.4 Remove input value for Input1, then click Submit
Expected behaviour:
Validation message that Input1 is required.
Current value for Input1 remain blank.
Previous value for Input2 remain in the input field.
Actual: As expected
h4. 6.5 Remove input value for Input2, then click Submit ( both Input fields are now blank )
Expected behaviour:
Validation message both input fields are required.
Input value for Input1 remain blank.
Input value for Input2 remain blank.
h3. Actual ( NOT AS EXPECTED, see below )
Validation message both input fields are required.
Input value for Input1 remain blank.
Input value for Input2 remain NON-blank. The previous value before it was blanked out and submitted is rendered / displayed on the page*

gimbal2 wrote:
jmsjr wrote:
I thought I was going crazy !Why? You created proper test cases and you proved something was off. At that point you get realistic, not crazy.
Perhaps you simply need to get it into your system to look for an issue tracker to see if something is known about it :)Yup. It is described in:
http://java.net/jira/browse/JAVASERVERFACES-2262
http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-939
However, as mentioned here, I have now found a different issue as described in that JBoss forums when using the same EL expression / same bean property:
in 1 inputText and 1 disabled inputText and 1 outputText or
in 1 inputText and 1 disabled inputText or
in 1 inputText and 1 outputText

JHS and JSF Validation Conversion Error Customizations

Hello
Have JHS done any work about JSF validation or conversion error customizations?
I mean the error messages such as "lablename:"value mus be entered etc.
What can i do if i want to globally customize and localize this error messages.
I have copied the key such as "javax.faces.component.UIInput.REQUIRED" in my appdeff resource bundle but JHS (or maybe ADF) gives own message yet.
I Apologize if my problem don't depend on JHS. I wonder that JHS overrided JSF default messages.
Thank You

JHeadstart does not use any JSF standard message.
JHeadstart uses ADF Faces which comes with its own bundle of error messages.
Please use the JDeveloper forum for instructions on modifying ADF Faces error messages.
Steven Davelaar,
JHeadstart Team.

Trying to understand a WS-I validation failure

I'm trying to understand the following WS-I validation failure message. I'm sure I'm making a basic mistake but I can't find an example of the use case where an xsd is imported. Can someone point out my error?
Thanks,
Bret
Validation failure:
Result failed:
Failure Message: A QName reference that is referring to a schema component, uses a namespace not defined in the targetNamespace attribute on the xs:schema element, or in the namespace attribute on an xs:import element within the xs:schema element.Failure Detail Message:
{http://Messages.xsd}SigReplyMessage,
{http://schemas.xmlsoap.org/wsdl/}string,
{http://Messages.xsd}SigRequestMessage
Element Location: lineNumber=8
My wsdl looks like this:
<definitions targetNamespace="urn:S3SignatureGenerator"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="urn:S3SignatureGenerator"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:messages="http://Messages.xsd">
<types>
<xsd:schema>
<xsd:import id="Messages.xsd"
schemaLocation="../../XSDDocument/Messages.xsd"
namespace="http://Messages.xsd"/>
</xsd:schema>
</types>
<message name="ReturnSignature">
<part name="SigAndExp" type="messages:SigReplyMessage"/>
</message>
<message name="RequestSignature">
<part name="Keys" type="messages:SigRequestMessage"/>
</message>
<portType name="SigGenerator">
<operation name="GetSignature">
<input message="tns:RequestSignature"/>
<output message="tns:ReturnSignature"/>
<fault name="sigFault" message="tns:SigFault"/>
</operation>
</portType>
<message name="SigFault">
<part name="faultMessage" element="string"/>
</message>
<binding name="SigGenSoapHttp" type="tns:SigGenerator">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="GetSignature">
<soap:operation soapAction="urn:S3SignatureGenerator/GetSignature"/>
<input>
<soap:body use="literal" parts="SecretKey PublicKey"/>
</input>
<output>
<soap:body use="literal" parts="Signature"/>
</output>
<fault name="sigFault">
<soap:body use="literal" parts="SecretKey PublicKey"/>
</fault>
</operation>
</binding>
<service name="SignatureGenerationService">
<port name="SigGenSoapHttpPort" binding="tns:SigGenSoapHttp">
<soap:address location="tbd"/>
</port>
</service>
</definitions>
Messages.xsd looks like this:
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.bret.org/S3test/Messages"
targetNamespace="http://www.bret.org/S3test/Messages"
elementFormDefault="qualified">
<xsd:complexType name="sigRequestMessage">
<xsd:sequence>
<xsd:element name="publicKey" type="xsd:string"/>
<xsd:element name="privateKey" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="sigReplyMessage">
<xsd:sequence>
<xsd:element name="Signature" type="xsd:string"/>
<xsd:element name="expiration" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Hi Bret,
Sorry it's taken me a bit of time to respond, but please find below a run-down of the WS-I related problems I spotted in your WSDL document. The first few are related to the import error you saw, and there's a few others that I'll also discuss. Apologies in advance if you've already spotted and corrected those.
I'll use line numbering based on the formatting of the WSDL and XSD that you supplied.
BP2417 (the one you asked about)
The line number in the error is a red herring. There are two problems here:
- WSDL document, line 29: You're using the XSD type string unqualified - it should be xsd:string.
- WSDL document, lines 8 and 13; schema, lines 3 and 4: The namespaces you're using don't match. Either change the namespaces in the schema to be http://Messages.xsd, or change the namespaces in the WSDL to http://www.bret.org/S3test/Messages.
BP2202
You should declare UTF-8 or UTF-16 encoding when creating WSDL or schema documents. The easiest way to do this is to go to Tools|Preferences, and set JDeveloper's default encoding to either UTF-8 or UTF-16.
BP2032
WSDL document, line 26 and 43: The name attribute of the fault should read SigFault, not sigFault, as WSDL is case-sensitive.
WSDL document, line 44: You should use a soap:fault element, not a soap:body element, to bind a fault, thus:
<soap:fault name="SigFault" use="literal"/>
BP2012
WSDL document, lines 17 and 20: Message parts in a document-bound service like this one should reference XSD elements and not complexTypes. What you need to do is define two elements in your messages schema whose types are SigReplyMessage and SigRequestMessage respectively, and then reference those elements from the WSDL.
WSDL document, line 38: The value of the parts attribute should be Keys to match the name of the part child of the RequestSignature.
WSDL document, line 41: The value of the parts attribute should be SigAndExp to match the name of the part child of the ReturnSignature.
WSDL document, line 44: The value of the parts attribute should be faultMessage to match the name of the part child of the SigFault.
BP2115
WSDL document, lines 17 and 20: The names of the elements should be sigReplyMessage and sigRequestMessage and not SigReplyMessage and SigRequestMessage, again because WSDL is case-sensitive.
WSDL document, line 30: The element attribute of the part references xsd:string, which is not an element but a complexType. You'll need to add an element declaration to your schema, which is of type xsd:string.
I've included corrected versions of your WSDL and schema below, I hope this helps. I also note you've posted a few other messages related to WS-I and WSDL, I hope I've managed to cover those in this message too.
Regards,
Alan.
WSDL:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="urn:S3SignatureGenerator"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="urn:S3SignatureGenerator"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:messages="http://Messages.xsd">
<types>
<xsd:schema>
<xsd:import id="Messages.xsd"
schemaLocation="Messages.xsd"
namespace="http://Messages.xsd"/>
</xsd:schema>
</types>
<message name="ReturnSignature">
<part name="SigAndExp" element="messages:sigReplyMessage"/>
</message>
<message name="RequestSignature">
<part name="Keys" element="messages:sigRequestMessage"/>
</message>
<message name="SigFault">
<part name="faultMessage" element="messages:faultMessage"/>
</message>
<portType name="SigGenerator">
<operation name="GetSignature">
<input message="tns:RequestSignature"/>
<output message="tns:ReturnSignature"/>
<fault name="SigFault" message="tns:SigFault"/>
</operation>
</portType>
<binding name="SigGenSoapHttp" type="tns:SigGenerator">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="GetSignature">
<soap:operation soapAction="urn:S3SignatureGenerator/GetSignature"/>
<input>
<soap:body use="literal" parts="Keys"/>
</input>
<output>
<soap:body use="literal" parts="SigAndExp"/>
</output>
<fault name="SigFault">
<soap:fault name="SigFault" use="literal"/>
</fault>
</operation>
</binding>
<service name="SignatureGenerationService">
<port name="SigGenSoapHttpPort" binding="tns:SigGenSoapHttp">
<soap:address location="tbd"/>
</port>
</service>
</definitions>
Schema:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://Messages.xsd"
targetNamespace="http://Messages.xsd"
elementFormDefault="qualified">
<xsd:element name="sigRequestMessage">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="publicKey" type="xsd:string"/>
<xsd:element name="privateKey" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sigReplyMessage">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Signature" type="xsd:string"/>
<xsd:element name="expiration" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="faultMessage" type="xsd:string"/>
</xsd:schema>

JSF Validation failure causes entered values to be lost

Similar Messages

Maybe you are looking for