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

Alexandros Karypidis (JIRA) jira-events at lists.jboss.org
Fri Nov 6 03:59:17 EST 2009


    [ https://jira.jboss.org/jira/browse/JBWS-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12493498#action_12493498 ] 

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.


> JAX-WS Client endpoint configuration in jbossws-cxf.xml is ignored
> ------------------------------------------------------------------
>
>                 Key: JBWS-2822
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2822
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>    Affects Versions: jbossws-cxf-3.2.0
>         Environment: Windows XP 32bit, Sun JDK 1.6.0_16, JBoss AS 5.1.0.GA with JBossWS-CXF 3.2.0.GA
>            Reporter: Alexandros Karypidis
>         Attachments: jboss-cxf.client-jaxws-cfg-bug.zip
>
>
> Normally, in order to configure endpoints and clients in CXF you use Spring's beans.xml. While this works for service provider endpoints, it is ignored for client stubs.

-- 
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

        


More information about the jbossws-issues mailing list