Sorry to keep bothering on this subject... but has anyone got any insight into
what might be causing the problem? I put the problem on the shelf for a few
months because I got badly stuck, but eventually its an issue I will need to
resolve. Please help! Thank you.
View the original post :
Thanks for the assistance so far. Following your suggestion Bill Burke, I get
an exception while deploying just the shared entity/session bean ejb3 archive.
| 09:20:11,276 ERROR [Ejb3Module] Initialization failed
jboss.j2ee:service=EJB3,module=beans.ejb3
| java.lang.NullPointerException
Hello!
Why are you putting Entity beans in ejb3 file? I think JBoss searches entities
and persistence.xml in .par.
regards
blacky
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916924#3916924
Reply to the post :
As far as I know, the .par archive format used to be in the EJB3 spec but I
read somewhere that it is not going to be in the final release. The .ejb3
archive format is a JBoss specific version of the .par archive, and they are
equivalent.
Anyways, I tried renaming the archives to have a .par
yxw84 wrote : such that the following line:
|
| | hibernate.connection.datasource=java:/DefaultDS
| |
| becomes:
|
| | hibernate.connection.datasource=java:/DB1
| |
|
| then both EAR files connect to DB1. I am unable to get each EAR to connect
to its own DB. Do you
Hello !
I have the same problem ..
To try to resolve it I do the following things :
I use the name attribute of SessionBean Annotation with a @AppName@ like this :
@Stateless(name=@[EMAIL PROTECTED])
in the persistence.xml :
@[EMAIL PROTECTED]
With Ant I copy all my sources to a
Thank you for the reply Bill Burke. I already have two Postgre databases setup
and registered as you suggested. They are both Postgre databases, and here are
their configuration files:
db1-ds.xml:
| datasources
| local-tx-datasource
| jndi-nameDB1/jndi-name
|
Hello !
I have the same problems ...
Did anyone find any answer ?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916413#3916413
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3916413
You need to set up a JBoss Datasource!!! DO NOT USE THE
hibernate.connection.datasource property.
There are example DS files under: jboss/docs/examples/jca or check the JBoss
App Server documentation.
View the original post :
I am still stuck on this. In my session bean, I print out a few lines of debug
messages.
09:10:25,481 INFO [STDOUT] Start check, does user exist?
09:10:25,482 INFO [STDOUT] We are using manager: [EMAIL PROTECTED]
09:10:25,500 INFO [STDOUT] Finished checking. User does not exist.
09:10:39,313
Still stuck, but I found out that both EAR files are connecting to the
DefaultDS hypersonic database that is setup with JBoss. How would I specify
exactly what database each EAR should connect to? Here are the persistence.xml
files within my skeleton ejb3 files within each EAR:
entity-manager
I managed to get rid of the deployment exceptions, by not using the jar-file
option in persistence.xml but instead just deploying the ejb3 file containing
my entity and session beans into the deploy directory. Then, the skeleton
persistence.xml file in my EARs has no problem finding the
I forgot to mention that everything works perfectly for single deployments. I
only run into trouble when doing multiple deployments onto the same instance.
Lastly, in the second scenario where I try to deploy two EARs each fully
containing their needed classes, both applications end up working,
13 matches
Mail list logo
