Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1123

WELD-000075 error message with AspectJ

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 1.1.4.Final
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
    • Steps to Reproduce:
      Hide

      1) Please read the readme.txt file under NestedWeb directory
      2) Under eclipse Indigo

      • make a NestedEar project (ear)
      • make NestedWeb project (war)
      • Copy paste the source file into NestedWeb project.
      • Build and deploy the project
        3) Launch the workbench : http://localhost:8080/NestedWeb/index.html
        4) You should see the home page "Integration Bug Hunter" with a tab panel

      Then to reproduce the bug

      • Configure the NestedWeb as an AspectJ project
      • Build and deploy the project, you will get the WELD-000075 Normal scoped managed....

      The question is why to project without AspectJ is running well and with AspectJ is not running? What add AspectJ to the class to trigger such error.

      Note that we use Inter-Type declaration for logging.

      public aspect LoggingBehavior {
      	public interface Loggable { }
      	private final transient Logger Loggable.log = Logger.getLogger(this.getClass());
      	public Logger Loggable.getLog() {
      		return log;
      	}
       
      	declare parents : com.nested.web.controller.BaseController implements Loggable;
      
      

      Note also that the project run perfectly under WAS/RAD with Spring as injection of dependency.

      See the attached files as demo.

      Show
      1) Please read the readme.txt file under NestedWeb directory 2) Under eclipse Indigo make a NestedEar project (ear) make NestedWeb project (war) Copy paste the source file into NestedWeb project. Build and deploy the project 3) Launch the workbench : http://localhost:8080/NestedWeb/index.html 4) You should see the home page "Integration Bug Hunter" with a tab panel Then to reproduce the bug Configure the NestedWeb as an AspectJ project Build and deploy the project, you will get the WELD-000075 Normal scoped managed.... The question is why to project without AspectJ is running well and with AspectJ is not running? What add AspectJ to the class to trigger such error. Note that we use Inter-Type declaration for logging. public aspect LoggingBehavior { public interface Loggable { } private final transient Logger Loggable.log = Logger.getLogger(this.getClass()); public Logger Loggable.getLog() { return log; }   declare parents : com.nested.web.controller.BaseController implements Loggable; Note also that the project run perfectly under WAS/RAD with Spring as injection of dependency. See the attached files as demo.

      Description

      We have an application - Without AspectJ, the application is running smoothly but as soon as we activate aspectJ, if we tried to deploy and run the application we got the following error message:

      GRAVE: Exception while loading the app
      GRAVE: Exception while loading the app : WELD-000075 Normal scoped managed bean implementation class has a public field:  public@Named @RequestScoped class com.nested.web.controller.PanelTwoController
      org.jboss.weld.exceptions.DefinitionException: WELD-000075 Normal scoped managed bean implementation class has a public field:  public@Named @RequestScoped class com.nested.web.controller.PanelTwoController
      	at org.jboss.weld.bean.ManagedBean.checkBeanImplementation(ManagedBean.java:438)
      	at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:191)
      	at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:322)
      	at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:115)
      	at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:204)
      	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:344)
      	at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:179)
      	at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
      	at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:277)
      	at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:460)
      	at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
      	at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
      	at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jorelia64 Jean ANDRE
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: