MTOM sample from CXF distribution does work with proxy authentication ?
Hello to all,
I have a problem with a generated client ( it's included in mtom samples
from Apache CXF 2.0 distribution) when I am behind of the corporate
firewall. I can't pass the proxy server and I have the error : Server
returned HTTP response code: 407 for URL ... . I know that I need an user
and password setted before calling TestMtomService method like below.
TestMtomService tms = new TestMtomService(wsdlURL, SERVICE_NAME);
TestMtom port = (TestMtom) tms.getPort(PORT_NAME, TestMtom.class);
Binding binding = ((BindingProvider)port).getBinding();
((SOAPBinding)binding).setMTOMEnabled(true);
Client clt = ClientProxy.getClient(port);
I tried many posibilities but without any success.
More , a created a cxf.xml file on a client side that is loaded (it seems)
by method call new TestMtomService(wsdlURL, SERVICE_NAME) . I let these
settings in it :
http-conf:conduit
name={http://cxf.apache.org/mime}TestMtomPort.http-conduit;
http-conf:client Connection=Keep-Alive
MaxRetransmits=1
AllowChunking=false
ProxyServer=1.1.1.1
ProxyServerPort= /
http-conf:basicAuthSupplier class=demo.mtom.client.ClientAuthent/
http-conf:authorization /
http-conf:proxyAuthorization /
/http-conf:conduit
Also I created a class named demo.mtom.client.ClientAuthent which
extends HttpBasicAuthSupplier and override getPreemptiveUserPass
public UserPass getPreemptiveUserPass(
String conduitName,
URL currentURL,
Message message)
{
return createUserPass( myuser ,mypassword);
}
I don't know what other settings have to do for reading all informations for
ProxyServer, ProxyPort, ProxyUser and ProxyPassword.
Also, I didn't find out others attributes for http-conf:authorization /
and http-conf:proxyAuthorization /.
Maybe this will solve the problem.
Can somebody give a hint ?
Thank in advance for help,
Petrica
--
View this message in context:
http://www.nabble.com/MTOM-sample-from-CXF-distribution-does-work-with-proxy-authentication---tf4210852.html#a11978143
Sent from the cxf-user mailing list archive at Nabble.com.
Re: JAXBElement
I am using XFire web services. I tried with aegis binding xml to change minOccurs of required property, but it is not working. Here is my aegis xml **LogonInTO.aegis.xml* mappings xmlns:np=http://singularity.co.uk/webservices/spp; mapping name=np:LogonInTO property name=password minOccurs=1 nillable=false/ property name=userId minOccurs=1 nillable=false/ /mapping /mappings *** The LogonInTO complex type in wsdl before applying aegis was as below xsd:complexType name=LogonInTO xsd:sequence xsd:element minOccurs=0 name=logonProtocol type=xsd:short/ xsd:element minOccurs=0 name=password nillable=true type=xsd:string/ xsd:element minOccurs=0 name=unConditional type=xsd:boolean/ xsd:element minOccurs=0 name=userId nillable=true type=xsd:string/ /xsd:sequence /xsd:complexType And after applying aegis, LogonInTO complex type in wsdl is as below xsd:complexType name=LogonInTO xsd:sequence xsd:element minOccurs=0 name=logonProtocol type=xsd:short/ xsd:element name=password type=xsd:string/ xsd:element minOccurs=0 name=unConditional type=xsd:boolean/ xsd:element name=userId type=xsd:string/ /xsd:sequence /xsd:complexType Is this the right way of changing minOccurs, otherwise please let me know, how to do it. Thanks Regards, Srinivas. gdprao wrote: I remember that I too have faced the same problem once. When I changed that element in XSD with minoccurs=1, it generated String type correctly instead of JAXBElement. Thanks, Durga velidandas wrote: I am getting the String parameter types being set as JAXBElement type. How to send String type parameter types here. Srinivas. -- View this message in context: http://www.nabble.com/JAXBElement-tf4207085.html#a11978580 Sent from the cxf-user mailing list archive at Nabble.com.
RE: How to deploy to JBoss?
I think you need to drop the jar file containing org.apache.cxf.transport.servlet.CXFServlet class into jboss\default\server\lib folder OR add this jar to web-inf\lib folder of the war being deployed. Srinivas. -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 12:40 To: cxf-user@incubator.apache.org Subject: How to deploy to JBoss? I have been going through the CXF samples; those I have tried work fine, both in standalone mode and with the server part deployed to Tomcat. What do I need to do if I want to deploy to JBoss instead of Tomcat? I tried to simply drop helloworld.war into the C:\opt\jboss\jboss- 4.0.4.GA\server\default\deploy directory, this gave a class not found exception: 09:00:31,501 ERROR [MainDeployer] Could not create deployment: file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.cxf.transport.servlet.CXFServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment( WebServiceDeployerJSE.java:161) ... Regards, Erlend Leganger My environment: rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02 set JAVA_HOME=c:\opt\java\jdk1.5.0_12 set AXIS2_HOME=c:\opt\axis2\axis2-1.3-RC2 set ANT_HOME=c:\opt\ant\apache-ant-1.7.0 set CATALINA_HOME=c:\opt\tomcat\apache-tomcat-5.5.23 set JBOSS_HOME=c:\opt\jboss\jboss-4.0.4.GA set CFX_HOME=c:\opt\cxf\apache-cxf-2.0-incubator set PATH=C:\WINDOWS set PATH=%PATH%;C:\WINDOWS\system32 set PATH=%PATH%;C:\WINDOWS\System32\Wbem set PATH=%PATH%;%JAVA_HOME%\bin set PATH=%PATH%;%CATALINA_HOME%\bin set PATH=%PATH%;%JBOSS_HOME%\bin set PATH=%PATH%;%ANT_HOME%\bin set CLASSPATH=.;%CFX_HOME%\lib\cxf-manifest-incubator.jar;.\build\classes __ __ This e-mail has been scanned for all viruses by MessageLabs. __ __ This e-mail has been scanned for all viruses by MessageLabs. To learn more about Singularity's business process management solutions and services please visit: www.singularity.co.uk www.singularity.us.com Singularity operates globally through its offices in New York, London, Singapore, Ireland and India. Singularity Limited is incorporated in the United Kingdom with Registration Number NI 31519 and its Registered Office at 100 Patrick Street, Derry, BT48 7EL, United Kingdom.
Re: How to deploy to JBoss?
I tried the following: - copied all files from cxf's modules directory into jboss' server/default/deploy/lib - restarted jboss - dropped helloworld.war into jboss' server/default/deploy This made a difference, but it still doesn't work, here's the jboss log: 09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld, warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/ 09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as unavailable 09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw load() exception java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry When trying ant client-servlet, jboss refuses to respond to the client, it logs: 09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable What is missing now and how do I fix it? Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: I think you need to drop the jar file containing org.apache.cxf.transport.servlet.CXFServlet class into jboss\default\server\lib folder OR add this jar to web-inf\lib folder of the war being deployed. Srinivas. -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 12:40 To: cxf-user@incubator.apache.org Subject: How to deploy to JBoss? I have been going through the CXF samples; those I have tried work fine, both in standalone mode and with the server part deployed to Tomcat. What do I need to do if I want to deploy to JBoss instead of Tomcat? I tried to simply drop helloworld.war into the C:\opt\jboss\jboss- 4.0.4.GA\server\default\deploy directory, this gave a class not found exception: 09:00:31,501 ERROR [MainDeployer] Could not create deployment: file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.cxf.transport.servlet.CXFServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment( WebServiceDeployerJSE.java:161) ... Regards, Erlend Leganger My environment: rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02 set JAVA_HOME=c:\opt\java\jdk1.5.0_12 set AXIS2_HOME=c:\opt\axis2\axis2-1.3-RC2 set ANT_HOME=c:\opt\ant\apache-ant-1.7.0 set CATALINA_HOME=c:\opt\tomcat\apache-tomcat-5.5.23 set JBOSS_HOME=c:\opt\jboss\jboss-4.0.4.GA set CFX_HOME=c:\opt\cxf\apache-cxf-2.0-incubator set PATH=C:\WINDOWS set PATH=%PATH%;C:\WINDOWS\system32 set PATH=%PATH%;C:\WINDOWS\System32\Wbem set PATH=%PATH%;%JAVA_HOME%\bin set PATH=%PATH%;%CATALINA_HOME%\bin set PATH=%PATH%;%JBOSS_HOME%\bin set PATH=%PATH%;%ANT_HOME%\bin set CLASSPATH=.;%CFX_HOME%\lib\cxf-manifest-incubator.jar;.\build\classes __ __ This e-mail has been scanned for all viruses by MessageLabs. __ __ This e-mail has been scanned for all viruses by MessageLabs. To learn more about Singularity's business process management solutions and services please visit: www.singularity.co.uk www.singularity.us.com Singularity operates globally through its offices in New York, London, Singapore, Ireland and India. Singularity Limited is incorporated in the United Kingdom with Registration Number NI 31519 and its Registered Office at 100 Patrick Street, Derry, BT48 7EL, United Kingdom.
Re: REST url quirk...
Hi Brad,
This was a bug in the JRA jar. You can try updating to the alpha-4 snapshot
and it should fix things:
http://repo1.maven.org/maven2/org/codehaus/jra/jra/1.0-alpha-4/jra-1.0-alpha-4.jar
(If that doesn't work try the 2.0.1/SNAPSHOT builds from CXF as well, but
I'm pretty sure CXF didn't require any changes for the problem)
- Dan
On 8/2/07, Brad Harper [EMAIL PROTECTED] wrote:
I have several identically configured REST services working with one
exception. When the method I call is getMediaType(s) - ( /rest/mediaTypes
/rest/mediaType/{1} ), the get mediaTypes services returns the correct
data. However, when I try to access a specific type by id
/rest/mediaTypes/1, I still get the entire list back. Basically CXF is
not
interpreting the '/1' appended to the url. Renaming the exact methods and
corresponding annotations to getXMediaTypes resolves the issue. Could
this
be a naming collision with something in the HTTP headers?
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
Re: How to deploy to JBoss?
You were right, it wasn't copied. I tried to copy it from cxf-2.0-incubator/lib into jboss-4.0.4.GA/default/server/lib, restarted - then jboss was missing some other spring stuff. Copied all spring*.jar from cxf into jboss, restarted, then some other stuff was missing. Finally copied all files from cxf/lib into default/server/lib, restarted jboss and then it worked! - thanks a lot! Is this this the proper way to do it? I felt like I was polluting the jboss installation with all this cxf stuff... Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: Check for spring-beans-2.0.4.jar, copied or not? -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 13:23 To: cxf-user@incubator.apache.org Subject: Re: How to deploy to JBoss? I tried the following: - copied all files from cxf's modules directory into jboss' server/default/deploy/lib - restarted jboss - dropped helloworld.war into jboss' server/default/deploy This made a difference, but it still doesn't work, here's the jboss log: 09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld, warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/ 09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as unavailable 09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw load() exception java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry When trying ant client-servlet, jboss refuses to respond to the client, it logs: 09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable What is missing now and how do I fix it? Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: I think you need to drop the jar file containing org.apache.cxf.transport.servlet.CXFServlet class into jboss\default\server\lib folder OR add this jar to web-inf\lib folder of the war being deployed. Srinivas. -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 12:40 To: cxf-user@incubator.apache.org Subject: How to deploy to JBoss? I have been going through the CXF samples; those I have tried work fine, both in standalone mode and with the server part deployed to Tomcat. What do I need to do if I want to deploy to JBoss instead of Tomcat? I tried to simply drop helloworld.war into the C:\opt\jboss\jboss- 4.0.4.GA\server\default\deploy directory, this gave a class not found exception: 09:00:31,501 ERROR [MainDeployer] Could not create deployment: file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.cxf.transport.servlet.CXFServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment( WebServiceDeployerJSE.java:161) ... Regards, Erlend Leganger My environment: rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02 set JAVA_HOME=c:\opt\java\jdk1.5.0_12 set AXIS2_HOME=c:\opt\axis2\axis2-1.3-RC2 set ANT_HOME=c:\opt\ant\apache-ant-1.7.0 set CATALINA_HOME=c:\opt\tomcat\apache-tomcat-5.5.23 set JBOSS_HOME=c:\opt\jboss\jboss-4.0.4.GA set CFX_HOME=c:\opt\cxf\apache-cxf-2.0-incubator set PATH=C:\WINDOWS set PATH=%PATH%;C:\WINDOWS\system32 set PATH=%PATH%;C:\WINDOWS\System32\Wbem set PATH=%PATH%;%JAVA_HOME%\bin set PATH=%PATH%;%CATALINA_HOME%\bin set PATH=%PATH%;%JBOSS_HOME%\bin set PATH=%PATH%;%ANT_HOME%\bin set CLASSPATH=.;%CFX_HOME%\lib\cxf-manifest-incubator.jar;.\build\classes __ __ This e-mail has been scanned for all viruses by MessageLabs. __ __ __ __ This e-mail has been scanned for all viruses by MessageLabs. To learn more about Singularity's business process management solutions and services please visit: www.singularity.co.uk www.singularity.us.com Singularity operates globally through its offices in New York, London, Singapore, Ireland and India. Singularity Limited is incorporated in the United Kingdom with Registration Number NI 31519 and its Registered Office at 100 Patrick Street, Derry, BT48 7EL, United Kingdom. __ __ This e-mail has been scanned for all viruses by MessageLabs. __ __
Re: WHICH_JARS not actual
On Friday 03 August 2007 05:30, Gustavo Morozowski wrote: Any updates on WHICH_JARS for 2.0.1? Unforuntately, not nearly changed enough. I did add mention of the asm jar which was added. But that's probably about the only change. :-( Dan Gustavo On 7/17/07, Dan Diephouse [EMAIL PROTECTED] wrote: Hi Deno, That is correct - you can just use the single spring jar. - Dan On 7/16/07, Deno Vichas [EMAIL PROTECTED] wrote: (somebody correctly me if I'm wrong here) you can just all the main spring jar and not all the smaller individuals ones. Sure, your project will be slightly bigger but less jars I have to keep track of the better. -Original Message- From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 7:30 AM To: cxf-user@incubator.apache.org Subject: RE: WHICH_JARS not actual Yes ,we should update the WHICH_JARS to refelect the recent changes. For the second issue, current CXF servlet only support SpringBusFactory which relates on Spring. So you have to include the Spring jars for wiring the CXF components with the Bus. Willem. -Original Message- From: Lukas Zapletal [mailto:[EMAIL PROTECTED] Sent: Mon 7/16/2007 21:54 To: cxf-user@incubator.apache.org Subject: WHICH_JARS not actual Hello all, it seems WHICH_JARS file is not actual. CXF itself needs xml-resolver.jar and I am sure there will be other JARs that should be included in the minimal CXF install. The second issue about the libraries is that CXF depends on Spring even when I do not use it. I have created just a Servlet in the web.xml but when my container tried to load the application I get an exception. As a temporary solution I am adding all JARs to my servlet. Could you check the WHICH_JARS file please? 15:37:03,713 ERROR [[CXFServlet]] Allocate exception for servlet CXFServlet java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapp er.jav a:1104) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper. java:8 06) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapp erValv e.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardConte xtValv e.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Secu rityAs sociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextV alve.j ava:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValv e.java :128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValv e.java :104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(Cach edConn ectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngine Valve. java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter. java:2 41) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.j ava:84 4) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.pr ocess( Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java :447) at java.lang.Thread.run(Unknown Source) 15:37:23,331 INFO [[CXFServlet]] Servlet CXFServlet is currently unavailable -- Lukas Zapletal http://lukas.zapletalovi.com -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
RE: How to deploy to JBoss?
You should be able to drop all those same jars into the WEB-INF/lib of your web application-- then you wouldn't need to copy them into the Jboss server lib. -Chris -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: Friday, August 03, 2007 8:32 AM To: cxf-user@incubator.apache.org Subject: Re: How to deploy to JBoss? You were right, it wasn't copied. I tried to copy it from cxf-2.0-incubator/lib into jboss-4.0.4.GA/default/server/lib, restarted - then jboss was missing some other spring stuff. Copied all spring*.jar from cxf into jboss, restarted, then some other stuff was missing. Finally copied all files from cxf/lib into default/server/lib, restarted jboss and then it worked! - thanks a lot! Is this this the proper way to do it? I felt like I was polluting the jboss installation with all this cxf stuff... Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: Check for spring-beans-2.0.4.jar, copied or not? -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 13:23 To: cxf-user@incubator.apache.org Subject: Re: How to deploy to JBoss? I tried the following: - copied all files from cxf's modules directory into jboss' server/default/deploy/lib - restarted jboss - dropped helloworld.war into jboss' server/default/deploy This made a difference, but it still doesn't work, here's the jboss log: 09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld, warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/ 09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as unavailable 09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw load() exception java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry When trying ant client-servlet, jboss refuses to respond to the client, it logs: 09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable What is missing now and how do I fix it? Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: I think you need to drop the jar file containing org.apache.cxf.transport.servlet.CXFServlet class into jboss\default\server\lib folder OR add this jar to web-inf\lib folder of the war being deployed. Srinivas. -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 12:40 To: cxf-user@incubator.apache.org Subject: How to deploy to JBoss? I have been going through the CXF samples; those I have tried work fine, both in standalone mode and with the server part deployed to Tomcat. What do I need to do if I want to deploy to JBoss instead of Tomcat? I tried to simply drop helloworld.war into the C:\opt\jboss\jboss- 4.0.4.GA\server\default\deploy directory, this gave a class not found exception: 09:00:31,501 ERROR [MainDeployer] Could not create deployment: file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.cxf.transport.servlet.CXFServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment( WebServiceDeployerJSE.java:161) ... Regards, Erlend Leganger My environment: rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02 set JAVA_HOME=c:\opt\java\jdk1.5.0_12 set AXIS2_HOME=c:\opt\axis2\axis2-1.3-RC2 set ANT_HOME=c:\opt\ant\apache-ant-1.7.0 set CATALINA_HOME=c:\opt\tomcat\apache-tomcat-5.5.23 set JBOSS_HOME=c:\opt\jboss\jboss-4.0.4.GA set CFX_HOME=c:\opt\cxf\apache-cxf-2.0-incubator set PATH=C:\WINDOWS set PATH=%PATH%;C:\WINDOWS\system32 set PATH=%PATH%;C:\WINDOWS\System32\Wbem set PATH=%PATH%;%JAVA_HOME%\bin set PATH=%PATH%;%CATALINA_HOME%\bin set PATH=%PATH%;%JBOSS_HOME%\bin set PATH=%PATH%;%ANT_HOME%\bin set CLASSPATH=.;%CFX_HOME%\lib\cxf-manifest-incubator.jar;.\build\classes __ __ This e-mail has been scanned for all viruses by MessageLabs. __ __ __ __ This e-mail has been scanned for all viruses by MessageLabs. To learn more about Singularity's business process management solutions and services please visit: www.singularity.co.uk www.singularity.us.com Singularity operates globally through its offices in New York, London, Singapore, Ireland and India. Singularity Limited is incorporated in the United Kingdom with Registration Number NI 31519 and its Registered Office
Re: How to deploy to JBoss?
I agree with Ray here - why support Tomcat deployment only? If the war had all the required files in it, we could have a generic ant deploy/ant undeploy which merely copied/deleted the war file in the correct directory for the container of choice. This would require that you manually configured common_build.xml with the actual deployment target directory (in my case C:\opt\jboss\jboss-4.0.4.GA\server\default\deploy), but then you would have a generic deployment mechanism (assuming that copying a war to a directory is all that is required to deploy to a container) which in my case would support jboss. - Erlend Leganger On 03/08/07, Ray Krueger [EMAIL PROTECTED] wrote: The CXF crew should look at making the samples deploy in a more standard fashion. Currently the deployment requires man-handling all of the cxf jars into Tomcat's classpath, rather than packaging them into a WAR. Building a WAR would give us the ability to try out the samples in our container of choice; or the companys container of choice as the case may be. On 8/3/07, Christopher Moesel [EMAIL PROTECTED] wrote: You should be able to drop all those same jars into the WEB-INF/lib of your web application-- then you wouldn't need to copy them into the Jboss server lib. -Chris -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: Friday, August 03, 2007 8:32 AM To: cxf-user@incubator.apache.org Subject: Re: How to deploy to JBoss? You were right, it wasn't copied. I tried to copy it from cxf-2.0-incubator/lib into jboss-4.0.4.GA/default/server/lib, restarted - then jboss was missing some other spring stuff. Copied all spring*.jar from cxf into jboss, restarted, then some other stuff was missing. Finally copied all files from cxf/lib into default/server/lib, restarted jboss and then it worked! - thanks a lot! Is this this the proper way to do it? I felt like I was polluting the jboss installation with all this cxf stuff... Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: Check for spring-beans-2.0.4.jar, copied or not? -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 13:23 To: cxf-user@incubator.apache.org Subject: Re: How to deploy to JBoss? I tried the following: - copied all files from cxf's modules directory into jboss' server/default/deploy/lib - restarted jboss - dropped helloworld.war into jboss' server/default/deploy This made a difference, but it still doesn't work, here's the jboss log: 09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld, warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/ 09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as unavailable 09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw load() exception java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry When trying ant client-servlet, jboss refuses to respond to the client, it logs: 09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable What is missing now and how do I fix it? Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: I think you need to drop the jar file containing org.apache.cxf.transport.servlet.CXFServlet class into jboss\default\server\lib folder OR add this jar to web-inf\lib folder of the war being deployed. Srinivas. -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 12:40 To: cxf-user@incubator.apache.org Subject: How to deploy to JBoss? I have been going through the CXF samples; those I have tried work fine, both in standalone mode and with the server part deployed to Tomcat. What do I need to do if I want to deploy to JBoss instead of Tomcat? I tried to simply drop helloworld.war into the C:\opt\jboss\jboss- 4.0.4.GA\server\default\deploy directory, this gave a class not found exception: 09:00:31,501 ERROR [MainDeployer] Could not create deployment: file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.cxf.transport.servlet.CXFServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment( WebServiceDeployerJSE.java:161) ... Regards, Erlend Leganger My environment: rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02 set JAVA_HOME=c:\opt\java\jdk1.5.0_12 set
Re: How to deploy to JBoss?
Thanks for the clarification Ray, I got a bit carried away...
I added the following stuff to my common_build.xml:
target name=jboss.deploy description=deploy the application into
jboss
antcall target=war/
copy file=${war.dir}/${cxf.war.file.name}.war
todir=${env.JBOSS_HOME}/server/default/deploy/
/target
target name=jboss.undeploy
delete file=${env.JBOSS_HOME}/server/default/deploy/${
cxf.war.file.name}.war/
delete dir=${env.JBOSS_HOME}/server/default/deploy/${
cxf.war.file.name}/
/target
With this and with the additional the changes to common_build.xml reported
earlier in the thread to produce a properly packaged war, I can now do ant
jboss.deploy and get get the samples to run in jboss without manually
copying jars from cxf to jboss. The war increased in size (about
1.000times...) - this is no problem for me right now.
- Erlend Leganger
On 03/08/07, Ray Krueger [EMAIL PROTECTED] wrote:
Well, what I was saying really was to produce a properly packaged war
file. The ant common_build.xml can still deploy that war to tomcat for
you. I have no problem with that, it's nice and simple and quick.
If you want to eval another container you just copy the war over and go...
On 8/3/07, Erlend Leganger [EMAIL PROTECTED] wrote:
I agree with Ray here - why support Tomcat deployment only?
If the war had all the required files in it, we could have a generic ant
deploy/ant undeploy which merely copied/deleted the war file in the
correct
directory for the container of choice. This would require that you
manually
configured common_build.xml with the actual deployment target directory
(in
my case C:\opt\jboss\jboss-4.0.4.GA\server\default\deploy), but then you
would have a generic deployment mechanism (assuming that copying a war
to a
directory is all that is required to deploy to a container) which in my
case
would support jboss.
- Erlend Leganger
On 03/08/07, Ray Krueger [EMAIL PROTECTED] wrote:
The CXF crew should look at making the samples deploy in a more
standard fashion.
Currently the deployment requires man-handling all of the cxf jars
into Tomcat's classpath, rather than packaging them into a WAR.
Building a WAR would give us the ability to try out the samples in our
container of choice; or the companys container of choice as the case
may be.
On 8/3/07, Christopher Moesel [EMAIL PROTECTED] wrote:
You should be able to drop all those same jars into the WEB-INF/lib
of
your web application-- then you wouldn't need to copy them into the
Jboss server lib.
-Chris
-Original Message-
From: Erlend Leganger [mailto:[EMAIL PROTECTED]
Sent: Friday, August 03, 2007 8:32 AM
To: cxf-user@incubator.apache.org
Subject: Re: How to deploy to JBoss?
You were right, it wasn't copied. I tried to copy it from
cxf-2.0-incubator/lib
into jboss-4.0.4.GA/default/server/lib, restarted - then jboss was
missing
some other spring stuff. Copied all spring*.jar from cxf into jboss,
restarted, then some other stuff was missing. Finally copied all
files
from
cxf/lib into default/server/lib, restarted jboss and then it worked!
-
thanks a lot!
Is this this the proper way to do it? I felt like I was polluting
the
jboss
installation with all this cxf stuff...
Regards,
Erlend Leganger
On 03/08/07, Velidanda Srinivas
[EMAIL PROTECTED]
wrote:
Check for spring-beans-2.0.4.jar, copied or not?
-Original Message-
From: Erlend Leganger [mailto:[EMAIL PROTECTED]
Sent: 03 August 2007 13:23
To: cxf-user@incubator.apache.org
Subject: Re: How to deploy to JBoss?
I tried the following:
- copied all files from cxf's modules directory into jboss'
server/default/deploy/lib
- restarted jboss
- dropped helloworld.war into jboss' server/default/deploy
This made a difference, but it still doesn't work, here's the
jboss log:
09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld,
warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/
09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as
unavailable
09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw
load()
exception java.lang.NoClassDefFoundError:
org/springframework/beans/factory/support/BeanDefinitionRegistry
When trying ant client-servlet, jboss refuses to respond to
the client, it
logs:
09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable
09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable
09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable
What is missing now and how do I fix it?
Regards,
Erlend Leganger
On 03/08/07, Velidanda Srinivas
Re: WHICH_JARS not actual
Hi Gustavo, Seems this slipped through the cracks for 2.0.1 (which is being voted on right now). I created a JIRA issue so that doesn't happen again: https://issues.apache.org/jira/browse/CXF-878 Feel free to attach your comments/concerns. If you have any specific questions about what jars are needed for CXF feel free to ask here and we'll try to provide you with some answers. Regards, - Dan On 8/3/07, Gustavo Morozowski [EMAIL PROTECTED] wrote: Any updates on WHICH_JARS for 2.0.1? Gustavo On 7/17/07, Dan Diephouse [EMAIL PROTECTED] wrote: Hi Deno, That is correct - you can just use the single spring jar. - Dan On 7/16/07, Deno Vichas [EMAIL PROTECTED] wrote: (somebody correctly me if I'm wrong here) you can just all the main spring jar and not all the smaller individuals ones. Sure, your project will be slightly bigger but less jars I have to keep track of the better. -Original Message- From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 7:30 AM To: cxf-user@incubator.apache.org Subject: RE: WHICH_JARS not actual Yes ,we should update the WHICH_JARS to refelect the recent changes. For the second issue, current CXF servlet only support SpringBusFactory which relates on Spring. So you have to include the Spring jars for wiring the CXF components with the Bus. Willem. -Original Message- From: Lukas Zapletal [mailto:[EMAIL PROTECTED] Sent: Mon 7/16/2007 21:54 To: cxf-user@incubator.apache.org Subject: WHICH_JARS not actual Hello all, it seems WHICH_JARS file is not actual. CXF itself needs xml-resolver.jar and I am sure there will be other JARs that should be included in the minimal CXF install. The second issue about the libraries is that CXF depends on Spring even when I do not use it. I have created just a Servlet in the web.xml but when my container tried to load the application I get an exception. As a temporary solution I am adding all JARs to my servlet. Could you check the WHICH_JARS file please? 15:37:03,713 ERROR [[CXFServlet]] Allocate exception for servlet CXFServlet java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.catalina.core.StandardWrapper.loadServlet( StandardWrapper.jav a:1104) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java :8 06) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValv e.java:129) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValv e.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke (SecurityAs sociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke( JaccContextValve.j ava:84) at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java :128) at org.apache.catalina.valves.ErrorReportValve.invoke( ErrorReportValve.java :104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke (CachedConn ectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve. java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java :2 41) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :84 4) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java :447) at java.lang.Thread.run(Unknown Source) 15:37:23,331 INFO [[CXFServlet]] Servlet CXFServlet is currently unavailable -- Lukas Zapletal http://lukas.zapletalovi.com -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: YOKO CXF CORBA Web Service using ProviderCorbaMessage
Hello, To get Dispatch/Provider interface working with CORBA binding, we need to figure out what the T is in the ProviderT. I understand. Its a question to Yoko developers. If you use CORBA server web services client as described in YOKO ws\hello_world sample (i.e., the server is using CORBA binding, the client is using SOAP or XML binding), DispatchSource should definitely work, because what sent on the wire is SOAP or XML message. You say you have CORBA service and WS client implemented with DispatchSource should work? Or what you mean exactly with working Dispatch? Talking about WS client calling CORBA we have tried to use dynamic proxy over CORBA and it doesnt work: QName svcQname = new QName( http://schemas.apache.org/yoko/idl/calc;, com.pikeelectronic.calc.CalculatorCORBAService); QName portQName = new QName( http://schemas.apache.org/yoko/idl/calc;, com.pikeelectronic.calc.CalculatorCORBAPort); File wsdl = new File(calc-soapbinding.wsdl); Service svc = Service.create(wsdl.toURL(),svcQname); ComPikeelectronicCalcCalculator calc = svc.getPort(portQName, ComPikeelectronicCalcCalculator.class); double result = calc.add(4, 5); System.out.println(result); When I run this with SOAP binding it works but when I try to do this with CORBA binding I am getting exception: INFO: Interceptor has thrown exception, unwinding now java.lang.NullPointerException at org.apache.yoko.bindings.corba.interceptors.CorbaStreamOutInterceptor.handleOutBoundMessage(CorbaStreamOutInterceptor.java:78) at org.apache.yoko.bindings.corba.interceptors.CorbaStreamOutInterceptor.handleMessage(CorbaStreamOutInterceptor.java:65) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:206) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:204) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:134) at $Proxy34.add(Unknown Source) at com.pikeelectronic.calc.WSDIIClient.main(WSDIIClient.java:46) javax.xml.ws.WebServiceException: java.lang.NullPointerException at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:172) at $Proxy34.add(Unknown Source) at com.pikeelectronic.calc.WSDIIClient.main(WSDIIClient.java:46) Caused by: java.lang.NullPointerException at org.apache.yoko.bindings.corba.interceptors.CorbaStreamOutInterceptor.handleOutBoundMessage(CorbaStreamOutInterceptor.java:78) at org.apache.yoko.bindings.corba.interceptors.CorbaStreamOutInterceptor.handleMessage(CorbaStreamOutInterceptor.java:65) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:206) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:204) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:134) ... 2 more Jervis -Original Message- From: Lukas Zapletal [ mailto:[EMAIL PROTECTED] Sent: 2007年8月2日 23:00 To: cxf-user@incubator.apache.org; [EMAIL PROTECTED] Subject: Re: YOKO CXF CORBA Web Service using ProviderCorbaMessage Hello, the operation info and CORBA parameters are not the reason why do we need the support. We would like to create a web service provider that will be accessible from CORBA client. We have no clue how to do this because we cannot simply create ProviderCorbaMessage, ProviderSOAPMessage or even ProviderSource. Exception occurs when we try this so it seems nobody ever used it before and the code contains a bug or we are doing something wrong. On the other side we are also trying to call (normal) CORBA service with web service client implemented in CXF/Yoko dynamicaly (DII client). We do not know if is it possible to create SOAPMessage and pass it to Yoko CORBA binding along with WSDL file to make a dynamic call. It seems to me the terms corba cxf binding and dynamic cannot live together... Best regards, Lukas 2007/8/2, Liu, Jervis [EMAIL PROTECTED]: Hi, have a new question. I suppose the reason why you want to use Provider interface for CORBA binding is that you want to access raw CORBA message payload so that you can parse operation info and input parameters by yourself. However the question is what the raw CORBA message payload is? In the world of SOAP binding or XML binding, the content sent on the wire normally can be represented as XML, thus we can have typed provider interface like ProviderSource, ProviderSOAPMessage. However, in the
Re: How to deploy to JBoss?
The CXF crew should look at making the samples deploy in a more standard fashion. Currently the deployment requires man-handling all of the cxf jars into Tomcat's classpath, rather than packaging them into a WAR. Building a WAR would give us the ability to try out the samples in our container of choice; or the companys container of choice as the case may be. On 8/3/07, Christopher Moesel [EMAIL PROTECTED] wrote: You should be able to drop all those same jars into the WEB-INF/lib of your web application-- then you wouldn't need to copy them into the Jboss server lib. -Chris -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: Friday, August 03, 2007 8:32 AM To: cxf-user@incubator.apache.org Subject: Re: How to deploy to JBoss? You were right, it wasn't copied. I tried to copy it from cxf-2.0-incubator/lib into jboss-4.0.4.GA/default/server/lib, restarted - then jboss was missing some other spring stuff. Copied all spring*.jar from cxf into jboss, restarted, then some other stuff was missing. Finally copied all files from cxf/lib into default/server/lib, restarted jboss and then it worked! - thanks a lot! Is this this the proper way to do it? I felt like I was polluting the jboss installation with all this cxf stuff... Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: Check for spring-beans-2.0.4.jar, copied or not? -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 13:23 To: cxf-user@incubator.apache.org Subject: Re: How to deploy to JBoss? I tried the following: - copied all files from cxf's modules directory into jboss' server/default/deploy/lib - restarted jboss - dropped helloworld.war into jboss' server/default/deploy This made a difference, but it still doesn't work, here's the jboss log: 09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld, warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/ 09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as unavailable 09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw load() exception java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry When trying ant client-servlet, jboss refuses to respond to the client, it logs: 09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable What is missing now and how do I fix it? Regards, Erlend Leganger On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED] wrote: I think you need to drop the jar file containing org.apache.cxf.transport.servlet.CXFServlet class into jboss\default\server\lib folder OR add this jar to web-inf\lib folder of the war being deployed. Srinivas. -Original Message- From: Erlend Leganger [mailto:[EMAIL PROTECTED] Sent: 03 August 2007 12:40 To: cxf-user@incubator.apache.org Subject: How to deploy to JBoss? I have been going through the CXF samples; those I have tried work fine, both in standalone mode and with the server part deployed to Tomcat. What do I need to do if I want to deploy to JBoss instead of Tomcat? I tried to simply drop helloworld.war into the C:\opt\jboss\jboss- 4.0.4.GA\server\default\deploy directory, this gave a class not found exception: 09:00:31,501 ERROR [MainDeployer] Could not create deployment: file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war org.jboss.ws.WSException: java.lang.ClassNotFoundException: org.apache.cxf.transport.servlet.CXFServlet at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment( WebServiceDeployerJSE.java:161) ... Regards, Erlend Leganger My environment: rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02 set JAVA_HOME=c:\opt\java\jdk1.5.0_12 set AXIS2_HOME=c:\opt\axis2\axis2-1.3-RC2 set ANT_HOME=c:\opt\ant\apache-ant-1.7.0 set CATALINA_HOME=c:\opt\tomcat\apache-tomcat-5.5.23 set JBOSS_HOME=c:\opt\jboss\jboss-4.0.4.GA set CFX_HOME=c:\opt\cxf\apache-cxf-2.0-incubator set PATH=C:\WINDOWS set PATH=%PATH%;C:\WINDOWS\system32 set PATH=%PATH%;C:\WINDOWS\System32\Wbem set PATH=%PATH%;%JAVA_HOME%\bin set PATH=%PATH%;%CATALINA_HOME%\bin set PATH=%PATH%;%JBOSS_HOME%\bin set PATH=%PATH%;%ANT_HOME%\bin set CLASSPATH=.;%CFX_HOME%\lib\cxf-manifest-incubator.jar;.\build\classes __ __ This e-mail has been scanned for all viruses by MessageLabs. __
Re: How to deploy to JBoss?
I added the following to war destfile... in common_build.xml:
lib dir=${cxf.home}/modules/lib
lib dir=${cxf.home}/lib/lib
After ant war, the resulting helloworld.war increased in size from 19K to
19M and had all the good stuff in the WEB-INF/lib directory.
Dropping helloworld.war into jboss/server/default/deploy (I reinstalled
jboss to get back to a virgin state) gave a fully functional Hello World
example without any manual copying to pollute the jboss directories. So, the
suggestion from Cristopher and Velidanda worked - thanks!
- Erlend Leganger
On 03/08/07, Christopher Moesel [EMAIL PROTECTED] wrote:
You should be able to drop all those same jars into the WEB-INF/lib of
your web application-- then you wouldn't need to copy them into the
Jboss server lib.
-Chris
-Original Message-
From: Erlend Leganger [mailto:[EMAIL PROTECTED]
Sent: Friday, August 03, 2007 8:32 AM
To: cxf-user@incubator.apache.org
Subject: Re: How to deploy to JBoss?
You were right, it wasn't copied. I tried to copy it from
cxf-2.0-incubator/lib
into jboss-4.0.4.GA/default/server/lib, restarted - then jboss was
missing
some other spring stuff. Copied all spring*.jar from cxf into jboss,
restarted, then some other stuff was missing. Finally copied all files
from
cxf/lib into default/server/lib, restarted jboss and then it worked! -
thanks a lot!
Is this this the proper way to do it? I felt like I was polluting the
jboss
installation with all this cxf stuff...
Regards,
Erlend Leganger
On 03/08/07, Velidanda Srinivas [EMAIL PROTECTED]
wrote:
Check for spring-beans-2.0.4.jar, copied or not?
-Original Message-
From: Erlend Leganger [mailto:[EMAIL PROTECTED]
Sent: 03 August 2007 13:23
To: cxf-user@incubator.apache.org
Subject: Re: How to deploy to JBoss?
I tried the following:
- copied all files from cxf's modules directory into jboss'
server/default/deploy/lib
- restarted jboss
- dropped helloworld.war into jboss' server/default/deploy
This made a difference, but it still doesn't work, here's the
jboss log:
09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld,
warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/
09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as
unavailable
09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw load()
exception java.lang.NoClassDefFoundError:
org/springframework/beans/factory/support/BeanDefinitionRegistry
When trying ant client-servlet, jboss refuses to respond to
the client, it
logs:
09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable
09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable
09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable
What is missing now and how do I fix it?
Regards,
Erlend Leganger
On 03/08/07, Velidanda Srinivas
[EMAIL PROTECTED]
wrote:
I think you need to drop the jar file containing
org.apache.cxf.transport.servlet.CXFServlet class
into jboss\default\server\lib folder OR add this jar to
web-inf\lib folder
of the war being deployed.
Srinivas.
-Original Message-
From: Erlend Leganger [mailto:[EMAIL PROTECTED]
Sent: 03 August 2007 12:40
To: cxf-user@incubator.apache.org
Subject: How to deploy to JBoss?
I have been going through the CXF samples; those I have tried
work fine,
both in standalone mode and with the server part deployed
to Tomcat.
What do I need to do if I want to deploy to JBoss instead of
Tomcat? I tried
to simply drop helloworld.war into the C:\opt\jboss\jboss-
4.0.4.GA\server\default\deploy directory, this gave a
class not found
exception:
09:00:31,501 ERROR [MainDeployer] Could not create deployment:
file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war
org.jboss.ws.WSException: java.lang.ClassNotFoundException:
org.apache.cxf.transport.servlet.CXFServlet
at
org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(
WebServiceDeployerJSE.java:161)
...
Regards,
Erlend Leganger
My environment:
rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02
set JAVA_HOME=c:\opt\java\jdk1.5.0_12
set AXIS2_HOME=c:\opt\axis2\axis2-1.3-RC2
set ANT_HOME=c:\opt\ant\apache-ant-1.7.0
set CATALINA_HOME=c:\opt\tomcat\apache-tomcat-5.5.23
set JBOSS_HOME=c:\opt\jboss\jboss-4.0.4.GA
set CFX_HOME=c:\opt\cxf\apache-cxf-2.0-incubator
set PATH=C:\WINDOWS
set PATH=%PATH%;C:\WINDOWS\system32
set PATH=%PATH%;C:\WINDOWS\System32\Wbem
set PATH=%PATH%;%JAVA_HOME%\bin
set PATH=%PATH%;%CATALINA_HOME%\bin
set PATH=%PATH%;%JBOSS_HOME%\bin
set PATH=%PATH%;%ANT_HOME%\bin
set
CLASSPATH=.;%CFX_HOME%\lib\cxf-manifest-incubator.jar;.\build\classes
RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage
Hi Lukas, none of these ProviderCorbaMessage, ProviderSOAPMessage or ProviderSource is supposed to work with CORBA binding. The type class T in ProviderT has to be something that can represent the message (or message payload) you sent on the wire DIRECTLY. What I mean by “directly” is without any extra marshaling/unmarshalling or transformation for example, using a data binding to map one type to another type. In the case of SOAP binding or XML binding, the content type is text/xml, the wire message can always be represented as Source or SOAPMessage (SOAP binding) object. The message sent on the wire for CORBA biding is in binary format. A simple question, in the Dispatch example you gave in your previous email, how can you transform a Source that represents a xml document of tns:add xmlns:tns= http://schemas.apache.org/yoko/idl/calc/ http://schemas.apache.org/yoko/idl/calc/ into a binary format of CORBA message? The T in ProviderT or DispatchT has to be something that you can take it and sent it out on the wire directly without any transformation. This is why DispatchSource won’t work. To get Dispatch/Provider interface working with CORBA binding, we need to figure out what the T is in the ProviderT. If you use CORBA server web services client as described in YOKO ws\hello_world sample (i.e., the server is using CORBA binding, the client is using SOAP or XML binding), DispatchSource should definitely work, because what sent on the wire is SOAP or XML message. Jervis -Original Message- From: Lukas Zapletal [ mailto:[EMAIL PROTECTED] Sent: 2007年8月2日 23:00 To: cxf-user@incubator.apache.org; [EMAIL PROTECTED] Subject: Re: YOKO CXF CORBA Web Service using ProviderCorbaMessage Hello, the operation info and CORBA parameters are not the reason why do we need the support. We would like to create a web service provider that will be accessible from CORBA client. We have no clue how to do this because we cannot simply create ProviderCorbaMessage, ProviderSOAPMessage or even ProviderSource. Exception occurs when we try this so it seems nobody ever used it before and the code contains a bug or we are doing something wrong. On the other side we are also trying to call (normal) CORBA service with web service client implemented in CXF/Yoko dynamicaly (DII client). We do not know if is it possible to create SOAPMessage and pass it to Yoko CORBA binding along with WSDL file to make a dynamic call. It seems to me the terms corba cxf binding and dynamic cannot live together... Best regards, Lukas 2007/8/2, Liu, Jervis [EMAIL PROTECTED]: Hi, have a new question. I suppose the reason why you want to use Provider interface for CORBA binding is that you want to access raw CORBA message payload so that you can parse operation info and input parameters by yourself. However the question is what the raw CORBA message payload is? In the world of SOAP binding or XML binding, the content sent on the wire normally can be represented as XML, thus we can have typed provider interface like ProviderSource, ProviderSOAPMessage. However, in the world of CORBA, I don't think we have a well-defined type to represent raw CORBA message payload, do we? Please note, org.apache.yoko.bindings.corba.CorbaMessage is not the one we are looking for. Same as the org.apache.cxf.binding.soap.SoapMessage and org.apache.cxf.binding.xml.XMLMessage, they are just a content holder, which represent the whole input/output message rather than the message payload. The type class that can be used in ProviderT is sth that can be produced by ObjectT = DataReader.read(...). Before we can go ahead to support ProviderT for CORBA binding, we really need to figure out what the T is. BTW, if what you want is CorbaMessage, you can access it from Exchange. See Dan's previous comment in this thread on how to access Exchange. I will send this message across to yoko mailing list, hopefully Yoko guys can give some insight on this. Cheers, Jervis -Original Message- From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] Sent: 2007年7月30日 19:52 To: cxf-user@incubator.apache.org; Liu, Jervis Subject: RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage Hi Jervis, it really sounds great, cxf would be more flexible then. Thank you for your replies. So do you plan adding support of that to cxf? And would it be possible to know when? :-) Cheers, Michael -Original Message- From: Liu, Jervis [ mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 1:12 PM To: cxf-user@incubator.apache.org; [EMAIL PROTECTED] Cc: Michal ?afr; [EMAIL PROTECTED] Subject: RE: YOKO CXF CORBA Web Service using ProviderCorbaMessage Coming to think of this again, I found supporting ProviderCorbaMessage isn't that difficult as I originally thought. We have some manual checks of binding type in DispatchInDatabindingInterceptor\DispatchOutDatabindingInterceptor, such as if (binding ==
Re: YOKO CXF CORBA Web Service using ProviderCorbaMessage
I have also tried dynamic proxy call:
QName operationQName = new QName(
http://schemas.apache.org/yoko/idl/calc;,
add);
JaxWsClientFactoryBean client = new JaxWsClientFactoryBean();
client.setAddress(http://localhost/soap/calc;);
client.setServiceClass(ComPikeelectronicCalcCalculator.class);
ClientImpl SOAPclient = (ClientImpl)client.create();
Object[] SOAPresult = null;
Object[] params = { new Double(4), new Double(2) };
try {
SOAPresult = SOAPclient.invoke(operationQName,
params);
} catch (Exception e) {
e.printStackTrace();
}
System.out.println(SOAPresult);
I am getting the same result. Maybe I need to wrap the input
parameters (double, double) into Any type because it seems the CORBA
binding expects something else. Any pointers here?
Have a nice weekend.
2007/8/2, Lukas Zapletal [EMAIL PROTECTED]:
I thought DII and Dispatch are equal. So is there a possibility to
call a CORBA service in y dynamic way? Example of the client:
QName svcQname = new QName(
http://schemas.apache.org/yoko/idl/calc;,
com.pikeelectronic.calc.CalculatorCORBAService);
QName portQName = new QName(
http://schemas.apache.org/yoko/idl/calc;,
com.pikeelectronic.calc.CalculatorCORBAPort);
Service svc = Service.create(svcQname);
svc.addPort(portQName, SOAPBinding.SOAP11HTTP_BINDING,
corbaloc::localhost:4/calc);
// Create the dynamic invocation object from this service.
DispatchSource dispatch = svc.createDispatch(
portQName,
Source.class,
Service.Mode.PAYLOAD);
String content =
tns:add
xmlns:tns=\http://schemas.apache.org/yoko/idl/calc\; +
x2/x y4/y +
/tns:add;
ByteArrayInputStream bais = new
ByteArrayInputStream(content.getBytes());
Source input = new StreamSource(bais);
// Invoke the operation.
Source response = dispatch.invoke(input);
// Process the response.
StreamResult result = new StreamResult(new
ByteArrayOutputStream());
Transformer trans =
TransformerFactory.newInstance().newTransformer();
trans.transform(response, result);
ByteArrayOutputStream baos = (ByteArrayOutputStream)
result.getOutputStream();
// Write out the response content.
String responseContent = new String(baos.toByteArray());
System.out.println(responseContent);
I am getting an exception:
2.8.2007 15:11:31 org.apache.cxf.jaxws.DispatchImpl invoke
INFO: Dispatch: invoke called
2.8.2007 15:11:31 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now
java.lang.NullPointerException
at
org.apache.yoko.bindings.corba.TypeMapCache.get(TypeMapCache.java:38)
at
org.apache.yoko.bindings.corba.CorbaConduit.init(CorbaConduit.java:86)
at
org.apache.yoko.bindings.corba.CorbaBindingFactory.getConduit(CorbaBindingFactory.java:109)
at
org.apache.yoko.bindings.corba.CorbaBindingFactory.getConduit(CorbaBindingFactory.java:104)
at
org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:73)
at
org.apache.cxf.endpoint.UpfrontConduitSelector.selectConduit(UpfrontConduitSelector.java:71)
at
org.apache.cxf.message.ExchangeImpl.getConduit(ExchangeImpl.java:50)
at
org.apache.cxf.interceptor.MessageSenderInterceptor.getConduit(MessageSenderInterceptor.java:71)
at
org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:46)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:206)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:163)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:112)
at com.pikeelectronic.calc.WSDIIClient.main(WSDIIClient.java:51)
java.lang.ClassCastException: java.lang.NullPointerException cannot be
cast to org.apache.cxf.interceptor.Fault
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:171)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:112)
at com.pikeelectronic.calc.WSDIIClient.main(WSDIIClient.java:51)
How sould I pass the
Re: Exception not showing up in WSDL with Aegis binding
If you're using the JAX-WS frontend, then you do need to use the @WebFault annotation per the JAX-WS spec. With the simple frontend there were some bugs in 2.0, but I believe this is fixed in 2.0.1 which will be released in the next few days (fingers crossed - we're voting on it right now). In the mean time you can try a SNAPSHOT build if you want. Cheers, - Dan On 8/3/07, Zarar Siddiqi [EMAIL PROTECTED] wrote: The solution was to specify a name attribute for the @WebFault annotation. Once I specified @WebFault(name=WSException), it appeared in the WSDL. Wouldn't it be better if it defaulted to the class name? It would me more inline with how XFire rendered the WSDL. Zarar Zarar Siddiqi wrote: I'm using the Aegis binding and all is well except that the Exception (Fault) is not showing up in the WSDL. Here's my Spring config. bean id=aegisBean class=org.apache.cxf.aegis.databinding.AegisDatabinding/ bean id=aegisServiceFactoryBean class=org.apache.cxf.aegis.databinding.AegisServiceFactoryBean/ bean class=org.apache.cxf.frontend.ServerFactoryBean init-method=create property name=serviceBean ref=personSoapService/ property name=address value=/PersonService/ property name=dataBinding ref=aegisBean/ property name=serviceFactory ref=aegisServiceFactoryBean/ /bean My interface and implementation classes have methods called: public Email getEmail() throws WSException; public Address getAddress() throws WSException; The Email and and Address objects get translated to complexType name=Email and complexType name=Address but the WSException never shows up in the WSDL. I'm migrating from XFire and this was never a problem there. There's a xsd:complexType name=WSException missing from the WSDL that is generated through CXF which was present in XFire. I tried annotating WSException with the @WebFault annotation but that didn't help. Is this is a bug or am I missing something? Any help is appreciated. Thanks, Zarar -- View this message in context: http://www.nabble.com/Exception-not-showing-up-in-WSDL-with-Aegis-binding-tf4208423.html#a11977298 Sent from the cxf-user mailing list archive at Nabble.com. -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: WHICH_JARS not actual
Any updates on WHICH_JARS for 2.0.1? Gustavo On 7/17/07, Dan Diephouse [EMAIL PROTECTED] wrote: Hi Deno, That is correct - you can just use the single spring jar. - Dan On 7/16/07, Deno Vichas [EMAIL PROTECTED] wrote: (somebody correctly me if I'm wrong here) you can just all the main spring jar and not all the smaller individuals ones. Sure, your project will be slightly bigger but less jars I have to keep track of the better. -Original Message- From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 7:30 AM To: cxf-user@incubator.apache.org Subject: RE: WHICH_JARS not actual Yes ,we should update the WHICH_JARS to refelect the recent changes. For the second issue, current CXF servlet only support SpringBusFactory which relates on Spring. So you have to include the Spring jars for wiring the CXF components with the Bus. Willem. -Original Message- From: Lukas Zapletal [mailto:[EMAIL PROTECTED] Sent: Mon 7/16/2007 21:54 To: cxf-user@incubator.apache.org Subject: WHICH_JARS not actual Hello all, it seems WHICH_JARS file is not actual. CXF itself needs xml-resolver.jar and I am sure there will be other JARs that should be included in the minimal CXF install. The second issue about the libraries is that CXF depends on Spring even when I do not use it. I have created just a Servlet in the web.xml but when my container tried to load the application I get an exception. As a temporary solution I am adding all JARs to my servlet. Could you check the WHICH_JARS file please? 15:37:03,713 ERROR [[CXFServlet]] Allocate exception for servlet CXFServlet java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav a:1104) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:8 06) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs sociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j ava:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn ectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2 41) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:84 4) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) 15:37:23,331 INFO [[CXFServlet]] Servlet CXFServlet is currently unavailable -- Lukas Zapletal http://lukas.zapletalovi.com -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: REST url quirk...
Hmm... looks like there may be a similar issue still around. I've upgraded
to the latest jra jar and I'm already using the latest snapshot.
/rest/mediaTypes/{any id} still invokes and returns /rest/mediaTypes.
On 8/3/07, Dan Diephouse [EMAIL PROTECTED] wrote:
Hi Brad,
This was a bug in the JRA jar. You can try updating to the alpha-4
snapshot
and it should fix things:
http://repo1.maven.org/maven2/org/codehaus/jra/jra/1.0-alpha-4/jra-1.0-alpha-4.jar
(If that doesn't work try the 2.0.1/SNAPSHOT builds from CXF as well, but
I'm pretty sure CXF didn't require any changes for the problem)
- Dan
On 8/2/07, Brad Harper [EMAIL PROTECTED] wrote:
I have several identically configured REST services working with one
exception. When the method I call is getMediaType(s) - (
/rest/mediaTypes
/rest/mediaType/{1} ), the get mediaTypes services returns the correct
data. However, when I try to access a specific type by id
/rest/mediaTypes/1, I still get the entire list back. Basically CXF is
not
interpreting the '/1' appended to the url. Renaming the exact methods
and
corresponding annotations to getXMediaTypes resolves the issue. Could
this
be a naming collision with something in the HTTP headers?
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
RE: WHICH_JARS not actual
Um, can't someone automate pulling the classpath out of the manifest jar? Or, on the other hand, keep the facts about all the dependencies in some XML file which is XSLT's to make either the manifest or the human-readable content? -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Friday, August 03, 2007 9:37 AM To: cxf-user@incubator.apache.org Cc: Gustavo Morozowski Subject: Re: WHICH_JARS not actual On Friday 03 August 2007 05:30, Gustavo Morozowski wrote: Any updates on WHICH_JARS for 2.0.1? Unforuntately, not nearly changed enough. I did add mention of the asm jar which was added. But that's probably about the only change. :-( Dan Gustavo On 7/17/07, Dan Diephouse [EMAIL PROTECTED] wrote: Hi Deno, That is correct - you can just use the single spring jar. - Dan On 7/16/07, Deno Vichas [EMAIL PROTECTED] wrote: (somebody correctly me if I'm wrong here) you can just all the main spring jar and not all the smaller individuals ones. Sure, your project will be slightly bigger but less jars I have to keep track of the better. -Original Message- From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 7:30 AM To: cxf-user@incubator.apache.org Subject: RE: WHICH_JARS not actual Yes ,we should update the WHICH_JARS to refelect the recent changes. For the second issue, current CXF servlet only support SpringBusFactory which relates on Spring. So you have to include the Spring jars for wiring the CXF components with the Bus. Willem. -Original Message- From: Lukas Zapletal [mailto:[EMAIL PROTECTED] Sent: Mon 7/16/2007 21:54 To: cxf-user@incubator.apache.org Subject: WHICH_JARS not actual Hello all, it seems WHICH_JARS file is not actual. CXF itself needs xml-resolver.jar and I am sure there will be other JARs that should be included in the minimal CXF install. The second issue about the libraries is that CXF depends on Spring even when I do not use it. I have created just a Servlet in the web.xml but when my container tried to load the application I get an exception. As a temporary solution I am adding all JARs to my servlet. Could you check the WHICH_JARS file please? 15:37:03,713 ERROR [[CXFServlet]] Allocate exception for servlet CXFServlet java.lang.NoClassDefFoundError: org/springframework/beans/factory/support/BeanDefinitionRegistry at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapp er.jav a:1104) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper. java:8 06) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapp erValv e.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardConte xtValv e.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Secu rityAs sociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextV alve.j ava:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValv e.java :128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValv e.java :104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(Cach edConn ectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngine Valve. java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter. java:2 41) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.j ava:84 4) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.pr ocess( Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java :447) at java.lang.Thread.run(Unknown Source) 15:37:23,331 INFO [[CXFServlet]] Servlet CXFServlet is currently unavailable -- Lukas Zapletal http://lukas.zapletalovi.com -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
EditGrid CXF
Hiya
Has somebody tried to use EditGrid webservice with cxf ? I am using the
dynamic client factory and get the following fault.
Is there something bad trying this ?
Cheers
Tog
Found JAXB 2.1
3 août 2007 22:30:24
org.apache.cxf.endpoint.dynamic.DynamicClientFactoryaddSchemas
INFO: Loading the JAXB 2.1 simple binding for client.
java.lang.RuntimeException: Error compiling schema from WSDL at {
http://labs.editgrid.com/sandbox/static/EditGrid.wsdl}: undefined simple or
complex type 'soapenc:Array'
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory$InnerErrorListener.error
(DynamicClientFactory.java:409)
at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.error(
SchemaCompilerImpl.java:264)
at com.sun.tools.xjc.util.ErrorReceiverFilter.error(
ErrorReceiverFilter.java:61)
at com.sun.xml.xsom.impl.parser.ParserContext$2.error(
ParserContext.java:156)
at com.sun.xml.xsom.impl.parser.ParserContext$1.reportError(
ParserContext.java:134)
at com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.reportError(
NGCCRuntimeEx.java:131)
at com.sun.xml.xsom.impl.parser.DelayedRef.resolve(DelayedRef.java
:90)
at com.sun.xml.xsom.impl.parser.DelayedRef.run(DelayedRef.java:65)
at com.sun.xml.xsom.impl.parser.ParserContext.getResult(
ParserContext.java:94)
at com.sun.xml.xsom.parser.XSOMParser.getResult(XSOMParser.java:190)
at com.sun.tools.xjc.ModelLoader.createXSOM(ModelLoader.java:500)
at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(
SchemaCompilerImpl.java:216)
at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(
SchemaCompilerImpl.java:69)
at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient
(DynamicClientFactory.java:166)
at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient
(DynamicClientFactory.java:137)
Getting jaxws:server syntax working for spring transaction proxying
I know dan did a post on this but I still haven't been able to get this working, the syntax he specified in his post didnt match the schema, when I looked in the schema it looked like you were supposed to put the implementing bean in the servicebean class but it doesnt seem to work. It doesnt throw any errors until you actually access the service though then you get a cant find observer error for the url. (Ive tried both with and without the pound sign in front of transDataService as well) Did anybody get the other solution working to fix the spring transactional web service problem? jaxws:server id=testService address=/testService serviceClass=com.visualio.dataserver.webservices.DataServiceImpl serviceBean=transDataService /jaxws:server bean id=transDataService class=org.springframework.transaction.interceptor.TransactionProxyFactoryBean property name=targetref local=dataServiceImpl//property property name=transactionManagerref local=transactionManager//property property name=transactionAttributes props !-- Avoid PROPAGATION_REQUIRED !! It could kill your performances by generating a new transaction on each request !! -- prop key=get*PROPAGATION_SUPPORTS,readOnly/prop prop key=find*PROPAGATION_REQUIRED,readOnly/prop prop key=load*PROPAGATION_REQUIRED,readOnly/prop prop key=save*PROPAGATION_REQUIRED/prop prop key=Save*PROPAGATION_REQUIRED/prop /props /property /bean bean id=dataServiceImpl class=com.visualio.dataserver.webservices.DataServiceImpl property name=snapshotDAO ref bean=snapshotDAO/ /property /bean Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/
