Error accessing my newly develop services

Hi, I got the below error when trying to access my service wsdl using this url: http://localhost:8080/my-services\services;. Any idea on this error are welcome. Thanks. java.lang.UnsupportedClassVersionError: Bad version number in .class file java.lang.ClassLoader.defineClass1(Native

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

The Xerces 2.8.1 JAR is in the classpath. Do I also 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

Re: Error accessing my newly develop services

What's your version of tomcat and tomcat and cxf? Looks like a jdk version problem CXF require jdk5+ and tomcat 5.5+ Regards, James Hi, I got the below error when trying to access my service wsdl using this url: http://localhost:8080/my-services\services;. Any idea on this error are

Re: groovy/grails, CXF and generated classes

Hi, It may relate to your environments. Xerces should be the first one in the class path. Can you list them, such as CXF version, JDK version ,Groovy's version ? A simple test case will be helpful for debugging. Willem. Jason Botwick wrote: The Xerces 2.8.1 JAR is in the classpath. Do I also

Re: Error accessing my newly develop services

Now I've found the problem. I compile the code using 1.6 jdk and try to run it using 1.5 jdk. Thanks for your comment anyway, James Mao wrote: What's your version of tomcat and tomcat and cxf? Looks like a jdk version problem CXF require jdk5+ and tomcat 5.5+ Regards, James Hi,

Re: possible problems in mixing https and http?

I'm not quite sure fixing that jira will solve this particular issue. It seems to me that CXF has trouble connecting 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

Re: possible problems in mixing https and http?

AFAIK, HTTPConduit will not take any charge to load WSDL related information. We just use java's URL to get wsdl not the HTTPConduit. Willem. Christian Vest Hansen wrote: I'm not quite sure fixing that jira will solve this particular issue. It seems to me that CXF has trouble connecting

Null object passed into Dispatch marshalling

I've googled this error message, but all the results seem to apply to bugs in the CXF samples. I'm using the message provider technique for handling incoming SOAP messages and continually receive this exception: Nov 1, 2007 10:59:36 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO:

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

Greetings I have a couple web services that I wrote. I followed the tutorial from the apache site for creating a spring based ws using cfx. This morning I checked my web services out of subversion and I can no longer build them (in eclipse). In my applicationBeans.xml I get the message : the

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

On 11/1/07, Troy Bull [EMAIL PROTECTED] wrote: Greetings I have a couple web services that I wrote. I followed the tutorial from the apache site for creating a spring based ws using cfx. This morning I checked my web services out of subversion and I can no longer build them (in eclipse).

Re: Null object passed into Dispatch marshalling

Do I need to write an interceptor? Or do I need to configure the endpoint to not attempt to marshal the request? On 11/1/07, Todd Orr [EMAIL PROTECTED] wrote: I've googled this error message, but all the results seem to apply to bugs in the CXF samples. I'm using the message provider technique

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

What version of CXF? Did you update to 2.0.2? Dan On Thursday 01 November 2007, Troy Bull wrote: Greetings I have a couple web services that I wrote. I followed the tutorial from the apache site for creating a spring based ws using cfx. This morning I checked my web services out of

Re: Null object passed into Dispatch marshalling

Todd, Are you sure it's not hitting your code?This exception is on the OUTBOUND chain while trying to write a response.That suggests your code was called and you returned null from your invoke method. (which according to spec is not allowed) Dan On Thursday 01 November 2007,

Migrating XFire/Aegis inheritance to CXF

I'd like to bump the question posed a few weeks ago by Nalyd (see http://www.nabble.com/Aegis-inheritance-tf4668138.html#a13335122). I am attempting to ensure that some additional classes which are not present in my service interfaces get bound along with the others, a common problem given a

RE: Migrating XFire/Aegis inheritance to CXF

I pessimistically think that you've found a bug. Could you please drop this into JIRA? -Original Message- From: Segal, Jeffrey [mailto:[EMAIL PROTECTED] Sent: Thursday, November 01, 2007 4:31 PM To: cxf-user@incubator.apache.org Subject: Migrating XFire/Aegis inheritance to CXF

Re: Suggestion for new Main Wiki page for documentation

Looks great to me! BTW, Eclipse Tooling for CXF (in Eclipse STP) has release its 0.7 version [1] and we need to update its related document. In case anyone has interesting doing update, I filed a JIRA here [2]. The latest Eclipse STP version (snapshot version) has also done significant

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: form attribute on xsd:element versus jaxb

Is there any JIRA created for this issue? If not, I can go ahead and created one. Thanks, Bo On 10/31/07, Daniel Kulp [EMAIL PROTECTED] wrote: On Tuesday 30 October 2007, Benson Margulies wrote: I don't see how the @XmlElement annotation can do the job. At least in the version of JAXB we