This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin in Action and have Dmitry Jemerov & Svetlana Isakova on-line!
See this thread for details.
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

cleared scwcd exam with 62% -sonimoni  RSS feed

manish sarda
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
first of all sorry for posting the message in new topic as i has to change my id so that naming policy could be followed
i just made it
i use whizlabs it was ok not to the standarad of enthuware's jqplus(my personal opinion)
i would like to thank ken for his notes and also miftakhan's notes(Only if i would have studied them before going to exam)
i would like to make a point please read the notes of miftakhan
they are very detailed and question were asked on the topics like type of value of auth-constraint --basic,digest,form,client-cert The URL to notes are
i had four question on auth-constraint.
also i had two question of design patterns not in the objectives)
(copied from miftakhan's notes)
13.1. Front Component: Provides centralized dispatching of requests, e.g. via a controller servlet; enables centralized handling of security, navigation, and presentation formatting
13.2. Fa�ade: Provides a layer between clients and subsystems of a complex system; shields clients from subsystem components, making the subsystems easier to use.
13.3. Factory: Handles requests for object creation
13.4. Singleton: A class which can have at most one instance
13.5. Template Method: The key idea is that there is a basic algorithm we want to stay the same, but we want to let subclasses vary how they do the steps. The Template Method says to define the algorithm in the parent class, but implementations of the steps in the subclasses.
13.6. Bimodal Data Access: Under certain conditions, allows designer to trade off data consistency for access efficiency. JDBC provides read-only, potentially dirty reads of lists of objects, bypassing the functionality, and the overhead, of Entity enterprise beans. At the same time, Entity enterprise beans can still be used for transactional access to enterprise data. Which mechanism to select depends on the requirements of the application operation.
13.7. Session Entity Fa�ade: Being an instance of the Facade pattern, this pattern shares its applicability. In the context of J2EE application development, use the Session Facade pattern when you want to provide a simple interface to a complex subsystem of enterprise beans or when you want to reduce communication and dependencies between client objects and enterprise beans.
Manish Sarda
B.Com,Grad CWA.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!