enterprise logging using jboss tools

Reading the errors of wildfly – weld, sometimes you can see some NUMBERS to identify the error..

/**
* Log messages for Contexts
* Message Ids: 000200 – 000299
*/

@MessageLogger(projectCode = WELD_PROJECT_CODE)
public interface ContextLogger extends WeldLogger

 

@LogMessage(level = Level.TRACE)
@Message(id = 200, value = “Looked for {0} and got {1} in {2}”, format = Format.MESSAGE_FORMAT)
void contextualInstanceFound(Object param1, Object param2, Object param3);

The theory:
https://developer.jboss.org/wiki/JBossLoggingTooling
the code:
https://github.com/wildfly/quickstart/tree/11.x/logging-tools

ejb3: transactions

sometimes, i need a little review of things…

Making sense of EJB3.x Transaction Attributes – Part 2 (MANDATORY)

 

Making sense of EJB3.x Transaction Attributes – Part 1 (REQUIRES_NEW)

 

Making sense of EJB3.x Transaction Attributes – Part 4 (NEVER)

 

EJB3.x JPA: When to use rollback() and setRollbackOnly()

 

EJB 3.x JPA: Bean-Managed Transaction with javax.ejb.UserTransaction

 

http://what-when-how.com/enterprise-javabeans-3/container-managed-transactions-ejb-3/