FatalError: The required attribute 'FeatureDefinitionScope' is missing

Hi all,
I'm trying to export a Subsite from a WSS 3.0 SharePoint to SharePoint Foundation 2013. I haven't installed or enabled any further features on both servers. While importing the site via Import -SPWeb I got the Error FatalError: The required attribute
'FeatureDefinitionScope' is missing. I compared the features and cant see any obvious difference. Any Suggestions what else I can do?
Here is the whole Error message
[29.01.2014 15:01:05] [ListItem] [default.master] Verbose: List URL: /websites/Webseitesammlung/_catalogs/masterpage
[29.01.2014 15:01:06] FatalError: The required attribute 'FeatureDefinitionScope' is missing.
[29.01.2014 15:01:06] Debug: at System.Xml.Schema.XmlSchemaValidator.SendValidationEvent(XmlSchemaValidationException e, XmlSeverityType severity)
at System.Xml.Schema.XmlSchemaValidator.CheckRequiredAttributes(SchemaElementDecl currentElementDecl)
at System.Xml.Schema.XmlSchemaValidator.ValidateEndOfAttributes(XmlSchemaInfo schemaInfo)
at System.Xml.XsdValidatingReader.ProcessElementEvent()
at System.Xml.XsdValidatingReader.Read()
at System.Xml.XmlReader.ReadToDescendant(String name)
at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
at Microsoft.SharePoint.Deployment.SPImport.Run()
[29.01.2014 15:01:06] Progress: Import did not complete.
Thanks for any suggestions!

You can't use export and import, as this will not work across versions. Your path to 2013 should be attaching your wss3.0 db to 2010, so that it can upgrade, and then detach and attach it to 2013. Backup/Restore does NOT work across versions...
even 2010 to 2013...

Similar Messages

How to manage with the required attribute with the h:selectOneMenu ?

dear all,
I have form with some drop down list.
All have a default value to invite user to select a criteria.
By submitting my form I have an actionListener method wich check validity of the fields.
I would like to display a message near the <h:selectOneMenu> to point the attention of the user about selection must be done.
I try following:
<h:selectOneMenu id="idContractNature" required="#{applicationController.requiredContract}" partialSubmit="true" valueChangeListener="#{applicationController.valueChangeContractType}" value="#{applicationBackingInfo.opportunityInfo.contractNatureId}">
<f:selectItems id="SlctContractNatureItms" value="#{applicationDefaultDataController.contractNatures}"/>
</h:selectOneMenu>
<h:message for="idContractNature"></h:message>I set the required attribute to true in the actionListener method if the contract id is equal to 0 (my default value)
But it doesn't work.
How can i check the validity of the drop down list?
I set the required attribute to true when the

thanks but can set null for the value of the default value due to:
Can't set property 'contractNatureId' of type 'int' on class '....' to value 'null'.
because it's a list SelectItem with int / string

How to change the required attribute of a field

Hi,
I'm using jdeveloper 10g, uix and jHeadstart to generate my application.
In my form, I have some attributes that are required and if I change a checkbox, some of these fields that was required, must now be not required.
How can I do this?
Any ideas?
Thanks!
Martin

Sounds like a custom validation, but you could also use a partial rendering and EL to achieve this. Lets say you could set the 'required' property of the field based on the EL expression calculating the value in the other field

Problem with the "required" attribute in input_text (in 1.0 beta)

