]
Carlo de Wolf updated EJBTHREE-710:
-----------------------------------
Priority: Major (was: Blocker)
Cleanup E-EJB3 package/code/logging
-----------------------------------
Key: EJBTHREE-710
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-710
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Christian Bauer
This is E-EJB3 RC9. The following issues are not minor, they would make me feel uneasy if
I was a user:
1. The bundled embedded-jboss-beans.xml uses xmlns="urn:jboss:bean-deployer"
and everybody gets a nice WARN on startup that
xmlns="urn:jboss:bean-deployer:2.0" should be used. Change that in the
distributed configuration file.
2. [java] 13:40:10,676 WARN Ejb3Configuration:104 - Persistence provider caller does not
implements the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
It's OK to warn users that something is not right, but if something is not right in
our distribution there should be a note in the README or something that tells me as a user
that this is OK for the moment. Like a link to a JIRA issue.
3. [java] 13:44:59,381 WARN JBossTimerServiceFactory:112 - TIMER SERVICE IS NOT
INSTALLED -- Uh, yes, because I don't want it. Find a way for users to disable this
warning. I don't see any way to disable the timer service in embedded-jboss-beans.xml
and I don't want the .rar and .jar in my libs.
4. In RC9 there is code that prints debugging stuff on STDOUT:
[java] lookup
[java] UserTransaction: org.jboss.ejb3.embedded.UserTransactionImpl
[java] MessageHandlerBean: org.jnp.interfaces.NamingContext
This is triggered by
EJB3StandaloneBootstrap.scanClasspath("helloworld-ejb3/build"), please remove
from code...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: