qwef

public class ApplicationContextBasicFindTest { AnnotationConfigApplicationContext ac = new AnnotationConfigApplicationContext(AppConfig.class); @Test @DisplayName("빈 이름으로 조회") public void findBeanByName(){ MemberService memberService = ac.getBean("memberService", MemberService.class); //Assertions.assertThat(memberService.getClass()).isEqualTo(MemberServiceImpl.class); Assertions.assertThat(memb..

public class ApplicationContextInfoTest { AnnotationConfigApplicationContext ac = new AnnotationConfigApplicationContext(AppConfig.class); @Test @DisplayName("모든 빈 출력") public void findAllBean(){ String[] beanDefinitionNames = ac.getBeanDefinitionNames(); for (String beanDefinitionName : beanDefinitionNames) { Object bean = ac.getBean(beanDefinitionName); System.out.println("bean = " + bean); } ..

앞에서 했고, ApplicationContext를 BeanFactory가 감싸고 있는데, ApplicationContext가 여러 기능을 가지고 있고 컨테이너를 관리하므로 ApplicationContext를 그냥 컨테이너로 보면 된다.

@Configuration public class AppConfig { @Bean public MemberService memberService(){ return new MemberServiceImpl(memberRepository()); } @Bean public MemberRepository memberRepository() { return new MemoryMemberRepository(); } @Bean public OrderService orderService(){ return new OrderServiceImpl(memberRepository(), discountPolicy()); } @Bean public DiscountPolicy discountPolicy() { return new Rat..

IoC 제어흐름 역전 프레임워크가 알아서 구현객체 생성, 본래 클라이언트가 스스로 객체생성, 연결, 실행이 자연스러운 흐름이었지만, AppConfig 등장 이후 각 구현체는 자신의 로직만 담당. 프레임워크 vs 라이브러리 프레임워크: 내가 작성한 코드들을 제어, 대신 실행 라이브러리: 내가 제어 흐름을 담당하는 코드를 직접 짜면 라이브러리 정적인 객체 의존관계 코드만 보고 알 수 있는 의존관계들. public class OrderServiceImpl implements OrderService{ private MemberRepository memberRepository; private DiscountPolicy discountPolicy; public OrderServiceImpl(MemberReposit..

AppConfig 덕에 앱의 사용 영역과 구성 영역이 분리 public class AppConfig { public MemberService memberService(){ return new MemberServiceImpl(memberRepository()); } private MemberRepository memberRepository() { return new MemoryMemberRepository(); } public OrderService orderService(){ return new OrderServiceImpl(memberRepository(), discountPolicy()); } private DiscountPolicy discountPolicy() { return new RateDis..

기존 어떤 구현체가 써져 있었는지 잘 안보임. public class AppConfig { public MemberService memberService(){ return new MemberServiceImpl(memberRepository()); } private MemberRepository memberRepository() { return new MemoryMemberRepository(); } public OrderService orderService(){ return new OrderServiceImpl(memberRepository(), discountPolicy()); } private DiscountPolicy discountPolicy() { return new FixDscountPoli..

결국, 역할은 있지만 그걸 구체적으로 누가 할지 선택하는 감독자 역할이 필요. 그 감독자가 컨테이너 public class MemberServiceImpl implements MemberService{ private final MemberRepository memberRepository; public MemberServiceImpl(MemberRepository memberRepository) { this.memberRepository = memberRepository; } @Override public void join(Member member) { memberRepository.save(member); } @Override public Member findMember(Long memberId) { r..

public class OrderServiceImpl implements OrderService{ private MemberRepository memberRepository = new MemoryMemberRepository(); private final DiscountPolicy discountPolicy = new FixDscountPolicy(); @Override public Order createOrder(Long memberId, String itemName, int itemPrice) { Member member = memberRepository.findById(memberId); int discountPrice = discountPolicy.discount(member, itemPrice)..

public class RateDiscountPolicy implements DiscountPolicy{ private int discountPercent = 10; @Override public int discount(Member member, int price) { if(member.getGrade() == Grade.VIP){ return price * discountPercent / 100; }else{ return 0; } } } 저 할인 퍼센트.. 처음에 그냥 간단하게 price / discountPercent 이렇게 생각했는데 그러면 안된다.. 로직이 어렵다고 해서 뭔소린가 했더니.. 이게 참 테스트가 중요하다.. 다방면으로 테스트 해 봐야 한다. price = 10000,discountPe..