Re: Client time-out not working

You need to create the client first or you can't get a real client. So the code snippet should be JaxWsProxyFactoryBean proxyFactory = new JaxWsProxyFactoryBean(); proxyFactory.setServiceClass(CustomerService.class); proxyFactory.setAddress(serviceURL);

Re: Using logger !

I think you are talking about two difference thing. One is the Logging{In|Out}Interceptor which logs the request and response message and it could be configured with annotation. The other is the logging.Properties file which could configure the j.u.l 's logging level. Since the logging

Re: cxf.apache.org down?

You can get the CXF schema information here [1] [1] http://cwiki.apache.org/CXF20DOC/schemas-and-namespaces.html Willem toddmcgrath wrote: Hi everybody, I'm getting validation errors on app startup with a CXF client. I'm assuming it's because http://cxf.apache.org/ is down? This is probably

Re: servlet transport question

Hi Leos, Please see my comments in the mail. [EMAIL PROTECTED] wrote: Rafael, thank you for your message. Especially the note about FQCN for Endpoint is crucial for me! Can somebody update http://cwiki.apache.org/CXF20DOC/servlet-transport.html ? Sure, I will take care of it. After,

Re: Multiple addresses for a service

the correct bean. We just need to take into account the path separator / and only select the one that has a full match. On Mon, Apr 14, 2008 at 4:15 AM, Willem Jiang [EMAIL PROTECTED] wrote: That is because CXF support to map a Http request to a soap request, such as http://localhost:9000/SoapContext

Re: Local transport is both up and down at the same time, sort of.

Just as DanK said , if you want to use the local transport across the web apps, you need to share the bus between these apps. It is not a easy way to do that. How about starting a stand http servlet transport to do that ? Willem Benson Margulies wrote: JNI is a pain in a web container. It

Re: Using cxf with external web-services

There are the outputs of the Spring's logger which uses the common log, if you have the log4j jar in your class path, common log will pick them up. You may turn off the log by putting the log4j logger.property file in your class path and set the Spring logging level to WARNING. Willem Tim

Re: Multiple addresses for a service

That is because CXF support to map a Http request to a soap request, such as http://localhost:9000/SoapContext/SoapPort/greetMe/requestType/cxf;. To implement this by default , CXF use the match the first policy(call the String.startWith()) to lookup the proper destination. With these policy

Re: Local transport is both up and down at the same time, sort of.

at 7:34 AM, Benson Margulies [EMAIL PROTECTED] wrote: I see your point. Maybe I made a cut-and-paste error and set up the service factory instead of the proxy factory. On Thu, Apr 10, 2008 at 4:14 AM, Willem Jiang [EMAIL PROTECTED] wrote: Hi Benson, I am confused about the Webapp#2's

Re: Local transport is both up and down at the same time, sort of.

Hi Benson, I am confused about the Webapp#2's log. [java] Apr 9, 2008 9:11:35 PM org.apache.cxf.transport.local.LocalTransportFactory createDestination [java] INFO: Creating destination for address local://RosetteTextAnalyzer It looks you create the same local transport destination in

Re: Webservice client sending null parameters to host

FYI, the jetty engine is just used for implementing the http transport, it will not modify any of the Request or Response message. I think there may be different xml library in the WAR class path and the in the jetty embedded class path. Willem depstei2 wrote: Hi Dan, thanks for your help,

Re: HTTPS and CXF Protocol mismatch: engine's protocol is http, the url protocol is https

We have two configuration system properties to set the configuration file, one is cxf.config.file for the configuration file in the class path such as -Dcxf.config.file=SercureServer.xml , the other is cxf.config.file.url which is used for the point out the configuration's URL. In your case ,

Re: HTTPS and CXF Protocol mismatch: engine's protocol is http, the url protocol is https

Hi , How did you feed the CXF configuration to the server? Here is a document [1]to show how to supply a configuration file to CXF. [1]http://cwiki.apache.org/CXF20DOC/configuration.html Willem [EMAIL PROTECTED] wrote: Hi guys, I have some problems with CXF and HTTPS. My configuration file

Re: IncompatibleClassChangeError: DefinitionImpl

If you are working on the WebSphere with CXF. Here is one solution[1] for your case. [1]http://cwiki.apache.org/confluence/display/CXF20DOC/AppServerGuide#AppServerGuide-Websphere Willem Scott Anderson wrote: I get this exception when I try to instantiate my Service class: Exception in

Re: service caching

more code to add. That said, I don't think it's a bad idea at all. On the contrary, it's a good idea. It's just a bit of work. Dan On Tuesday 04 March 2008, Willem Jiang wrote: Hi Dan, I think we could cache the ServiceInfo object and DataBinding object which will take lots of time

Re: Code Fisrt + JSON: xmlbinding problem

You could fill a jira and attach the test case with it. Willem On 3/5/08, Luca Ceppelli [EMAIL PROTECTED] wrote: !-- @page { size: 21cm 29.7cm; margin: 2cm } P { margin-bottom: 0.21cm } -- Hi all. I'm trying to

Re: Accessing WebService that requires username/password

Does the WSDL_LOCATION also point to the server which you need to access? If so , here is my explain of this issue. In CXF we just use WSDL4J and use a common URL class to load the wsdl, so what you set on the client side will not affect the WSDL4J's URL. CXF will build a service model with the

Re: service caching

if WSDLManagerImpl.getDefinition(URL url) is called. First in getDefintion(URL url) at line 147 and second in loadDefinition(String url) at line 201. On Mon, Mar 3, 2008 at 9:43 AM, Willem Jiang [EMAIL PROTECTED] wrote: Hi, I just went through the code, we really cache the WSDL definition in CXF. Could you

Re: Rampart and CXF

Hi, You just use the FooService (client) as usual. The cxfClient will build up the interceptors each time before it send out the message when you invoke the client proxy method. I will update the wiki as you suggested. BTW, You could also add the interceptor through the

Re: Maven generate-sources target issues

Hi, Please add the below repository into your pom: repositories repository idjava.net/id urlhttp://download.java.net/maven/1//url layoutlegacy/layout /repository /repositories Then you will get the jar. Willem Bjorn Townsend wrote: Hello, I'm trying to generate sources

Re: service caching

that the wsdl is put into the definitionMap twice if WSDLManagerImpl.getDefinition(URL url) is called. First in getDefintion(URL url) at line 147 and second in loadDefinition(String url) at line 201. On Mon, Mar 3, 2008 at 9:43 AM, Willem Jiang [EMAIL PROTECTED] wrote: Hi, I just went

Re: Illegal Protocol https for HTTP URLConnection Factory

What's your 2nd CXF Client 's configuration? Did you set the Client Parameters for it ? Here is one http conduit per client in CXF. Willem yulinxp wrote: My excitement for my first CXF client connection didn't last long. Now I have another problem for my 2nd CXF client connection to

Re: service caching

caching of services? Axis does not seem to have this issue. Christopher Cheng wrote: Attached is the log - Original Message - From: Willem Jiang [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Saturday, March 01, 2008 8:53 PM Subject: Re: service caching? Hi Could you

Re: soap address question

yulinxp wrote: Using browser, when type in the url defined in soap:address, browser should be able to locate the page, right? It depends on the service implementation. CXF support to use http get method to access the service , you can find more information here[1] 1) For example, for

Re: client code to access java_first_jaxws on tomcat

Hi Dan, You set the wrong endpointAddress. http://localhost:8080/helloworld/services/hello_world?wsdl; is the service wsdl url. you need to set the endpointAddress to be http://localhost:8080/helloworld/services/hello_world; Willem Daniel Lipofsky wrote: I am trying to learn CXF, I

Re: JAX-RS in 2.0.4-incubator?

