Understanding Java Composition Part 1

Java Composition Part 1- From my Complete Java Developer course.

[@FontySchriek]

This is an excellent example of Aggregation, not of Composition! In Composition the PC is the owner of its parts (motherboard,case, monitor) to enforce life-long dependency , so the motherboard, case and monitor objects should never exist as stand alone objects outside of the PC object, since this would mean you still would have a reference to them, even if you would mark the PC object for deletion (by setting: thePC = null;)

[@missjude01]

so should the motherboard, case and monitor be created inside the PC constructor? or should the tutorial be renamed to aggregration in java?

[@muhammedwafa9646]

the fun thing is i am taking your course on Udemy and i did not understand it there, then i said maybe i can find anything on youtube that can help, then i found you lol .. the same video that i did not understand earlier.

[@bern1223]

You monster. You took one of the greatest IDE's in the world and you put it on light theme! I could hardly recognize it! Great tutorial though.

[@karthiknatarajan8990]

but it is aggregation not composition because lifetime of monitor case is not dependent of pc object

[@kwabenaampofo5094]

seen other videos on the topic, this has been the best so far. thanks for making this

[@SamuelNKiap]

I enjoyed the tutorial as Aggregation. Composition should have code to create contained object inside the constructor.

[@Frazful]

Best video on composition I came across. Subbed, thank you sir!

[@inayatullah67]

I'm a taking course of yours on udemy and its fantastic.

[@bilalrana4863]

Great example to explain Composition Thanks Tim !!

[@amirsmair71]

finally i understand this concept .. thanks so much

[@yamaraahi]

.Thank You .You just described a great example greatly but for suggestion, I think it might be better to make it simpler ... I mean do not going too much on details would be better

[@milosdjokovic5735]

Good job! Very well explained

[@anikv25]

Thank you!

[@deactivisiongames9961]

Great work !!!!!

[@atomatom4825]

Good job

[@deactivisiongames9961]

Loved your tutorial !!!!!

[@mohammadsulaiman2301]

thanks

[@weetyytasdsa3855]

do you make sure this is Composition ? if it compostion why dont you try add line pc = null and see whether or not Case ,Monitor and Motherboard already delete ?

[@krishnashakya2858]

Pretty neat. thank you

[@facundocolino5017]

There is something that I can't undestand. For instance if the PC object is composed by a Case object, I think that you should have a new Case() sentence inside the PC constructor. The way you implemented it, creating the Case object in the main and passing the reference to the set method, looks more like aggregation than composition to me.

[@mk42948]

Greate, thanks)

[@jecksonulloa1174]

Thank you!!!

[@ckbapps2009]

I have owned the full course... Very depth course.. I have one problem. In Monitor class, in getter method public String getNativeResolution() { return nativeResolution; } It is showing me an error - Incompatible types: Required: Java.lang.String Found: com.Composition.Resolution I am also using same IDE.... Please help

[@sovanraksa2112]

Thank you so much

[@rizwandogar9563]

Hey Awesome man Thanku #Tim

[@TheLearnProgrammingChannel]

+Rizwan Dogan Thanks for that :)

[@CuteWorld.1]

thanks a lot

[@avi_mukesh]

Thank you so much for this video! Very nicely explained. However, I have one question: where you called the drawPixelAt() method like thePC.getMonitor().drawPixelAt(x,y,""), this does the same thing as theMonitor.drawPixelAt(x,y,""). Why is the previous way better? Is it simply so you only have to remember the name of the PC object?

[@niklasmenard4872]

A few very interesting points made in this video and I like that the computer example is easy to visualize. Maybe next time use less time creating classes and more focus on the subject at hand (what is composition). This is my personal opinion though.

[@TheLearnProgrammingChannel]

Thanks for the feedback Niklas :)

[@jdfdoyley]

Great tutorial Tim, however, I wanted to know what your reason for using only "getters" as oppose to using both "getters and setters"?

[@TheLearnProgrammingChannel]

Thanks Jason. The reason is sometimes you may have a class where you don't want to allow an external class to update fields directly. Think of a bank account for example. You would probably be happy to have a getter to retrieve the balance, but would not want a setter to update the balance directly. You would probably want to only allow the balance to be affected by a particular method that validates the amount passed, logs the transaction, etc.

[@prakashale1627]

Brilliant tutorial that I have ever watched ! By the way, I got a question, which platform you are using for code, I don't think it is eclipse :)

[@TheLearnProgrammingChannel]

Thanks :) It's IntelliJ, the IDE by Jetbrains

[@ef28525]

Lately i've been hearing Composition > Inheritance, but i've been having trouble understanding how to build structures so that they avoid inheritance. Can someone give an example of how the vehicle class could be set up as composition instead of inheritance.

[@bohdanbrazhynenko9684]

Hi there! Did you find the answer to your question? I am also concerned about this issue(

[@RamaKrishna-xp4ju]

Great Video .. Can I know any videos on jsp

[@TheLearnProgrammingChannel]

+Rama Krishna I dont, sorry.

[@irasemaangeles9035]

Aggregation please!!

[@TheKarl321]

can't believe i baught the course from udemy

[@TheLearnProgrammingChannel]

+Karl Samaha You are enjoying the course on udemy? This is one of the 100+ videos on udemy for this course.