Open sandeepkhanzode opened 7 years ago
@sandeepkhanzode well, if you pass NULL
and there is @NotNull
annotation, you get an exception. That's what jcabi-aspects is doing.
I'm not sending null, still getting same exception(may not be empty). Below is the method argument
@NotBlank @FormParam(MOBILE_PHONE_NUMBER) String mobilePhoneNumber
I started to integrate jcabi-aspects into an already built Spring application with JSR-303 Hibernate-Validator based annotations. The @Loggable seems to work displaying the time, etc. But the existing TestNG test cases fail at weird code locations. Weird since the @NotNull annotation should not fail because a properly mocked instance of the argument is being passed in the test. I can verify this by removing the ajc plugin from the build->plugins in pom.xml and running the test. Of course, everything works properly.
I am not sure why the MethodValidator of jcabi is being invoked at the stack trace below. Please let me know what I should check. Thanks!!
I am using jcabi-aspects v.0.22.5 and aspectjrt v.1.5.4
I also see this in the logs for init JMockit mocks ...