Exactly how to do this depends on the version of Jackson that you’re using. This changed around version 1.9, before that, you could do this by adding @JsonIgnore to the getter. Which you’ve tried: Add @JsonIgnore on the getter method only Do this, and also add a specific @JsonProperty annotation for your JSON “password” field … Read more
The persistence.xml has a jar-file that you can use. From the Java EE 5 tutorial: <persistence> <persistence-unit name=”OrderManagement”> <description>This unit manages orders and customers. It does not rely on any vendor-specific features and can therefore be deployed to any persistence provider. </description> <jta-data-source>jdbc/MyOrderDB</jta-data-source> <jar-file>MyOrderApp.jar</jar-file> <class>com.widgets.Order</class> <class>com.widgets.Customer</class> </persistence-unit> </persistence> This file defines a persistence unit named … Read more
There are arguments for both, but most of them stem from certain user requirements “what if you need to add logic for”, or “xxxx breaks encapsulation”. However, nobody has really commented on the theory, and given a properly reasoned argument. What is Hibernate/JPA actually doing when it persists an object – well, it is persisting … Read more
@Component Preferable for component scanning and automatic wiring. When should you use @Bean? Sometimes automatic configuration is not an option. When? Let’s imagine that you want to wire components from 3rd-party libraries (you don’t have the source code so you can’t annotate its classes with @Component), so automatic configuration is not possible. The @Bean annotation … Read more
Compile constants can only be primitives and Strings: 15.28. Constant Expressions A compile-time constant expression is an expression denoting a value of primitive type or a String that does not complete abruptly and is composed using only the following: Literals of primitive type and literals of type String Casts to primitive types and casts to … Read more
The best way is: <bean id=”dao” class=”org.mockito.Mockito” factory-method=”mock”> <constructor-arg value=”com.package.Dao” /> </bean> Update In the context file this mock must be listed before any autowired field depending on it is declared.
The answer your question is no – @Transactional will have no effect if used to annotate private methods. The proxy generator will ignore them. This is documented in Spring Manual chapter 10.5.6: Method visibility and @Transactional When using proxies, you should apply the @Transactional annotation only to methods with public visibility. If you do annotate … Read more
I think transactions belong on the service layer. It’s the one that knows about units of work and use cases. It’s the right answer if you have several DAOs injected into a service that need to work together in a single transaction.
<context:annotation-config> is used to activate annotations in beans already registered in the application context (no matter if they were defined with XML or by package scanning). <context:component-scan> can also do what <context:annotation-config> does but <context:component-scan> also scans packages to find and register beans within the application context. I’ll use some examples to show the differences/similarities. … Read more
It’s a function annotation. In more detail, Python 2.x has docstrings, which allow you to attach a metadata string to various types of object. This is amazingly handy, so Python 3 extends the feature by allowing you to attach metadata to functions describing their parameters and return values. There’s no preconceived use case, but the … Read more