Please svn move them to ejb-container or a similar module.
On Monday 12 December 2011 11:22 PM, Cheng Fang wrote:
> Hi Sahoo,
> From the commit message, they were moved from ejb-container to ejb-connector to address issue http://java.net/jira/browse/GLASSFISH-17038 (3.1.1 deployment performance - ejb container module get loaded for a pure web application)
> Now that you've added @AnnotationHandlerFor to enable the dynamic handler loading, we can move them back to ejb-container.
> These ejb-related annotation handlers are now in ejb-connector module in both trunk and 3.1.2 workspaces. I noticed @AnnotationHandlerFor is only available in trunk. Sahoo, do you plan to port it to 3.1.2, too? If not, we will just leave ejb annotation handler classes in ejb-connector.
> r48934 | cf126330 | 2011-08-19 17:58:39 -0400 (Fri, 19 Aug 2011) | 2 lines
> Fix issue 17038 3.1.1 deployment performance - ejb container module get loaded for a pure web application. Move annotation handler
> classes, archivist classes, scanner classes and related from ejb-container to ejb-connector, ran QL and ejb devtests. (the same s
> et of fix is also in 3.1.2 branch.)
> On 12/9/11 10:27 PM, Sahoo wrote:
>> Marina, Cheng,
>> Do one of you remember why they are kept in connector module now? I would like them to be moved to some implementation module.