cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Oster (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CXF-2419) WSDL2Java -allowElementReferences causes fatal errors in operation dispatching
Date Wed, 02 Sep 2009 15:17:32 GMT

     [ https://issues.apache.org/jira/browse/CXF-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Scott Oster updated CXF-2419:
-----------------------------

    Attachment: wsdl_first_element_ref_withflag.zip
                wsdl_first_element_ref_noflag.zip

The wsdl_first_element_ref_noflag.zip is the wsdl_first sample modified from the 2.2.3 release
to have the WSDL make use of an element reference, which (without passing the -allowElementReferences
flag) will cause the greetMe operation to be BARE style.  This zip file is a working project
with this modification (server and client updated to BARE methods).

The wsdl_first_element_ref_withflag.zip is the same project, but WSDL2Java was run passing
the -allowElementReferences flag (by modifying the common_build.xml call to wsdl2java [not
included]), which will cause the greetMe operation to be WRAPPED style.  Running this project
causes the reported exception to be raised when the greetMe operation is invoked.

> WSDL2Java -allowElementReferences causes fatal errors in operation dispatching
> ------------------------------------------------------------------------------
>
>                 Key: CXF-2419
>                 URL: https://issues.apache.org/jira/browse/CXF-2419
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.2.3, 2.3
>            Reporter: Scott Oster
>            Priority: Critical
>         Attachments: wsdl_first_element_ref_noflag.zip, wsdl_first_element_ref_withflag.zip
>
>
> If I make use of local element references in WSDL, and run WSDL2Java passing the -allowElementReferences
flag, the code all gets properly generated with appropriate unwrapping, however, the service
does not work as the exchange is unable to locate the appropriate method in the implementation.
 The following error is generated whenever a method using element references is invokved:
> Sep 2, 2009 11:04:57 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept
> WARNING: Application has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: null while invoking <null> with params [oster].
> 	at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:152)
> 	at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJAXWSMethodInvoker.java:83)
> 	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:126)
> 	at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:55)
> 	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:68)
> 	at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 	at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> 	at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:98)
> 	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
> 	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:104)
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:302)
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:266)
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:326)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
> Caused by: java.lang.NullPointerException
> 	at org.apache.cxf.service.invoker.AbstractInvoker.insertExchange(AbstractInvoker.java:171)
> 	at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:160)
> 	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:82)
> 	... 24 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message