Hi,
I suspect your service/endpoint name for your cxf bc provider is not
match the one used in your wsdl, what's your xbean.xml for cxf bc
provider?
Freeman
On 2009-9-3, at 下午10:17, Brian Taylor wrote:
Hi,
Thanks again Freeman.
I'm calling the CXF BC Provider service from the EIP router as the
last call
in a Pipeline Route; I'm not writing any code. Everything is working
correctly until an EIP Pipeline route service makes the final In-
Only call
(and yes the Provider service is also In-Only) to this CXF BC
Provider when
it throws a NPE at line 199. It looks like the 'ei' variable is not
getting
instantiated, I assume when the SU is initialized. Attached is the
part of
the log file [1] showing the SU initialization, Abstract WSDL[2], and
Concrete WSDL[3]. Is anything unusual with it, besides having the
Binding
definition in the Abstract WSDL? If I cut the Binding out of the
Abstract
and paste it in the Concrete WSDL I get some weird error saying it
can't
parse the prolog so I've kept it like it is.
Respectfully,
Brian
[1] http://www.nabble.com/file/p25277060/Copy%2Bof%2Bservicemix.log
Copy+of+servicemix.log
[2] http://www.nabble.com/file/p25277060/FulfillmentBusinessProcess.wsdl
FulfillmentBusinessProcess.wsdl
[3] http://www.nabble.com/file/p25277060/Fulfillment-Fulfillment.wsdl
Fulfillment-Fulfillment.wsdl
Freeman Fang wrote:
Hi,
Take a look at CxfBcProviderTest[1] as an example.
[1]https://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/src/test/java/org/apache/servicemix/cxfbc/CxfBcProviderTest.java
Freeman
On 2009-9-3, at 上午5:31, Brian Taylor wrote:
Sorry to bounce this, but I'm still getting a NPE on line 199. Any
idea what
could result in the 'ei' variable becoming null?
Brian Taylor wrote:
Thanks Freeman for the quick response.
I'm attempting to route a message via the NMR to an external
service
through the CXF BC. I've configured the Provider in the BC and
placed the
WSDLs (Concrete and imported Abstract) in ServiceMix's root (I'm
unable to
get the SUs to use the <classpath> in their xbean.xml). I'm getting
a NPE
at runtime (process()) in class CxfBcProvider.java at line 199. It
appears
the ei (EndpointInformation) variable was not instantiated during
service
unit loading on ServiceMix startup.
Looking in the debug statements in the ServiceMix console upon
startup I
noticed the following lines which might be some useful indicator
but
unsure:
DEBUG - ConfigurerImpl - Could not find a definition for bean
with id
[port uri here].http-conduit - no injection will be performed
DEBUG - ConfigurerImpl - Could not find a definition for bean
with id
[service uri here] - no injection will be performed
...
DEBUG - HTTPConduit - Conduit [port uri here].http-conduit has been
configured for plain http.
...
DEBUG - CxfBcComponent - Service unit initialized
Respectfully,
Brian
Freeman Fang wrote:
Hi,
You may need take a look at the cxf-wsdl-first example shipped
with kit.
Freeman
On 2009-9-2, at 下午10:05, Brian Taylor wrote:
Does anyone know of where I can get either an example of or
instructions on
how to set up SOAP Binding in CXF for the CXF BC? I couldn't find
them on
the Apache CXF site (
http://cwiki.apache.org/CXF20DOC/configuration.html
http://cwiki.apache.org/CXF20DOC/configuration.html - Bottom of
page).
--
View this message in context:
http://www.nabble.com/CXF-BC%3A-SOAP-Binding-Example-tp25258212p25258212.html
Sent from the ServiceMix - User mailing list archive at
Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
--
View this message in context:
http://www.nabble.com/CXF-BC%3A-SOAP-Binding-Example-tp25258212p25266124.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
--
View this message in context:
http://www.nabble.com/CXF-BC%3A-SOAP-Binding-Example-tp25258212p25277060.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
