-
1. Re: jboss.xml
dlmiles Apr 26, 2005 7:16 AM (in response to kirillp)I hit that problem too. Break the file, make up a tag element and re-deploy, stand back from the errors, not nice but sheds light on us mushrooms :).
Maybe someone knows how to enable logging (maybe it should be on by default) would probably fix many peoples deployment problems if they could see whats going on inside the deployer ? -
2. Re: jboss.xml
kirillp Apr 26, 2005 7:22 AM (in response to kirillp)Done that, no errors reported.
obviously, JBoss does not see the file...
I tried putting it into the META-INF of the EAR module but to no avail :( -
3. Re: jboss.xml
dlmiles Apr 26, 2005 7:37 AM (in response to kirillp)Ok I just checked from a working setup...
Create an empty "' inside of your <enterprise-beans> element. It doesn't like that. Creating just inside it doesn't notice. -
4. Re: jboss.xml
dlmiles Apr 26, 2005 7:40 AM (in response to kirillp)"dlmiles" wrote:
Create an empty "<session></session>' inside ...
I think the BBCode ate it.Create an empty <session></session> inside of your <enterprise-beans> element. It doesn't like that. Creating <test></test> just inside <jboss> it doesn't notice.
-
5. Re: jboss.xml
kirillp Apr 26, 2005 8:25 AM (in response to kirillp)Thanks for your reply, but let me make sure I understand you correctly.
You are saying that the following will be ok in jboss.xml:
<enterprise-beans></enterprise-beans> -
6. Re: jboss.xml
kirillp Apr 26, 2005 9:01 AM (in response to kirillp)Ok, it ate the tags as well, but I got it working anyway.
The jboss.xml was failing silently. Now it's working. Thanks for yoyr help.