Hot swap/deploy with 5.0

[lovelyliatroim]

Hi Folks,
Im currently setting up my development environment and would like to be able to do a hot swap during development. I have read the articles here
http://wiki.jboss.org/wiki/Wiki.jsp?page=DeploymentScanner
http://wiki.jboss.org/wiki/Wiki.jsp?page=ExplodedDeployment

This tells you how to go about it but i have one small problem. In the above steps it tells you to update your URLDeploymentScanner in the jboss-service.xml but in 5.0Beta2 there is no more an entry for the URLDeploymentScanner.

i dont want to have to re-war/re-ear every time i make a change in development so i have tried to get hot swap to work for me.

So what i have is as follows, i have an exploded ear and war(inside ear) and I have set eclipse to output classes into the exploded directories, now when i make a change i run an ant script that touches the appropriate xml file whether it be application.xml or web.xml. The problem is that JBoss doesnt respond at all. How can or do i get hot swap to work with 5.0 version??

Cheers,
LL

[peterj]

See my reply at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114741#4114741

[lovelyliatroim]

Just an update on this. Ive downloaded 5.0 Bet3 and want to get hotswap to work.
Im still having the same problem as before with Beta2, JBoss doesnt respond to the touching of the xml files.

I have seen this post and it is same issue.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=125750

Justed tested this on windows and not on unix box.

Just FYI.
LL

[vbatista]

Hi,
The tests on the post:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=125750
Were done on a Linux box.

PeterJ, have you tested re-deployment (touching application.xml and/or web.xml of exploded applications)? I couldn't get it to work with JBoss-5.0.0.Beta2 and Beta3 on a Linux box.

Any help would be appreciated.
Best regards,
Victor

[peterj]

No, I have not tested anything on beta3. I went on vacation the day after it came out and do not go back to work until Jan 7th, at which time I will immerse myself in beta3 for several weeks. I will know more then. Though I suspect you will have to wait for CR1 (candidate release 1) or CR2 before all of the various broken deployment issues have been fixed.