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 Method) java.lang.ClassLoader.defineClass(Unknown Source) java.security.SecureClassLoader.defineClass(Unknown Source) org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1847) org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:873) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1326) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1205) org.apache.cxf.common.classloader.ClassLoaderUtils.loadClass(ClassLoaderUtils.java:111) org.apache.cxf.jaxws.spring.EndpointDefinitionParser.loadImplementor(EndpointDefinitionParser.java:132) org.apache.cxf.jaxws.spring.EndpointDefinitionParser.doParse(EndpointDefinitionParser.java:86) org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:70) org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:56) org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69) org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1114) org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1104) org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:133) org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:90) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:458) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:353) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) org.apache.cxf.transport.servlet.CXFServlet.loadAdditionalConfig(CXFServlet.java:201) org.apache.cxf.transport.servlet.CXFServlet.loadSpringBus(CXFServlet.java:171) org.apache.cxf.transport.servlet.CXFServlet.init(CXFServlet.java:98) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) java.lang.Thread.run(Unknown Source) -- View this message in context: http://www.nabble.com/Error-accessing-my-newly-develop-services-tf4729713.html#a13524223 Sent from the cxf-user mailing list archive at Nabble.com.
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 . . . sorry, forgot to mention that.
Any other suggestions?
On Oct 27, 2007, at 11:37 PM, Willem2 wrote:
Hi,
It may relate to the Xerces Implementation.
CXF can work with xecesImpl 2.8.1 , please make sure this jar is in your
class path.
Willem.
jwagon wrote:
I'm trying to get a simple service client running against the following
WSDL:
I used SoapUI 1.7.6 to generate the service classes, one of which is
this:
@WebServiceClient(name = api, targetNamespace =
http://api.bronto.com;, wsdlLocation =
http://api.bronto.com/?q=mail_3wsdl;)
public class Api extends Service {
private final static URL WSDL_LOCATION;
private final static QName SERVICE = new
QName(http://api.bronto.com;, api);
private final static QName ApiPort = new
QName(http://api.bronto.com;, apiPort);
static {
URL url = null;
try {
url = new URL(http://api.bronto.com/?q=mail_3wsdl;);
} catch (MalformedURLException e) {
System.err.println(Can not initialize the default wsdl
from http://api.bronto.com/?q=mail_3wsdl;);
// e.printStackTrace();
}
WSDL_LOCATION = url;
}
public Api(URL wsdlLocation, QName serviceName) {
super(wsdlLocation, serviceName);
}
public Api() {
super(WSDL_LOCATION, SERVICE);
}
/**
*
* @return
* returns ApiPort
*/
@WebEndpoint(name = apiPort)
public ApiPortType getApiPort() {
return (ApiPortType)super.getPort(ApiPort, ApiPortType.class);
}
}
But when I execute the following code in a brand new Grails app
(Grails 0.6, Groovy 1.1b):
I get the error below. Not even where to start looking to solve this
one (except Google, which I already tried). Any suggestions?
org.codehaus.groovy.runtime.InvokerInvocationException:
java.lang.RuntimeException:
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in
class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean
failed; nested exception is
org.springframework.beans.BeanInstantiationException: Could not
instantiate bean class [org.apache.cxf.wsdl11.WSDLManagerImpl]:
Constructor threw exception; nested exception is
java.lang.ClassCastException:
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
at
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:64)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelper.java:678)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:689)
at
groovy.lang.ExpandoMetaClass.invokeMethod(ExpandoMetaClass.java:894)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:531)
at groovy.lang.Closure.call(Closure.java:290)
at groovy.lang.Closure.call(Closure.java:285)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.handleAction(SimpleGrailsControllerHelper.java:526)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.executeAction(SimpleGrailsControllerHelper.java:385)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.handleURI(SimpleGrailsControllerHelper.java:240)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.handleURI(SimpleGrailsControllerHelper.java:152)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsController.handleRequest(SimpleGrailsController.java:88)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:45)
at
org.codehaus.groovy.grails.web.servlet.GrailsDispatcherServlet.doDispatch(GrailsDispatcherServlet.java:241)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:755)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:396)
at
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:350)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
--
View this message in context:
http://www.nabble.com/groovy-grails%2C-CXF-and-generated-classes-tf4700854.html#a13449798
Sent from the cxf-user mailing list archive at Nabble.com.
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 give your some points from my view. [1]https://issues.apache.org/jira/browse/CXF-341 Willem. Christian Vest Hansen wrote: We're planning on exposing a number of web services through HTTPS, however, many of the WSDLs will refer to and import schema files that we have stored in a central repository - and this repository is accessed through ordinary HTTP. In other words, our clients access a WSDL through HTTPS - this WSDL has references to a schema that the client has to access through plain HTTP. Will this cause any problems with HTTPConduits and other configurations that clients will have in order to access the otherwise HTTPS enabled web service?
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 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 . . . sorry, forgot to mention that.
Any other suggestions?
On Oct 27, 2007, at 11:37 PM, Willem2 wrote:
Hi,
It may relate to the Xerces Implementation.
CXF can work with xecesImpl 2.8.1 , please make sure this jar is
in your
class path.
Willem.
jwagon wrote:
I'm trying to get a simple service client running against the
following
WSDL:
I used SoapUI 1.7.6 to generate the service classes, one of
which is this:
@WebServiceClient(name = api, targetNamespace =
http://api.bronto.com;, wsdlLocation =
http://api.bronto.com/?q=mail_3wsdl;)
public class Api extends Service {
private final static URL WSDL_LOCATION;
private final static QName SERVICE = new
QName(http://api.bronto.com;, api);
private final static QName ApiPort = new
QName(http://api.bronto.com;, apiPort);
static {
URL url = null;
try {
url = new URL(http://api.bronto.com/?q=mail_3wsdl;);
} catch (MalformedURLException e) {
System.err.println(Can not initialize the default wsdl
from http://api.bronto.com/?q=mail_3wsdl;);
// e.printStackTrace();
}
WSDL_LOCATION = url;
}
public Api(URL wsdlLocation, QName serviceName) {
super(wsdlLocation, serviceName);
}
public Api() {
super(WSDL_LOCATION, SERVICE);
}
/**
*
* @return
* returns ApiPort
*/
@WebEndpoint(name = apiPort)
public ApiPortType getApiPort() {
return (ApiPortType)super.getPort(ApiPort,
ApiPortType.class);
}
}
But when I execute the following code in a brand new Grails app
(Grails 0.6, Groovy 1.1b):
I get the error below. Not even where to start looking to solve
this
one (except Google, which I already tried). Any suggestions?
org.codehaus.groovy.runtime.InvokerInvocationException:
java.lang.RuntimeException:
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'org.apache.cxf.wsdl.WSDLManager'
defined in
class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean
failed; nested exception is
org.springframework.beans.BeanInstantiationException: Could not
instantiate bean class [org.apache.cxf.wsdl11.WSDLManagerImpl]:
Constructor threw exception; nested exception is
java.lang.ClassCastException:
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
at
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke
(ReflectionMetaMethod.java:64)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke
(MetaClassHelper.java:678)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:
689)
at groovy.lang.ExpandoMetaClass.invokeMethod
(ExpandoMetaClass.java:894)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:
531)
at groovy.lang.Closure.call(Closure.java:290)
at groovy.lang.Closure.call(Closure.java:285)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHe
lper.handleAction(SimpleGrailsControllerHelper.java:526)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHe
lper.executeAction(SimpleGrailsControllerHelper.java:385)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHe
lper.handleURI(SimpleGrailsControllerHelper.java:240)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHe
lper.handleURI(SimpleGrailsControllerHelper.java:152)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsController.h
andleRequest(SimpleGrailsController.java:88)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.
handle(SimpleControllerHandlerAdapter.java:45)
at
org.codehaus.groovy.grails.web.servlet.GrailsDispatcherServlet.doDi
spatch(GrailsDispatcherServlet.java:241)
at
org.springframework.web.servlet.DispatcherServlet.doService
(DispatcherServlet.java:755)
at
org.springframework.web.servlet.FrameworkServlet.processRequest
(FrameworkServlet.java:396)
at
org.springframework.web.servlet.FrameworkServlet.doGet
(FrameworkServlet.java:350)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
--
View this message in context: http://www.nabble.com/groovy-grails%
2C-CXF-and-generated-classes-tf4700854.html#a13449798
Sent from the cxf-user mailing list archive at Nabble.com.
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 welcome. Thanks. java.lang.UnsupportedClassVersionError: Bad version number in .class file java.lang.ClassLoader.defineClass1(Native Method) java.lang.ClassLoader.defineClass(Unknown Source) java.security.SecureClassLoader.defineClass(Unknown Source) org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1847) org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:873) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1326) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1205) org.apache.cxf.common.classloader.ClassLoaderUtils.loadClass(ClassLoaderUtils.java:111) org.apache.cxf.jaxws.spring.EndpointDefinitionParser.loadImplementor(EndpointDefinitionParser.java:132) org.apache.cxf.jaxws.spring.EndpointDefinitionParser.doParse(EndpointDefinitionParser.java:86) org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:70) org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:56) org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69) org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1114) org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1104) org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:133) org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:90) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:458) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:353) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) org.apache.cxf.transport.servlet.CXFServlet.loadAdditionalConfig(CXFServlet.java:201) org.apache.cxf.transport.servlet.CXFServlet.loadSpringBus(CXFServlet.java:171) org.apache.cxf.transport.servlet.CXFServlet.init(CXFServlet.java:98) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) java.lang.Thread.run(Unknown Source)
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 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 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 . . . sorry, forgot to mention that.
Any other suggestions?
On Oct 27, 2007, at 11:37 PM, Willem2 wrote:
Hi,
It may relate to the Xerces Implementation.
CXF can work with xecesImpl 2.8.1 , please make sure this jar is in
your
class path.
Willem.
jwagon wrote:
I'm trying to get a simple service client running against the
following
WSDL:
I used SoapUI 1.7.6 to generate the service classes, one of which
is this:
@WebServiceClient(name = api, targetNamespace =
http://api.bronto.com;, wsdlLocation =
http://api.bronto.com/?q=mail_3wsdl;)
public class Api extends Service {
private final static URL WSDL_LOCATION;
private final static QName SERVICE = new
QName(http://api.bronto.com;, api);
private final static QName ApiPort = new
QName(http://api.bronto.com;, apiPort);
static {
URL url = null;
try {
url = new URL(http://api.bronto.com/?q=mail_3wsdl;);
} catch (MalformedURLException e) {
System.err.println(Can not initialize the default wsdl
from http://api.bronto.com/?q=mail_3wsdl;);
// e.printStackTrace();
}
WSDL_LOCATION = url;
}
public Api(URL wsdlLocation, QName serviceName) {
super(wsdlLocation, serviceName);
}
public Api() {
super(WSDL_LOCATION, SERVICE);
}
/**
*
* @return
* returns ApiPort
*/
@WebEndpoint(name = apiPort)
public ApiPortType getApiPort() {
return (ApiPortType)super.getPort(ApiPort,
ApiPortType.class);
}
}
But when I execute the following code in a brand new Grails app
(Grails 0.6, Groovy 1.1b):
I get the error below. Not even where to start looking to solve this
one (except Google, which I already tried). Any suggestions?
org.codehaus.groovy.runtime.InvokerInvocationException:
java.lang.RuntimeException:
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in
class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean
failed; nested exception is
org.springframework.beans.BeanInstantiationException: Could not
instantiate bean class [org.apache.cxf.wsdl11.WSDLManagerImpl]:
Constructor threw exception; nested exception is
java.lang.ClassCastException:
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
at
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:64)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelper.java:678)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:689)
at
groovy.lang.ExpandoMetaClass.invokeMethod(ExpandoMetaClass.java:894)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:531)
at groovy.lang.Closure.call(Closure.java:290)
at groovy.lang.Closure.call(Closure.java:285)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.handleAction(SimpleGrailsControllerHelper.java:526)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.executeAction(SimpleGrailsControllerHelper.java:385)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.handleURI(SimpleGrailsControllerHelper.java:240)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsControllerHelper.handleURI(SimpleGrailsControllerHelper.java:152)
at
org.codehaus.groovy.grails.web.servlet.mvc.SimpleGrailsController.handleRequest(SimpleGrailsController.java:88)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:45)
at
org.codehaus.groovy.grails.web.servlet.GrailsDispatcherServlet.doDispatch(GrailsDispatcherServlet.java:241)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:755)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:396)
at
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:350)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
--
View this message in
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, 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 Method) java.lang.ClassLoader.defineClass(Unknown Source) java.security.SecureClassLoader.defineClass(Unknown Source) org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1847) org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:873) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1326) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1205) org.apache.cxf.common.classloader.ClassLoaderUtils.loadClass(ClassLoaderUtils.java:111) org.apache.cxf.jaxws.spring.EndpointDefinitionParser.loadImplementor(EndpointDefinitionParser.java:132) org.apache.cxf.jaxws.spring.EndpointDefinitionParser.doParse(EndpointDefinitionParser.java:86) org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:70) org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:56) org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69) org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1114) org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1104) org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:133) org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:90) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:458) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:353) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) org.apache.cxf.transport.servlet.CXFServlet.loadAdditionalConfig(CXFServlet.java:201) org.apache.cxf.transport.servlet.CXFServlet.loadSpringBus(CXFServlet.java:171) org.apache.cxf.transport.servlet.CXFServlet.init(CXFServlet.java:98) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) java.lang.Thread.run(Unknown Source) -- View this message in context: http://www.nabble.com/Error-accessing-my-newly-develop-services-tf4729713.html#a13525655 Sent from the cxf-user mailing list archive at Nabble.com.
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 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 give your some points from my view. [1]https://issues.apache.org/jira/browse/CXF-341 Willem. Christian Vest Hansen wrote: We're planning on exposing a number of web services through HTTPS, however, many of the WSDLs will refer to and import schema files that we have stored in a central repository - and this repository is accessed through ordinary HTTP. In other words, our clients access a WSDL through HTTPS - this WSDL has references to a schema that the client has to access through plain HTTP. Will this cause any problems with HTTPConduits and other configurations that clients will have in order to access the otherwise HTTPS enabled web service? -- Venlig hilsen / Kind regards, Christian Vest Hansen.
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 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 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 give your some points from my view. [1]https://issues.apache.org/jira/browse/CXF-341 Willem. Christian Vest Hansen wrote: We're planning on exposing a number of web services through HTTPS, however, many of the WSDLs will refer to and import schema files that we have stored in a central repository - and this repository is accessed through ordinary HTTP. In other words, our clients access a WSDL through HTTPS - this WSDL has references to a schema that the client has to access through plain HTTP. Will this cause any problems with HTTPConduits and other configurations that clients will have in order to access the otherwise HTTPS enabled web service?
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: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: Null object passed into Dispatch marshalling at org.apache.cxf.jaxws.interceptors.DispatchOutDatabindingInterceptor.handleMessage(DispatchOutDatabindingInterceptor.java:94) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:74) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:235) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:140) at org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:278) at org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:256) at javax.servlet.http.HttpServlet.service(HttpServlet.java:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:820) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) It never reaches my code, so I assume this is either a bug in CXF or an incorrect configuration on my part. Any ideas?
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 matching wildcard is strict, but no declaration can be found for element jaxws.endpoint I sure dont know what I did to break these but I am in a real bind, if anyone could tell me what to do to fix this I would really appreciate it. For reference here is my beans.xml file that eclipse complains about: beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:jaxws=http://cxf.apache.org/jaxws; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd; import resource=classpath:META-INF/cxf/cxf.xml / import resource=classpath:META-INF/cxf/cxf-extension-soap.xml / import resource=classpath:META-INF/cxf/cxf-servlet.xml / jaxws:endpoint id=helloWorld implementor=#helloWorldBean address=/HelloWorld /jaxws:endpoint /beans Please help, Thanks in advance. Troy
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). In my applicationBeans.xml I get the message : the matching wildcard is strict, but no declaration can be found for element jaxws.endpoint I sure dont know what I did to break these but I am in a real bind, if anyone could tell me what to do to fix this I would really appreciate it. For reference here is my beans.xml file that eclipse complains about: beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:jaxws=http://cxf.apache.org/jaxws; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd; import resource=classpath:META-INF/cxf/cxf.xml / import resource=classpath:META-INF/cxf/cxf-extension-soap.xml / import resource=classpath:META-INF/cxf/cxf-servlet.xml / jaxws:endpoint id=helloWorld implementor=#helloWorldBean address=/HelloWorld /jaxws:endpoint /beans Please help, Thanks in advance. Troy I just redid the example from http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html it now fails with the same error message at the step where I create beans.xml. I know this used to work because I wrote several of these that are currently deployed and working, I can not redeploy them now (it appears).
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 for handling incoming SOAP messages and continually receive this exception: Nov 1, 2007 10:59:36 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: Null object passed into Dispatch marshalling at org.apache.cxf.jaxws.interceptors.DispatchOutDatabindingInterceptor.handleMessage(DispatchOutDatabindingInterceptor.java:94) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:74) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:235) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:140) at org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:278) at org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:256) at javax.servlet.http.HttpServlet.service(HttpServlet.java:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:820) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) It never reaches my code, so I assume this is either a bug in CXF or an incorrect configuration on my part. Any ideas?
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 subversion and I can no longer build them (in eclipse). In my applicationBeans.xml I get the message : the matching wildcard is strict, but no declaration can be found for element jaxws.endpoint I sure dont know what I did to break these but I am in a real bind, if anyone could tell me what to do to fix this I would really appreciate it. For reference here is my beans.xml file that eclipse complains about: beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:jaxws=http://cxf.apache.org/jaxws; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd; import resource=classpath:META-INF/cxf/cxf.xml / import resource=classpath:META-INF/cxf/cxf-extension-soap.xml / import resource=classpath:META-INF/cxf/cxf-servlet.xml / jaxws:endpoint id=helloWorld implementor=#helloWorldBean address=/HelloWorld /jaxws:endpoint /beans Please help, Thanks in advance. Troy -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
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, Todd Orr wrote: 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 for handling incoming SOAP messages and continually receive this exception: Nov 1, 2007 10:59:36 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: Null object passed into Dispatch marshalling at org.apache.cxf.jaxws.interceptors.DispatchOutDatabindingInterceptor. handleMessage(DispatchOutDatabindingInterceptor.java:94) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercep torChain.java:207) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(Ou tgoingChainInterceptor.java:74) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercep torChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInit iationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(Servle tDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination (ServletController.java:235) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletCon troller.java:140) at org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:2 78) at org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:2 56) at javax.servlet.http.HttpServlet.service(HttpServlet.java:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:42 8) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicat ionHandler.java:473) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicatio nContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:820) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java :245) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) It never reaches my code, so I assume this is either a bug in CXF or an incorrect configuration on my part. Any ideas? -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
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 service such as:
public void queue(Job job);
where there exists the following classes:
public class BigJob extends Job { ... }
public class SmallJob extends Job {...}
In this case, Job will be bound to XML elements, but BigJob and SmallJob
will not. XFire does support this, documented at
http://xfire.codehaus.org/Aegis+Inheritance. However, I cannot find a
similar piece of documentation on porting this solution to CXF. It
seems as if the support is all still there but not necessarily exposed
(see http://cwiki.apache.org/CXF20DOC/aegis-theory-of-operation.html).
I have played around with a few things in my Spring configuration, such
as adding something like this to my ServiceFactoryBean:
bean id='jaxws-and-aegis-service-factory'
class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean
...
property name=properties
map
entry key=writeXsiType
value type=java.lang.Booleantrue/value
/entry
entry key=overrideTypesList
list
valuecom.foo.bar.BigJob/value
valuecom.foo.bar.SmallJob/value
/list
/entry
/map
/property
...
/bean
This deploys without error, but my WSDL and corresponding stubs do not
include the overridden types. Any ideas?
Thanks!
Jeff
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
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 service such as:
public void queue(Job job);
where there exists the following classes:
public class BigJob extends Job { ... }
public class SmallJob extends Job {...}
In this case, Job will be bound to XML elements, but BigJob and
SmallJob
will not. XFire does support this, documented at
http://xfire.codehaus.org/Aegis+Inheritance. However, I cannot find a
similar piece of documentation on porting this solution to CXF. It
seems as if the support is all still there but not necessarily exposed
(see http://cwiki.apache.org/CXF20DOC/aegis-theory-of-operation.html).
I have played around with a few things in my Spring configuration,
such
as adding something like this to my ServiceFactoryBean:
bean id='jaxws-and-aegis-service-factory'
class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean
...
property name=properties
map
entry key=writeXsiType
value type=java.lang.Booleantrue/value
/entry
entry key=overrideTypesList
list
valuecom.foo.bar.BigJob/value
valuecom.foo.bar.SmallJob/value
/list
/entry
/map
/property
...
/bean
This deploys without error, but my WSDL and corresponding stubs do not
include the overridden types. Any ideas?
Thanks!
Jeff
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 improvement to Java First Approach (include Aegis binding support!). If anyone to try it out, go ahead to Eclipse STP site and try it. Cheers, Bo [1] http://wiki.eclipse.org/STP_Service_Creation_getting_started_guide_for_stp_0.7 [2] https://issues.apache.org/jira/browse/CXF-1165 On 11/2/07, Christian Schneider [EMAIL PROTECTED] wrote: Hi, I have switched the index page to the new content. To keep consistency I think we should also change the navigation page. Like with the Index page I have added a new Wiki page for discussion: http://cwiki.apache.org/confluence/display/CXF20DOC/Navigation+New I have already synced to page to the Index structure. What do you think? Best regards Christian Daniel Kulp schrieb: +1 to making the switch. Dan
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 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 matching wildcard is strict, but no declaration can be found for element jaxws.endpoint I sure dont know what I did to break these but I am in a real bind, if anyone could tell me what to do to fix this I would really appreciate it. For reference here is my beans.xml file that eclipse complains about: beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:jaxws=http://cxf.apache.org/jaxws; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd; import resource=classpath:META-INF/cxf/cxf.xml / import resource=classpath:META-INF/cxf/cxf-extension-soap.xml / import resource=classpath:META-INF/cxf/cxf-servlet.xml / jaxws:endpoint id=helloWorld implementor=#helloWorldBean address=/HelloWorld /jaxws:endpoint /beans Please help, Thanks in advance. Troy I just redid the example from http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html it now fails with the same error message at the step where I create beans.xml. I know this used to work because I wrote several of these that are currently deployed and working, I can not redeploy them now (it appears).
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 have in 2.0.3, @XmlElement can't control the form, only the namespace. That's kind of the point.If @XmlElement is not there or if the namespace attribute is unspecified, it uses the namespace information from the package-info which is should be whatever from the default is for the schema. If the element in the schema has a form that doesn't match the default, jaxb will output either: 1) @XmlElement(namespace = ) (unqualified) 2) @XmlElement(namespace = http://blah.blah.blah;) (qualified, namespace will match the schema namespace) Dan -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 3:10 PM To: cxf-user@incubator.apache.org Cc: Benson Margulies Subject: Re: form attribute on xsd:element versus jaxb Actually, I think if the form doesn't equal the schema form, it outputs the @XmlElement annotation with the proper namespace attribute. If it does agree, it doesn't. Something like that at least. Dan On Monday 29 October 2007, Benson Margulies wrote: So far as I can see, JAXB has no place to annotate an element that has a form= that disagrees with the schema default. Should wsdl2java complain when someone feeds it such a schema? I just tried it with the current 2.0.3 snapshot, and no error emerged. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
