hybris

• 
  

Java Ecommerce Platforms

• Hybris
•  

JPA Errors

• o.h.t.s.e.i.InformationExtractorJdbcDatabaseMetaDataImpl:365 - HHH000262: 

  Table not found:

  • the solution of above is terminate the current application

    • remove the application from the server and restart 

domain modelling

• write the queries that would be executed against the domain model. 
• test their performance
• 
  

UML

• careful written specification
• use case
• domain model
• architecture diagram 
• model driven architecture
• 
  

• agile modeling classDiagram
• association class 
• c_unidir_bidir_relationships.html 
•  One rule in database design is that a running system should never require a design change just to add data (changes to the design do occur, of course, just not in response to a new data value).
•  association
  aggregation
  dependency
  weak entity
  
  association class
  abstraction through interface
  abstract class
  cardinality
  unidirectional vs bidirectional relationships
  
  
  constraints and validation
  data binding
  type conversion
  
  
  component diagram
  deployment diagram
  
  use case diagrams
  
  ================================
  
  
  OOAD
  UML
  Agile modelling
  Design Pattern
  JPA
  hibernate
  
  Iconix
  RUP
  ====================
  the best practices of above all
  
  book JPA with hibernate by gavin king
  
  
  •  sequence diagram
  • dependency vs association
  • it's a best practice to prefer unidirectional relationships in a model whenever possible
  • if we group similar attributes in the form of a multiple classes then the change in one wont change all the clases. instead if there is a single class then if any change is made then whole class is affected
  • 
    
    

data type

• int is the best data type if only year has to be stored
• 
  

Stay Motivated

• Learn the Basics
• Study
• best books
• reference documentation
• Meditate
• Always Experiment
• Note down the confusion
• Ask the expert
• Stackoverflow
• Never ever think negative
• Refine
• Test everything
• Make notes of the lessons
• Learn from the best by paying
• Teach for free 
• watch videos
• Connect with the Community of the like minded people
• NEVER GIVE UP
• Think about Gail Devers and Magic Johnson
• Be Pure
• Help Others
• Fight
• Focus on what you love
• Sacrifice everything for the Goal
• Dream Dream Dream
• Passion My friend
• If you believe you can do it
• Always Say I shall do it!!!
• Pray Hard
• Work Harder
• Remember Lincoln
• Enhance your focus
• Remember Arjuna
• Consistency is the key
• water can break mountains
• Remember Eklavya
• Nobody taught him
• Refine your Code
• Apply the Design Patterns
• Apply the Best Practices
• 
  

Spring Expression Language

• SPEL

 

The best Practices

• JMX
• Web Services
• OSGi
• MicroServices
• Clusters
• Load Balancing
• UML
• Visual Paradigm
• Functionalities in the form of REST
•  Messaging 
• WebSocket
• RabbitMQ
• STOMP
• 
  

JPA

• mapped superclass should be represented as abstract classes in Java. 
• super classes that represent partial state  should better be represented as abstract classes
• single table inheritance is the best strategy
• In single table inheritance mapping the subclasses do not require to have id fields.

inheritance

• apply inheritance to class only if it is really required esp with respect to JPA. ie it should be done if data is divided among the subclasses to a great extent not just to share common methods otherwise it will create complex joins and take much time for accessing the required data.
•