Re: JAX-WS MessageContext properties

Hi Dhiraj, Yes, for DOMSource Provider, runtime can't get operation name. Please refer JaxWS 2.0 spec p111. Regards Jeff - Original Message - From: Bokde, Dhiraj [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Wednesday, August 15, 2007 4:45 AM Subject: RE: JAX-WS

Re: Jaxb Complex type

Hi, Is it the generics? I'm not sure about this, have not investigate into it, but can give you a quick answer, java2wsdl don't support Aegis yet. James Hi - I got a complex type as follows: @XmlType(name = PaginatedResult, namespace = ReactorWSConstants.RBX_MODEL_NS) public class

Re: Adding interceptors to a JAX-WS client via the API

Hi Jeff, Is it possible that theWeblogic server uses a different implementation of javax.xml.ws.spi.Provider, i.e. is there another META-INF/services/javax.xml.ws.Provider file on the classpath, before the one in the cxf-rt-frontend-jaxws jar? This would not affect the creation of a JAX-WS

RE: How to pass options to java2wsdl in the maven codegen plugin?

Hi Jason, Looking through the code for the java2wsdl goal, it doesn't appear that there is any way for passing in extra arguments. If this is something you'd like to see in CXF, I'd suggest submitting an issue to JIRA. It shouldn't be too hard to add. http://issues.apache.org/jira/browse/CXF

Re: CXFServlet throws NullPointerException when using cxf.xml

Does anyone have a clue why the bus.getExtension(ResourceManager.class) would return null? The mere existence of a cxf.xml in my app causes the NPE I mentioned below. On 8/14/07, Ray Krueger [EMAIL PROTECTED] wrote: If I add the following cxf.xml file (from he wiki) to my build I get a

Re: java2wsdl - wsdl2java lossy? (newbie alert!)

Hello Brett, Am Donnerstag, den 09.08.2007, 23:37 -0500 schrieb Brett Wooldridge: I may return to CXF at some point, the level of activity here is encouraging and leads me to think CXF will improve over time. However -- and really, I don't mean to knock you guys on your own list but I've

Re: Jaxb Complex type

Hi James - As I mention in the previous post it was my fault, I didn't put a non param constructor, now that I put it is working fine I get a complex type in my WSDL types schema. But I think I did found a bug in the WSDL generation using Aegis, I would post jira bug for this as soon as

Re: java2wsdl - wsdl2java lossy? (newbie alert!)

Yes, most certainly, but it does not incorporate the library architecturally within it. That was the point I was trying to make. Glen Am Mittwoch, den 15.08.2007, 10:37 -0400 schrieb Randy Burgess: Metro has Spring support. https://jax-ws-commons.dev.java.net/spring/ Regards, Randy

Re: client libaries

Hi Abid, This page documents how to use WSDL2Java to generate a client: http://cwiki.apache.org/CXF20DOC/wsdl-to-java.html Or are you looking for something different? Cheers, - Dan On 8/14/07, Abid Hussain [EMAIL PROTECTED] wrote: Hello everybody, I was using XFire till now and was very

Handling MTOM in DataSourceType and Base64Type

