"deanhiller" wrote:
I find myself needing to restart the server every time I change xxx.pages.xml files even though I read that jboss tools supports hot redeploy of those files. How do I configure jboss so that seam reloads just the pages files(and hopefully not the entire app)???
JBoss Tools doesn't do anything specific for pages.xml beyond making sure the file is copied to the deployment when you edit it.
If Seam supports it then it should work - but I must admit I haven't tried it for that specific feature. Where did you read about it ?
Also, I read about the dev directory and deployment to that dir causes seam to reload in just the changed components(including annotations), BUT if I do that, won't tomcat then redeploy the entire app.
Why should tomcat reload the app because Seam dynamically reload classes from the /dev folder ?
This sounds like it defeats the purpose as tomcat redeploys the entire app on every class file change unless you set up the context.xml file but then your files are not copied to the target dirs.
I don't understand "but then your files are not copied to the target dirs" ? What does that mean ? (btw. tomcat eclipse integration is not done by jboss tools, its done by WTP)
About your other question since the files are in /dev and not in /classes then tomcat doesn't know about them so it shouldn't care.
ie. how to configure this as well even though, it is very annoying that it has to be a dev dir....would be much nicer if the components.xml had a configure option I could turn on and off instead(that is probably more a seam forum question I guess though).
Yup, but if the .class are in the "normal" classpath location then Seam wouldn't be able to do anything - then it becomes the VM or the container's job.
