Hi all,
I have an ear application running on JBoss 4.2.1 GA that contains 2 EJB
Stateless jar's. I have only one persistence unit define in the
persistence.xml of only one of the jar/META-INF.
All is container-managed, so JTA is used and I don't need to manage
transaction. The isolation lev
Hi,
I m trying to make a shared repository with Jackrabbit. For this, I need to
register in the JNDI the 'javax.jcr.Repository'.
As explained by Apache for Tomcat, I m trying to adapt the config within JBoss
4.2.1. Here is my config:
in /default/deploy/jboss-web.deployer/server.xml:
|
Hi,
I am using JBoss v 4.2.1GA, on Solaris platform and when JBoss tries to deploy
an MDB in my application, here is what happens:
On Windows, I have no problem. On Unix Solaris, it fails if I start JBoss with
my ear in the farm directory. If I hot deploy my ear, all is working too.
Config
I
My problem is, only on Unix Sun Solaris, that the DefaultDS is bound after the
DefaultJMSProvider. On Windows OS, DefaultDS is bound before and everything
works.
Would it be possible that the recursive scan on Solaris doesn't work as it
would?
View the original post :
http://www.jboss.com/
What I do here, not very clean but it works,
I have created an annotation called Sequence and then I place it on my bean as
follow
@Sequence(name="TABLE_SEQ") where table_seq is the name of my Oracle sequence.
In my persistent class, I create a new persistent bean when needed with empty
prop
