[jira] Updated: (CXF-2936) NullPointerException in ServerImpl combining JAX-RS and Simple Frontend
[
https://issues.apache.org/jira/browse/CXF-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-2936:
Summary: NullPointerException in ServerImpl combining JAX-RS and Simple
Frontend (was: NullPointerException at )
> NullPointerException in ServerImpl combining JAX-RS and Simple Frontend
> ---
>
> Key: CXF-2936
> URL: https://issues.apache.org/jira/browse/CXF-2936
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.2.9
> Environment: Windows 7 64-Bit, Java 1.6.0_17, Jetty 7.0.0.pre5
>Reporter: Dennis Kieselhorst
>Priority: Critical
>
> After adding JAXRS to an existing CXF webservice application (using simple
> frontend) the startup fails with a NPE in ServerImpl:
> {noformat}
> 2010-08-11 10:07:26.980::WARN: Failed startup of context
> org.mortbay.jetty.plugin.jetty6pluginwebappcont...@608925b0
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name
> 'org.apache.cxf.jaxrs.spring.JAXRSServerFactoryBeanDefinitionParser$SpringJAXRSServerFactoryBean---47367291':
> Invocation of init method failed;
> nested exception is
> org.apache.cxf.service.factory.ServiceConstructionException
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1412)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:574)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
> at
> org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
> at
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
> at
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:579)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:156)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1215)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:548)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:348)
> at
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:107)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:222)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:384)
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:320)
> at
> org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:205)
> at
> org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
> at
[jira] Created: (CXF-2936) NullPointerException at
NullPointerException at
Key: CXF-2936
URL: https://issues.apache.org/jira/browse/CXF-2936
Project: CXF
Issue Type: Bug
Components: JAX-RS
Affects Versions: 2.2.9
Environment: Windows 7 64-Bit, Java 1.6.0_17, Jetty 7.0.0.pre5
Reporter: Dennis Kieselhorst
Priority: Critical
After adding JAXRS to an existing CXF webservice application (using simple
frontend) the startup fails with a NPE in ServerImpl:
{noformat}
2010-08-11 10:07:26.980::WARN: Failed startup of context
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@608925b0
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name
'org.apache.cxf.jaxrs.spring.JAXRSServerFactoryBeanDefinitionParser$SpringJAXRSServerFactoryBean---47367291':
Invocation of init method failed;
nested exception is org.apache.cxf.service.factory.ServiceConstructionException
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1412)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:574)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
at
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:579)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:156)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1215)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:548)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:348)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:107)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:384)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:320)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:205)
at
org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apa
Re: Can't find the request for service's Observer
You have: The createdFromAPI means at some point, you will be calling Endpoint.publish to publish it. Are you? If not, I would remove that and add an address attribute of something like "/myservice" or similar so CXF will publish it at startup. Dan On Tuesday 10 August 2010 7:48:10 am Amit Rathi wrote: > Hi, I have developed a web service using CXF2.2.8, when I deployed it on > web logic application server & try to access the WSDL url in IE its > throwing exception. Below are the various files I am using. Kindly help > me, its urgent. Let me know if you need anything more from my side. > > cxf.xml > --- > --- > --- xmlns="http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:jaxws="http://cxf.apache.org/jaxws"; > xmlns:context="http://www.springframework.org/schema/context"; > xsi:schemaLocation=" > HYPERLINK > "http://www.springframework.org/schema/beans"http://www.springframework.or > g/schema/beanshttps://issues.apache.org/jira/images/icons/linkext7.gif > HYPERLINK > "http://www.springframework.org/schema/beans/spring-beans.xsd"http://www.s > pringframework.org/schema/beans/spring-beans.xsdhttps://issues.apache.org/j > ira/images/icons/linkext7.gif HYPERLINK > "http://www.springframework.org/schema/context"http://www.springframework. > org/schema/contexthttps://issues.apache.org/jira/images/icons/linkext7.gif > HYPERLINK > "http://www.springframework.org/schema/context/spring-context-2.5.xsd"http > ://www.springframework.org/schema/context/spring-context-2.5.xsdhttps://iss > ues.apache.org/jira/images/icons/linkext7.gif"> > > > > class="org.apache.cxf.bus.spring.BusApplicationListener"/> id="org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor" > class="org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor"/> > class="org.apache.cxf.bus.spring.Jsr250BeanPostProcessor"/> id="org.apache.cxf.bus.spring.BusExtensionPostProcessor" > class="org.apache.cxf.bus.spring.BusExtensionPostProcessor"/> > > class="org.apache.cxf.bus.resource.ResourceManagerImpl"> name="resolvers"> > > > > class="org.apache.cxf.bus.spring.BusApplicationContextResourceResolver"/> > > > > > class="org.apache.cxf.configuration.spring.ConfigurerImpl"> > > > class="org.apache.cxf.binding.BindingFactoryManagerImpl"> name="mapProvider"> > > > > > > > > > class="org.apache.cxf.transport.DestinationFactoryManagerImpl"> name="mapProvider"> > > > > > > > > > class="org.apache.cxf.transport.ConduitInitiatorManagerImpl"> name="mapProvider"> > > > > > > > > > class="org.apache.cxf.wsdl11.WSDLManagerImpl"> ref="cxf"/> > > > class="org.apache.cxf.phase.PhaseManagerImpl"> > > > > class="org.apache.cxf.workqueue.WorkQueueManagerImpl"> name="bus" ref="cxf"/> > > > class="org.apache.cxf.buslifecycle.CXFBusLifeCycleManager"> name="bus" ref="cxf"/> > > > class="org.apache.cxf.endpoint.ServerRegistryImpl"> ref="cxf"/> > > > class="org.apache.cxf.endpoint.ServerLifeCycleManagerImpl"/> id="org.apache.cxf.endpoint.ClientLifeCycleManager" > class="org.apache.cxf.endpoint.ClientLifeCycleManagerImpl"/> > > class="org.apache.cxf.transport.http.QueryHandlerRegistryImpl"> name="bus" ref="cxf"/> > > > > > > > > > > class="org.apache.cxf.endpoint.EndpointResolverRegistryImpl"> name="bus" ref="cxf"/> > > class="org.apache.cxf.headers.HeaderManagerImpl"> ref="cxf"/> > > class="org.apache.cxf.catalog.OASISCatalogManager"> ref="cxf"/> > > > class="org.apache.cxf.endpoint.ServiceContractResolverRegistryImpl"> > > > > createdFromAPI="true"> > > > > > > wsdlLocation="wsdl/GetWFPProfileInfoService.wsdl" > createdFromAPI="true"> > > > > > > createdFromAPI="true"> > > > > > > wsdlLocation="wsdl/GetSoftwareAssetInfoService.wsdl" > createdFromAPI="true"> > > > > > > > --- > --- > --- > > > > cxf-servlet.xml > --- > --- > --- xmlns="http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:foo="http://cxf.apache.org/configuration/foo"; > xsi:schemaLocation=" > HYPERLINK > "http://www.springframework.org/schema/beans"http://www.springframework.or > g/schema/beanshttps://issues.apache.org/jira/images/icons/linkext7.gif > HYPERLINK > "http://www.springframework.org/schema/beans/spring-beans.xsd"http://www.s > pringframework.org/sche
[jira] Resolved: (CXF-2898) Support jetty version 7
[ https://issues.apache.org/jira/browse/CXF-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2898. -- Fix Version/s: 2.3 Resolution: Fixed > Support jetty version 7 > --- > > Key: CXF-2898 > URL: https://issues.apache.org/jira/browse/CXF-2898 > Project: CXF > Issue Type: Improvement > Components: Transports >Affects Versions: 2.2.9 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.3 > > Attachments: CXF-2898-2.diff, CXF-2898.diff > > > It would be convenient to be able to use jetty 7. I think that this requires > a new transport, since the dependency structure is changed, so I don't see an > easy way to make a single transport module do both. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CXF-2384) SOAPFaultExcption thrown instead of a WebServiceException
[
https://issues.apache.org/jira/browse/CXF-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niek Palm reopened CXF-2384:
I test the solution against 2.2.7 and 2.2.9, it seems still not fixed.
I test the the solution by calling a not running service. We still get a
SOAPFaultException which means that there is a SOAPFault. Since the service
cannot be called there is no SOAPFault. The correct solution should be throw an
exception that is a instance of WebServiceException based on a
ConnectionException in stead of throwing an SOAPFaultException based on a
ConnectionException.
So here a CXF code snippet.
class: org.apache.cxf.jaxws.DispatchImpl
...
private RuntimeException mapException(Exception ex) {
if (ex instanceof Fault && ex.getCause() instanceof IOException) {
throw new WebServiceException(ex.getMessage(), ex.getCause());
}
should be changed to some like:
...
private RuntimeException mapException(Exception ex) {
if (ex instanceof Fault && (ex.getCause() instanceof IOException ||
ex.getCause() instanceof ConnectionException)) {
throw new WebServiceException(ex.getMessage(), ex.getCause());
}
Maybe there is no need (anymore to check against an IOExcption
> SOAPFaultExcption thrown instead of a WebServiceException
> -
>
> Key: CXF-2384
> URL: https://issues.apache.org/jira/browse/CXF-2384
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.2
> Environment: jdk1.6, ubuntu 9.10
>Reporter: Niek Palm
>Assignee: Daniel Kulp
> Fix For: 2.2.7
>
>
> When the connection of the webservice is lost we get a SoapFaultException
> instead of of a WebServiceException. We use the dispachter in the following
> way:
>
> Service service = Service.create(SERVICE_NAME);
> service.addPort(PORT_NAME, SOAPBinding.SOAP11HTTP_BINDING,
> url.toString());
> Dispatch dispatch = service.createDispatch(PORT_NAME,
> SOAPMessage.class, Service.Mode.MESSAGE);
> SOAPMessage response = dispatch.invoke(request);
> Looking in the API
> (http://java.sun.com/javase/6/docs/api/javax/xml/ws/Dispatch.html#invoke(T)),
> there is specified that any communication problem will cause in a
> WebServiceException. To our point of view this is a bug in cxf.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2937) character encoding in cxf-codegen is wrong
character encoding in cxf-codegen is wrong -- Key: CXF-2937 URL: https://issues.apache.org/jira/browse/CXF-2937 Project: CXF Issue Type: Bug Components: Tooling Affects Versions: 2.2.9 Environment: windows, sun java 6 Reporter: Martin Goldhahn Fix For: 2.2.10 We develop on linux and Windows concurrently. Therefor we choose to use UTF-8 as source ancoding. We also set the property project.build.sourceEncoding in maven to utf-8. Further we have a utf-8 encoded WSDL with some comments in Norwegian (containing letters like åæø). On Windows the generated code contains these characters as ISO-8859-1 even though I set -Dfile.encoding=utf-8 on the maven command line. A workaround is to set the property project.build.sourceEncoding in a maven profile and activate it by OS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2937) character encoding in cxf-codegen is wrong
[ https://issues.apache.org/jira/browse/CXF-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Goldhahn updated CXF-2937: - Description: We develop on linux and Windows concurrently. Therefor we choose to use UTF-8 as source encoding. We also set the property project.build.sourceEncoding in maven to utf-8. Further we have a utf-8 encoded WSDL with some comments in Norwegian (containing letters like åæø). On Windows the generated code contains these characters as ISO-8859-1 even though I set -Dfile.encoding=utf-8 on the maven command line. A workaround is to set the property project.build.sourceEncoding in a maven profile and activate it by OS. was: We develop on linux and Windows concurrently. Therefor we choose to use UTF-8 as source ancoding. We also set the property project.build.sourceEncoding in maven to utf-8. Further we have a utf-8 encoded WSDL with some comments in Norwegian (containing letters like åæø). On Windows the generated code contains these characters as ISO-8859-1 even though I set -Dfile.encoding=utf-8 on the maven command line. A workaround is to set the property project.build.sourceEncoding in a maven profile and activate it by OS. > character encoding in cxf-codegen is wrong > -- > > Key: CXF-2937 > URL: https://issues.apache.org/jira/browse/CXF-2937 > Project: CXF > Issue Type: Bug > Components: Tooling >Affects Versions: 2.2.9 > Environment: windows, sun java 6 >Reporter: Martin Goldhahn > Fix For: 2.2.10 > > > We develop on linux and Windows concurrently. Therefor we choose to use UTF-8 > as source encoding. We also set the property project.build.sourceEncoding in > maven to utf-8. > Further we have a utf-8 encoded WSDL with some comments in Norwegian > (containing letters like åæø). On Windows the generated code contains these > characters as ISO-8859-1 even though I set -Dfile.encoding=utf-8 on the maven > command line. > A workaround is to set the property project.build.sourceEncoding in a maven > profile and activate it by OS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2919) NullPointerException at org.apache.cxf.staxutils.StaxUtils.writeNode(Node, XMLStreamWriter, boolean) when DOCTYPE is in a XML Schema
[
https://issues.apache.org/jira/browse/CXF-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2919.
--
Assignee: Daniel Kulp
Fix Version/s: 2.2.10
Resolution: Fixed
Added a null guard
> NullPointerException at org.apache.cxf.staxutils.StaxUtils.writeNode(Node,
> XMLStreamWriter, boolean) when DOCTYPE is in a XML Schema
>
>
> Key: CXF-2919
> URL: https://issues.apache.org/jira/browse/CXF-2919
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.9
>Reporter: Mauro Molinari
>Assignee: Daniel Kulp
>Priority: Critical
> Fix For: 2.2.10
>
>
> Following a contract first approach, if I expose a WSDL which imports a XSD
> with a DOCTYPE declaration, for instance:
>
> "http://www.w3.org/2001/XMLSchema.dtd";>
>
> http://www.w3.org/2001/XMLSchema"; [...]>
> then, when invoking the CXFServlet to show this XSD I get the following
> exception:
> java.lang.NullPointerException
> at
> com.sun.xml.internal.stream.writers.UTF8OutputStreamWriter.write(UTF8OutputStreamWriter.java:127)
> at
> com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeDTD(XMLStreamWriterImpl.java:722)
> at org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:775)
> at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:600)
> at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:588)
> at org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:762)
> at
> org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:230)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:162)
> at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:619)
> This is because org.apache.cxf.staxutils.StaxUtils.writeNode(Node,
> XMLStreamWriter, boolean) does the following for a Node of type
> DOCUMENT_TYPE_NODE:
> try {
> writer.writeDTD(((DocumentType)n).getTextContent());
> } catch (UnsupportedOperationException ex) {
> //can we ignore? DOM writers really don't allow this
> //as there isn't a way to write a DTD in dom
> }
> However, org.w3c.dom.Node.getTextContent() by contract returns NULL for a
> Node of type DOCUMENT_TYPE_NODE. This causes the NPE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2384) SOAPFaultExcption thrown instead of a WebServiceException
[ https://issues.apache.org/jira/browse/CXF-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897362#action_12897362 ] Daniel Kulp commented on CXF-2384: -- You'll probably need to provide a full test case. If you see the test that was added for this: http://svn.apache.org/viewvc/cxf/trunk/systests/jaxws/src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java?view=markup (line 128) you can see it specifically asserts that it's not a SOAPFaultException. > SOAPFaultExcption thrown instead of a WebServiceException > - > > Key: CXF-2384 > URL: https://issues.apache.org/jira/browse/CXF-2384 > Project: CXF > Issue Type: Bug >Affects Versions: 2.2.2 > Environment: jdk1.6, ubuntu 9.10 >Reporter: Niek Palm >Assignee: Daniel Kulp > Fix For: 2.2.7 > > > When the connection of the webservice is lost we get a SoapFaultException > instead of of a WebServiceException. We use the dispachter in the following > way: > > Service service = Service.create(SERVICE_NAME); > service.addPort(PORT_NAME, SOAPBinding.SOAP11HTTP_BINDING, > url.toString()); > Dispatch dispatch = service.createDispatch(PORT_NAME, > SOAPMessage.class, Service.Mode.MESSAGE); > SOAPMessage response = dispatch.invoke(request); > Looking in the API > (http://java.sun.com/javase/6/docs/api/javax/xml/ws/Dispatch.html#invoke(T)), > there is specified that any communication problem will cause in a > WebServiceException. To our point of view this is a bug in cxf. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Can't find the request for service's Observer
On Wednesday 11 August 2010 9:14:07 am Amit Rathi wrote: > Hi Dan, > > I did the same & it's working fine now. I am able to see the WSDL in the > browser. The generated WSDL shows the complete content of > referred(imported) xsd's. Just one clarification, is there any > configuration by which generated wsdl doesn't show the content of referred > xsd & just show the import statement. In general, no. Not right now. With your config, however, it should be using the wsdl you have configured in your jaxws:endpoint. Thus, if it has imports, it should be using them. > There is one issue. When I tried to test this using SOAPUI 1.7.6, its > failing with the below error > > Issue1 with soapUI: Tue Aug 10 16:10:51 EDT 2010:ERROR:An error occured > [https://localhost:32253/xyzservices/services/GetSoftwareAssetInfoService? > wsdl:0: error: src-resolve: attribute > 'mediat...@http://service.xyz.com/provider/xyzservices/NameANDAddress/x200 > 4/' not found.], see error log for details No idea. We'd probably need to see the wsdl and imports and such. Dan > > > I am not getting what is the exact problem. > > Kindly suggest. > > Thanks & Regards > Amit > > -Original Message- > From: Daniel Kulp [mailto:dk...@apache.org] > Sent: Wednesday, August 11, 2010 4:13 PM > To: us...@cxf.apache.org > Cc: Amit Rathi; issues@cxf.apache.org; eca.amitra...@gmail.com > Subject: Re: Can't find the request for service's Observer > > > You have: > > wsdlLocation="wsdl/GetSoftwareAssetInfoService.wsdl" > createdFromAPI="true"> > > > The createdFromAPI means at some point, you will be calling > Endpoint.publish to publish it. Are you? If not, I would remove that and > add an address attribute of something like "/myservice" or similar so CXF > will publish it at startup. > > Dan > > On Tuesday 10 August 2010 7:48:10 am Amit Rathi wrote: > > Hi, I have developed a web service using CXF2.2.8, when I deployed it on > > web logic application server & try to access the WSDL url in IE its > > throwing exception. Below are the various files I am using. Kindly help > > me, its urgent. Let me know if you need anything more from my side. > > > > cxf.xml > > - > > -- > > > > --- --- > xmlns="http://www.springframework.org/schema/beans"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xmlns:jaxws="http://cxf.apache.org/jaxws"; > > xmlns:context="http://www.springframework.org/schema/context"; > > xsi:schemaLocation=" > > HYPERLINK > > "http://www.springframework.org/schema/beans"http://www.springframework.o > > r g/schema/beanshttps://issues.apache.org/jira/images/icons/linkext7.gif > > HYPERLINK > > "http://www.springframework.org/schema/beans/spring-beans.xsd"http://www. > > s > > pringframework.org/schema/beans/spring-beans.xsdhttps://issues.apache.or > > g/j ira/images/icons/linkext7.gif HYPERLINK > > "http://www.springframework.org/schema/context"http://www.springframework > > . > > org/schema/contexthttps://issues.apache.org/jira/images/icons/linkext7.g > > if HYPERLINK > > "http://www.springframework.org/schema/context/spring-context-2.5.xsd"htt > > p > > > > ://www.springframework.org/schema/context/spring-context-2.5.xsdhttps://i > > :ss > > > > ues.apache.org/jira/images/icons/linkext7.gif"> > > > > > > > > > class="org.apache.cxf.bus.spring.BusApplicationListener"/> > id="org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor" > > class="org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor"/> > > > class="org.apache.cxf.bus.spring.Jsr250BeanPostProcessor"/> > id="org.apache.cxf.bus.spring.BusExtensionPostProcessor" > > class="org.apache.cxf.bus.spring.BusExtensionPostProcessor"/> > > > > > class="org.apache.cxf.bus.resource.ResourceManagerImpl"> > name="resolvers"> > > > > > > > > > class="org.apache.cxf.bus.spring.BusApplicationContextResourceResolver"/> > > > > > > > > > > > class="org.apache.cxf.configuration.spring.ConfigurerImpl"> > > > > > > > class="org.apache.cxf.binding.BindingFactoryManagerImpl"> > name="mapProvider"> > > > > > > > > > > > > > > > > > > > class="org.apache.cxf.transport.DestinationFactoryManagerImpl"> > name="mapProvider"> > > > > > value="org.apache.cxf.transport.DestinationFactory"/> > name="idsProperty" value="transportIds"/> > > > > > > > > > > > > > class="org.apache.cxf.transport.ConduitInitiatorManagerImpl"> > name="mapProvider"> > > > > > > > > > > > > > > > > > > > class="org.apache.cxf.wsdl11.WSDLManagerImpl"> > ref="cxf"/> > > > > > > > class="org.apache.cxf.phase.PhaseManagerImpl"> > > > > > > > > > class="org.apache.cxf.workqueue.WorkQueueManagerImpl"> > name="bus" ref="cxf"/> > > > > > > > class="org.apache.cxf.buslifecycle.CXFBusLifeCycleManager"> > name="bus" ref="cxf"/> >
[jira] Commented: (CXF-2936) NullPointerException in ServerImpl combining JAX-RS and Simple Frontend
[
https://issues.apache.org/jira/browse/CXF-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897549#action_12897549
]
Daniel Kulp commented on CXF-2936:
--
Can you create a sample for this? The above is really not much to go on.
> NullPointerException in ServerImpl combining JAX-RS and Simple Frontend
> ---
>
> Key: CXF-2936
> URL: https://issues.apache.org/jira/browse/CXF-2936
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.2.9
> Environment: Windows 7 64-Bit, Java 1.6.0_17, Jetty 7.0.0.pre5
>Reporter: Dennis Kieselhorst
>Priority: Critical
>
> After adding JAXRS to an existing CXF webservice application (using simple
> frontend) the startup fails with a NPE in ServerImpl:
> {noformat}
> 2010-08-11 10:07:26.980::WARN: Failed startup of context
> org.mortbay.jetty.plugin.jetty6pluginwebappcont...@608925b0
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name
> 'org.apache.cxf.jaxrs.spring.JAXRSServerFactoryBeanDefinitionParser$SpringJAXRSServerFactoryBean---47367291':
> Invocation of init method failed;
> nested exception is
> org.apache.cxf.service.factory.ServiceConstructionException
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1412)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:574)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
> at
> org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
> at
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
> at
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:579)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:156)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1215)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:548)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:348)
> at
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:107)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:222)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:384)
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:320)
> at
> org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:205)
> at
> org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
> at
[jira] Resolved: (CXF-2933) Can't find the request for service's Observer
[ https://issues.apache.org/jira/browse/CXF-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2933. -- Fix Version/s: Invalid Resolution: Invalid Config issue as mentioned on the user list. > Can't find the request for service's Observer > - > > Key: CXF-2933 > URL: https://issues.apache.org/jira/browse/CXF-2933 > Project: CXF > Issue Type: Task > Components: JAX-WS Runtime >Affects Versions: 2.2.8 > Environment: Windows XP, JDK 1.6, Weblogic application server 10.3 >Reporter: amit rathi > Fix For: Invalid > > > Hi, I have developed a webservice using CXF2.2.8, when I deployed it on > weblogic application server & try to access the WSDL url in IE its throwing > exception. > Below are the various files I am using. Kindly help me, its urgent. Let me > know if you need anything more from my side. > cxf.xml > - > http://www.springframework.org/schema/beans"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xmlns:jaxws="http://cxf.apache.org/jaxws"; >xmlns:context="http://www.springframework.org/schema/context"; >xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context-2.5.xsd";> > > > class="org.apache.cxf.bus.spring.BusApplicationListener"/> > class="org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor"/> > class="org.apache.cxf.bus.spring.Jsr250BeanPostProcessor"/> > class="org.apache.cxf.bus.spring.BusExtensionPostProcessor"/> > > class="org.apache.cxf.bus.resource.ResourceManagerImpl"> > > > > > class="org.apache.cxf.bus.spring.BusApplicationContextResourceResolver"/> > > > > >class="org.apache.cxf.configuration.spring.ConfigurerImpl"> > > > class="org.apache.cxf.binding.BindingFactoryManagerImpl"> > > >value="org.apache.cxf.binding.BindingFactory"/> > > > > > > > class="org.apache.cxf.transport.DestinationFactoryManagerImpl"> > > >value="org.apache.cxf.transport.DestinationFactory"/> > > > > > > > class="org.apache.cxf.transport.ConduitInitiatorManagerImpl"> > > >value="org.apache.cxf.transport.ConduitInitiator"/> > > > > > > > class="org.apache.cxf.wsdl11.WSDLManagerImpl"> > > > > class="org.apache.cxf.phase.PhaseManagerImpl"> > > > > class="org.apache.cxf.workqueue.WorkQueueManagerImpl"> > > > > class="org.apache.cxf.buslifecycle.CXFBusLifeCycleManager"> > > > > class="org.apache.cxf.endpoint.ServerRegistryImpl"> > > > class="org.apache.cxf.endpoint.ServerLifeCycleManagerImpl"/> > class="org.apache.cxf.endpoint.ClientLifeCycleManagerImpl"/> > > class="org.apache.cxf.transport.http.QueryHandlerRegistryImpl"> > > > >class="org.apache.cxf.transport.http.WSDLQueryHandler"> > > > > > > class="org.apache.cxf.endpoint.EndpointResolverRegistryImpl"> > > > class="org.apache.cxf.headers.HeaderManagerImpl"> > > > class="org.apache.cxf.catalog.OASISCatalogManager"> > > > class="org.apache.cxf.endpoint.ServiceContractResolverRegistryImpl"> > > > > createdFromAPI="true"> > > > > > > wsdlLocation="wsdl/GetWFPProfileInfoService.wsdl" > createdFromAPI="true"> > > > > > createdFromAPI="true"> > > > > > > wsdlLocation="wsdl/GetSoftwareAssetInfoService.wsdl" > createdFromAPI="true"> > > > > > > > ---
[jira] Resolved: (CXF-2849) Update to jaxws2.2 API
[ https://issues.apache.org/jira/browse/CXF-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2849. -- Fix Version/s: 2.3 (was: 2.2.10) Resolution: Fixed trunk is passing the tck > Update to jaxws2.2 API > -- > > Key: CXF-2849 > URL: https://issues.apache.org/jira/browse/CXF-2849 > Project: CXF > Issue Type: Task > Components: JAX-WS Runtime >Reporter: jimma >Assignee: jimma > Fix For: 2.3 > > > Update the jaxws api to 2.2 . We also need to create endorsed dir for jdk1.6 > and endorse the jaxws2.2 api jar to compiler and surefire maven plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
