Type of inheritance

what is the meaning of type of inheritance.
What is the importance of Normal inheritance(additive),local value overwrite inherited values,no inheritance and no local redefinition of inherited values.
can anybody explain in detail.
Thank you
Regards,
Yshu

Hi. The easiest way to find out is go into a sandbox system and change the types in SM30 and view T77OMATTR and see what the difference is.
Normal inheritance (additive) means that attributes are inherited and can be added to at lower levels. You get a little + button and can add extra values lower down. If you want to exclude values lower down you need to add the same value and tick the "exclude" option.
Local values overwrite means that you can not add extra values lower down. You get a replace button and can press it and put in a new value at the lower level, that is all.
No inheritance means that the attribute is not passed down at all to lower levels.
Inherited values can not be redefined locally means that the values can not be changed or added to at a lower level. They can be excluded or set as default lower, but not changed.
Regards,
Dave.

Similar Messages

Possibility of returning derived type from inherited operator

Hello forum,
I am wondering the possibility of returning a derived type from an inherited operator. A test case would include two class definitions such as:
Public Class Base
Dim _a
Public ReadOnly Property A As Integer
Get
Return _a
End Get
End Property
Public Shared Operator +(ByVal base1 As Base, _
ByVal base2 As Base) As Base
Return New Base(base1.A + base2.A)
End Operator
Public Sub New(ByVal a As Integer)
_a = a
End Sub
End Class
Public Class Derived
Inherits Base
Public Sub New(ByVal a As Integer)
MyBase.New(a)
End Sub
End Class
and implementation such as:
Dim derivedA As Derived = New Derived(1)
Dim derivedB As Derived = New Derived(1)
Dim derivedResult As Derived = derivedA + derivedB
'would like result as derived, not base!
This test case returns the error that the derivedResult cannot by cast to the base type (as this is how the operator is defined). I am wondering: is there a way to change the operator definition so that the derived type is returned from the operation? There
could be many derived types and avoiding overloading the method in each type definition could reduce the amount of code.
Many thanks.

I'm just Frank, not "Mr. Smith". ;-)
I suspect that Reed is onto it with generics. He's quite familiar with it and in a question I posted a few years ago - about derived classes - he answered it using generics.
Let's see what you or he comes up with. :)
Still lost in code, just at a little higher level.
Haha, I was like "who is Mr. Smith.... oh yeah, that's Frank's last name". ;)
@James3210: same here... it's just Reed. Wearing a shirt with a collar is about as formal as I get. :)
Anyway, back to the subject at hand, I think the generic method in conjunction with the operator overload is the way to go. Since you'll have to write the operator on each class anyway, at least you can copy-paste the operator code and then just change
the type used for "T":
Public Class FooBase
Private anInteger As Integer
Protected Shared Function Add(Of T As {FooBase, New})(source As T, target As T) As FooBase
Return New T() With {.anInteger = source.anInteger + target.anInteger}
End Function
Public Shared Operator +(source As FooBase, target As FooBase) As FooBase
Return FooBase.Add(Of FooBase)(source, target)
End Operator
End Class
Public Class DerivedFoo
Inherits FooBase
Public Overloads Shared Operator +(source As DerivedFoo, target As DerivedFoo) As DerivedFoo
Return FooBase.Add(Of DerivedFoo)(source, target)
End Operator
End Class
Public Class DerivedFooTwo
Inherits FooBase
Public Overloads Shared Operator +(source As DerivedFooTwo, target As DerivedFooTwo) As DerivedFooTwo
Return FooBase.Add(Of DerivedFooTwo)(source, target)
End Operator
End Class
In this example the shared Add() method is internal to the FooBase objects, but you could make the access modifier public if you wanted to expose the method for direct use.
-EDIT-
Sorry, I forgot you wanted to return the object type from the operator, not the internal result. I've updated the code to return a new object instance.
Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

Data Modeler: Super Type and Inheritance when engineered to Relational Mode

PLEASE IGNORE THIS MESSAGE, I'VE SORTED IT. MY STUPIDITY HAS BEEN RECTIFIED BY READING THE MANUAL!!
Hi
I have a logical model that I'm playing with where I want to set a super type entity that contains common columns for all sub-type entities a la java inheritance.
When I engineer this with the super type entity method set to 'Table for each entity' it creates a table for the super and sub entities and links them with a PK-FK.
That's not what I was expecting.... I would like to get :
PARENT ENTITY (Super Type)
ATTRIBUTE1
ATTRIBUTE2
and
CHILD ENTIRY (Super Type = PARENT ENTITY)
CHILD_ID PK
DESCRIPTION
when this is engineered I'd like:
TABLE = CHILD_ENTITY
Columns:
CHILD_ID PK
DESCRIPTION
ATTRIBUTE1
ATTRIBUTE2
Any ideas what I'm going wrong here????
Cheers
Chris
Edited by: chriseb on Aug 13, 2009 2:46 PM

