GlassFish runs JWSDP samples...again...

So I decided to revert the deployment check that we added in the GlassFish build32 reported by ias The issue was that we added a deployment check for pre-Java EE 5 applications to ensure that classes were not containing Java EE 5 annotations.

I decided to add the check because I anticipated that many folks would want to try the new cool features of Java EE 5 the cheap way : they would just take an existing J2EE 1.4 applications and add a couple of annotations to their sources to try injection. The result of such an experiment is always a NullPointerException since injection is not supported for pre-Java EE 5 applications. For injection to work, they also need to also update their deployment descriptor version to Java EE 5 so annotation processing can happen.

Well, little I knew that JWSDP 2.0 samples needed to run on top of the Application Server 8.1 (with the updated JWSDP bits), therefore that's exactly what they wanted : J2EE 1.4 xml and annotations...

As it turns out, they are using JSR 181 annotations which only their runtime would interpret. Well, JSR 181 being part of Java EE 5, we flagged those and failed deployment.

Here goes my safeguard idea...

So we could still do it, making a small exception case for JSR 181 annotations (since they are optional in J2EE 1.4). However, we also found out that doing this check has a deployment time cost (about 10% performance degradation for pre Java EE 5 applications) but can be turned off if necessary.

Should we do it ?

I would like to hear from the community...

Comments:

Post a Comment:
Comments are closed for this entry.
About

dochez

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today