hammock Add JNDI server support

JNDI server is mandatory if we want to add feature like #24 and JTA support.

Sep 03 '16 14:09 antoinesd

I think there's some ways to do the integration without JNDI. Specifically, overriding the Bittronix integration in hibernate to not use JNDI to look up the user transaction. This would be true of other JTA impls out there. Narayana seems to be notorious for its use of JNDI so I'd be cautious to bring it in.

Sep 03 '16 20:09 johnament

You're right, we could do without JNDI, but it may imply that we'll have to support specific integration should we have multiple JPA impl support later. I have to check, but JPA support datasource addition in persistence.xml only thru JNDI lookup.

Sep 04 '16 11:09 antoinesd

Also not true. We can implement PersistenceUnitInfo and provide the DataSource instance as needed.

Sep 04 '16 21:09 johnament

Antoine and I spoke about this. We agreed, the best solution is to provide a "simple" JNDI like service for binding beans, probably just named beans, in a look up.

Sep 21 '16 21:09 johnament