Hello, I found a difference of behavior in handling of MTOM in Aegis org.apache.cxf.aegis.type.basic.Base64Type and org.apache.cxf.aegis.type.mtom.DataSourceType. The approach is more or less the same as in XFire-1.2.6, where I meet it at the first time ( and got some interoperability issues

Problems consuming rpc literal service

Hi all, I have a very strange problem consuming a rpc/literal http soap service. With version 2.0-incubator I got some complex object, but it had no content. Maybe this is similar to thread http://www.nabble.com/WS-client-returning-uninitialized-objects-tf4144602.html#a11788382 Today I

RE: How to pass options to java2wsdl in the maven codegen plugin?

Filed... https://issues.apache.org/jira/browse/CXF-910 Thanks, Jason Christopher Moesel wrote: Hi Jason, Looking through the code for the java2wsdl goal, it doesn't appear that there is any way for passing in extra arguments. If this is something you'd like to see in CXF, I'd

AJAX - [JSON] - REST service

Hi guys, I am in the process of validating using web services in conjonction with an AJAX layer on the front-side. The architecture of this might look like: - using CXF to expose REST services - these services will throw out some JSON (via Jettison) - the client side will use YUI to access

Re: wsdl returns No service was found. after refreshing Spring context

Hi Choreo, Hmm - I've never tried such a thing. I'm wondering, does Spring fully destroy all the previous beans? I could imagine there would be problems if Spring didn't call stop() on your simple:server/. Actually, now that I look through our source, it seems that the

Deploying CXF to Weblogic 10.0

So I've been trying to get CXF to deploy to a BEA Weblogic 10.0 application server. However, I am running into a number of issues. Most of them have to do with the numerous JARs that come with CXF and conflicts with BEA (surprise surprise). I've opened up support tickets with BEA anyway to see

Re: Handle exceptions on the client side

Hi Stefan, What does your server/client xml look like? Your code looks correct to me. - Dan On 8/15/07, Stefan Alexandrescu [EMAIL PROTECTED] wrote: Hi there , I had a problem with handling exception on the client side . Please someone can help me with this issue ? I used the latest

Re: AJAX - [JSON] - REST service

Am Mittwoch, den 15.08.2007, 13:48 -0400 schrieb Jean-Sebastien Bournival: Hi guys, I am in the process of validating using web services in conjonction with an AJAX layer on the front-side. The architecture of this might look like: - using CXF to expose REST services - these services

Re: Deploying CXF to Weblogic 10.0

Am Mittwoch, den 15.08.2007, 14:41 -0400 schrieb Tchang, Jeffrey (Genworth): So I've been trying to get CXF to deploy to a BEA Weblogic 10.0 application server. However, I am running into a number of issues. Most of them have to do with the numerous JARs that come with CXF and conflicts

RE: Deploying CXF to Weblogic 10.0

So I've been trying to get CXF to deploy to a BEA Weblogic 10.0 application server. However, I am running into a number of issues. Most of them have to do with the numerous JARs that come with CXF and conflicts with BEA (surprise surprise). I've opened up support tickets with BEA

Re: writing a service with spring

Matt, I'm going to ask a seemingly stupid question. But what do you mean by having them on your classpath? I use eclipse with the WTP and I stop and start tomcat from within eclipse and deploy my webapp as well without anything getting dropped into the tomcat directories. I ran into this problem

[U] RE: Deploying CXF to Weblogic 10.0

UNCLASSIFIED I have 2.0-incubator working fine in Weblogic 9.2 using a JAX-WS frontend. It's probably overkill but I have even more in my prefer-application-packages. Here's my weblogic-application.xml contents : ?xml version=1.0 encoding=UTF-8? weblogic-application

Re: How to pass options to java2wsdl in the maven codegen plugin?

So, any other options you want to add in? Is it ok to close CXF-910? Cheers, James Interestingly, looking at the source code there, it does appear that a lot of the parameters are exposed as regular tags(none of which are documented here:

Re: How to pass options to java2wsdl in the maven codegen plugin?

Well, It should accept the full set of arguments that java2wsdl supports, I should think... Using the extraarg model, you don't have to worry about whatever other args get added to java2wsdl later on (Also I spoke to soon, there are a few other things I wanted at least to try setting,

Re: How to pass options to java2wsdl in the maven codegen plugin?

Hi Jason, I happen to agree with you, but we are doing anther java2* tools, called java2ws, which will include more options, and it'll in our 2.1 release i guess. So, I think we can do the same thing as wsdl2java goal here. Cheers, James Well, It should accept the full set of arguments

Re: How to pass options to java2wsdl in the maven codegen plugin?

Jason, Yeah, I saw the issues you report, i'll take care of it. Currently, we don't have the documents for java2ws but you can track the issue https://issues.apache.org/jira/browse/CXF-890 It includes couple sub tasks. Cheers, James James, Thanks for taking a look, to the extent it makes

How to generate complex type restrictions with code-first development

Hi, I am interested in trying to create some complex xsd types, using code first development So far, I've seen how to do some things, like create enums by using the @XmlEnum annotation, etc What i haven't come accross is a way to specify some of the interesting restriction facets,