Attribute Validation error.     

I keep getting this error. It is so damn vague.

Exceptions
13:27:07.007 - Template Exception - in D:\Coldfusion
Applications\b2\security tests\control.cfm : line 34
Attribute Validation error.

Similar Messages

  • Getting mandatory attribute validation error when the value is defaulted through customization

    Hi
    I am getting Mandatory attribute validation error when we default the value through customization.
    In the UI we have attribute called Last Name which is mandatory at EO level. Customer wanted to default Last name to some value, through page composer it is defaulted to some text and saved.
    When ever we open the page the the same value is defaulted as Last Name and appearing in the UI. But when we submit the page, EO level validation is failing. hence we are getting last name is missing.
    When i debug the code last name attribute value for EO is blank.
    In the UI the attribute last name is associated with bindings  --> #{bindings.lastname.inputvalue}
    The validation is failing if we remove the default binding associated with inputtext box.
    Can some body help what can be reason and is there any solution?
    Thanks,
    Praveen

    version 12.1.2
    I am struggling with same situation, I can't set the default value at business component because, the default value comes from a REST service at run time. In page A,  I have a field F1 that contains value from REST service. Page B has a database bound field F2, whose default value should come from F1 in Page A when a user navigates from Page A to Page B. If I set the value of F2 to be the value of F1, then it displays the value in the UI, but nothing gets submitted to EO and fails at commit.
    To make things difficult, here is my situation: Page A lives in bounded taskflow TF1, and Page B lives in bounded taskflow TF2. So I have created an input parameter P1 in TF 2, which carries over the value of F1 in Page A to Page B. When I am in Page B, I can successfully see the value of the taskflow input parameter P1. So, how do I  programmatically set the value of field F2 with the value of input parameter P1?
    I tried setting the F2.inputValue  in a method call M1 in  taskflow TF2 prior to Page B, but I get null pointer exception as it can't see field F2 yet.
    It seems like a simple thing to do, but I have spent a lot of time trying to make it work without any success.
    I would greatly appreciate any guidance.

  • Attribute validation error for tag CFQUERY

    I have a CF application that's running fine on a shared host. I now have a VPS running version of CF 9. When I try to use this on the VPS, I get the following error:
    Attribute validation error for tag CFQUERY.
    The value of the attribute datasource, which is currently '', is invalid.
    The datasource is being set in application.cfc, and again works just fine in the shared environment.
    The only differences is the shared is running on Windows, and the VPS is Linux. Also, the Windows is running version 9,0,1,274733 and the Linux is 9,0,0,251028
    Any help would be greatly appreciated.

    bbholdem wrote:
    I have a CF application that's running fine on a shared host. I now have a VPS running version of CF 9. When I try to use this on the VPS, I get the following error:
    Attribute validation error for tag CFQUERY.
    The value of the attribute datasource, which is currently '', is invalid.
    The cause of the error is obvious. Somewhere in your application, the cfquery tag is used as follows, with an empty string as datasource:
    <cfquery datasource="">
    </cfquery>
    That is a mistake. The error message should tell you where that occurs.

  • Weird attribute validation error

    Hi!
    I'm trying to get an XML message to validate in Spring WS. I have the following XML Schema:
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema version="1.0"
               xmlns:xs="http://www.w3.org/2001/XMLSchema"
               elementFormDefault="qualified"
               targetNamespace="http://namespace.lantmateriet.se/distribution/products/geoaccess/admindirekt/v1"
               xmlns:app="http://namespace.lantmateriet.se/distribution/products/geoaccess/admindirekt/v1">
      <xs:element name="FindCountyRequest">
        <xs:complexType>
          <xs:choice>
            <xs:element name="id" type="xs:string"  form="unqualified"/>
            <xs:element name="name" type="xs:string"  form="unqualified"/>
          </xs:choice>
          <xs:attribute name="detail" use="required">
              <xs:simpleType>
                  <xs:restriction base="xs:string">
                      <xs:enumeration value="GENERAL"/>
                      <xs:enumeration value="DETAILED"/>
                  </xs:restriction>
              </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:schema>When I send the following message...:
    <?xml version="1.0" encoding="UTF-8"?>
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
                   xmlns:app="http://namespace.lantmateriet.se/distribution/products/geoaccess/admindirekt/v1"
       <soap:Header/>
       <soap:Body>
          <app:FindCountyRequest detail="DETAILED">
             <id>21</id>
          </app:FindCountyRequest>
       </soap:Body>
    </soap:Envelope>...I get this error:
    WARN  XML validation error on request: cvc-complex-type.3.2.2: Attribute 'detail' is not allowed to appear in element 'app:FindCountyRequest'. at org.springframework.ws.soap.server.endpoint.interceptor.AbstractFaultCreatingValidatingInterceptor.handleRequestValidationErrors(AbstractFaultCreatingValidatingInterceptor.java:154)
    WARN  XML validation error on request: cvc-complex-type.4: Attribute 'detail' must appear on element 'app:FindCountyRequest'. at org.springframework.ws.soap.server.endpoint.interceptor.AbstractFaultCreatingValidatingInterceptor.handleRequestValidationErrors(AbstractFaultCreatingValidatingInterceptor.java:154)What?! How come it says that I must have the attribute and that, at the same time, it is not allowed?
    Any ideas?
    Thanks!

    I've come to the conclusion that the attribute is in the wrong namespace.
    How do I fix the schema so that the message validates?

  • When using CORBA I get an Attribute validation error for CFOBJECT

    Any ideas about whats going on here?
    The value of the TYPE attribute, which is currently ”CORBA”, must be one of the values: CORBA,COM,COMPONENT,JAVA,DOTNET,WEBSERVICE,.NET.

    Here you go...
    code:
    <!--- <cfobject
    action=”create”
    type=”CORBA”
    name=”session.TargetService”
    class=”Targets.TargetService”
    context=”NameService”
    > --->
    <cfscript>
    session.TargetService = createObject("CORBA","NameService","Target.TargetService");
    </cfscript>
    <cfdump var="#session.TargetService#">
    screenshots:
    ColdFusion Version: This is ColdFusion 10,283111
    JVM Config (slightly redacted):
    Message was edited by: Ched Cheatham

  • Validation error for tag cfloop

    Hi All,
    Complete newbie to CF here.  I've inherited (or bought) an online business which has its site written in CF.  I haven't done this sort of stuff before but do work SQL for a living and object oriented stuff plus have done a bit of html and php so CF isn't mind blowing to me (in its simple form).
    I've downloaded my site on to my computer to run a local copy that I can hack to pieces if needs be.  For some reason, I have a few problems with the site running locally.  The first error I'm getting is a Attribute validation error for tag cfloop.
    Basically, index.cfm has this bit of code in it:
    <cfinvoke component="#datasets#" method="storedProcedure" returnvariable="getFeaturedWineries_qry">
        <cfinvokeargument name="storedProcedure" value="usp_GetFeaturedWineries">
    </cfinvoke>
    Ok, easy enough.  Anyway, there's a call down the page to:
    <cfinclude template = "#REQUEST.CFMPath#includes/displayFeaturedWineries.cfm">
    Within displayFeaturedWineries.cfm is the code that calls the stored proc invoked above:
    <cfloop query="getFeaturedWineries_qry" startrow="1" endrow="2">
    Bam, that's where the error occurs.  "The value of the attribute query, which is currently getFeaturedWineries_qry, is invalid.
    What???  The stored proc exists and it only returns two records (which begs me to wonder why you would have startrow and endrow but anyway, it doesn't work with or without it).
    The other interesting thing is that this works on production, NO PROBLEM!!!  WTF?  How can it work on production but not locally.
    The only thing I'm starting to think is:
    a)  I've missed a setting somewhere in CF or
    b)  I'm running Apache as compared to IIS or
    c)  I'm running SQL 2008 and CF 9 which will no doubt be different to the production host server.
    Should B or C be causing THAT type of problem??
    Thanks,
    Matt

    I'm not sure what code apart from the above is going to show you what you could possibly need to solve this, but here goes.  The following is only snippets of the code, but they are the relavant snippets.  Other stored procs work.  The cfdump for getFeaturedWineries_qry shows 'usp_getFeaturedWineries'.  I know its there because I've been unable to run "EXEC usp_getFeaturedWineries" after copying it straight out of the code.  As previously stated, there are other stored procs which are running fine.
    datasets.cfc
        <cffunction name="storedProcedure">
            <cfargument name="storedProcedure" required="Yes" type="string">
            <cfstoredproc procedure = "#ARGUMENTS.storedProcedure#"
                          datasource = "#REQUEST.DSN_NAME#"
                          username   = "#REQUEST.DSN_USER#"
                          password   = "#REQUEST.DSN_PASS#"
                          returncode = "Yes">
                <cfprocresult name="storedProcedure" resultset="1">
            </cfstoredproc>
            <cfreturn storedProcedure>
        </cffunction>
    application.cfm
        <!--- DATA SOURCE VARIABLES --->
        <cfset DSN_NAME = "boutiqueWineriesTest">
        <cfset DSN_USER = "coldfusion">
        <cfset DSN_PASS = "coldfusion">
    index.cfm
    <cfobject component="#COMP_REF#.datasets" name="datasets">
    <cfinvoke component="#datasets#" method="storedProcedure" returnvariable="getFeaturedWineries_qry">
        <cfinvokeargument name="storedProcedure" value="usp_getFeaturedWineries">
    </cfinvoke>
    <cfinclude template = "#REQUEST.CFMPath#includes/displayFeaturedWineries.cfm">
    displayFeaturedWineries.cfm
             <cfloop query="getFeaturedWineries_qry" startrow="1" endrow="2">
    Attribute validation error for tag cfloop.
    The value of the attribute query, which is currently  getFeaturedWineries_qry, is invalid.                                                                                  The error occurred in C:\apps\iishome\includes\displayFeaturedWineries.cfm:  line 33
    Called from C:\apps\iishome\index.cfm: line 399
    Called from C:\apps\iishome\index.cfm: line 79
    Called from C:\apps\iishome\index.cfm: line 1
    31 :      <tr>
    32 :           <td width="626" colspan="3" class="productCenter_bg2">
    33 :          <cfloop query="getFeaturedWineries_qry" startrow="1" endrow="2">
    34 :              <div class="productCennews">
    35 :                  <table border="0" cellspacing="0" cellpadding="0">

  • Validation errors reset item attributes

    I have some java script code that gets executed with an onchange event to set the disable attribute of other fields. It works great. But if I get an error when validation is run, it resets the item attributes back to disable=false. Why is this and how do I get around it? Thanks in advance for your help.
    Code from javascript...
    function set_other_fields(pThis){
    if (pThis.value == 'U') {                 
    document.getElementById('P12_DEFAULT_VALUE').disabled=true;
    document.getElementById('P12_DEFAULT_VALUE').value='';
    document.getElementById('P12_LOOKUP_NAME_LKUP_ID').disabled=true;
    document.getElementById('P12_LOOKUP_NAME_LKUP_ID').value='';
    if (pThis.value == 'D') {
    document.getElementById('P12_LOOKUP_NAME_LKUP_ID').disabled=true;
    document.getElementById('P12_LOOKUP_NAME_LKUP_ID').value='';
    document.getElementById('P12_DEFAULT_VALUE').disabled=false;
    if (pThis.value == 'L') {
    document.getElementById('P12_LOOKUP_NAME_LKUP_ID').disabled=false;
    document.getElementById('P12_DEFAULT_VALUE').disabled=true;
    document.getElementById('P12_DEFAULT_VALUE').value='';
    }

    Hi Kristina,
    The disabled values will be reset as the page is reloaded after the validation errors and the onchange event isn't triggered.
    You can force your javascript to run whenever the page is rendered (and this would be on the initial load as well), by adding a call to your function somewhere underneath both the function and all relevant fields. So, add something like the following somewhere at the bottom of your page:
    &lt;script type="text/javascript"&gt;
    set_other_fields(document.getElementById("ID_of_the_field_that_has_the_onchange"));
    &lt;/script&gt;Because this isn't within a function block itself, it will be run as soon as it is loaded by the browser - hence ensuring that everything is on the page before this point.
    Andy

  • Button condition on page item and Validation error Conflict

    Hi,
    I have a select list page item and a button on page whose condition is based on the select list page item value(eg, If (:P2_item1='val1'){return true;}) with condition type=PL/SQL function returning boolean. This buttons submits the page.
    It' coming fine in normal case. However, if I select some value val2 from the list and then click the button, and if there are any validation errors (like mandatory check or email check fail etc), then the button disappears because it evaluates the button condition based on the changed value(val2), but the page has not yet been submitted because of validation errors.
    I think this can be solved if I create the button condition based upon database column value instead of page item as db col value won't change until the page is submitted.
    This look like very basic use-case and I would like to know if there is any better solution to this problem.
    Note: I am using Apex 4.2.1

    I don't want to show/hide the button on the change of the page item lov value, so i am not using Dynamic action.
    What i was is to make button visible based on a condition(which is based on page item), for which we have condition attribute of a button available.
    This is a very common thing where a user chooses the button condition as Value of item/column in expression 1 is null/expr2. But what if the user changes the page item value but it doesn't get submit due to validation error. In that case, the button condition fails.
    So, i guess i have to use column name in expression 1, can u tell how to do that?
    Expression 1 = IF (:P2_STATUS='val1') then return true;
    How to change the above to use db column 'status' instead? Any direct way(like #Status#) or I have to query db to get it using select.
    Any alternative approach?

  • XML validation error while parsing MXI Manifest

    Hi,
    I have created an hybrid extension for Photoshop. I want to upload my extension on Adobe Exchange. during the upload process I get an error,
    "XML validation error while parsing MXI Manifest: Declarations can only occur in the doctype declaration. Line: 19 Position: 791 Last 80 unconsumed characters".
    The error description specifies that description in MXI file is not valid. Below are the contents of my MXI file.
    <macromedia-extension
               name="yyy"
               id="com.yyy"
               version="1.0.0"
               type="object"
               requires-restart="true">
              <author name="abcd" />
              <products>
              <product familyname="Photoshop" maxversion="" primary="true" version="12.0"/>  
              </products>
    <description>
              <![CDATA[
    <p><font size="14" color="black"><b>abcd</b> qwertyuioipafgjhkjljljklkjl
    <br><br>
    Open Extension via: Photoshop top menu > Window > Extensions > abcd.
    <br><br>
    Online support at: <a href="http://www.abcd.com/help.php">http://www.abcd.com/help.php</a></font></p>
    <br>]]>
    </description>
    <ui-access>
              </ui-access>
    <license-agreement>
    </license-agreement>
    <files>
                <file destination="$ExtensionSpecificEMStore/com.abcd/html/abcd.html" products="" source="zxp-support/Description/abcd.html"/>
                <file destination="$ExtensionSpecificEMStore/com.abcd/html/abcd.png" products="" source="zxp-support/Description/abcd.png"/>
                <file destination="" file-type="CSXS" products="" source="abcd.zxp"/> 
                <file destination="$automate" file-type="plugin" platform="mac" products="Photoshop" source="mac/abcd.plugin"/>
                <file destination="$automate" file-type="plugin" platform="win" products="Photoshop32" source="win32/abcd.8li"/>
                <file destination="$automate" file-type="plugin" platform="win" products="Photoshop64" source="win64/abcd.8li"/>
    </files>
    </macromedia-extension>
    Can anyone please point out why am I getting the error?
    Thanks

    Hi CarlSun,
    Thanks for the reply. I have made the changes suggested by you.
    I have few queries:
    1.  Can we use attribute "source" in the description tag?
         I have created a local html page and specified it in source attribute. but the Extension Manager CS6 did not render the local html page and displayed      the following:
         No description avaliable. Click the following link for more details.
         "http://www.abcd.html". Is it possible to display a local html page in Extension Manager CS6?
    2. Can I display an image (png) in CDATA under description tag? If yes, then can you please guide me how can I do so?
    3. As suggested in tech notes MXI file must include UTF-8 encoding as header (<?xml version="1.0" encoding="UTF-8"?>). The MXI I am using does      not have this header. Do I need to include the header?
    Thanks

  • Validation error corrupts component tree?

    I've got a strange problem trying to use validation on input fields.
    The basic setup is as follows:
    I've got a page divided into two parts with separate h:form tags, the one holding a dataTable with some elements and the other showing the element details in inputFields once an item is selected in the dataTable via a commandLink. A commandButton on the detail side allows you to update the values of the selected item which is being reflected in the dataTable on reload. So far so good.
    Here comes the strange part:
    All the inputFields are marked required. Now once you leave a field empty and try to submit the form, you get a validation error as expected. BUT if you now select a different element from the dataTable, ONLY the field whose validation formerly failed is being updated, the other fields still show the same value as before. The backing bean method that belongs to the commandLink is being executed, and the underlying data object of the input fields is being set properly, only the values in the component tree aren't updated. This behaviour persists until you enter a valid value in the formerly invalid input field and submit. Debugging shows that as long as at least one field has had validation errors, only the getter of these backing beans properties are being invoked during render response phase, as opposed to the "normal" case where the getters of all the backing beans properties are being called.
    For some reason, the render response phase seems to ignore the other components in the component tree when there was some validation error on one or more fields.
    Another interesting observation:
    This is the behaviour if I don't specify an action attribute in the commandLink selecting an element from the dataTable, as I want to return to the same page again. But if I define a navigation case that brings me to the same page and put that into the action attribute, the problem doesn't occur. Unfortunately this is no option for me, as I'm aiming to do all this with ajax.
    I've created a simple example so you can try out yourself:
    test.jsp:
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
    <html>
    <head>
    <title>validator test</title>
    </head>
    <body>
    <f:view>
         <h:form id="form1">
              <h:dataTable id="table" value="#{bean.datas}" var="data" binding="#{bean.table}" border="1">
                   <h:column>
                        <h:commandLink actionListener="#{bean.selectData}" value="#{data.string1}" />
                   </h:column>
                   <h:column>
                        <h:outputText value="#{data.string2}" />
                   </h:column>
              </h:dataTable>
              </h:form>
         <hr />
         <h:form id="form2">
              <h:inputText value="#{bean.data.string1}" id="field1" required="true" />
              <h:inputText value="#{bean.data.string2}" id="field2" required="true"/>
              <h:commandButton value="submit" />
         </h:form>
    </f:view>
    </body>
    </html>Bean.java:
    needs to be defined in faces-config.xml as bean "bean" with session scope
    import java.util.ArrayList;
    import java.util.List;
    import javax.faces.component.html.HtmlDataTable;
    import javax.faces.event.ActionEvent;
    public class Bean {
         private Data data;
         private List<Data> datas;
         private HtmlDataTable table;
         public Bean() {
              datas = new ArrayList<Data>();
              datas.add(new Data("data1value1","data1value2"));
              datas.add(new Data("data2value1",""));
         public void selectData(ActionEvent event) {
              data = (Data)table.getRowData();
         public List<Data> getDatas() {
              return datas;
         public Data getData() {
              return data;
         public void setData(Data data) {
              this.data = data;
         public HtmlDataTable getTable() {
              return table;
         public void setTable(HtmlDataTable table) {
              this.table = table;
         public class Data {
              private String string1;
              private String string2;
              public Data(String string1, String string2) {
                   this.string1 = string1;
                   this.string2 = string2;
              public String getString1() {
                   return string1;
              public void setString1(String value) {
                   string1 = value;
              public String getString2() {
                   return string2;
              public void setString2(String value) {
                   string2 = value;
    }My system setup:
    WinXP Professional
    JDK 1.6.0-b105
    Tomcat 5.5.20 (also tried 6.0.7)
    JSF RI 1.1.02_b08 (also tried 1.2_04-b10-p01, different but anyway not expected behaviour with MyFaces 1.1.5)
    Thanks for any input,
    Harry.

    Is there noone here who can tell me if this is behavior like specified or if I miss some point?
    A possible solution seems to be telling JSF programmatically to rebuild the view root. Does anyone if this is possible?

  • Help needed to resolve there is no attribute X errors..

    On my website http://www.dorffdesign.nl/ there is a problem. Ive put the FB Like button there and it worked fine for a while. But now its gone. So ive run
    http://validator.w3.org/ on it and came up with the next errors:
    ========================================================================================== ==============================================
      Line 232, Column 32: there is no attribute "data-href" <div class="fb-like" data-href="http://www.dorffdesign.nl/" data-send="true" da… ✉  
      Line 232, Column 71: there is no attribute "data-send" …http://www.dorffdesign.nl/" data-send="true" data-width="450" data-show-faces=… ✉  
      Line 232, Column 89: there is no attribute "data-width" …orffdesign.nl/" data-send="true" data-width="450" data-show-faces="true"></div> ✉  
      Line 232, Column 111: there is no attribute "data-show-faces" …orffdesign.nl/" data-send="true" data-width="450" data-show-faces="true"></div>
    ========================================================================================== ===============================================
    In dreamweaver ive use this code for the FB likke button:
    <div id="fb-root"></div>
    <script>(function(d, s, id) {
      var js, fjs = d.getElementsByTagName(s)[0];
      if (d.getElementById(id)) return;
      js = d.createElement(s); js.id = id;
      js.src = "//connect.facebook.net/nl_NL/all.js#xfbml=1";
      fjs.parentNode.insertBefore(js, fjs);
    }(document, 'script', 'facebook-jssdk'));</script>
    ========================================================================================== ===========
    <div class="fb-like" data-href="http://www.dorffdesign.nl/" data-send="true" data-width="450" data-show-faces="true"></div>
    I really want to solve this so im hoping if you can point me into the right direction.
    Regards

    Hi ive bin able to put the fb like button on my page. But i totally forgot how i have to place the fb like button under the black box named portfolio.
    I hope you can tell me.
    Regards
    Date: Wed, 7 Nov 2012 07:41:54 -0700
    From: [email protected]
    To: [email protected]
    Subject: Help needed to resolve there is no attribute X errors..
        Re: Help needed to resolve there is no attribute X errors..
        created by MurraySummers in Dreamweaver General - View the full discussion
    You can either ignore those errors (since they have no impact on your page's functionality) or you can use DW to convert your page to an HTML5 doctype (File > Convert > HTML 5, and then the errors will go away.
         Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4829606#4829606
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4829606#4829606
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4829606#4829606. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Dreamweaver General by email or at Adobe Community
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Lax validation errors on schema import ('version' exceeds maximum length)

    I have a schema as per below. I'm trying to import it into Oracle 10.2.0.2.0. However, I'm getting the following lax validation error:
    Error loading ora_business_rule.xsd:ORA-30951: Element or attribute at Xpath /schema[@version] exceeds maximum length
    I can fix it by modifying the attribute and shortening it but I'd like to know why it's occuring. Insofar as I can tell there is no imposed limit on the size of schema attributes according to the W3C standard. Which then makes me wonder: does Oracle impose limits on the length of all attributes or is this specific to 'version' ? If there is a limit, what is the upper bound (in bytes) ? Where is this documented?
    Cheers,
    Daniel
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:br="http://foo.com/BusinessRule_PSG_V001" targetNamespace="http://foo.com/BusinessRule_PSG_V001" elementFormDefault="qualified" attributeFormDefault="unqualified" version="last committed on $LastChangedDate: 2006-05-19 11:00:52 +1000 (Fri, 19 May 2006) $">
         <xs:element name="edit">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="edit_id" type="xs:string"/>
                        <xs:element ref="br:business_rule"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="derivation">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="derivation_id" type="xs:string"/>
                        <xs:element ref="br:derivation_type"/>
                        <xs:element ref="br:business_rule"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="derivation_type">
              <xs:simpleType>
                   <xs:restriction base="xs:NMTOKENS">
                        <xs:enumeration value="complex"/>
                        <xs:enumeration value="format"/>
                        <xs:enumeration value="formula"/>
                        <xs:enumeration value="recode"/>
                        <xs:enumeration value="SAS code"/>
                        <xs:enumeration value="transfer"/>
                        <xs:enumeration value="count"/>
                        <xs:enumeration value="sum"/>
                        <xs:enumeration value="max"/>
                        <xs:enumeration value="min"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <xs:element name="business_rule"></xs:element>
    </xs:schema>

    Opps -- Sorry it's a decision we took when looking at Version
    When we registered the Schema for Schemas during XDB bootstrap the Version attriubte was mapped to varchar2(12).
    SQL> desc xdb.xdb$schema_T
    Name                                      Null?    Type
    SCHEMA_URL                                         VARCHAR2(700)
    TARGET_NAMESPACE                                   VARCHAR2(2000)
    VERSION                                            VARCHAR2(12)
    NUM_PROPS                                          NUMBER(38)
    FINAL_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
    BLOCK_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
    ELEMENT_FORM_DFLT                                  XDB.XDB$FORMCHOICE
    ATTRIBUTE_FORM_DFLT                                XDB.XDB$FORMCHOICE
    ELEMENTS                                           XDB.XDB$XMLTYPE_REF_LIST_T
    SIMPLE_TYPE                                        XDB.XDB$XMLTYPE_REF_LIST_T
    COMPLEX_TYPES                                      XDB.XDB$XMLTYPE_REF_LIST_T
    ATTRIBUTES                                         XDB.XDB$XMLTYPE_REF_LIST_T
    IMPORTS                                            XDB.XDB$IMPORT_LIST_T
    INCLUDES                                           XDB.XDB$INCLUDE_LIST_T
    FLAGS                                              RAW(4)
    SYS_XDBPD$                                         XDB.XDB$RAW_LIST_T
    ANNOTATIONS                                        XDB.XDB$ANNOTATION_LIST_T
    MAP_TO_NCHAR                                       RAW(1)
    MAP_TO_LOB                                         RAW(1)
    GROUPS                                             XDB.XDB$XMLTYPE_REF_LIST_T
    ATTRGROUPS                                         XDB.XDB$XMLTYPE_REF_LIST_T
    ID                                                 VARCHAR2(256)
    VARRAY_AS_TAB                                      RAW(1)
    SCHEMA_OWNER                                       VARCHAR2(30)
    NOTATIONS                                          XDB.XDB$NOTATION_LIST_T
    LANG                                               VARCHAR2(4000)
    SQL>

  • Validation error in Tag Library at deploy time

    I am trying to deploy a JSF2 app to NW CE 7.1 EHP1. This application deploy's fine to Tomcat. When I deploy to SAP it gives an error: Error in parsing [META-INF/primefaces-i.tld] TLD file in the following [D:\usr\sap\NCX\J00\j2ee\cluster\apps\com.sap\IDMear\servlet_jsp\IDM\root\WEB-INF\lib\primefaces-1.0.0.jar] JAR file.
    [EXCEPTION]
    com.sap.engine.lib.xml.parser.NestedSAXParseException: Fatal Error: org.xml.sax.SAXParseException: Validation error : line: 13; col: 16; :description : Element is not allowed.(:main:, row=13, col=17) -> org.xml.sax.SAXParseException: Validation error : line: 13; col: 16; :description : Element is not allowed.
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:140)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:174)
    at com.sap.engine.lib.processor.SchemaProcessor.parse(SchemaProcessor.java:197)
    at com.sap.engine.services.servlets_jsp.server.deploy.descriptor.TagLibDescriptor.loadDescriptorFromStream(TagLibDescriptor.java:90)
    From looking at the TLD XSD for JEE 5, the Description field should be allowed. Do you know why it is not comparing the TLD against the correct schema or if there is another explanation?
    This is a 3rd party faces component library. Here is where it fails:
    <?xml version="1.0" encoding="UTF-8"?>
    <taglib xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.1">
         <tlib-version>1.2</tlib-version>
         <short-name>i</short-name>
         <uri>http://primefaces.prime.com.tr/touch</uri>
         <tag>
              <name>application</name>
              <tag-class>org.primefaces.touch.component.application.ApplicationTag</tag-class>
              <body-content>JSP</body-content>
              <attribute>
                   <name>id</name>
                   <required>false</required>
                   <description><![CDATA[Id of the component]]></description>               <rtexprvalue>false</rtexprvalue>
              </attribute>
    Any suggestions would be appreciated.

    It looks like the 3rd party tld did not have the description in the correct order. It has been corrected in a new build.

  • XML validation errors in embedded OC4J jazn.xml

    hi
    If I open the jazn.xml of the embedded OC4J in JDeveloper 10.1.3.3.0 and select "Validate XML" from the context-menu on that file, I get these messages in the "XML Validation Errors - Log" :
    D:\oracle\jdevstudio10133\jdev\system\oracle.j2ee.10.1.3.41.57\embedded-oc4j\config\jazn.xml
        Error(10,28): <Line 10, Column 28>: XML-24535: (Error) Attribute 'schema-major-version' not expected.
        Error(10,28): <Line 10, Column 28>: XML-24535: (Error) Attribute 'schema-minor-version' not expected.
        Error(10,28): <Line 10, Column 28>: XML-24536: (Error) Missing Attribute 'filepath'
        Error(10,28): <Line 10, Column 28>: XML-24536: (Error) Missing Attribute 'OC4J_INSTANCE_ID'Strange, because I'm not aware of any changes I've made to this file.
    Could someone (from Oracle) please confirm that this is "intended", so I can exclude it as possible cause for the "security configuration issue" that I'm having.
    many thanks
    Jan Vervecken

    Thanks for your reply Frank.
    If "the content seems to be correct" then the XML schema jazn-10_0.xsd might not be what it should be.
    For the attributes "filepath" and "OC4J_INSTANCE_ID" it says they are "required", just like the validation by JDeveloper says, but they are not in the documentation.
    For the attributes "schema-major-version" and "schema-minor-version" the documentation says:
    "This attribute is not defined directly in the XSD for jazn.xml. It is according to the attributeGroup specification in the top-level OC4J XSD."
    Although there is no exact reference in that documentation, and also not in jazn-10_0.xsd, that XSD could be oc4j-10_0.xsd because it defines this:
        <xsd:attributeGroup name="oc4j-schemaVersionAttributeType">
            <xsd:annotation>
                <xsd:documentation>This type defines two different attributes which are intended to be used in the
                    root element of a schema document to define version 10.0 of the schema document.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:attribute name="schema-major-version" type="xsd:integer" fixed="10"/>
            <xsd:attribute name="schema-minor-version" type="xsd:integer" default="0"/>
        </xsd:attributeGroup>I'm not sure if it is the validation by JDeveloper that went wrong here, or the XML schema jazn-10_0.xsd that is incomplete about these "schema version" attributes.
    Anyway, it seems OK to exclude it as possible cause for the "security configuration issue" that I'm having.
    regards
    Jan

  • JSF, NetBeans and customizing of Standard Validation Errors

    Hello together,
    i want to use german Standard Validation Errors via a own .properties File:
    1.
    Here is my faces-config.xml ( the entries are uncommented ! ):
    <faces-config>
    <application>
    <locale-config>
    <default-locale>de</default-locale>
    <supported-locale>de</supported-locale>
    <supported-locale>en</supported-locale>
    </locale-config>
    *<message-bundle>alles.mymessages</message-bundle>*
    </application>
    </faces-config>
    2.
    Here is mymessages.properties-File in package alles:
    javax.faces.validator.NOT_IN_RANGE=Das angegebene Attribut liegt nicht zwischen den erwarteten Werten {0} und {1}.
    javax.faces.validator.NOT_IN_RANGE_detail="{2}"\:Eingegebener Wert liegt nicht im erwarteten Bereich von {0} bis {1}.
    javax.faces.validator.LongRangeValidator.LIMIT=Validierungsfehler
    javax.faces.validator.LongRangeValidator.LIMIT_detail=Eingegebener Wert kann nicht in den korrekten Typ umgewandelt werden.
    javax.faces.validator.LongRangeValidator.MAXIMUM=Validierungsfehler
    javax.faces.validator.LongRangeValidator.MAXIMUM_detail="{1}"\:Wert ist gr\u00F6\u00DFer als das erlaubte Maximum"{0}".
    3.
    Here the part of the JSF-View with the Validator:
    <ui:textField binding="#{WorkTypeEdit.textFieldBeschartKzSoll}" converter="#{WorkTypeEdit.bigIntegerConverter1}"
    id="textFieldBeschartKzSoll" required="true" style="height: 24px; width: 48px" validator="#{WorkTypeEdit.longRangeValidator1.validate}"/>
    The application still shows the standard englisch validation error text. What is wrong here ?
    I' am using NetBeans 5.5.1 with VWP and the deploment is to Glassfish server.
    Thanks a lot.
    HJA

    Hello Raymond,
    i did some coding and create additional a custom validator:
    My JSF-View part:
    <ui:textField binding="#{WorkTypeEdit.textFieldBeschartKzSoll}" converter="#{WorkTypeEdit.integerConverter1}"
    id="textFieldBeschartKzSoll" maxLength="2" required="true" style="height: 24px; width: 48px" *validator="#{MyValidation.validateInput}">*
    *<f:validateLongRange minimum="1" maximum="9"></f:validateLongRange>*
    </ui:textField>
    My custom validator in Myvalidation class:
    public void validateInput (FacesContext facescontext, UIComponent component, Object value) throws ValidatorException
    long min = 0, max = 0;
    Locale locale = facescontext.getViewRoot ().getLocale ();
    String mb = facescontext.getApplication ().getMessageBundle ();
    ResourceBundle rb = ResourceBundle.getBundle (mb, locale);
    Validator[] validator = ((UIInput) component).getValidators ();
    for (int i=0; i < validator.length; i++)
    if (validator[i] instanceof LongRangeValidator)
    LongRangeValidator lv = (LongRangeValidator) validator;
    long lvalue = Long.valueOf ((String)value.toString ());
    min = lv.getMinimum ();
    max = lv.getMaximum ();
    if (lvalue < min || lvalue > max)
    ((UIInput) component).setValid (false);
    *String message = rb.getString ("javax.faces.validator.NOT_IN_RANGE");*
    *String messageDetail = rb.getString ("javax.faces.validator.NOT_IN_RANGE_detail");*
    *facescontext.addMessage (component.getClientId (facescontext), new FacesMessage (FacesMessage.SEVERITY_ERROR,message,messageDetail));* }
    What happen now is, at first i get the german message because of rb.getString........ so the locale is working
    and then the englisch message follows in the message component.
    Sorry that i take your time so long...
    HJA

Maybe you are looking for