-
1. Re: persistence.xml not deployed to ejb's META-INF directory
Anything in the error log ?
Anything in the server log ? -
2. Re: persistence.xml not deployed to ejb's META-INF directory
It is possible that you have *.xml files excluded.
Check the following preference:
Window>Preferences>Java>Compiler>Building>Output Folder>Filtered Resources.
It should contain only *.launch.
Some projects change this preference (TPTP 4.5.1, for instance). -
3. Re: persistence.xml not deployed to ejb's META-INF directory
....why does TPTP 4.x change that ? any bugid for that ?
-
4. Re: persistence.xml not deployed to ejb's META-INF directory
Snjeza, thanks so much! I had indeed installed TPTP 4.5.1, so the Filtered Resources was the problem. It contained: *.launch,*.testsuite,*.deploy,*.location,*.execution,*.datapool,*.artifact,*.testlog,*.xml,*.html,*.svg
I changed it to only *.launch and it worked as before.
Max, I found no errors or messages in the Server or Error logs. TPTP is the problem. Should JBoss Tools emit a warning if it realizes that certain important files are not deployed? That makes sense to me, but I don't know where you draw the line between A) non-standard (but desired) settings and B) incorrect settings. -
5. Re: persistence.xml not deployed to ejb's META-INF directory
Thanks for verifying that, this also explains a couple of other issues we have seen similar to this.
With respect to error/warn about this then in this specific case it is clearly TPTP that is doing things wrong changing a global setting like this that normally should be set by the user - and in that case the user would have set it and then that might be his intention.
With respect to emitting a warning then that is tricky since we deploy incrementally meaning we can't really know when and what to validate...but I guess some level of checks could be added when a deploy has finished BUT the problem is that in JEE6 descriptors is not a requirement PLUS if the resource filter is in place we will never even know the file is there...