Suppose you wanted to display a more meaningfull message instead of the default "Validation Error: Value is required", e.g. "Please enter your e-mail address". Looks like the only way to do this is to write a custom validator. However, if required="true" in the input_text, you will get the default message, if you don't set "required", your custom validator is not called at all.
This is something that needs to be addressed, because it will be very common to want to have meaningfull error messages (I can't imagine somebody will approve a commercial application which will display messages like "Validation Error: Value is required").
As a workaround, I tried setting an error message in the action handler, but I can't seem to get the component from within the bean code. In the action method I have:
FacesContext context = FacesContext.getCurrentInstance();
UIInput component = (UIInput) context.getViewRoot().findComponent("testInput");where testInput is the id of the input_text - findComponent() returns null.
P.S. Btw, I noticed that now in 1.0 the ids look like this id0:testInput which is a really bad choice if you have to write any JavaScript handler, e.g. onClick(), since id0:testInput is not a valid JavaScript variable name. You can still find it by going through all the document.forms[0].elements[n].name and set it up that way, but it's a hassle.

Thanks,
findComponent("formName:inputName")worked fine.
But still, I think that if you have a custom validator
it should be called regardless of whether there is
something in the input or not (or maybe bypass the
default validation if "required" attribute is set, but
there is a custom validator), because that's the only
way you can change the default "Value required"
message using a validator. If you have to check it in
the action method, you might as well do the whole
validation there, which makes validators pointless.The expert group considered this decision carefully, and concluded that the current behavior was the best -- if there is no input data, skip any specified validations -- because of the likelihood for things like null pointer exceptons in validators that are not prepared for this scenario.
One approach to dealing with this if you would prefer different behavior for your own components is to subclass UIInput and override the validate() method to do something different.
Craig

How to override the default "required" attribute for the UIComponent?

Hi, consider the following markup: <h:inputText id="txt_firstName" value="#{myBean.firstName}" required="true"/>
if I leave this field empty and hit the submit button, the required validator will fire an error msg. If however, I leave an empty space in the text box and hit submit button, it will go through no problem.
I'd like to override the required attribute, so it will trim the spaces first before decide if it really is empty:
//whatever the name of the method i'm overriding....
String value = (String)value;
if(value==null)throw new ValidatorException(whateverDefinedInTheBundle);
value = value.trim();
if(value.length==0)throw new ValidatorException(whateverDefinedInTheBundle);
How can I go about doing that?
Thank you.

Did you already try
 <af:treeTable value="#{bindings.DashProjectPhasesDev.treeModel}"
 var="node"
 selectionListener="#{bindings.DashProjectPhasesDev.treeModel.makeCurrent}"
 rowSelection="none" rowBandingInterval="0"
 inlineStyle="width:810px; height:1100px;"> Check the last line with inlineStyle...
Julian

[svn:fx-trunk] 7553: Fix the default value of the [skinPart] "required" attribute for asdoc.

Revision: 7553
Author:   [email protected]
Date:     2009-06-04 09:32:51 -0700 (Thu, 04 Jun 2009)
Log Message:
Fix the default value of the "required" attribute for asdoc.
Bugs: SDK-21488
QE Notes: None.
Doc Notes: None.
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21488
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelGenerator.java

${ui:cond( uix.current.isNewRow, 'true', ui:cond( bindings.AddProjectNutsoverleg.value == 1, 'true', 'false' ) ) } notice the '.value' it could also be '.inputValue'.
If not there is also an option to make sure that when the checkbox is empty a value is returned anyways this work like this:
protected void processUpdateModel( DataActionContext ctx )
    //First look for the request parameter
    Object cbInRequest = ctx.getHttpServletRequest().getParameter( "nameofthecheckbox" );
    //We only need to do anything if it was not submitted
    if( cbInRequest == null )
      // Get hold of the Form Bean containing the record
      BindingContainerActionForm updateForm = (BindingContainerActionForm) ctx.getActionForm();
      //Get the binding for our particular column
      JUCtrlAttrsBinding checkBoxBinding = (JUCtrlAttrsBinding)updateForm.get( "nameofthecheckbox" );
      //Reset that explicitly to the *unchecked* value
      checkBoxBinding.setAttribute( 0, new oracle.jbo.domain.Number( 0 ) );
    super.processUpdateModel( ctx );
}Maybe this helps.

Question on Required Attribute Behavior

I am having difficulty understanding what the correct behavior of a "required attribute" should be. Im using 9ifs.
Using the Java API, I created a new content type derived from DOCUMENT, named it CLASSIFIED_DOCUMENT, associated a new file extension "cla" with it, and created a new required attribute called "Security_Level". From ifsmgr, I can see the new type and see that Security_Level
is a required attribute. When I upload a file with the "cla" extension from the Viewer, it is entered into the database and correctly associated with the CLASSIFIED_DOCUMENT content type. So far so good.
However, I have not supplied a value for the required attribute, and nothing complains that the Security_Level field is null. It seems to me that IFS should not allow the item to be entered into the database without this required attribute having a value, or perhaps a dialog box should pop up which forces one to enter values for required attributes before the instance of CLASSIFIED_DOCUMENT is entered into the database. Lacking that, an invalid instance is silently slipped into the DB...
So on to my specific questions:
How does one enter required attribute data when uploading using the Viewer?
Shouldn't IFS be complaining when a CLASSIFIED_DOCUMENT is uploaded without Security_Level being set?
Will required attribute constraints also be "ignored" when performing a programmatic file creation
(similar to the "Hello World" example) of an instance of CLASSIFIED_DOCUMENT?
Do I need to do other things when creating a required attribute using Java that will actually cause the attribute to be, well, REQUIRED?
Is there a RTFM answer to this, and if so, can some kind soul please point me to the correct FM to R? I have the Developer's Guide and the IFS javadocs. The Guide has good examples but is woefully inadequate if you want to do something different from the examples. The jovadocs are of course good reference material but have nothing in the way of "application notes". I have looked at the
example code and it suffers from the same shortfall as the Guide: if you want to do something different from what is in the example code, you're on your own!
Is there a document that I should be reading but have missed?
Thank you,
Jeff Rininger

