[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2822) JAX-WS Client endpoint configuration in jbossws-cxf.xml is ignored

[ https://jira.jboss.org/jira/browse/JBWS-2822?page=com.atlassian.jira.plug... ] Alexandros Karypidis commented on JBWS-2822: -------------------------------------------- Some additional notes: 1) The "WorkingServlet" will probably throw and exception about missing the derby database driver. This simply shows that the configuration is picked up normally and is the desirable behavior. If you want to see a fully successful invocation, place a derby.jar (any version) in your test environment. As was explained to me in this forum thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=162775 you will need to put the jar in the server/_cfg_/deployers/jbossws.deployer directory for it to become visible. If you do that, the ClassNotFound exception will go away and you will see a directory "wsrm-working-db" is created, containing a derby database. 2) The issue seems to affect not just the JAX-WS front-end, but also all "client side" configuration. For example, in the thread mentioned just before (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=162775) you can configure the HTTP conduit using <http:conduit name="{http://messaging/}AsyncMessagingImplPort.http-conduit"> <http:client DecoupledEndpoint="http://localhost:9999/decoupled_endpoint" /> </http:conduit> Again, the WorkingServlet would pick this up and require jetty (as described in that thread) but the BugServlet would ignore it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira