-
15. Re: Overriding clientBindUrl does not work! Why?
Any idea what i should change to be able to run the webcontext annotation as well in the bean? (Need it to work in JBossWS as well...)
-
16. Re: Overriding clientBindUrl does not work! Why?
"eminil" wrote:
Any idea what i should change to be able to run the webcontext annotation as well in the bean? (Need it to work in JBossWS as well...)
We have been going to and fro on many issues in this single thread :) It's difficult to understand what the real issue at this point is. Could you please provide more details of the latest issue including the entire exception stacktrace, the relevant code and the relevant parts of config files? Also, if this is a separate issue than what you started off with, then create a separate thread so that we do not end up creation confusion in this thread. -
17. Re: Overriding clientBindUrl does not work! Why?
Okay. Lets just say this issue is resolved. I will continue my problems in another thread :P
The issue i had in this thread was getting the <client-bind-url> in jboss.xml to override the clientBindUrl in the annoation of the bean.
First the jboss.xml failed to read, but this was fixed by changing the schemas to 5_0 instead of 5_1.
Then i had put the jboss.xml in the wrong META-INF folder. It should have been in the ejb jar instead of in the ear.
When these things were resolved the remote client is now able to connect to the bean.
Now i'll continue my other problems with also hooking up the bean to JBossWS in another thread.
Thanks all for the help! :)