Hello,
I am new to cxf and have creating web service using simple:server
configuration exposing my service bean. Now, I want to expose another
service bean using jms and spring configuration. Is there a sample I can use
to expose my service for jms without using wsdl file?
thanks.
--
View this
Hello,
I am learning to use cxf (migrated from xfire) and in previous cxf 2.0
release, I had no problem running the following client creating by using
some of the sample code for cxf with spring.
JaxWsProxyFactoryBean jf = new JaxWsProxyFactoryBean();
what I
am missing.
Aurelije wrote:
Hi,
I have included all jars from cxf 2.0.2 lib directory when running client
and I did not have any problems after that.
Regards,
Aurelije
On 9/26/07, mule1 [EMAIL PROTECTED] wrote:
Hello,
I am learning to use cxf (migrated from xfire
Hello,
actually in my first email, I was trying to create client two ways and both
ways are resulting in error.
If I use this:
ClientProxyFactoryBean f = new ClientProxyFactoryBean();
f.setAddress(http://localhost:8080/serviceurl;);
f.setServiceClass(MyCxfWebService.class);
Hello Dan,
I tried several things to debug to see what is going on.
First, I tried to test the sample spring helloworld client application as
standalone client that comes with the cxf download and it works with no
problem.
So, I copied the HelloWorld.java and HelloWorldImpl.java in my
Sorry - Please read HelloWorldNew as HelloWorld in my configuration/code in
my previous post - To test, I had created two interfaces - one HelloWorld
and other HelloWorldNew
--
View this message in context:
Hello Wellem,
I really don't have anything extra on sever side. To make testing this
problem simple, I added the HelloWorld sample code in my server side code
and it just seems that the client code when trying to use it when deployed
on web application gives the error.
The configuration on
Willem - Thanks. I configured it using that example. With this simple
frontend, how can I set 'wrapped = true?
--
View this message in context:
http://www.nabble.com/cxf-plain-xml-http-configuration-using-simple-frontend-tf4591639.html#a13117511
Sent from the cxf-user mailing list archive at
Hello,
I am confused a little for this - I want to do wsdl first configuration and
I define my jaxws:endpoint with wsdlLocation=WEB-INF/hello.wsdl - but it
just seems that the service is build from the java class and not wsdl file.
e.g. If I specify a completely wrong wsdl filename in
Hello,
I was wondering how is jms with cxf different than spring's jms using
jmstemplate? Meaning what are positive points for each of them?
--
View this message in context:
http://www.nabble.com/spring-only-jms-vs-jms-with-cxf-tf4664593.html#a13325081
Sent from the cxf-user mailing list
Hello,
For some of the cxf examples for REST style services, where e.g for a class
Customer with method Customer findCustomer(String name, String company), the
xml looks like following:
findCustomers
nameDan/name
companyAcme Inc/company
/findCustomers
If I don't want my xml element to be named
Hello,
I have exposed my service using simple frontend spring configuration for xml
over http. In my service class, I have method names, which comes out as
operation name in the wsdl file for xml binding. Is it possible to change
this operation name either from the configuration file or some
Hello,
what would be all the places where I need to specify targetNamespace= in
my annotation? I currently have tried with @WebResult(name=myresultxx,
targetNamespace=) and the element still comes up with 'ns'. So, not sure
where else I need to have the tragetNamespace=
--
View this message
Hello,
I want to introduce my own interceptor in my jaxws configuration where
before the response xml is generated, I want it to go through an xslt
transformer to transform the response xml. How can I introduce this
interceptor?
--
View this message in context:
return class is my bean class - not java class.
--
View this message in context:
http://www.nabble.com/SOAP-Namspace-change-in-2.0.3---Please-Advise-tf4772597.html#a13916358
Sent from the cxf-user mailing list archive at Nabble.com.
yes after the response XML is geneated, but before it is sent out.
--
View this message in context:
http://www.nabble.com/what-would-be-the-best-place-to-introduce-xslt-transformer-for-response-message-tf4862565.html#a13916324
Sent from the cxf-user mailing list archive at Nabble.com.
is it possible to have the response xml document to drop the NS prefixes with
jaxb?
--
View this message in context:
http://www.nabble.com/SOAP-Namspace-change-in-2.0.3---Please-Advise-tf4772597.html#a13913734
Sent from the cxf-user mailing list archive at Nabble.com.
Hello,
I am not clear exactly what you said. I looked at the SAAJOutInterceptor,
but didn't clearly understand how I can get the message content - either
bytes or something that I can use to tranform with an xslt transfomer. If
possible, can you provide me some sample lines of code? Thanks.
--
Hello,
Is it possible to do jaxb xml element mapping in the configuration file
instead of using the annotations such as @XmlElement etc?
--
View this message in context:
http://www.nabble.com/jaxb-xml-element-mapping-via-configuration-file-tf4878381.html#a13960372
Sent from the cxf-user mailing
Hello,
I am little bit stuck and need to get this working for a release and not
sure what I am doing wrong to expose same service class for both SOAP and
XML messaging. I am having problem with some annotations for XmlElement for
an Array property on my response object class. If I annotate the
the
MessageContentList after it comes back on the client side (I am using
JaxWsProxyFactoryBean), the MessageContentList has this array property value
coming out as null. Please help me understand what I am missing on client
side to get the correct response data.
thanks.
mule1 wrote:
Hello,
I am little bit
beans loaded. I need some guidance what I am missing in my
upgrade from 2.0.2 to 2.0.3.
mule1 wrote:
Hello,
I am using cxf.xml to configure all my beans and everything worked fine in
2.0.2. However, on upgrade to 2.0.3, while deploying the application, I
get these errors:
2007-11-28 13:58
filename also as cxf.xml where I am importing import
resource=classpath:META-INF/cxf/cxf.xml/ - and it just seems that the
addition of that bean definition in the META-INF/cxf/cxf.xml is causing
never ending circular references. Please help to figure out what I need to
resolve this issue.
mule1
I am really stuck with this upgrade problem from 2.0.2 to 2.0.3 - Can someone
provide input for this? I need to upgrade to 2.0.3 for some issues that are
fixed in 2.0.3.
thanks.
mule1 wrote:
even with just the following in cxf.xml, I get those errors.
code
beans xmlns=http
Hello,
Yes I have looked at that configuration documentation at :
http://cwiki.apache.org/CXF20DOC/configuration.html and I don't have my own
cxf-servlet.xml defined at all. The one referenced in cxf.xml is the cxf's
import.
My configuration is very similar and simple.
1. In my web.xml, I have
Hello,
With cxf, is there a way to post an outbound message on to a client's url?
e.g. I have a method that generates a message in xml format. I need to post
this to a client's url. Not sure whether there is a way I can do this with
cxf.
Thanks.
--
View this message in context:
, den 06.12.2007, 16:15 -0800 schrieb mule1:
Sorry, didn't clarify what I meant by client. By client, I meant third
party
customer - has a url exposed to which I need to post the respose.
Meaning,
my outbound message, which is currently in xml format needs to be posted
to
that third part
27 matches
Mail list logo