I recently tried to deploy my EJB application (.jar file) on a UNIX system,
using exactly the same JBoss & Tomcat versions as the Windows environment it
was developed on, and exactly the same database for persistence.
However, as soon as JBoss parses my first entity bean in the ejb-jar.xml file
I'm stuck.
I can't figure out how to correctly declare a statfeul session bean in the
ejb-jar.xml file!!!
The bean works, except it's attributes aren't being stored in between method
invocations.
Does anyone have a snippet of EJB-JAR.xml for a stateful session bean, please?
BTW - where are
I have tried to implement a stateful session bean which holds 3 Strings as
attributes between method invocations.
The problem is that the 3 Strings are not persisted in between invocations &
when I need to use them, they are all 'null'.
Do I need to add any special syntax to the EJB-JAR file f
I have an entity bean whose semantics require that a subset of it's attributes
are used as the primary key, rather than just one attribute. It has 4
attributes, 2 of which I need to constitute the primary key.
The problem is that I don't know hoe to declare more than one cmp-field as the
prima
I would like one of my entity beans to have an attribute of type Array (or any
Java list), but am not sure how to define the O/R mapping for this type - can
anyone please help me? I assume that a new table will be created for the array
to be stored in.
The values stored in the array will all b
I was wondering if the latest version of JBoss supported the CMP of
references to other Entity beans, as mandated
by EJB 2.0?
The examples I have been reading are using
the technique of storing both a
If I start JBoss with the "run_with_tomcat" script, how can I be sure that
they are both running under the same JVM?
Is this the correct way of starting JBoss & Tomcat within the same JVM?
I get no error messages upon initialization, and the test deployment works
fine.
Thanks
__
I am installing a JBOSS-TOMCAT system and am currently using JDK-1.2.1. I was
unable to install JBOSS-2.4 as it uses some of the newly introduced classes to
JDK-1.3. I have now successfully installed JBOSS-2.2.2, which is working OK.
My dilemma is : should I continue to use JBOSS-2.2.2 with JDK