custom tags: changing TagHandler on JBoss

I deployed a custom tag on JBoss. However if I make a change in TagHandler change does not take affect. I tried to reload application on JBoss: jboss.jca -> name=myApp,service=ManagedConnectionPool -> stop -> start, but no changes are seen. The only way I make my changes live is if I rename my TagHandler. I am restarting JBoss application correctly? Anything else I should do?

thanks,
Alex

Alex,
I'm not sure how you're deploying your app, but I think you might be invoking stop and start on the wrong mbean. are you developing in an exploded directory in the deploy dir, or are you redeploying your war after you make the change?

I'm running jboss-3.2.1/tomcat-4.1.24, so I'll tell you how it will work here.

For the first case, after you change your class and recompile, all you should have to do is touch the web.xml file and jboss will redeploy your web module.

For the second case, if your putting a new war file in the deploy directory, it should be redeploying. If it's not, there's another problem.

I also might not have understood your question. If I can help any more please let me know.

I never did touch web.xml. I guess I'll give it a try. Thanks a lot man!

Ok, I searched for web.xml in /export/home/jboss/ and I found about 10 places where web.xml is. One of them was /export/home/jboss-3.2.3/server/default/deploy/myApp.war/WEB-INF/web.xml, so figured that's the one. I ran touch web.xml and got "ERROR 500" after. Have to restart jboss now. So is this wrong web.xml file?

If that's the no context configured version of Error 500, you might need to wait longer while it redeploys.

in the server/default/log directory, it helps to have a session that's running a "tail -f server.log"

That way you can see what's going on in the server.

If it's not a "no context configured" error, is there any more info you can give me? That should be the correct web.xml