Article:
  Aspect-Oriented Programming and JBoss
Subject:   Logging and tracing code
Date:   2003-05-29 11:10:37
From:   warjort
Response to: Logging and tracing code

http://www.jboss.org/index.html?module=html&op=userdisplay&id=developers/projects/jboss/aop


Do you want secured/transactional/clustered pojo?
This is already exists with jboss4


Regards,
Adrian

Main Topics Oldest First

Showing messages 1 through 1 of 1.

  • Logging and tracing code
    2003-05-29 14:22:58  anonymous2 [View]

    All of those things (security, transactions, clustering) are all great, but any reasonable engineer is going to find a lot of things to be concerned about with this approach.

    First, AOP is hacking the byte-code at runtime. This is a huge red flag that if it is really no problem needs to be addressed up front.

    Second, can I debug it? Can I step through line by line as the method gets called and the aspects get invoked, then as the main body runs and the aspects are re-invoked, etc.

    Third, has this technology ever been used IN PRODUCTION? We have heard a lot about AOP theory and example implementations from PARC, but what about real use on a web application has a healthy amount of tables and real business logic with transactional edge cases?

    Plus there are possible interaction issues. What if my security aspect requires a database lookup within a nested transaction aspect? Will it find a read-lock table and go into deadlock?