Hi Jeff -
Thanks for the feedback.
REQUIRED attributes are exactly what you describe: they are a way to ensure an attribute has a non-null value when a new object is created or when that attribute is updated in an existing object.
From an API perspective, in creating a new object, that value can be supplied in three ways: explicitly by setting an attribute in the LibraryObjectDefinition, through a VALUEDEFAULT on the attribute, or (advanced topic) through custom server extensibility code.
One thing to keep in mind: REQUIRED checks are (intentionally) not performed in administration mode. You might want to try creating an object as a non-admin user. That should cause the check to be performed.
David Pitfield
Oracle

Required attribute does not work with any data type other than String

sir,
I am a new to JSF. My problem is that I have used an integer type data in my page which is taking its value from a bean.But in jsf code I have used the required attribute for the <h:inputText> but if I leave the text box empty it is not showing the validation error which it show show. Another problem is that the page is also not navigating to the next page.
The code is
<h:inputText value="#{UserBean.age}" required="true"/>
where age is of integer type

Well. The fact that it is not jumping to the next view is "works as required". The assumption is, that once you say a field is required, it could be that the application CANNOT function without that value. Therefor the initial view is redisplayed until all required values are entered.
IF you need a different behaviour, then the OptionalValidator-package which is currently in development state, is the way to go. It allows to specify different validating strategies for different links on a view (no validation, soft validation (== allow to go on, but produce warning messages), hard validation (== the way JSF works right now)). The problem is that with JSF 1.1 it is quite difficult to implement this behaviour. For simple validators (no parameters) it is working, but for complex validators (requiring parameters) not yet. For more info: http://wiki.apache.org/myfaces/OptionalValidationFramework
No comment on the String-only behaviour, as I have not yet tested/observed that problem...
hth
Alexander

Automatic Generation of classes with required attribute names

Hi ,
I am new to XML technologies ...I am having a problem in deciding whether I
should use JAXB or Castor for data binding.
The problem is the attributes I am to use are named differently as that found in
the DTD.I have creted my own classes using the required attribute names and the
n mapped them using the Castor mapping with the attributes.
I was wondering how should I achieve --"automatic generation of classes" with th
e specified attribute names?
I understand that JAXB can be used to automatically generate classes ,but this
uses the same default names as that of the XML file ..is there a way of forcing
JAXB to generate classes that use my name attributes rather than that of the XM
L dtd
If I use Castor ..is there a way to do the same.Generate Classes with the specif
id attributes

Hi ,
I am new to XML technologies ...I am having a problem in deciding whether I
should use JAXB or Castor for data binding.
The problem is the attributes I am to use are named differently as that found in
the DTD.I have creted my own classes using the required attribute names and the
n mapped them using the Castor mapping with the attributes.
I was wondering how should I achieve --"automatic generation of classes" with th
e specified attribute names?
I understand that JAXB can be used to automatically generate classes ,but this
uses the same default names as that of the XML file ..is there a way of forcing
JAXB to generate classes that use my name attributes rather than that of the XM
L dtd
If I use Castor ..is there a way to do the same.Generate Classes with the specif
id attributes

Using value binding expressions to set 'required' attribute

I am trying to use a value binding expression to determine whether the value of various input control's is required or not according to where they are used and not having much luck. I wonder if anyone can shed some light on this...
The following expression works: <h:inputText id="name" required="#{true}"/> whereas <c:set var="required" value="true" scope="request"/>
<h:inputText id="name" required="#{required}"/> does not, even though the expression evaluates to true! I have tried numerous variations (requestScope.required, required == true, required ? true : false, etc.) to no avail. Interestingly, #{1 == 1} or binding to a backing bean method works, but as soon as you add a request variable it breaks.
Am I doing something wrong, is this something that JSF doesn't allow, or just a bug in the RI? Note that I don't want to vary this flag between multiple submissions of the same form, I am just trying to reuse the same JSP include to generate form controls for required and optional data on different forms to avoid a whole lot of cutting any pasting.
Any pointers gratefully received.
-- Keith Wilson

I had something like this happen, and here's what I concluded the problem was. Perhaps your problem is similar.
In the first non-working example you show a request-scope variable being set in the JSP page, and then use that to set the "required" attribute. But consider what happens when you submit the form. There is no longer any request-scope variable set because we have a new request and we don't go through the JSP page! (Not before validation is checked, anyhow).
So basically I concluded that the variable had to be in (say) session scope for it to work as you would like.

