Clearly the second. Like EE runs on top of SE, low level and cross cutting concerns, which Configuration obviously is, are better handled on SE level, being flexible enough so it fits well into EE. Let Tamaya run only as EE component will disqualify it for being able to configure the EE parts itself, which is one of the targets. Fortunately including a SE component in EE is not a big thing, despite that it shows the areas, where the EE spec still has its huge long time deficencies, e.g. the specification of classloaders.
We have to find sensible solutions for that areas, but perhaps our work even helps to increase preasure on the EE spec (Oracle) to tackle this topic finally ;) Anatole . 2015-01-03 15:21 GMT+01:00 John D. Ament <[email protected]>: > All, > > I'd like to bring this discussion up because it seems like we have > different takes. > > Is Tamaya intended solely for use within containers, or is it a plain Java > SE library that happens to be able to run within a container? > > John > -- *Anatole Tresch* Java Engineer & Architect, JSR Spec Lead Glärnischweg 10 CH - 8620 Wetzikon *Switzerland, Europe Zurich, GMT+1* *Twitter: @atsticks* *Blogs: **http://javaremarkables.blogspot.ch/ <http://javaremarkables.blogspot.ch/>* *Google: atsticksMobile +41-76 344 62 79*