Hi Tom, JAX-RS support is only in the CXF 2.1. Willem. Tom Davies wrote: Is JAX-RS support in 2.0.4, or only in 2.1? If it is in 2.0.4, which jars do I need (I can't find cxf-rt-frontend-jaxrs) Thanks, Tom -- ATLASSIAN - http://www.atlassian.com Our products help over 8,500 customers in

Re: how to configure HTTPConduit for client using java code

Hi , I think the default Data Binding in the ServiceFactory is JaxbDatabinding. That's why you need to do when you want to use AegisDatabinding. Willem. yulinxp wrote: Why/when is it needed to set AegisDatabinding for client at all ? ClientProxyFactoryBean factory = new

Re: Lazy instantiation of Web Service Client

Hi Richard Hi For the client instantiation, it just need to create the service model[1] first. If you add the wsdlLocation attribute in your SEI's WebService annotation or specify the wsdlLocation property for the JaxWsProxyFactoryBean with your service endpoint's address, the client will

Re: JMS connect exception, but service published

Hi , Currently , CXF the destination active method do not throw the Exception , and the JMSDestination just swallows the exceptions. You can fill a JIRA to add a feature request for it. Willem. Mayank Thakore wrote: Hi, When publishing a web service on jms transport, if activemq is not

Re: Issue with CXF: Marshalling Error: Error writing request body to server

Please take a look at the wiki page[1], If you wanted to use MTOM to send the binary part of the message as an optimized attachment you would need to add the xmime:expectedContentTypes attribute to the element containing the binary data. This attribute is defined in the

Re: Query About Request Context

FYI, currently we have some a JIRA[1] for tracing this issue. https://issues.apache.org/jira/browse/CXF-1410 Willem. SantoshAkhilesh wrote: Hi, So far I had an idea that request context is put in thread local but I realized it is not. Why the request context is not threadlocal ? If I want

Re: Query About Request Context

This link [1] may help your to get the whole story. [1]http://www.nabble.com/Request-ResponseContext-of-JaxWsClientProxy-td10327781.html#a10335673 Willem. Sky-Tiger wrote: See this: public class JaxWsClientProxy extends org.apache.cxf.frontend.ClientProxy implements InvocationHandler,

Re: Issue with CXF: Marshalling Error: Error writing request body to server

Hi, Did you enable the MTOM feature? Please refer the below link for more information. http://cwiki.apache.org/CXF20DOC/mtom.html Willem. Tor Arne Kvaløy wrote: Hello! I have ran into a serious problem with CXF on the client side. I have tried quite a few things but I am right now quite

Re: WebSecurity error when using Simple Frontend / Aegis binding

Hi , There are some difference between the simple front end and jaxws front end to detail with the fault message. The WebFault annotation will take effect when you are using the jaxws front end , but when you using simple front you need let the exception class inherit the

Re: HttpSession and Endpoints

the SessionManager is stateful, but not the interceptors. But the interceptors do call into my application code, is that a bad practice? Willem Jiang wrote: It is not easy to share the http conduit between the different proxy, since you need to hack the HttpTransportFactory and handle

Re: HttpSession and Endpoints

It is not easy to share the http conduit between the different proxy, since you need to hack the HttpTransportFactory and handle theconfiguration of the http conduit. I don't think using the interceptor could resolve the problem that you met. Because when you using the interceptor to hold the

Re: Leaving CXF for Glasshfish Metro

AFAIK you just have trouble to create the DynamicClientFactory instance, which mainly create the CXF bus instance. I think you can try out to deploy the basic simples into your Tomcat6. May be it will show you the key of the issue. You can download the CXF kit here[1] , and try the

Re: HttpSession and Endpoints

Yes , CXF do not share the http conduit between the different client proxy. If you want to share the session between the client proxy, I am afraid you need to hack the CXF http conduit code to handle the cookie in you application code. Willem. Chris Campbell wrote: The problem is that I get

Re: jms header properties

Hi Mayank, Here is a systest [1] testContextPropogation() for setting the JMS header. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/jms/JMSClientServerTest.java Willem. Mayank Thakore wrote: Hi, How to set header/property fields in

Re: Problem: When invoke HttpServletRequet.getRemoteAddr(), it return the old client IP...

Hi Cam you show me how can you get the ctx object ? If the ctx that you use is get from WebServiceContext which has a thread local variable , it is injected to CXF for getting the message context. I don't know if this can relate to the issue that you met. Willem. Prinston wrote: Dears: I

Re: problem using local transport

Hi, Did you do any setting up the transportIds for the local transport in CXF bus? You need to override the CXF bus default loading transport factory to local transport. Here are an example of setting the bus with code in the jaxws front end test module[1], and a spring configuration file

Re: CXF Servlet setup problem

Yes , here is another way which will not use the org.springframework.web.context.ContextLoaderListener to start the endpoints. You can find the example form CXF's hello world examples [1] As Dan Kulp has said , you don't need imports any of classpath:META-INF/cxf-. [1]

Re: Use Tomcat

sending files Willem Jiang pisze: Hi Pawel Did you use CXFServlet transport which delegate the http transport to a CXFServlet ? If so , could you show me your Web.xml and Beans.xml? In you case I think you still start a new Jetty engine for listening the port. Willem. Pawel Janusz wrote

Re: Simple Front end/Aegis binding server side set up problem

They are the spring description files of cxf components. import resource=classpath:META-INF/cxf/cxf.xml / this is the cxf core component. import resource=classpath:META-INF/cxf/cxf-extension-soap.xml / this is the soap component configuration file. import

Re: Some basic question on wsdl generated services

Hi Mayank My comments are in the mail. Mayank Thakore wrote: Hi, Few basic questions: 1. If we generate service implementation objects using wsdl2java, is it possible to avoid it referring back to the wsdl file in the annotations? You just need to remove the wsdlLocation attribute from

Re: WS-Security

Hi Which CXF version are you using? Please check your class to make sure cxf module jars are consistent. If they are CXF 2.0.3 please make sure there is no any CXF 2.0.2 or CXF 2.1 jars in your class path. I just checked the CXF codes, there some changes of

Re: cxf without spring

Yes, you could init a bus without the spring just as Glen shows. Here is one thing that I should say about the bus = BusFactory.newInstance().createBus(); The BusFactory will check your class path , if it can find some spring relate class , it will use SpringBusFactory to load bus. Unless

Re: WS-Security

I think you can use ssl to secure your RESTful service and don't know if there is other way to do it. AFAIK Jervis just commit a sample of it [1], please check it out from 2.1 snapshot ;) BTW, I think we need keep our conversion in the CXF user group, to share the knowledge more wildly.

Re: Parameter size limit?

Hi Chad, I don't think CXF has the parameter size limit, since I am successful to send the more than 60K binary parameter to CXF server. Did you try to call the service with CXF client ? Maybe you can compare the CXF client and Flex requests' different. Just my two cents. Willem. Trarman

Re: Using HTTPClient as a transport

Hi Barrie, We do not use HTTPClient to send the request in CXF HTTP transport. If you want to replace the CXF's HTTPConduit[1] with HTTPClient , I think you need to implement the Conduit[2] API with HTTPClient. Anyway , you can fill a JIRA[3] for it and the patches are welcome ;)

Re: exposed methods with Aegis binding

Hi, Aegis Binding is a data binding , it will not effect which method will be export to the web service. If you are using JaxWs front end , you could use the annotation to define your SEI ( which will be mapped to the WSDL operation) You can find the example here[1].

Re: Cannot get WebServiceContext or access the httpservletrequest

Hi , It looks like Spring 2.5 will take the charge of the dependency injection of the WebServiceContext. CXF can do it with itself Resource Injector, but Spring can't resolve the WebServiceContext instance. If you can turn off the Spring 2.5 annotation resource injection feature , I think

Re: Cannot get WebServiceContext or access the httpservletrequest

Hi Graham, I can show your the code how does CXF inject the WebServiceContext. It's the JaxWsServerFactoryBean[1]'s injectResources method. Maybe you can find a way to configure the resource resolver with this code. BTW, Why are you want to use Spring 2.5 ? CXF can work with Spring 2.0.x

Re: How to substitute the placeholders in the config files ?

Hi Alex , Here is an example for your replace the ${} palceholders in the spring configuration file. Code : [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/http_jetty/EngineLifecycleTest.java Configuration file :

Re: JAX-WS handler attachment options within Apache CXF

For the server side, you may set the HandlerChain after the endpoint.publish is called. Willem. James Mao wrote: Probably this way is safer getBinding().getHandlerChain().add(YourHandler) James Glen, The answer is YES, you can do it programmatically Service side API

Re: Problems integrating CXF and Grails

Hi Alex, CXF need to use XercesImpl 2.8.1.jar. Please make sure this jar be loaded first. Willem. Alex Shneyderman wrote: I am using Grails framework in conjunction with CXF and I am getting the following error trying to instantiate a SOAP interface to the remote service: Message:

Re: Problems integrating CXF and Grails

Hi Alex , We use 2.8.1 on the development environment , you can try out the 2.9.1 but I don't test it yet. Willem. Alex Shneyderman wrote: Does it have to be exactly that version ? or 2.9.1 will do as well ? On Dec 23, 2007 2:07 PM, Willem Jiang [EMAIL PROTECTED] wrote: Hi Alex, CXF

Re: CXF and JSON

Hi , You can find the example in the CXF_KIT/samples/restful_http_binding Willem. Vespa, Anthony J wrote: I'm considering implementing (or re-implementing) a service from REST/SOAP to JSON. I'm wondering if someone has a workable example (the docs I've found are a bit sparse) in terms of how

Re: Strange error with JAX-WS and JDK 1.5

Hi , I think Resin 3.1.3 may ship a earlier version of jaxws-api.jar and CXF need to use the jaxws-api.2.0.jar. As you know , JDK 1.60_02 ships with jaxws-api.2.0 jar , so Resin's jaxws-api jar will get no chance to be loaded. But there is no any jaxws-api.jar in JDK 1.5.0_06, and the Resin's

Re: Strange error with JAX-WS and JDK 1.5

. The problem I have is that I can not put the jar file production environment in the jre directory. Also, loading war libs first is out of question. Is there a way to configure Resin to load the jar from a different directory before the app server libs? On Dec 20, 2007 6:14 PM, Willem Jiang [EMAIL PROTECTED

Re: any irc channel for equivalent to this mailing list?

It is [EMAIL PROTECTED] Willem. Nino Saturnino Martinez Vazquez Wael wrote: And subject should have been any irc channel equivalent to this mailing list? Sorry for my poor spelling today. Nino Saturnino Martinez Vazquez Wael wrote: are there?

Re: SOAP flow Compression?

You just need to remove the LoggingInInterceptor from the interceptor chain, but I do not know how do you add the interceptor into the bus? BTW: We fixed the CachedOutputStream error in CXF 2.0.3. I think you just need to move to a new version of it :) Willem. Tophebboy wrote: I searched for

Re: SOAP flow Compression?

Hi, Can I see your bus configuration file ? The NPE is caused by you do not set the bus rightly. I just checked the code , you may not include the right bus. Willem. Tophebboy wrote: On top of that, on the server side, launching Tomcat now gives me 2 errors: 17 déc. 2007 14:45:35

Re: Dynamic client basic auth

Hi Guillaume, Please see my comments in the mail. tog wrote: Hi Willem, Can you explain in details your sentence: The AuthorizationPolicy only works for HTTP Conduit of HTTP Destination. as I am not familiar with CXF internals. CXF http transport is implemented by two component HTTP

Re: HTTP Binding for RESTful service

Hi, You need include the below line in your configuration file which will load the http binding for you to use. import resource=classpath:META-INF/cxf/cxf-extension-http-binding.xml/ Willem. priya j wrote: Hi all, This is priya, I am using CFX for my application. I have successfully

Re: org.apache.cxf.interceptor.Fault: Marshalling Error with NFL/GroovyWS

Hi Guillaume The exception is caused by my patch for removing @Resource(name = activationNamespaces) to support Spring 2.5. I did a quick fixing for it few days ago , so the exception will go way when you get the latest snapshot. BTW, This exception only happened when your are useing

Re: PropertyPlaceHolderConfigurer and cxf.xml

Hi , You can find an example in CXF systest [1] [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/http_jetty/EngineLifecycleTest.java Willem. Bc. Jiří Mikulášek wrote: Hi all, I would like to use PropertyPlaceHolder inc cxf.xml tu enable

Re: Addressing namespace compatability issue with WCF

Hi Paul, I just went through the ws-rm's code , there are some hard codes which set the addressing namespace to be http://schemas.xmlsoap.org/ws/2004/08/addressing; and there is a comment in the VersionTransformer.java file. The motivation for using different native and exposed types is

Re: Annotations

Hi, I do not think JAXB's annotation can implment the behavior that you want. Maybe you can define a parent class to be used in the method A, and a child class which extends the parent class with addition attributes to be used in the method B. Cheers, Willem. Thorsten Kraus wrote: Thanks a

Re: odd injection error in running sample jms project

Can you fill a JIRA[1] and submit your test case ? It will helpful for use to trace the bug. [1]http://issues.apache.org/jira/browse Willem. ahwulf wrote: If I turn off FINE and thus ignore the error, the server app still doesn't load - it loops endlessly apparently reloading all the beans. I

Re: restful_http_binding and WebServiceContext

FYI , DI happens in JaxWsServerFactoryBean's[1] init() method. [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/JaxWsServerFactoryBean.java Willem. Davide Gesino wrote: Hi, It's quite strange, the context should be injected... I

Re: disable-address-updates breaks ServiceName?wsdl url

(AddressType.class) != null) { d2.getEndpointInfo().getExtensor(AddressType.class).setLocation(base + path); } } } lastBase = base; } Willem. Christian Vest Hansen wrote: 2007/11/27, Willem Jiang [EMAIL PROTECTED]: Can I see your

Re: New Servlet

Hi Guillaume You can find the samples in the Servlet systest[1] (Spring or Non-Spring). [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/servlet Cheers, Willem. tog wrote: Hiya, Is there somewhere an example of the on spring servlet usage

Re: disable-address-updates breaks ServiceName?wsdl url

Can I see your whole web.xml and endpoint configuration file (bean.xml or cxf-servlet.xml)? I think there must be something wrong with them. BTW, Can you get the wsdl by removing the disable-address-updates and base-addresses parameters in your web.xml? Willem. Christian Vest Hansen wrote:

Re: restful_http_binding and WebServiceContext

Hi Mike, I just checked the code , you need to specify the Service Bean object to be injected with the WebServiceContext. Here is an example for you: private static void createRestService(Object serviceObj) { // Build up the server factory bean JaxWsServerFactoryBean sf = new

Re: How to export non-annotated service in spring

Hi, You can use the simple front end custom server bean definition. Please see [1] for more information. [1] http://cwiki.apache.org/CXF20DOC/simple-frontend.html Willem. ojs wrote: Hello, I'm trying to switch from xfire to cxf - don't had much luck so far... My xfire configuration (in

Re: How to export non-annotated service in spring

Hi, Can you show me your web.xml ? There must be something wrong with your web.xml. Willem. ojs wrote: Willem2 wrote: You can use the simple front end custom server bean definition. Please see [1] for more information. [1] http://cwiki.apache.org/CXF20DOC/simple-frontend.html I

Re: Gzip encoding

Hi Richard, Which version of CXF do you use? I think it probably is a bug of the JaxWsClientProxyFactoryBean. Willem. Shaw, Richard A wrote: I've tried this and it doesn't seem to work. My config file is shown below. The http-conf works fine but not the jaxws:client. I've tried uisng a

Re: Return direct XML

Hi, You can try it. I am also looking forward that the DynamicClientFactory can work with Aegis Binding. And the patch of it is welcome :) Willem. Benjamin Coiffe wrote: Hi, I was trying to use Aegis Binding on the Dynamic client (DynamicClientFactory.createClient()) but it is hard coded

Re: client https and server http

One comment about configuring the http conduit with Java code. The configure the http conduit with Java code should work, you just need set the right endpoint address. Please check out the CXF systest [1] 's testHttpsBasicConnection().

Re: Return direct XML

Yep, I think the initial thought just wanted it works only by setting the JAXB Context with the WSDL dynamically, it may skip the part of JAXB DataBinding. Maybe we can get it workable by refactoring the DynamicClientFactory to accept different DataBinding Context ? I don't know if Aegis

Re: JMS configuration for consumer

Hi Patrick, I don't think CXF JMS transport will recognize the address that you wrote in the soap:address. Now CXF JMS transport just consumer the address information which define as jms:address which is defined by CXF itself. You can find some example wsdl here [1]. BTW It looks like your

Re: Bus has no BindingFactoryManager extension in AbstractBindingFactory.registerWithBindingManager

Hi Tom, Can you try your application with the Spring 2.0.6? We did not develop and test CXF with Spring 2.5-rc1. Willem. Tom Davies wrote: I'm using apache-cxf-2.0.3-incubator-20071102.144221-7 (although I see the same problem with 2.0.2) and Spring 2.5-rc1 I have a simple servlet

Re: Transactional web service using CXF, Spring and JPA

Yep, CXF has the invoker[1] to take care the whole invoking stuff. Jeff just showed you the basic use scenario which treats the implementor as a singleton in the default bean Invoker. All the client sides concurrency invocations will be end up in this singleton invoker, so we can still use

Re: other spring cxf resources ?

Hi , Actually, you could change the client's service URL per message. You can find more information here [1] [1]http://www.nabble.com/Client-question-tf4357978.html#a12419843 Willem. Mohammad Shamsi wrote: Hi Glen, Sorry, my application is not really a distributed app. i just run it on 9

Re: ClientFactoryBean AbstractMethodError

Hi , Can you check xercesImpl-2.8.1.jar is in the class path of your test with JUnit? I can find the method org.apache.xerces.dom.DocumentImpl.getInputEncoding() in that jar. Willem. Todd Orr wrote: hanks. That doesn't really explain, to me, why the server starts up fine when deployed but

Re: Mulitple protocols on one IMPL?

Hi, You can use JAXWS API to publish different transport with a single implementor. eg. Endpoint.publish(Address some where, implemetor); But for your JMS transport , you need to do some configuration to setup the JMS address. You can find some information here [1] and some discussions in

Re: groovy/grails, CXF and generated classes

Hi, The exception is thrown from org.apache.cxf.wsdl11.WSDLManagerImpl which uses a DocumentBuilderFactory to load the WSDL. You class path may do no include a right version of jaxp and you need to put the XecesImpl 2.8.1.jar in you class path. Willem. Jason Botwick wrote: It is . . .

Re: possible problems in mixing https and http?

Hi Christian, I think we could achieve you goal by letting service that CXF published the WSDL with user defined , so you could add what you want https or http protocol string on the address or the xsd including part. Here is a JIRA[1] of trace it, if you have time to write a patch , I can

Re: groovy/grails, CXF and generated classes

need some other version of JAXP? I have seldom met an intelligent person whose views were not narrowed and distorted by religion. ~ James Buchanan On Nov 1, 2007, at 3:31 AM, Willem Jiang wrote: Hi, The exception is thrown from org.apache.cxf.wsdl11.WSDLManagerImpl which uses

Re: possible problems in mixing https and http?

to anything HTTP once it has been configured to use HTTPS. 2007/11/1, Willem Jiang [EMAIL PROTECTED]: Hi Christian, I think we could achieve you goal by letting service that CXF published the WSDL with user defined , so you could add what you want https or http protocol string

Re: the matching wildcard is strict, but no declaration can be found for element jaxws.endpoint

Hi Troy, Which CXF version are you working with ? I just went through your beans.xml and can't tell any thing wrong there. Maybe a simple test case can give us some clues. Willem. Troy Bull wrote: On 11/1/07, Troy Bull [EMAIL PROTECTED] wrote: Greetings I have a couple web services that

Re: Server returned HTTP response code: 411

Hi , O, if you import the file in the Spring applicaiton context, the configure will not take any effect in the CXF which version is below 2.0.3. We just fixed it in the 2.0.3 SNAPSHOT. Here is the JIRA[1] which traced the issue. [1] http://issues.apache.org/jira/browse/CXF-922 Willem.

Re: endpoint rewriting

Hi Christian, NO , you can't specify a full URL address instead of the related path for the endpoint which you want to publish with the Servlet transport. Because CXFServlet can't know your Web container's listen port and related context, so it alway update the endpoint's address with the

Re: CXF + oc4j

Aha. It is the because the oc4j'sWebService class is out of date. You need let oc4j load the CXF shipped geronimo-ws-metadata*.jar first. You can find more information about how to let CXF work with AppServer here[1] [1]http://cwiki.apache.org/CXF20DOC/appserverguide.html Willem. Hoda,

Re: undocumented configuration with jetty

) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349) at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) On Thursday 25 October 2007, Willem Jiang wrote: Hi , I

Re: undocumented configuration with jetty

what you have in http://cwiki.apache.org/CXF20DOC/jetty-configuration.html how can I get reference to the server in my app so that my other servlets can be registered as well? Thanks for all your help so far. On Monday 29 October 2007, Willem Jiang wrote: O, I can tell the reason form

Re: empty response object

Hi , Did this message is created by CXF Server ? And please tell me the CXF version that you uses. If it is CXF's bug, please fill a JIRA[1] for it , and a simple test case will be helpful for us to debug. [1] http://issues.apache.org/jira/browse/CXF Willem tirtza wrote: I get an empty

Re: how clients handle changing wsdls

Hi Christian, I think if you still use the old wsdl to create the service , the client can still work. I just did a quick test for your case by remove the WSDL2Java generated SEI's method. It can reproduce your case. On the client side if I use the ?wsdl which is generated by CXF to create

Re: undocumented configuration with jetty

Hi , I write a simple test with your case. The services are all published :) Please see the below code. public class JettyServer { public static void main(String[] args) throws Exception { org.mortbay.jetty.Server httpServer = new Server(9000); ContextHandlerCollection

  1   2   3   >