Hi Chris,
I'm glad that you have sorted it out. Then you can mark the question as answered.
Philip

How to use Object types with inheritance in design editor

Does anyone know how to implement Oracle object sub types in Design editor.
Is there a way of using the Database design transformer to convert entities to Object types rather than tables?
Thanks in anticipation
David

What database and connection type are you using? Are you connecting the report directly to the database, or trying to assign the datasource to object data?
It sounds like you might be trying to use a linked list, collection or other C# construct to pass your data in. This currently isn't supported by the Crystal Reports SDK. You can use a DataSet or a DataTable, and possibly also an IDataReader depending on which version of Crystal Reports you're referencing in your project. Of course you can also connect directly to the database, even if the database isn't on the same machine as the application.
The way to show master records with detail information is through the use of subreports and linked subreport parameters. Linked subreports take their parameter value from a record in the main report, so that only the data appropriate to that master record is displayed. The guys over in the [report design|SAP Crystal Reports; forum can help you out with this if you have questions on the specifics.

Hide a field inherited by the content type in a custom list definition

The requirement is to create new content type that inherits from a Parent content type. I also created custom document library definition that uses the newly created content type.
There are some fields that are inherited from the parent type that I would like "NOT TO" show in the edit/display form in the libraries created based on the new list definition.
How can I achieve this? In the list definition, I added ShowInEditForm="FALSE" and ShowInDisplayForm="FALSE" ShowInViewForm="FALSE".
But these fields won't hide and it still shows up when a new document is uploaded. Any help would be appreciated.
Thanks!

Hey,
Have
this link for your reference. It will help you.
Thanks. Please mark it as an answer if it helps.

Versioning and Video Content type does not work.

Hello,
I have out of the box sharepoint installed.
When I apply versioning to a library. And try to see "Document set version history" (as I suggest Video content type actually inherits from Document Set). I don't see any version.
Can you tell me how can i see versions of the "Video" content type item in this Version History window?

Document set versions are slightly different than item versions. Document sets can be managed by a separate ribbon tab called Document Set and group called Manage.
Check below link for detail go through:
How to retrieve document set version history
Manage versions for Document Set
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer :)

Error while adding content type fields in the EditForm.aspx for an customlist item.

This is office 365. I have content type which is attached to custom list.
Added new site column "CustomerAction" which was added to Content type, now when I added this field in the EDITForm.aspx using the SharePoint designer, this form is called when the custom list item is being edited.
But when I added this extra field to EDITFORM.aspx it is giving error,. the standard correlationid error.
Can anyone suggest, what could be problem !
Thanks
Labhesh
Labhesh Shrimali

Hi Labhesh,
When we add the site column to the content type, there is an option to update the all
content types which inheriting from this type.
If we set this to Yes, then the site column will be added to the list where the content type or its child content type has been used and this column will be added to the EDITFORM.aspx too.
So we don’t need to re-add this site column to EDITFORM.aspx.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Issue with New Document in a document library with multiple content types

Hi,
I have a created a custom list definition based on a document library. I added 3 content types in this list, one is a document set (lets call it DOCSET), the two others are content types inheriting from Document (DOCA and DOCB).
I deployed the list definition with a site scoped feature and the list instance with a web scoped feature. After activating the two features, the list is created and the content types are present in the list.
When I click in the New Document button and choose either the DOCA or DOCB content type, a Word document opens and the DOCA content type is always associated to this Word document.
With SharePoint Manager 2013 I saw that the template.dotx document was not in the Forms/DOCA or Forms/DOCB folder.
So I decided to remove all the content types from the list definition and add them by code with the ListAdded event receiver. I used list.ContentTypes.Add to add the content types to the list.
With this method the templates are correctly copied from the template.dotx in the RootFolder/Forms folder of my list. These templates have the rights content type id, but the New Document button still does not work properly.
So I looked at the Content Types inside my library and saw that the DocumentTemplateUrl linked to the RootFolder/Forms/template.dotx and not the RootFolder/Forms/DOCA/template.dotx or RootFolder/Forms/DOCB/template.dotx.
I debugged my code to look closer and see that right after the list.ContentTypes.Add, the DocumentTemplateUrl is correclty set but when my EventReceiver finishes, the DocumentTemplateUrl get back to the RootFolder/Forms/template.dotx.
Have you any idea why this is not working ?
Regards

