Here the demo - Please, read the readme file. The zip file does not contain libraries.

Please see also the bug report on Eclipse / AJDT.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=378361

This the version with AspectJ annotation - This version give an accurate error message as you can see on bug_378361.

From https://bugs.eclipse.org/bugs/show_bug.cgi?id=378361, it seems that is not a problem of AspectJ but a problem of the CDI due to a "private static final". Could you please check from your side.

>> Could you please check from your side.

Could you create an Arquillian test for this?

I never did that, waou !
Why don't use the test demo we sent to you - Andrew from Eclipse/AspectJ compiler did it easily, ready to use, just put the needed libraries (read the readme.txt file from the root directory of NestedWebX directory). Andrew from eclipse/AspectJ did a good part of the work by determining the exact problem and the responsibility of the bug. So it is your turn

Moreover, if somebody can tell me how to update Weld in GlassFich...

>> So it is your turn
I don't think free OSS works this way.
Specially with semi-exotic usage ala AspectJ.
It's been 2004 when I last used it, and unfortunately no time to renew my knowledge.

>> Moreover, if somebody can tell me how to update Weld in GlassFich...
Just take Weld bundle from new release and you should be fine - it's back compatible.

Ok thank you - Just take a look at the workbench, inside aspects folder and you will see that AspectJ has greatly evolved. Now, you can produce java standard class annotated with specific AspectJ annotation. Under Eclipse, AspectJ compiler and editor works pretty fine. At the aspects folder, you can see different AspectJ annotated classes, most of them have their content commented. It is just different styles/way for the same goal, native (with .aj extension) and .java (for annotated).

As soon as I can, will ugrade Glassfish with the new bundle and will let you know the result.

Could you please assist me because under GlassFish, the WELD is packaging inside the OSGI framework. Then we need to generate the weld-osgi-bundle.jar which contain Weld. Could you please generate this file for testing with the hope, it will be the only file to be replaced. Thank you.

Hello, I've download the source code from the repository, unfortunately, it was the version 1.1.6 (core - weld-core-1.1.6.Final-32-gd28ddf1) and it does not compile... Some classes are missing !??)

How to get the version 1.1.8 ? Open source ready to compile, the project, not only the source??

Then I found a bundle osgi at this address below and I did a replace.
http://mvnrepository.com/artifact/org.jboss.weld/weld-osgi-bundle/1.1.6.Final

Unfortunately, even if glassFish display the good version - INFO: WELD-000900 1.1.6 (Final) - I got the exception : by java.lang.NoClassDefFoundError: org/jboss/weld/interceptor/proxy/LifecycleMixin

Any clue?

Source is here: https://github.com/weld/core
No idea about NCDFE, it's GF, not JBossAS ...

Hi Justin, It is what I did first - but the zip or the download button give me only the version 1.1.6
Is there a 1.1.8 version ? Moreover the zip seems not to be entire since there is some errors under the IDE (some classes are missing.) So, how to download entirely the latest version to be able to build the project and be able to reconstruct the weld-osgi-bundle file ?

Due to of this problem, I've surfed on Internet and I've found a ready made weld-osgi-bundle.jar for 1.1.6 but it does not work.

Do you have or know a repository (maven or other) where to find the "ready made" files for GlassFish ?

Thank you very much - Regards

I got the same execption with 1.1.8 from:
http://mvnrepository.com/artifact/org.jboss.weld/weld-osgi-bundle

In fact, the problem comes from the structure of the file weld-osgi-bundle.jar.
At the version bundle with GlassFish (Weld 1.1.4), the package interceptor is outside the weld folder

• org\jboss\interceptor
• org\jboss\weld
• org\slf4j

and with the version 1.1.8, the interceptor package is inside the "weld" folder. Then, it is probably a problem of classPath. If the file from maven repository is good, it is not back-compatible.... Moving the missing package outside the weld folder, does not solve the problem. Worse, GlassFish recognize the file to be version 1.1.4 even if we put the version 1.1.8 !

So I'm not able to continue any investigation without any help - Then I cannot tell you if the version above 1.1.4 has the bug too - Sorry.

Finally I've took the ear from:
https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/weld/weld-osgi-bundle/1.1.8.Final/
Under Eclipse, the project 1.1.6 is not working - many errors - Under NetBean, it sounds good.

I've update GlassFish with this file - INFO: WELD-000900 1.1.8 (Final) - But it still not working even when the file comes from JBoss... So, it is not back compatible unless something is missing, I mean additional file is required to be updated.

The error we got is the same as 1.1.6 which is java.lang.NoClassDefFoundError: org/jboss/weld/interceptor/proxy/LifecycleMixin.

So, Justin, I also found this
https://community.jboss.org/thread/197617
and that: https://issues.jboss.org/browse/WELD-807
and.. http://java.net/jira/browse/GLASSFISH-10787

I don't think this is a weld bug. I think aspectj is adding a public field to the class at load time, and that is what is causing the problem. You need to fix your aspectj setup so this does not happen.

Well, are you really sure ? Because from Andy Clement (AspectJ team), after verification, it was clear for him that the error comes from Weld. It would be good to be SURE and if you can concretely verify the point, I will returned back to AspectJ Team.

Please read the conversation : https://bugs.eclipse.org/bugs/show_bug.cgi?id=378361

We did again the test as your comment put a doubt into my mind. I've also modified the setup of AspectJ compiler, with or without No-Inline, the application works!? Is there a cache problem with the IDE ?

We also updated JSF to 2.1.11 and RichFaces 4.2.2 but it is not linked.

Then, you can close the issue. Thank you