Tech Trek: A Software Engineer's Guide to Code and Beyond

Yesterday while working on my project, I got one requirement where I need to store list of Array into the database, I checked on Google, went through various site but didn't get much information. Everyone talks about creating new entity and do onetomany relationship BUT I wanted to create a collection of basic types. Finally I come across @ElementCollection annotation provided by JPA 2.0 which resolves my problem. Problem : Input JSON which we need to store in DB: { "schemas": ["urn:scim:schemas:core:1.0", "urn:scim:schemas:extension:enterprise:1.0"] }            Where schemas is Array of String. Solution : Just add following annotation in your POJO i,e @ElementCollection @CollectionTable(name = "SCIM_SCHEMAS", joinColumns = @JoinColumn(name = "SCHEMA_ID")) @Column(name = "SCIM_SCHEMA") private List<String> schemas; It will create the table named "SCIM_SCHEMAS" having columns 'SCHE...

This tutorial will demonstrate how can you generate Java Objects from XML documents using xjc tool. The tool “xjc” is used to generate the annotated Java classes from the XSD schema Suppose I am using below XML file to generate Java Objects i,e <?xml version="1.0" encoding="UTF-8"?> <adaptorapp id="application"> <instance id="instance1"> <connectiondetails> <accesskey>abcde</accesskey> <secretkey>fghij</secretkey> </connectiondetails> </instance> <instance id="instance2"> <connectiondetails> <accesskey>klmnop</accesskey> <secretkey>qrstuvwxyz</secretkey> </connectiondetails> </instance> </adaptorapp> Now  to generate Java Objects we need to create one xsd file(say "connection.xsd") : <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema...

In hibernate, You cannot have two classes with the same name in the same or different packages else you will get an error at runtime like " Caused by: org.hibernate.DuplicateMappingException: duplicate import: ....(try using auto-import="false ")" I have resolved this issue by adding property name on the Entity annotation. Let us suppose I have Meta class in two different packages "com.database.user" and "com.database.group', you can resolve it as : package com.database.user @Entity( name= "com.database.user" ) @Table(name="USER_META") public class Meta package com.database.group @Entity( name= "com.database.group" ) @Table(name="GROUP_META") public class Meta There must be some other ways too to resolve this issue, So please feel free to share it :)