Re: Problems with schema-validation-enabled

I see the problem... all your xsd's have the same target namespace. When we're looking them up, we're only looking at the namespace. I'll see what I can do with it tomorrow. Dan On May 19, 2008, at 11:32 AM, Nikolaj A. wrote: System specs. CXF 2.1 Tomcat 5.5.17 (I know it's old, but

Re: Another java2ws issue

I would probably need to see the full method signature as well as the Quote class (Quote is a concrete class, not an interface, right?) Dan On May 29, 2008, at 10:13 AM, harbhanu wrote: Hi, I am trying to generate the WSDL using the java2ws tool.for the SEI given at http://cwiki.ap

Re: NullPointer on service invocation with optional element not present

asm 2.2.3 is our "preferred" version, so it should have worked. If you remove asm jar from the classpath, a couple of codepaths have to revert to using reflection based stuff. What it looks like is the reflect based stuff is working ok, but there is a bug in the asm version. I added

Re: java.lang.StackOverflowError at org.apache.cxf.transport.http.WSDLQueryHandler.updateDefinition

It turned out that we had recursive imports in the WSDL. Eg. We had WSDL A and B, and WSDL A was importing WSDL B and WSDL B was importing WSDL A. I commented out the import WSDL in the subordinate WSDL and it worked out fine and CXF Webservice was able to serve WSDL. I went back to Tomcat 5.5.

Re: Mozilla-based browsers

I've tested it in firefox. If these others support the relatively minimal requirements, they should work, but I haven't tested them. On Thu, May 29, 2008 at 2:08 PM, Johnson, Eric <[EMAIL PROTECTED]> wrote: > The wiki says that client-side JavaScript is supported in Mozilla-based > browsers. Does

Mozilla-based browsers

The wiki says that client-side JavaScript is supported in Mozilla-based browsers. Does this include all browsers built using the Gecko engine like Flock? or just Firefox, SeaMonkey, and Camino? Is Safari supported?

Re: Did something change in the spring configuration options for jaxws:endpoint ?

Putting the imports at the top did the job! Thanks!! Try moving the s to the top of your Spring config file. I know the order of definition of Spring beans isn't supposed to matter, but in the case of CXF the bus dependency is handled by the XML parsing code rather than by a separate BeanFac

Logging messages from unit test

All, I'm running a junit test that calls several remote webservices using cxf. I've been beating my head against a wall trying to figure out to get cxf to log, on my local machine, the messages it's sending. Any thoughts on how to do this properly? Thanks a lot, -C-

Another java2ws issue

Hi, I am trying to generate the WSDL using the java2ws tool.for the SEI given at http://cwiki.apache.org/CXF20DOC/developing-a-service.html [Example8: Fully Annotated SEI] I have given my implementation of Quote, which contains an integer quote, along with a method to fetch it, namely fetchQ

RE: Problems with schema-validation-enabled

Hey Leo, I tried to replace the default xml parsers with woodstox by adding the following jars: stax2-2.1.jar wstx-asl-3.2.5.jar wstx-lgpl-3.2.5.jar and setting the following properties: -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory -Djavax.xml.stream.XMLOutputFactory=com

Communication problem & warning

Hi, after generating java code from wsdl (wcf style) I have such warning and cannot communicate to the service: WARNING: SP0100: Policy assertion Assertion[com.sun.xml.ws.security.impl.policy.SpnegoContextToken] { assertion data { namespace = 'http://schemas.xmlsoap.org/ws/2005/07/s

Re: REST XML missing declaration

Hi Yes, for this you need to create your own JAXBElementProvider (copy and paste the existing one) and remove the code line which registers a Marshaller.JAXB_FRAGMENT property... The existing JAXB provider will be fixed on the trunk too. Cheers, Sergey - Original Message - From: "Joh

Re: Really the Real One -- CXF 2.1 and REST Annotation

Hi JAX-RS provides a very flexible mechanism for matching URIs to classes and methods, courtesy of its matching algorithm and the URiTemplate spec. The matching starts from the root resource class which contains the initial Path declaration. So if you say have an existing JAXWS class then this s

Re: REST XML missing declaration

Sergey, So are you saying there's a way to do this now? John Baker -- Web SSO IT Infrastructure Deutsche Bank London URL: http://websso.cto.gt.intranet.db.com "Sergey Beryozkin" <[EMAIL PROTECTED]> 29/05/2008 09:46 Please respond to users@cxf.apache.org To cc Subject Re: REST XML m

Re: Did something change in the spring configuration options for jaxws:endpoint ?

Try moving the s to the top of your Spring config file. I know the order of definition of Spring beans isn't supposed to matter, but in the case of CXF the bus dependency is handled by the XML parsing code rather than by a separate BeanFactoryPostProcessor or similar, so the bus definition (in

Re: REST XML missing declaration

Hi, It will, there's a (copy&paste) fragment property in the existing provider which prevents JAXB from outputting a declaration. You'd also be able to control the encoding type of the given xml instance through a ProduceMime declaration... Cheers, Sergey Hello, I don't recall seeing a res

Fw: REST XML missing declaration

Hello, I don't recall seeing a response to this post. Will the proper XML declaration be included in the next release of CXF? Or does it require more thought? Thanks, John Baker -- Web SSO IT Infrastructure Deutsche Bank London URL: http://websso.cto.gt.intranet.db.com - Forwarded

Re: NullPointer on service invocation with optional element not present

This issue is definitely fixed by removing the asm.jar. As the error is really not comprehensible, is there any way cxf runtime could detect such icompatible JAR in classpath and warn the user for this ? Nico. 2008/5/28 nicolas de loof <[EMAIL PROTECTED]>: > I've made more investigation as the