How to hide the "Required" sign

Hello,
I need to hide all required signs from my OAMessageXXX items although they have the "required" attribute.
The reason: I need to navigate from left to write and not top down, so using MessageComponentLayout was out of the question since it navigates from top down and then Right. This is a known issue with OAF Rup5. As a workaround, I'm trying to design using Table Layout, but I have problem aligning items in two different rows when one has "Required" attribute and the other does not.
Here is a link to a screen shot that describes the issue: [Screen Shot describing the alignment issue|http://i34.tinypic.com/2jam6g2.jpg]
From the screen shot you can see that "VAR" field is not aligned correctly with "End Customer" field or other fields in the same column. I prefer to use the Required attribute since it helps me with the "client" validation and it is much more responsive then validating using code.
Thanks

Hi,
Thanks for the advice, but I did try the "Validator" option. The problem is that I losing the client side validation which in some point I was depended in my validation checks. I know I could write my own validations on the "server" side but at this stage of the project I prefer not to re-orgenize the logic and I need faster response time from the framework (so users wont whine ;-) )
As for the Prompt issue, I was asked to align labels to the left and not to the right. Unfortunately Oracle did not provide us with this option, so I had to find a workaround to this issue. So now I have 6 column instead of 3, I have fake required (gui only) on the "Label" items and I realy hoped that "Validator" option on the Input items will act as Required "yes" but without the Required flag.
This is really disappointment from Oracle design here, Layout design is not flexible enough...
Thanks you for you time and ideas
Edited by: Snagar on Oct 6, 2009 12:32 AM

Required attribute and cancel action

How am I supposed to handle the following case (simplified):
<h:inputText required="true" value="#{somebean.property}" />
<h:messages />
<h:commandButton type="submit" value="Cancel" action="cancel" />
The "cancel" action is configured in faces-config.xml to navigate to another page and works like expected without the "required" attribute.
But if I include the "required" attribute I get a validation error message and the navigation to the wanted page does not take place.
Michael

For action like "cancel" I would recommend to use attribute "immediate"
<h:commandButton action="cancel" value="Cancel" immediate="true"/>Vladimir

Required Attribute For mx:TextInput

Hi All,
I need to set required="true" attribute to
<mx:TextInput/> .
But as per the docs, there is no such attribute for this
component.
The <mx:FormItem/> has the required Attribute, but i am
not using the Forms , but a simple TextInput and it should be
entered mandatory by the User.
Any Idea's how to set required="true" for
<mx:TextInput/>
Regards,
Madan N

Hi ,
below is the code to display the TextInput
<mx:GridRow>
<mx:GridItem width="110"><mx:Label text="Name"
width="100" fontWeight="bold"/></mx:GridItem>
<mx:GridItem><mx:TextInput width="100" id="name"
tabIndex="1"/></mx:GridItem>
<mx:GridItem width="110"><mx:Label text="SurName"
width="100" fontWeight="bold"/></mx:GridItem>
<mx:GridItem><mx:TextInput width="100" id="surname"
tabIndex="2"/></mx:GridItem>
</mx:GridRow>
I need to show up the TextInputs as required and a tooltip
saying this field is required as that showsup when using
<mx:FormItem/>
Madan N

Required attribute in dsp input tag

Hi
dsp:input tag is unable identify the required attribute if i keep like this <dsp:input bean="something" type ="text" required="required"/>
but it is working if i keep like this <dsp:input bean="something" type ="text">
<dsp:tagAttribute name="required" value="required"/>
</dsp:input>
if i follow second option i am getting some issues in my application
please give me solution how 1st one will work

It should be required="true". For reference see
Oracle ATG Web Commerce - dsp:input

BC forms the required* is ignored allowing empty submissions

BC forms the required* option is being ignored allowing empty submissions any ideas?

The following cfform code from htmlgoodies.com shows that the required attribute does actually work:
<cfform>

<label for="name">Name:</label> 
<cfinput type="text" name="name" required="true" message="Please provide your name." />


<label for="email">Email Address:</label> 
<cfinput type="text" name="email" required="true" validate="email"
message="Please provide a valid email address." />


<label for="message">Your Message:</label> 
<cftextarea name="message" required="true" message="Please enter a message to send."/>

<cfinput type="submit" name="Submit" value="Send Message" />
</cfform>

FatalError: The required attribute 'FeatureDefinitionScope' is missing

Similar Messages

Maybe you are looking for