Using plain java classes instead of using SessionBeans would actually make
testing the component easier. You can write component tests as normal Junit
tests. You can run them outside the container (IDE, build script etc) by using
mocks for the dependent entity beans and if you want to test in
Where are you running this code.
If you run this code in the context of an existing transaction it will use only
one sql query. If the code is being executed without an existing transaction
each get method would lead to a new transaction being started and committed
once the get method is comple
I would suggest that you go ahead with the Single session bean solution. The
main reasons for using a stateless session bean would be to leverage the
declarative transaction support. If the transaction handling is straight
forward (all operations are carried out as a part of single transacti
You can try putting in the deploy directory or in lib directory of the choose
configuration i.e., default\lib for default configuration.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865851#3865851
Reply to the post :
http://www.jboss.org/index.html?module
Take a look at this page
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
I think you will either have to disable class loader isolation or use pass-by
value to solve this issue. Both have their pros / cons, you need to figure out
which one will work fo you.
View the original
create a WEB-INF\lib under your yourwebapp.war directory and add all the
dependent jars under it.
| yourwebapp.war
| WEB-INF
|lib
|
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858831#385
You can extract the common classes into a utility jar and add it as a java
module to your application. You can also put a class-path reference to the
utility jar in the manifest file of the ejb.jar and the war.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3
You can deploy your application as an exploded war i.e., create a
yourwebapp.war directory under the deploy directory and copy all the files
under it.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857309#3857309
Reply to the post :
http://www.jboss.org
I came across the following comment in the admin develop guide
anonymous wrote : While it does support propagating transaction contexts with
remote calls, it does not support propagating transaction contexts to other
virtual machines, so all transactional work must be done in the same virtual
m
I need to perform some operations when an application (ear) is succesfully
deployed. I need the name of the application and the context classloader
associated with it. What is the easiest way of doing this?
Will the context classloaders for the different ears deployed in a single JBoss
server
10 matches
Mail list logo