Hi,
Per my understanding, there is an issue about the DOCA and DOCB content types which inherits from Document Content Type in your custom list definition.
By default, if there is a custom content type inherits the OOTB Document Content Type, it will also inherits the template.dotx file from the OOTB Document Content Type.
The template URL of a custom content type which inherits the OOTB Document Content Type:
If you want to specify different templates for different content types, the code demo below would be helpful:
http://www.learningsharepoint.com/2010/07/14/programmatically-create-a-new-content-type-in-sharepoint-2010/
Thanks
Patrick Liang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Best Practises for using Content Types

We had third party vendor who migrated and re structured contents and sites in Sharepoint 2010. I noticed one unusual thing : In most cases they new separate site content types for every library in a site i.e. even if two libraries contain same set of metadata
columns they created separate site content types by duplicating it from the first one and gave it unique name and used in second library.
My point of view for content type is that they are used for re usability, i.e. if another library is needing same set of metadata columns then I would just reuse existing content type rather than creating another content type with different name by inheriting
it from the first one and having same set of columns.
When I asked vendor reason for this approach (for every library they created new content types and for libraries needing same set of meta data columns they just inherited from a custom site content type and created another duplicate one with same set of
meta data columns and gave it different name in most cases name of library ) they said they did that to classify documents which I did not agree with because by creating two document libraries classification is already done.
I need some expert advice on this, I will really appreciate: I understand content types are useful and they provide re usability but,
A) Do we need to create new site content types whenever we create new library ? (Even though we are not going to re use them)
B) What is best practice : if few libraries are needing same set of metadata columns
1) Create site a content type and reuse it in those libraries ? or
2) Create a site content type and create new content types by inheriting from site content type created at first and just give them different name even though all of them are having same set of columns ?
I need expert advice on this but following is my own opinion on this
I do not think point A) is a good practice and should not be used, we should create site content type only when we think it will be re used and we do not need to create site content type every time we create document library. Also I do not think point 2)
of B is a good practice as well
Dhaval Raval

It depends on the nature of the content types and the libraries. If the document types really are shared between document libraries then use the same ones. If the content types are distinct and non overlapping items that have different processes, rules or
uses then breaking them out into a separate content type is the way forward.
As an example for sharing content types: Teams A and B have different document libraries. Both fill in purchase orders, although they work on different projects. In this case they use the same form and sharing a content type is the no question approach.
As an example for different content types: A company has two arms, a consultancy where they send people out to client sites and a manufacturing team who build hardware. Both need to fill in timesheets but whilst the metadata fields on both are the same the
forms are different and/or are processed in a different manner.
You can make a case either way, i prefer to keep the content types simple and only expand out when there's a proven need and a user base with experience with them. It means that if you wanted to subdivide later you'd have more of a headache but that's a
risk I generally think works out.

Trouble finding schema type in JDeveloper XPath editor

Has anyone seen an issue where the JDeveloper XPath editor does not expose all XML schema types from a WSDL? The WSDL in question has a flattened WSDL with 4 different schema's (all having a different namespace). The xml elements in question have the nillable attribute set to "true" so I'm not sure if this could be causing the issue. Each schema does include namespace imports (<import namespace="" />) as well.
note: I will be unable to post wsdls as they contain proprietary info however they do validate in a XML validation tool.
JDeveloper version 10.1.3.3

It seems as if the xsd:extension element is not properly interpreted in JDeveloper. Post XPath query error - xml extension in schema gives a bug number but that was initiated in 2006 and it does not seem to be resolved. Does anyone know if this will be fixed in JDeveloper 11G. A workaround is to put all extension types within their parent or base type but it will probably break the web service and is almost impossible with size of the WSDLs I am working with.
Basically if this functionality is not fixed, it would eliminate developers from implementing any type of inheritance within web services. This needs to be fixed!

Inheritance for webservice parameters

Folks,
please pardon if this topic has been covered before, but my search has not found much on this specifically.
I am working on webservices using weblogic 9.1. Starting with an annotated Java bean, using jwsc/jws tasks to generate EJB, etc. All this is being done using ant scripts outside of the workbench.
I am running into a problem when I try to expose complex types with inheritance as web method parameters. If I have a base class A and classes B and C extend A, when I define webservice method to take A as an argument schema in WSDL does not include declarations for B and C.
If I create 2 separate methods for B and C, then I get correct WSDL.
I get the same behaviour if subclassing is involved with member variables of complex types.
Has anyone solved this problem before?
Thanks in advance for any tips.

