Well, as I said, instead of using transaction-type JTA, I'm using
RESOURCE_LOCAL and a non-jta-data-source. I think it's something about the
security, the transaction manager of hibernate (which is the persistence
provider for JBoss) cannot join with the JTA, which is managed by JBoss, and
the
I made a little change to persistence.xml, and now the client rung without
error, but when I call save (which in turn call entityManager.persist), no
change was made to the database
I can find Admin object by using find method, but cannot insert new, or update,
the method return no error, but
what I change in persistence.xml is
from
persistence-unit name=AdminEJB transaction-type=JTA
| jta-data-sourcejava:/MyDB/jta-data-source
| /persistence-unit
to
persistence-unit name=AdminEJB transaction-type=RESOURCE_LOCAL
|
Well, I'm using JBoss 4.2.2... and I read that topic,
As I stated in the previous post, I've already referenced the log4j.jar in the
JBOSS_HOME/client, but the client still throws that exception.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120432#4120432
I'm try to create an EJB3, hosted with JBoss. This is the steps that I have
been taking by now:
JBoss 4.2.2 GA
J2EE 5 U3 with JDK 1.6
MyEclipse 5.5
MS SQL 2005 Express
Step 1: Create a new EJB Project AdminEJB with MyEclipse, Choose J2EE 5.0,
setup connection driver and schema
Step 2: Use
For more specific, I'm using JBoss 4.2.2, MyEclipse 5.5 to create my EJB
project, I created the client outside MyEclipse.
I create a TestClient again in MyEclipse, and another funny thing happened,
please have a look here:
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120693#4120693
I'm trying to use EBJ3 to manage a table in my database, when I ran my test
client, I always received this:
Exception in thread main java.lang.NoSuchFieldError: TRACE
| at
org.jboss.logging.Log4jLoggerPlugin.isTraceEnabled(Log4jLoggerPlugin.java:85)
| at