Solved.
I used seam-gen to see what's going on, and the answer came quickly.
I had to put those fine grained files in the same folder as those views that
they defined but I had them in WEB-INF/classes! Don't know why I did that, but
it didn't have any side-effects until now.
View the origin
That is all that is required.
Put the seam src in your sourcepath and use your debugger.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050767#4050767
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050767
_
Sorry, I still could not get it work.
In my components.xml, I did in fact have debug=true so this means
hotDeployFilter is installed--the startup logs actually confirm this. Do I
need to do anything more to get those fine-grained page.xml to hot deploy
properly? Or that's pretty much it?
The hot deploy filter is installed whenever the debug=true. So your expectation
is correct.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050760#4050760
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050760
__
Ah okay. I was under the impression that if [core:init debug=true] is set,
then you'll get hot deploy services OOTB with Seam, but I guess it's an
expensive operation to scan through all *.page.xml in every request.
Thanks for the clarification.
View the original post :
http://www.jboss.com/i
When the hotDeployFilter is installed, the Pages component is refreshed on
every request.
So the fine-grained files are *definitely* hot-deployable (you are mistaken
about that).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050758#4050758
Reply to the pos
