spring dependency version
Hi all, It appears that CXF 2.0.1 incubator uses spring 2.0.4 by default. Does CXF work with a lower version of spring like 2.0.1? Thanks, jacob
How to publish a JaxWS service?
Hi, I am trying to create a very simple service using the documented Java First approach. The end point is configured based on this example. Does this publish my service? When I startup my server, I see a message saying my service is created from the implementor class. But I can't seem to get to it's wsdl. Do I have to create the wsdl separately? Thanks, Jacob
Re: DefaultTypaMappingRegistry issue [was: Aegis binding and property/fiels removal]
Benson,
I have seen a couple of issues related to Aegis binding.
1) If the simple front end POJO has java.lang.Object in it's signature,
binding fails if you send subclasses of Object in the soap message. This is
fairly easy to reproduce and seems to be related the name space handling in
the ObjectType class. I have solved it temporarily by extending the
ObjectType.
2) I have logged a Jira issue. (My first issue, so please forgive me if have
not filled all the fields correctly).
http://issues.apache.org/jira/browse/CXF-992
I hope these are on some one's radar.
Thanks,
Jacob
On 9/12/07, Benson Margulies <[EMAIL PROTECTED]> wrote:
>
> I have some ideas in this area, but we need to finish some of what's
> currently outstanding. We could enhance the options class.
>
> > -Original Message-
> > From: tog [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, September 11, 2007 10:21 AM
> > To: cxf-user@incubator.apache.org
> > Subject: DefaultTypaMappingRegistry issue [was: Aegis binding and
> > property/fiels removal]
> >
> > Hi Dan,
> >
> > Sorry not to follow up quickly. Actually, the
> DefaultTypaMappingRegistry
> > is
> > final and cannot be extended as you suggest.
> >
> > Some more insights on what I want to achieve. Today, in GroovyWS, the
> > users
> > have to write a .aegis.xml file for each bean they will write in
> Groovy.
> > This file is always the same containing the line:
> >
> >
> >
> > I would like to modify the behavior of the BeanType inside the Aegis
> > Binding
> > so that if such a field is present it can be ignored.
> >
> > Is there some documentation on how to modify the
> > DefaultTypeMappingRegisty ?
> >
> > Cheers
> > Guillaume
> >
> >
> > >
> > > Step 4: Write your own type registry to return your own TypeCreator
> > >
> > > public class MyTypeMappingRegistry extends
> DefaultTypeMappingRegistry {
> > >
> > > protected AbstractTypeCreator createDefaultTypeCreator() {
> > > AbstractTypeCreator creator = new MyTypeCreator();
> > > creator.setConfiguration(getConfiguration());
> > > return creator;
> > > }
> > > }
> > >
> > > Step 5: use it:
> > >
> > > ServerFactoryBean sfb = new ServerFactoryBean();
> > >
> > > AegisDatabinding db = new AegisDataBinding();
> > > db.setTypeMappingRegistry(new MyTypeMappingRegistry());
> > > sfb.setDatabinding(db);
> > > ...
> > >
> > > Hope that works for you!
> > >
> > > - Dan
> > >
> > > On 8/27/07, tog < [EMAIL PROTECTED]> wrote:
> > > >
> > > > Hiya
> > > >
> > > > I have some automatically generated classes that I use to generate
> a
> > > > server
> > > > using Aegis. This is done programmaticaly. I am using an
> > > > AegisServiceConfiguration class to avoid publishing methods that I
> > want
> > > to
> > > > remove. I would like similarly to remove some fields/properties
> from
> > the
> > > > serialization process.
> > > > How is that possible (programmaticaly) ?
> > > >
> > > > Thanks for your help.
> > > >
> > > > Guillaume
> > > >
> > >
> >
> >
> >
> > --
> >
> > Best Regards
> > Guillaume
> > http://cheztog.blogspot.com
> >
> > --
> >
> > Best Regards
> > Guillaume
> > http://cheztog.blogspot.com
>
Re: What are the min Maven2 dependencies?
Vincezo, You will find the information here. http://cwiki.apache.org/CXF20DOC/maven-integration-and-plugin.html. If you are using Aegis databinding, you will need to add that dependency. jacob On 9/11/07, Vincenzo Vitale <[EMAIL PROTECTED]> wrote: > > Hello all, > > I'm trying to expose a simple Spring service with CXF. > > I use Maven2 and the maven Jetty plug in to start the application during > development. > > What are the minimal dependencies I must add to my pom file? > > > > Thanks, > Vincenzo. >
Possible bug in Aegis data binding
Hi,
Let us say our operation has the Signature, doSomthing(String s1, String s2,
String s3);
Now if s2 is null, then onwards all the rest of the parameters are also not
populated. They all remain null.
The issue seems to be in XMLStreamDataReader.
if (elReader.isXsiNil()) {
elReader.readToEnd();
return null;
}
I believe that the readToEnd() here is the issue. Now this could be also
because, there is something I have not understood completely. Any
information would be very useful.
Thansk,
Jacob
Aegis data binding error
Hi all,
I am testing a simple service method that takes a java Object as parameter
using Aegis.
public String push(Object obj);
This uses the simple front end. As expected the generated wsdl has the xsd
anytype. But when I use a client created via the ClientproxyFactoryBean, I
get an error as follows.
java.lang.RuntimeException: org.apache.cxf.aegis.DatabindingException :
Could not determine how to read type:
{http://hello.com/}string
at org.apache.cxf.aegis.databinding.XMLStreamDataReader.read (
XMLStreamDataReader.java:83)
at org.apache.cxf.aegis.databinding.XMLStreamDataReader.read(
XMLStreamDataReader.java:42)
at org.apache.cxf.interceptor.DocLiteralInInterceptor.getPara(
DocLiteralInInterceptor.java :235)
at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(
DocLiteralInInterceptor.java:121)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
PhaseInterceptorChain.java:207)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
ChainInitiationObserver.java:73)
at org.apache.cxf.transport.servlet.ServletDestination.doMessage(
ServletDestination.java:78)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(
ServletController.java:231)
at org.apache.cxf.transport.servlet.ServletController.invoke(
ServletController.java:139)
at org.apache.cxf.transport.servlet.CXFServlet.invoke (
CXFServlet.java:271)
at org.apache.cxf.transport.servlet.CXFServlet.doPost(
CXFServlet.java:249)
Re: Simple front end and JAB customization
James, I am using the code first (Simple front end) approach. In this case how would I do the jaxb customization? Is it via annotations or is there a way to do this in the cxf.xml file? Between, I looked at the documentation in detail and they seem to be related to wsdltojava tool. Thanks in advance, Jacob On 8/30/07, James Mao <[EMAIL PROTECTED] > wrote: > > Yes, through jaxb customization > > http://cwiki.apache.org/confluence/display/CXF20DOC/Tools > > > James > > > Jacob Marcus wrote: > > Hi, > > > > Is there any way to customize JAXB type mapping when using the simple > front > > end? I would like to have the java.util.Date for the xsd:dateTime. > > > > Thanks, > > Jacob > > > > >
Simple front end and JAB customization
Hi, Is there any way to customize JAXB type mapping when using the simple front end? I would like to have the java.util.Date for the xsd:dateTime. Thanks, Jacob
Re: Simple front-end and xs:anyType
Hi, How do you customize the JAXB when using the simple front end.? The article talks about how to do it with the wsdl2ava tool, if I am not mistaken. Has some one tried this with the simple front end? Thanks, Jacob On 8/27/07, James Mao <[EMAIL PROTECTED]> wrote: > > You can customize the jaxb to use the java.util.Calendar or > java.util.Date in case of jaxb databinding. > Here's the documentation: > > http://cwiki.apache.org/confluence/display/CXF20DOC/WSDL+to+Java > (grep: *Q: How to map xsd:dateTime to java.util.Date?*) > > Cheers, > James > > > Thanks Dan! I have got it work. > > > > I notice one interesting thing though. If I send a Date from the client, > it > > is getting converted to an > > XMLGregorianCalendarImpl at the server side. I see that there is an > existing > > JIRA issue open on this. > > (https://issues.apache.org/jira/browse/CXF-369) > > > > I changed the data binding to use Aegis data binding and now see > > java.util.GregorianCalendar. > > > > Is there a way I can customize this to get java.util.Date at the server? > The > > Jira issue says you can customise jaxb binding using an xml snippet. It > is > > not clear, where this xml snippet will fits in. > > > > Thanks, > > J > > > > > > > > > > > > > > > > > > On 8/27/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > > >> Hi Jacob, > >> > >> You may have to turn on xsi:type writing for aegis. If you're using the > >> API, > >> it'll probably look something like this: > >> > >> ServerFactoryBean sf ... > >> Map props = new HashMap(); > >> props.put(AegisDatabinding.WRITE_XSI_TYPE_KEY, "true"); > >> sf.setProperties(props); > >> > >> Or in XML form: > >> > >> > >> > >> true > >> > >> > >> > >> Hope that helps some. Cheers, > >> - Dan > >> > >> > >> > >> On 8/27/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > >> > >>> Hi, > >>> > >>> Is there a way to support xs:anyType using the Simple frond end? I > tried > >>> > >> a > >> > >>> method like > >>> String push(Object obj) in my interface. The wsdl is successfully > >>> generated. > >>> However, when I try to call the method from my client, I get the > >>> > >> following > >> > >>> error. Any pointers would be great. > >>> > >>> org.apache.cxf.interceptor.Fault: object is not an instance of > declaring > >>> class > >>> at org.apache.cxf.service.invoker.AbstractInvoker.invoke( > >>> AbstractInvoker.java:92) > >>> at org.apache.cxf.service.invoker.AbstractInvoker.invoke( > >>> AbstractInvoker.java:62) > >>> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run( > >>> ServiceInvokerInterceptor.java:56) > >>> at org.apache.cxf.workqueue.SynchronousExecutor.execute( > >>> SynchronousExecutor.java:37) > >>> at > >>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage( > >>> ServiceInvokerInterceptor.java:92) > >>> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept( > >>> PhaseInterceptorChain.java:207) > >>> at org.apache.cxf.transport.ChainInitiationObserver.onMessage( > >>> ChainInitiationObserver.java:73) > >>> at > org.apache.cxf.transport.servlet.ServletDestination.doMessage > >>> > >> ( > >> > >>> ServletDestination.java:78) > >>> at > >>> org.apache.cxf.transport.servlet.ServletController.invokeDestination( > >>> ServletController.java:231) > >>> > >>> > >>> Thanks, > >>> Jacob > >>> > >>> > >> > >> -- > >> Dan Diephouse > >> Envoi Solutions > >> http://envoisolutions.com | http://netzooid.com/blog > >> > >> > > > > >
Complex type names in wsdl starts with lowercase?
I am looking into the wsdl generated from my simple front end java interface and notice that the complex types are named starting with lowercase if I use JAXB binding. For example, If I use Aegis binding the issue is not there. Is this a known issue? Is there a way to get JAXB also give the ClassName style names? Sample complex type using Aegis is, Thanks, Jacob
Generated wsdl in XFire Versus CXF
Hi all, I notice that in CXF, the xsd elements for method names have a type attribute. This was not the case in XFire. Here is an example of what I am talking about. My question is, is there a way to get CXF to spit out wsdl exactly as XFire? Thanks, Jacob XFire == CXF
Re: Simple front-end and xs:anyType
Thanks Dan! I have got it work. I notice one interesting thing though. If I send a Date from the client, it is getting converted to an XMLGregorianCalendarImpl at the server side. I see that there is an existing JIRA issue open on this. (https://issues.apache.org/jira/browse/CXF-369) I changed the data binding to use Aegis data binding and now see java.util.GregorianCalendar. Is there a way I can customize this to get java.util.Date at the server? The Jira issue says you can customise jaxb binding using an xml snippet. It is not clear, where this xml snippet will fits in. Thanks, J On 8/27/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > Hi Jacob, > > You may have to turn on xsi:type writing for aegis. If you're using the > API, > it'll probably look something like this: > > ServerFactoryBean sf ... > Map props = new HashMap(); > props.put(AegisDatabinding.WRITE_XSI_TYPE_KEY, "true"); > sf.setProperties(props); > > Or in XML form: > > > > true > > > > Hope that helps some. Cheers, > - Dan > > > > On 8/27/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > Is there a way to support xs:anyType using the Simple frond end? I tried > a > > method like > > String push(Object obj) in my interface. The wsdl is successfully > > generated. > > However, when I try to call the method from my client, I get the > following > > error. Any pointers would be great. > > > > org.apache.cxf.interceptor.Fault: object is not an instance of declaring > > class > > at org.apache.cxf.service.invoker.AbstractInvoker.invoke( > > AbstractInvoker.java:92) > > at org.apache.cxf.service.invoker.AbstractInvoker.invoke( > > AbstractInvoker.java:62) > > at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run( > > ServiceInvokerInterceptor.java:56) > > at org.apache.cxf.workqueue.SynchronousExecutor.execute( > > SynchronousExecutor.java:37) > > at > > org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage( > > ServiceInvokerInterceptor.java:92) > > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept( > > PhaseInterceptorChain.java:207) > > at org.apache.cxf.transport.ChainInitiationObserver.onMessage( > > ChainInitiationObserver.java:73) > > at org.apache.cxf.transport.servlet.ServletDestination.doMessage > ( > > ServletDestination.java:78) > > at > > org.apache.cxf.transport.servlet.ServletController.invokeDestination( > > ServletController.java:231) > > > > > > Thanks, > > Jacob > > > > > > -- > Dan Diephouse > Envoi Solutions > http://envoisolutions.com | http://netzooid.com/blog >
Simple front-end and xs:anyType
Hi, Is there a way to support xs:anyType using the Simple frond end? I tried a method like String push(Object obj) in my interface. The wsdl is successfully generated. However, when I try to call the method from my client, I get the following error. Any pointers would be great. org.apache.cxf.interceptor.Fault: object is not an instance of declaring class at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:92) at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:62) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run( ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute( SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage( ServiceInvokerInterceptor.java:92) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept( PhaseInterceptorChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage( ChainInitiationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage( ServletDestination.java:78) at org.apache.cxf.transport.servlet.ServletController.invokeDestination( ServletController.java:231) Thanks, Jacob
Re: Logging the received generated SOAP Messages
Hi, I have a related question. Suppose, you have a lot of end points and you want to perform a common logging/auditing across all of them. Is there a way you can intercept at a higher level than for each service? Something like at the ServletDestination level? This would be useful and a bit more easier than having to set up interceptors for each end point? Thanks, Jacob On 8/24/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > > Hi Holger, > > Actually we have LoggingInInterceptor and LoggingOutInterceptor for that > purpose. > You can add it two your endpoint on server side > EndpointImpl e = (EndpointImpl)Endpoint.publish(address, implementor); > e.getServer().getEndpoint().getInInterceptors().add(new > LoggingInInterceptor()); > e.getServer().getEndpoint().getOutInterceptors().add(new > LoggingOutInterceptor()); > > For client side, you can do it like > HelloPortType port = helloService.getHelloPort(); > Client client = ClientProxy.getClient(port); > client.getInInterceptors().add(new LoggingInInterceptor()); >client.getInOutterceptors().add(new LoggingOutInterceptor()); > > Also you can configure log features in spring file, you can refer to > > https://svn.apache.org/repos/asf/incubator/cxf/trunk/distribution/src/main/release/samples/wsdl_first/wsdl/cxf-servlet.xml > > Best Regards > > Freeman > > Holger Stolzenberg wrote: > > What is the easiest way to log the received and generated SOAP messages. > Currently I have an incoming/outgoing interceptor with phases receive/send > that simply log some properties of the SoapMessage interceptor method param. > What I want to log is the raw message data ( ... > ). > > > > Mit lieben Grüßen aus dem eWerk > > > > | Holger Stolzenberg > > | Softwareentwickler > > | > > | Geschäftsführer: > > | Frank Richter, Erik Wende, Hendrik Schubert > > | > > | eWerk IT GmbH > > | Markt 16 > > | Leipzig 04109 > > | http://www.ewerk.com > > | HRB 9065, AG Leipzig > > | Hauptniederlassung Leipzig > > | > > | fon +49.341.4 26 49-0 > > | fax +49.341.4 26 49-88 > > | mailto:[EMAIL PROTECTED] > > | > > | Support: > > | fon 0700 CALLME24 (0700 22556324) > > | fax 0700 CALLME24 (0700 22556324) > > | > > | Auskünfte und Angebote per Mail > > | sind freibleibend und unverbindlich. > > > > >
Re: Issue in a simple Client using ClientProxyFactoryBean
Thanks, that took care of it ! On 8/23/07, Willem Jiang <[EMAIL PROTECTED]> wrote: > > Hi > > The exception that you showed will be thrown when the transport > factories are not initiated properly. > > When you create the client which use the http transport, you need to > make sure the CXF core can load the cxf-rt-transports-http-jetty module. > If you are using spring to set up the ClientProxyFactoryBean you need to > include below line in the spring xml file > > > > If you are writing java code to create the client from > ClientProxyFactoryBean and not using the CXF bundler jar, you need to > make sure the cxf-rt-transports-http-jetty-*.jar is in your class path. > > Willem. > > Jacob Marcus wrote: > > Hi all, > > > > I have the webservice up and running on the server (deployed in a war > file). > > Trying to create a stand alone java client using the > ClientProxyFactoryBean > > keeps giving the following error. > > > > Any pointers would be great! > > > > Thanks, > > Jacob > > > > Exception in thread "main" java.lang.RuntimeException: Could not find > > conduit initiator for transport http://schemas.xmlsoap.org/soap/http > > at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit( > > SoapTransportFactory.java:148) > > at > org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit( > > AbstractConduitSelector.java:73) > > at org.apache.cxf.endpoint.UpfrontConduitSelector.prepare( > > UpfrontConduitSelector.java:61) > > at org.apache.cxf.endpoint.ClientImpl.prepareConduitSelector( > > ClientImpl.java:417) > > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:251) > > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:205) > > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java > :73) > > at org.apache.cxf.frontend.ClientProxy.invoke(ClientProxy.java:68) > > at $Proxy18.search(Unknown Source) > > > > >
Issue in a simple Client using ClientProxyFactoryBean
Hi all, I have the webservice up and running on the server (deployed in a war file). Trying to create a stand alone java client using the ClientProxyFactoryBean keeps giving the following error. Any pointers would be great! Thanks, Jacob Exception in thread "main" java.lang.RuntimeException: Could not find conduit initiator for transport http://schemas.xmlsoap.org/soap/http at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit( SoapTransportFactory.java:148) at org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit( AbstractConduitSelector.java:73) at org.apache.cxf.endpoint.UpfrontConduitSelector.prepare( UpfrontConduitSelector.java:61) at org.apache.cxf.endpoint.ClientImpl.prepareConduitSelector( ClientImpl.java:417) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:251) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:205) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.frontend.ClientProxy.invoke(ClientProxy.java:68) at $Proxy18.search(Unknown Source)
Maven build issue, (missing jaxb-impl:jar:2.0.5)
Hi all, Has anyone seen this problem before? Missing: -- 1) com.sun.xml.bind:jaxb-impl:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind-DartifactId=jaxb-impl -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) com.ironmountain.digital.erm.irmrap.cl:soap:jar:1.0-SNAPSHOT 2) org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.0.1-incubator 3) org.apache.cxf:cxf-rt-core:jar:2.0.1-incubator 4) com.sun.xml.bind:jaxb-impl:jar:2.0.5 I am using the following dependencies. org.apache.cxf cxf-rt-frontend-jaxws 2.0-incubator org.apache.cxf cxf-rt-transports-http 2.0-incubator Thanks, Jacob
Re: Using CXF
Cool. Everything works now. Including the serviceBean="#somebean". Thanks again, Jacob On 7/18/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: I think that section of the migration guide assumes that you've already imported the cxf bean definitions into your application. The cxf-* resources include some basic CXF bean definitions which are necessary to use CXF inside your spring application - like a definition for the Servlet transport or the Binding manager. So yes, you need to import these if you're going to use , , etc. Regards, - Dan On 7/18/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > If my services are defined in the cxf.xml, do I still need to import the > cxf > bean definitions.? I followed the instructions on this wiki page. > > > http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html#XFireMigrationGuide-services.xml > > Or are you saying that if I want to use a bean defined else where in my > cxf.xml, then I should import these ? > > Thanks, > Jacob > > > > On 7/18/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > > > Hi Jacob, > > You need to import the CXF bean definitions: > > > > > > > /> > > > > > > You can find for more details here: > > http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html > > > > Cheers, > > - Dan > > > > On 7/17/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > > > > > I am not importing the cxf bean definitions in my spring > configuration. > > > > > > Here is my cxf.xml file. > > > > > > > > > http://www.springframework.org/schema/beans"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > > xmlns:simple="http://cxf.apache.org/simple"; > > > xsi:schemaLocation=" > > > http://www.springframework.org/schema/beans > > > http://www.springframework.org/schema/beans/spring-beans.xsd > > > http://cxf.apache.org/simple > > > http://cxf.apache.org/schemas/simple.xsd";> > > > > > > > > serviceBean="#helloService" serviceClass=" > > > com.ironmountain.digital.erm.irmrap.cl.soap.util.Hello"> > > > > > > > > > > > > > > > The relevant portions of my web.xml is below. > > > > > > > > > > > > contextConfigLocation > > > > > > classpath:configuration-sprcfg.xml, > > > classpath:version-configuration-sprcfg.xml, > > > classpath:jmx-sprcfg.xml, > > > classpath:storage-common-sprcfg.xml, > > > classpath:services-authorization-sprcfg.xml, > > > classpath:services-sprcfg.xml, > > > classpath:cl-http-security-sprcfg.xml, > > > classpath:soap-sprcfg.xml > > > > > > > > > > > > > > > CXFServlet > > > CXF Servlet > > > > > > org.apache.cxf.transport.servlet.CXFServlet > > > > > > 3 > > > > > > > > > > > > CXFServlet > > > /cxfservices/* > > > > > > > > > > > > > > > org.springframework.web.context.ContextLoaderListener > > > > > > > > > > > > > > > On 7/17/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > > > > > > > Can you show me what your web.xml and whole cxf.xml look like? How > are > > > you > > > > importing the CXF bean definitions? > > > > > > > > Thanks, > > > > - Dan > > > > > > > > On 7/16/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Thanks Dan. That worked. > > > > > > > > > > from the cxf.xml I would like to refer to a bean defined else > where > > > > like, > > > > > > > > > > http://localhost:8081/tes/cxfservices/HelloWorld"; > > > > > serviceClass="com.test.HelloWorld"> > > > > > #helloService > > > > > > > > > > > > > > > This is giving me an error saying the bean with id helloService > > cannot > > > > be > > > > > found. It appears that the SpringBusFac
Re: Using CXF
If my services are defined in the cxf.xml, do I still need to import the cxf bean definitions.? I followed the instructions on this wiki page. http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html#XFireMigrationGuide-services.xml Or are you saying that if I want to use a bean defined else where in my cxf.xml, then I should import these ? Thanks, Jacob On 7/18/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: Hi Jacob, You need to import the CXF bean definitions: You can find for more details here: http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html Cheers, - Dan On 7/17/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > I am not importing the cxf bean definitions in my spring configuration. > > Here is my cxf.xml file. > > > http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:simple="http://cxf.apache.org/simple"; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://cxf.apache.org/simple > http://cxf.apache.org/schemas/simple.xsd";> > > serviceBean="#helloService" serviceClass=" > com.ironmountain.digital.erm.irmrap.cl.soap.util.Hello"> > > > > > The relevant portions of my web.xml is below. > > > > contextConfigLocation > > classpath:configuration-sprcfg.xml, > classpath:version-configuration-sprcfg.xml, > classpath:jmx-sprcfg.xml, > classpath:storage-common-sprcfg.xml, > classpath:services-authorization-sprcfg.xml, > classpath:services-sprcfg.xml, > classpath:cl-http-security-sprcfg.xml, > classpath:soap-sprcfg.xml > > > > > CXFServlet > CXF Servlet > > org.apache.cxf.transport.servlet.CXFServlet > > 3 > > > > CXFServlet > /cxfservices/* > > > > > org.springframework.web.context.ContextLoaderListener > > > > > On 7/17/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > > > Can you show me what your web.xml and whole cxf.xml look like? How are > you > > importing the CXF bean definitions? > > > > Thanks, > > - Dan > > > > On 7/16/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > > > > > Thanks Dan. That worked. > > > > > > from the cxf.xml I would like to refer to a bean defined else where > > like, > > > > > > http://localhost:8081/tes/cxfservices/HelloWorld"; > > > serviceClass="com.test.HelloWorld"> > > > #helloService > > > > > > > > > This is giving me an error saying the bean with id helloService cannot > > be > > > found. It appears that the SpringBusFactory does not have the bean > > > definition. Is there a way I can instruct the server to use a specific > > > bus? > > > > > > My spring application context is defined in the web.xml and I use the > > > ContextLoaderListener. > > > My problem is that the cxf.xml does not seem to be able to refer to > > beans > > > in > > > my application context. > > > > > > Thanks in advance for your help, > > > Jacob > > > > > > On 7/14/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi Jacob, > > > > > > > > I would go with something like: > > > > > > > > > > > > org.apache.cxf > > > > cxf-rt-frontend-jaxws > > > > 2.0-incubator > > > > > > > > > > > > org.apache.cxf > > > > cxf-rt-transports-http > > > > 2.0-incubator > > > > > > > > > > > > > > > > org.apache.cxf > > > > > cxf-rt-transports-http-jetty > > > > 2.0-incubator > > > > > > > > > > > > > > > > That will set you up to use the JAX-WS style annotated web services > > with > > > > JAXB. Spring is included by default. > > > > > > > > Let us know if you have more questions. I'll try to add this to the > > > xfire > > > > user's guide
Re: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)
Hi Willem/Dan, Is this last change around the serviceBean? Because, I had tried it earlier and it was not working. There is one more issue in using the cxf.xml in this fashion. If I do not refer to a bean using the # and instead give the class directly, it still does not work. For example, the following still does not work. The exception says "Could not find destination factory for transport http://schemas.xmlsoap.org/soap/http";. This error happens only if you do not have the dependency cxf-rt-transports-http-jetty. The behavior is different if you have this dependency. The only way I have been able to get the service fully functional without cxf-rt-transports-http-jetty is by embedding cxf in my spring config after importing the necessary configs. Hope the information helps. I would love to see the cxf.xml approach supported. The services.xml in XFire was a convenient way of keeping the stuff away from my other spring configs. Thanks, Jacob http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:simple="http://cxf.apache.org/simple"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/simple http://cxf.apache.org/schemas/simple.xsd";> On 7/18/07, Willem Jiang <[EMAIL PROTECTED]> wrote: Hi Dan, I did some clean up of the simple front-end spring parser, Can you review my last commit (svn commit: r557161)? Thanks, Willem. Dan Diephouse wrote: > With the simple frontend its called a serviceBean: > > serviceBean="#helloService" serviceClass="com.test.Hello"> > > > Cheers, > > - Dan > > On 7/17/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: >> >> Hi Willem, >> >> I believe I am using version CXF incubator 2.0. The simple.xsd does not >> support implementor as an attribute. It does support implementor as an >> element. But it needs child elements. >> >> Should I be using a different version (snapshot) of CXF? >> >> Thanks, >> Jacob >> >> On 7/17/07, Jiang, Ning (Willem) <[EMAIL PROTECTED]> wrote: >> > >> > >> > I think the spring syntext should be >> > > > implementor="#helloService" serviceClass="com.test.Hello"> >> > >> > >> > Because I checked the trunk code, it only deals with the attribute >> > implementor now. >> > >> > Willem. >> > >> > -Original Message- >> > From: Jacob Marcus [mailto:[EMAIL PROTECTED] >> > Sent: Tue 7/17/2007 22:55 >> > To: cxf-user@incubator.apache.org >> > Subject: Re: How can cxf.xml refer to beans defined in the application >> > context? (Xfire to CXF migration) >> > >> > I am using the Simple front end approach without annotations. >> > >> > > > serviceBean="#helloService" serviceClass="com.test.Hello"> >> > >> > >> > I think the problem is in the SpringBus. The CXFServlet does not >> seem to >> > have access to the ApplicationContext I have loaded using the >> > ContextLoaderLister in the web.xml >> > >> > Is there some additional configuration required? >> > >> > Thanks, >> > Jacob >> > >> > On 7/17/07, Jiang, Ning (Willem) <[EMAIL PROTECTED]> wrote: >> > > >> > > I think you could try to use the endpoint's attribute implementor. >> > > It should be workable with the # convention. >> > > Here is an example for it >> > > > > > implementor="#HelloService" >> > > address="/services/Greeter1"/> >> > > >> > > Willem >> > > >> > > >> > > -Original Message- >> > > From: Jacob Marcus [mailto:[EMAIL PROTECTED] >> > > Sent: Tue 7/17/2007 21:59 >> > > To: cxf-user@incubator.apache.org >> > > Subject: How can cxf.xml refer to beans defined in the application >> > > context? (Xfire to CXF migration) >> > > >> > > Hi all, >> > > >> > > I am an xfire user who is used to the xfire services.xml. I am now >> > porting >> > > the services.xml to cxf.xml and have it working for a simple 'Hello >> > World' >> > > case. >> > > >> > > I have a requirement to refer to beans defined else where in the >> cxf.xml >> > . >> > > XFire used to let me do this using the # convention. >> > > >> > > Example : #ihelloService. >> > > >> > > I tried a similar approach with cxf. However, it cannot find the >> bean. >> > > Has >> > > anybody tried this? Is this approach supported in cxf? >> > > >> > > Thanks, >> > > Jacob >> > > >> > > >> > > >> > >> > >> > > >
Re: Access to MessageContext in the implementations. (XFire to CXF question)
Neat! You guys rock!
On 7/17/07, Dan Diephouse <[EMAIL PROTECTED]> wrote:
Additionally, in CXF you can access the Exchange object (which is the
XFire
MessageContext equivalent) by adding it to your web service's parameter:
public String echo(String s, Exchange e) { ... }
Cheers,
- Dan
On 7/17/07, Christopher Moesel <[EMAIL PROTECTED]> wrote:
>
> Hi Jacob,
>
> I'm not sure how to do this without annotations. With annotations, you
> would do this the JAX-WS approved way, by adding this to your service
> implementation class:
>
> @Resource private WebServiceContext context;
>
> Then you could use the WebServiceContext object to get the message
> details. I'm not sure if there is a no-annotations way of doing it in
> CXF.
>
> -Chris
>
> -Original Message-
> From: Jacob Marcus [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 17, 2007 11:34 AM
> To: cxf-user@incubator.apache.org
> Subject: Access to MessageContext in the implementations. (XFire to CXF
> question)
>
> In XFire, there was a very convenient way to get a handle to the
> MessageContext in the web service implementations. This could be
> achieved by
> adding a MessageContext paramater to the method signature.
>
> Is there a similar strategy possible in CXF? Or is there a recomended
> approach? I am a potential Spring simple front-end user who does not
> want to
> use annotations.
>
> Thanks in advance,
> Jacob
>
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
Re: Using CXF
I am not importing the cxf bean definitions in my spring configuration. Here is my cxf.xml file. http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:simple="http://cxf.apache.org/simple"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/simple http://cxf.apache.org/schemas/simple.xsd";> The relevant portions of my web.xml is below. contextConfigLocation classpath:configuration-sprcfg.xml, classpath:version-configuration-sprcfg.xml, classpath:jmx-sprcfg.xml, classpath:storage-common-sprcfg.xml, classpath:services-authorization-sprcfg.xml, classpath:services-sprcfg.xml, classpath:cl-http-security-sprcfg.xml, classpath:soap-sprcfg.xml CXFServlet CXF Servlet org.apache.cxf.transport.servlet.CXFServlet 3 CXFServlet /cxfservices/* org.springframework.web.context.ContextLoaderListener On 7/17/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: Can you show me what your web.xml and whole cxf.xml look like? How are you importing the CXF bean definitions? Thanks, - Dan On 7/16/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > Thanks Dan. That worked. > > from the cxf.xml I would like to refer to a bean defined else where like, > > http://localhost:8081/tes/cxfservices/HelloWorld"; > serviceClass="com.test.HelloWorld"> > #helloService > > > This is giving me an error saying the bean with id helloService cannot be > found. It appears that the SpringBusFactory does not have the bean > definition. Is there a way I can instruct the server to use a specific > bus? > > My spring application context is defined in the web.xml and I use the > ContextLoaderListener. > My problem is that the cxf.xml does not seem to be able to refer to beans > in > my application context. > > Thanks in advance for your help, > Jacob > > On 7/14/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > > > Hi Jacob, > > > > I would go with something like: > > > > > > org.apache.cxf > > cxf-rt-frontend-jaxws > > 2.0-incubator > > > > > > org.apache.cxf > > cxf-rt-transports-http > > 2.0-incubator > > > > > > > > org.apache.cxf > > cxf-rt-transports-http-jetty > > 2.0-incubator > > > > > > > > That will set you up to use the JAX-WS style annotated web services with > > JAXB. Spring is included by default. > > > > Let us know if you have more questions. I'll try to add this to the > xfire > > user's guide. > > > > - Dan > > > > On 7/13/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > > > > > I am an XFire user planning to evaluate CXF for my project. What is > the > > > maven dependency for CXF to be used? While using XFire, I had the > > > following > > > dependencies. > > > > > > > > > org.codehaus.xfire > > > xfire-jaxb2 > > > 1.2.5 > > > > > > > > > org.codehaus.xfire > > > xfire-spring > > > 1.2.5 > > > > > > > > > org.springframework > > > spring > > > > > > > > > > > > > > > org.codehaus.xfire > > > xfire-java5 > > > 1.2.5 > > > > > > > > > Do we have something similar for CXF? I use spring. > > > > > > > > > > > -- > > Dan Diephouse > > Envoi Solutions > > http://envoisolutions.com | http://netzooid.com/blog > > > -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Access to MessageContext in the implementations. (XFire to CXF question)
In XFire, there was a very convenient way to get a handle to the MessageContext in the web service implementations. This could be achieved by adding a MessageContext paramater to the method signature. Is there a similar strategy possible in CXF? Or is there a recomended approach? I am a potential Spring simple front-end user who does not want to use annotations. Thanks in advance, Jacob
Re: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)
Hi Willem, I believe I am using version CXF incubator 2.0. The simple.xsd does not support implementor as an attribute. It does support implementor as an element. But it needs child elements. Should I be using a different version (snapshot) of CXF? Thanks, Jacob On 7/17/07, Jiang, Ning (Willem) <[EMAIL PROTECTED]> wrote: I think the spring syntext should be Because I checked the trunk code, it only deals with the attribute implementor now. Willem. -Original Message- From: Jacob Marcus [mailto:[EMAIL PROTECTED] Sent: Tue 7/17/2007 22:55 To: cxf-user@incubator.apache.org Subject: Re: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration) I am using the Simple front end approach without annotations. I think the problem is in the SpringBus. The CXFServlet does not seem to have access to the ApplicationContext I have loaded using the ContextLoaderLister in the web.xml Is there some additional configuration required? Thanks, Jacob On 7/17/07, Jiang, Ning (Willem) <[EMAIL PROTECTED]> wrote: > > I think you could try to use the endpoint's attribute implementor. > It should be workable with the # convention. > Here is an example for it >implementor="#HelloService" > address="/services/Greeter1"/> > > Willem > > > -Original Message- > From: Jacob Marcus [mailto:[EMAIL PROTECTED] > Sent: Tue 7/17/2007 21:59 > To: cxf-user@incubator.apache.org > Subject: How can cxf.xml refer to beans defined in the application > context? (Xfire to CXF migration) > > Hi all, > > I am an xfire user who is used to the xfire services.xml. I am now porting > the services.xml to cxf.xml and have it working for a simple 'Hello World' > case. > > I have a requirement to refer to beans defined else where in the cxf.xml . > XFire used to let me do this using the # convention. > > Example : #ihelloService. > > I tried a similar approach with cxf. However, it cannot find the bean. > Has > anybody tried this? Is this approach supported in cxf? > > Thanks, > Jacob > > >
Re: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)
I am using the Simple front end approach without annotations. I think the problem is in the SpringBus. The CXFServlet does not seem to have access to the ApplicationContext I have loaded using the ContextLoaderLister in the web.xml Is there some additional configuration required? Thanks, Jacob On 7/17/07, Jiang, Ning (Willem) <[EMAIL PROTECTED]> wrote: I think you could try to use the endpoint's attribute implementor. It should be workable with the # convention. Here is an example for it Willem -Original Message- From: Jacob Marcus [mailto:[EMAIL PROTECTED] Sent: Tue 7/17/2007 21:59 To: cxf-user@incubator.apache.org Subject: How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration) Hi all, I am an xfire user who is used to the xfire services.xml. I am now porting the services.xml to cxf.xml and have it working for a simple 'Hello World' case. I have a requirement to refer to beans defined else where in the cxf.xml. XFire used to let me do this using the # convention. Example : #ihelloService. I tried a similar approach with cxf. However, it cannot find the bean. Has anybody tried this? Is this approach supported in cxf? Thanks, Jacob
How can cxf.xml refer to beans defined in the application context? (Xfire to CXF migration)
Hi all, I am an xfire user who is used to the xfire services.xml. I am now porting the services.xml to cxf.xml and have it working for a simple 'Hello World' case. I have a requirement to refer to beans defined else where in the cxf.xml. XFire used to let me do this using the # convention. Example : #ihelloService. I tried a similar approach with cxf. However, it cannot find the bean. Has anybody tried this? Is this approach supported in cxf? Thanks, Jacob
Re: Issues with cxf.xml using spring and simple front end.
Thanks! that worked. When you are updating the wiki, you may want to check the sample xml file also. On 7/16/07, Willem Jiang <[EMAIL PROTECTED]> wrote: Here is a litter trick for the endpoint address setting with using servlet transport. I will update wiki for it. Because of CXFServlet can't get know the web server's listen port and the application deploied context path. When you want to use the Servlet transport , you just need to set the relate path such as /Hello. Then you can get the wsdl with this url http://localhost:8081/cxfservices/Hello?wsdl Cheers, Willem. Jacob Marcus wrote: > Hi all, > > I followed the documentation for converting an XFire services to an > equivalent cxf.xml with no luck. The sample cxf.xml given in the > documentation is broken. It is not a valid xml file. > ( http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html#XFireMigrationGuide-services.xml > > ) > > > My cxf.xml is given below. > > It seems to get deployed properly. I do get the service listed if I use a > URL like http://localhost:8081/cxfservices. However, if I try to > hit the wsdl using http://localhost:8081/cxfservices/Hello?wsdl , it > gives > me a message saying 'Service not found'. > > Do I need to specifiy something more in the cxf.xml? I am not using > annotations. > > Thanks, > Jacob > > > http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:simple=" http://cxf.apache.org/simple"; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://cxf.apache.org/simple > http://cxf.apache.org/schemas/simple.xsd "> > > address="http://localhost:8081/cxfservices/Hello"; > >serviceClass="com.test.Hello"> > > > > > > >
Issues with cxf.xml using spring and simple front end.
Hi all, I followed the documentation for converting an XFire services to an equivalent cxf.xml with no luck. The sample cxf.xml given in the documentation is broken. It is not a valid xml file. (http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html#XFireMigrationGuide-services.xml ) My cxf.xml is given below. It seems to get deployed properly. I do get the service listed if I use a URL like http://localhost:8081/cxfservices. However, if I try to hit the wsdl using http://localhost:8081/cxfservices/Hello?wsdl , it gives me a message saying 'Service not found'. Do I need to specifiy something more in the cxf.xml? I am not using annotations. Thanks, Jacob http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:simple=" http://cxf.apache.org/simple"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/simple http://cxf.apache.org/schemas/simple.xsd "> http://localhost:8081/cxfservices/Hello"; serviceClass="com.test.Hello">
Re: Using CXF
Thanks Dan. That worked. from the cxf.xml I would like to refer to a bean defined else where like, http://localhost:8081/tes/cxfservices/HelloWorld"; serviceClass="com.test.HelloWorld"> #helloService This is giving me an error saying the bean with id helloService cannot be found. It appears that the SpringBusFactory does not have the bean definition. Is there a way I can instruct the server to use a specific bus? My spring application context is defined in the web.xml and I use the ContextLoaderListener. My problem is that the cxf.xml does not seem to be able to refer to beans in my application context. Thanks in advance for your help, Jacob On 7/14/07, Dan Diephouse <[EMAIL PROTECTED]> wrote: Hi Jacob, I would go with something like: org.apache.cxf cxf-rt-frontend-jaxws 2.0-incubator org.apache.cxf cxf-rt-transports-http 2.0-incubator org.apache.cxf cxf-rt-transports-http-jetty 2.0-incubator That will set you up to use the JAX-WS style annotated web services with JAXB. Spring is included by default. Let us know if you have more questions. I'll try to add this to the xfire user's guide. - Dan On 7/13/07, Jacob Marcus <[EMAIL PROTECTED]> wrote: > > I am an XFire user planning to evaluate CXF for my project. What is the > maven dependency for CXF to be used? While using XFire, I had the > following > dependencies. > > > org.codehaus.xfire > xfire-jaxb2 > 1.2.5 > > > org.codehaus.xfire > xfire-spring > 1.2.5 > > > org.springframework > spring > > > > > org.codehaus.xfire > xfire-java5 > 1.2.5 > > > Do we have something similar for CXF? I use spring. > -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Using CXF
I am an XFire user planning to evaluate CXF for my project. What is the maven dependency for CXF to be used? While using XFire, I had the following dependencies. org.codehaus.xfire xfire-jaxb2 1.2.5 org.codehaus.xfire xfire-spring 1.2.5 org.springframework spring org.codehaus.xfire xfire-java5 1.2.5 Do we have something similar for CXF? I use spring.
