[wildfly-dev] WFLY-508, JBeret initial review and integration issues

[Jason Greene]

On Jul 24, 2013, at 12:05 PM, Cheng Fang <cfang at redhat.com> wrote:

>> #2) Why does JBeret duplicate facilities already present in the 
>> WildFly code base and deployer chain - e.g. annotation indexing, 
>> reflection indexing, thread management, parsing facilities, etc.?
> Batch spec require an impl to be run in either Java EE or Java SE 
> environment.  So inevitably certain services have to reside in JBeret 
> itself to satisfy the SE runtime.  Since we started the impl as a 
> standalone first, there may be certain aspects that do not fit nicely in 
> WildFly.  It is in the plan to better align with the appserver by 
> leveraging existing services when running inside WildFly.  For example, 
> use the concurrency utils in EE.

Yeah it would be nice if we could abstract that bit.

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat