jizzoe
What king of JVM are you running ?
Aren't you running it in green thread mode ?
Gozilla
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888453#3888453
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&
Yes, thats what happened.
AFAIK, you have to force the pass-by-value semantics somewhere, but I don't
remember where.
As I already said, I wouldn't go that way, I would simply wipe the client jar.
Cheers
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=387801
tigerreef, I don't get your point about anonymous wrote : I don't see how this
will work any other way with the deployment I want.
Using the UCL is the way to avoid an 'ejbclient.jar', because the classes are
found in the jar already. Just wipe it out.
If you absolutely wants to have an ejbclien
Hi tigerref,
I thing the problems comes from the fact that the classes in question exist in
two places in your EAR: once in the EJB jar and once in the war
(WEB-INF/classes).
anonymous wrote : Servlet>> o's CL: [EMAIL PROTECTED]
url=file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp27550TS
Hi morenito9000
Something you could also have tried is to specify the wildcard permission after
the other one. Order often made a difference in descriptors.
Gozilla
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872768#3872768
Reply to the post
Hi monocongo,
You may want to try to 'JBossConfigurator'
http://damon.sicore.org/blojsom/blog/default/Development/?permalink=jBossConfigurator.txt
They did aextensive job at searching the places where to change partition names, etc
...
I based my deployments on their job, it's working
Cheers,
Alexey,
anonymous wrote :
| read-only in jboss.xml has almost the same effect as running w/o transactions.
Read-only instance is not associated with the transaction (hence, is not synchronized
at commit), is locked only for the duration of the invocation, and is evicted from the
cache at the
(re-post since it seems that there is a gap in the forum somewhere between the 21th
and today)
---
Hi davidmboon
I think the problem comes from the fact that you are deploying your ears inside a
subdirectory of the deploy directory 'lms'.
Did you set the 'RecursiveSearch' attribute of the 'URLD
Hi davidmboon
I think the problem comes from the fact that you are deploying your ears inside a
subdirectory of the deploy directory 'lms'.
Did you set the 'RecursiveSearch' attribute of the 'URLDeploymentScanner' mbean to
true ?
Otherwise, (and that's what looks like) JBoss treat the lms dire
