David Jencks wrote:
I still need to find out why the autoredeploy is giving problems...
I had posted this on forums on the JBoss site, but not here, so FWIW,
here is my analysis of hot-deployment problems on JBoss 3.0.0. I have
recently managed to get HEAD to build on my machine (was using JDK1.4.1
and it soesn't like that at all!) and will test it there ASAP.
Hope this helps.
I tested hot deployment on the 3.0.0/Tomcat4 release, on WinXP/JDK1.4.0
and RH Linux 7.3/JDK1.4.0 and it happens on both :-( I am using cactus
to do my unit testing, so all the lookups are done from a webapp
deployed in the same EAR as the EJB.
The problem seems to be in JNDI or the web server classloader - here is
my analysis (I am testing an EJB called Role):
1. On first deployment, or restarted JBoss server, a lookup of
local/Role (RoleLocalHome interface) returns $Proxy34. This is the same
object listed in the management view as bound to local/Role, and all the
tests work fine.
2. Do a hot redeploy
3. Lookup local/Role from the servlet returns $Proxy34 as before, while
in the management view local/Role is bound to proxy: $Proxy45. Casting
this object to RoleLocalHome causes a ClassCastException.
(if you now restart the server, the tests work fine)
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