Hi,
following link could be helpful for webservice ( OCI) Parameters and configuration..
SAP Supplier Relationship Management - SAP SRM Open Catalog Interface (B2B-OCI) [original link is broken]
Thanks
siva prasad.s

Like and type...

Kindly let me know when I have to use LIKE and when I have to use TYPE Exactly.
What is the difference b/w both..
Akshihta.

hi,
TYPE <type>
to refer to any data type <type> that is already known at this point in the program. It can be used in any of the statements listed below. The expression <obj> is either the name of the data object or the expression.
ABAP Statements with TYPE References
Definition of local program types using
TYPES <t> TYPE <type>.
The new data type <t> has the same type as <type>.
Declaration of data objects using
DATA <f> TYPE <type>.
CLASS-DATA <f> TYPE <type>.
CONSTANTS <f> TYPE <type>.
STATICS <f> TYPE <type>.
PARAMETERS <f> TYPE <type>.
The data object <f> has a data type corresponding to the type <type>.
Dynamic creation of data objects using
CREATE DATA <dref> TYPE <type>.
Specification of the type of a formal parameter in a subroutine using
FORM ... USING|CHANGING TYPE <type> ...
The technical attributes of the formal parameter are inherited from those of the declared data type <type>. You can then only pass actual parameters that have these attributes.
Specification of the type of a formal parameter in a method using
METHODS <meth> ... IMPORTING|EXPORTING|CHANGING TYPE <type> ...
The technical attributes of the formal parameter are inherited from those of the declared data type <type>. You can then only pass actual parameters that have these attributes.
Specification of the type of a field symbol
FIELD-SYMBOLS <fs> TYPE <type>.
You use the LIKE addition, similarly to the TYP E addition , in various ABAP statements for defining data types and specifying the types of interface parameters or field symbols. The addition
LIKE <obj>.
ABAP Statements with LIKE References
Definition of local types in a program using
TYPES <t> LIKE <obj>.
The new data type <t> inherits all of the technical attributes of the data object <obj>.
Declaration of data objects using
DATA <f> LIKE <obj>.
CLASS-DATA <f> LIKE <obj>.
CONSTANTS <f> LIKE <obj>.
STATICS <f> LIKE <obj>.
PARAMETERS <f> LIKE <obj>.
The data object <f> inherits all of the technical attributes of the data object <obj>.
Dynamic creation of data objects using
CREATE DATA <dref> LIKE <obj>.
Specification of the type of a formal parameter in a subroutine using
FORM ... USING|CHANGING LIKE <obj> ...
The technical attributes of the formal parameter are inherited from those of the declared data object <obj>. You can then only pass actual parameters that have these attributes.
Specification of the type of a formal parameter in a method using
METHODS <meth> ... IMPORTING|EXPORTING|CHANGING LIKE <obj> ...
The technical attributes of the formal parameter are inherited from those of the declared data type <type>. You can then only pass actual parameters that have these attributes.
Specification of the type of a field symbol
FIELD-SYMBOLS <fs> LIKE <obj>.
The technical attributes of the field symbol <FS> are inherited from those of the declared data object <obj>. You can then only assign data objects that have these attributes.
You should also avoid using the LIKE addition in other ABAP programs except to refer to data objects
regards,
Ashokreddy.

WARNING: Complex type 'any' cannot be supported

Not sure what to make of this warning ... any suggestions?
oracle.adfinternal.model.adapter.webservice.MessagePart checkComplexPrototype
WARNING: Complex type 'any' cannot be supported

