I'll try to simplify my question. Does modification of application.xml while deployment causes application redeployment?
Hello, if I am not mistaken simply touching application.xml will cause redeployment.
does not work. at least while deployment
Maybe I can reset seam contexts or something like that
Seems like a dangerous thing to do (if you figure out how to get it working) considering the memory leak in jboss. (Or if you have some magic for fixing the mem leak, what is it?)
It works for me perfectly I just tested it on one of my exploded ears in my application server. Run the touch command on the application.xml in the exploded ear directory in your JBoss deploy dir. For example:
and you will see in your JBoss console that the entire ear gets redeployed.
He is right about that - you should look into why you are wanting to do this.
I guess I need to clear this. First of all, after magic string
application started successfullyI can simply restart application by touching application.xml.
Why I need to restart deployment? Because there is currently no EJB 3 hot deployment. I packed together business process definitions and jars with related seam component into single process archive. I made my own component to override seam core jbpm component. So I scan process archives for jars with Name-annotated classes. And if such classes found I copy corresponding jar file to ear lib folder and add respective module to application.xml.
After all modifications I need to restart application to force seam to rescan recently copied jars.
If there any scenario better then mine, You can freely offer them :)