hybris - Jalo Layer vs Service Layer -

whats difference between jalo layer , service layer in hybris commerce suite? appreciate if give example along with. know jalo layer has been deprecated still if have specify layer use in platform tell hybris or how tell hybris use specific layer ?

i think it's best if read on quite hybris wiki regarding both:

jalo: https://wiki.hybris.com/display/release5/jalo+layer

service layer: https://wiki.hybris.com/display/release5/servicelayer

you won't have specify 1 use (they both running) , if start new project must (or @ least really should!) use service layer exclusively jalo go away (so @ least quite time) in 1 of next major releases. in nutshell, jalo old persistence mechanism while service layer introduced address various problems jalo layer had (performance/caching, extensibility, etc etc).

so if only/mostly working on new projects won't have acquire knowledge jalo layer, if plan on becoming hybris consultant or work on old legacy hybris code have deal jalo more.

a small example: in items.xml files (where declare data model) can specify jaloclass attribute while make platform create java class you. e.g.: core-items.xml has product declared jaloclass="de.hybris.platform.jalo.product.product". platform automatically creates respective servicelayer class (always called *model.java, e.g. de.hybris.platform.core.model.product.productmodel. 1 limitation of jalo layer e.g. if want extend product item type in 1 of own extensions attribute, newly created attribute not @ product jalo class (as resides in platform , created once), instead available on extensions manager class bit unintuitive , cumbersome. service layer creates of model classes after analyzing , merging registered extensions , therefore able add attribute @ actual productmodel class. there many more differences, if have more concrete questions feel free ask them :)