I actuall have the same problem but I can give you some more context.
I have a Webservice made with JAX-WS in JDeveloper it uses Complex types with inheritance such as:
abstract class Mammal{
public Mammal get(){ return this; }
@WebService
public class Human extends Mammal {
@WebMethod
public Mammal get(){ return this; }
Exposing the WSDL to i.e. C# works perfectly the Polymorphism works like a charm, however when i follow the JSF tutorial from the JDeveloper page and want to add my method get i get the following error:
Sep 2, 2009 3:32:29 PM oracle.adf.adapterDC.webservice
WARNING: Complex type '{http://local/}mammal' cannot be supported
Is this due to that Mammal is Not exposed correctly or what could possible cause this?
A popup also shows that an error occured telling me the following:
"DCA-29000: Unexpected exception caught:
java.lang.NullPointerException, msg=null"
Thanks,
Filip

Content Types

So here is my scenario. We are a small business (3 people) who develop learning content and want to use a SP doc library to manage it.
Our hierarchy of content is as follows:
Curriculum 1
     ----> Course 1
            -----> Lesson 1
            -----> Lesson 2
    -----> Course 2
            ------> Lesson 3
           ------> Lesson 4
Curriculum 2 with courses and lessons and so on...
Our document is a Lesson. Lessons are used in courses. Courses are used in a Curriculum.
My though was that I could use Content Types for Courses that will contain all Course Names and the same for Curriculum for all Curriculum names as it will it a lot easier as we add more and more Lessons to the document Library.
But never having used content types before I am not sure how to do that. I know where the Content Types are added but I don't know how to add the data to the content types and then attach it to the Lesson documents.
Anyone have any ideas on what I might need to do?

it all depends on the total number of docs, docs/course, courses/curr, etc.But just at a glance of what you've shown here, I would say you will definitely want to use document sets, to enable them, activate the site collection level feature named document
sets. this is essentially a folder turned into a content type, so you can store documents within the "document" (set). great for metadata and properties in this scenario, as you can set a property on the document set and have all of the content
within it share that property value. you could then set more specific metadata on the sub-items. I would think something like this might work:
1 document library for each curriculum with custom columns that are specific to the entire curriculum as a whole (you could create a library with the columns, then save it as a template to reuse for new curriculum without having to redo the column settings).
also, make sure to allow management of content types on the library, this will let you specify which content types are allowed
1 content type which inherits from document set CT. set the columns which would be used for the course, you can also mark if those are shared to children or just apply to the doc set itself.
1 content type which is a child of Document which is fairly generic, but has the basic columns which apply to all your documents, from there, if you wanted, you could create children CTs of this to allow for a more customizable feel for different types of
lessons. maybe an online lesson vs inperson lesson uses different types of metadata columns, etc (this type of project is really all based on your business needs and extremely specific to each individual company/dept, etc. people quite frequently
hire consultants and bus. analysts specifically to design this hierarchy)
add the content types to your library and start messing about creating them and test how you like the shareing of properties, and views, etc. if you're going it alone on this in a small business, there will be a lot of trial & error and just getting
a feel for what you want/need. hopefully we can help you through it here in the forums
for reference (also, fyi, libraries are the same as lists, but with docs. so setting things up are the same either way. Also, 90% of the stuff you find for 2010 in this area will also work or be extremely similar in 2013). there's a lot
here, I would just skim some of it and try things out yourself.:
http://msdn.microsoft.com/en-us/library/ff630940(v=office.14).aspx - Create Lists with Custom Content Types in SharePoint 2010
http://office.microsoft.com/en-us/sharepoint-designer-help/create-and-edit-content-types-HA101774775.aspx - create/edit custom content
types with SharePoint Designer
http://www.learningsharepoint.com/2010/10/22/create-content-type-in-sharepoint-2010/ - quick walkthrough from creating the columsn, content type, then adding
to a list/library
http://www.sharepointnoob.com/2012/03/29/howto-create-site-column-sharepoint-2010/ - creating site columns
http://office.microsoft.com/en-us/sharepoint-server-help/introduction-to-document-sets-HA101782466.aspx - intro to document sets
http://msdn.microsoft.com/en-us/library/office/ee559339(v=office.14).aspx - more in depth on doc sets
http://technet.microsoft.com/en-us/library/cc262873(v=office.14).aspx - planning information architecture for SP
http://technet.microsoft.com/en-us/library/cc262900(v=office.15).aspx - information management & governance in SP
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

Inheritance architecture question

Hello,
I've an architecture question.
We have different types of users in our system, normal users, company "users", and some others.
In theory they all extend the normal user. But I've read alot about performance issues using join based inheritance mapping.
How would you suggest to design this?
Expected are around 15k normal users, a few hundred company users, and even a few hundred of each other user type.
Inheritance mapping? Which type?
No inheritance and append all attributes to one class (and leave these not used by the user-type null)?
Other ways?
thanks
Dirk

sorry dude, but there is only one way you are going to answer your question: research it. And that means try it out. Create a simple prototype setup where you have your inheritance structure and generate 15k of user data in it - then see what the performance is like with some simple test cases. Your prototype could be promoted to be the basis of the end product if the results or satisfying. If you know what you are doing this should only be a couple of hours of work - very much worth your time because it is going to potentially save you many refactoring hours later on.
You may also want to experiment with different persistence providers by the way (Hibernate, Toplink, Eclipselink, etc.) - each have their own way to implement the same spec, it may well be that one is more optimal than the other for your specific problem domain.
Remember: you are looking for a solution where the performance is acceptable - don't waste your time trying to find the solution that has the BEST performance.

Type of inheritance

Similar Messages

Maybe you are looking for