주제 비교 허브

EJB 3.0 vs Spring

EJB 3.0 과 Spring 의 차이를 구조화된 비교 표에서 확인한 뒤, 관련 면접 질문, 퀴즈, 유사 비교로 이어가세요.

11 비교 포인트

7 관련 비교

차이점 비교

EJB 3.0 vs Spring - A key comparison and difference of the topics or subjects that will help you understand which is best for your use case. Check out to compare Spring and EJB 3.0 as very common job interview questions.

비교 개요

EJB 3.0 과 Spring 의 차이

EJB 3.0 이 나란히 비교의 첫 번째 주제입니다.

11 현재 이 페이지에서 확인할 수 있는 비교 항목입니다.

Spring 이 나란히 비교의 두 번째 주제입니다.

EJB 3.0 Interview Online Test	Spring Interview Online Test
Dependency Injection: Can inject anything in the container including EJBs, data sources, JMS resources and JPA resources.	Dependency Injection: Can inject almost anything including lists, maps, properties and JNDI resources.
Transaction management: Works right out of the box, but only JTA is supported.	Transaction management: Have to configure it to make it work, but supports a number of strategies including JTA, JDBC and Hibernate.
Persistence: Tightly integrated through JPA.	Persistence: Framework support for JPA, Hibernate, JDBC, iBatis.
State management: Robust support through Stateful Session Beans and Extended Persistence Context.	State management: Indirect support dependent on web container session management.
Web Services: Seamless support for JAX-WS 2.0	Web Services: Poor direct support, best integration available is via configuring XFire for registered beans.
Messaging: Supported out of the box through Message Driven Beans.	Messaging: Need to add configuration for message listeners. However, JMSTemplate adds nice abstraction over JMS.
AOP: Simple but limited support through interceptors.	AOP: Robust support through AspectJ and Spring AOP alliance.
Security: Integrated support for declarative and programmatic security through JAAS.	Security: Must add and configure Acegi security. However, support beyond JAAS is possible through Acegi.
Scheduling: Simple scheduling possible through EJB Timer service.	Scheduling: Must add and configure Quartz for scheduling.
Remoting: Integrated support through Session Bean remote interfaces. Supports distributed transactions and security.	Remoting: Remoting support may be added via configuration. Remote transactions and security are not supported. However protocols other than RMI such as Hessian and Burlap are supported.
Use EJB 3 If: - You like annotation and dislike a lot of XML configuration. - You prefer a tightly integrated solution stack that makes sensible default choices for you and minimizes configuration. - Your application is very stateful. - Standardization is an important consideration. - You use JSF and are considering using Seam.	Use Spring if: - Your application requires fine-grained control at the container level. - Your application requires a lot of configuration beyond gluing together components and resources. - You need advance AOP feathers.

복습용 저장

이 항목을 북마크하거나, 어렵게 표시하거나, 복습 세트에 넣을 수 있습니다.

내 학습 라이브러리 열기

도움이 되었나요? 예 아니요

비슷한 비교 더 보기

아래에서 차이점 보기

아래의 모든 주제 비교를 살펴보거나, 위 검색창을 사용해 목록을 즉시 좁혀보세요.

집중 학습 경로, 모의고사, 면접 준비 콘텐츠로 실력을 키우세요.

EJB 3.0 vs Spring

차이점 비교

EJB 3.0 과 Spring 의 차이

복습용 저장

관련 차이점

아래에서 차이점 보기

WithoutBook