Hi Andi,
good to hear that it worked.
Sergey and I are planning to add a few more features so that some
common simple transformation can be performed in this way. If you have
some features in your mind that you would like to have, let us know.
Thanks.
regards, aki
2011/8/7 Kuhtz, Andreas
I was using 2.2.3 but changing to 2.4.0 fixed the issue. Which files
shouldn't I need to import?
Still strange though - I left the imports in beans.xml but there still
aren't any physical files anyway, are these being stepped over by CXF and
defaults applied?
-Original Message-
META-INF/cxf/cxf.xml is provided by CXF.
You can import the files with CXF 2.4.x but you don't need to import
them, as CXF switches to use other extension files which can be load
faster then spring configuration by default.
On Wed Aug 10 16:21:37 2011, David G wrote:
I was using 2.2.3 but
Hi,
In my case this is an extract of my configuration file
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-http.xml /
import resource=classpath:META-INF/cxf/cxf-extension-jaxws.xml /
import
Thanks Dan:
Yes , it is;
While mapping attachment to byte[], if attachment is big, the sun's decoder
will increase buffer and read from middle of buffer. This is corrected in
CXF-3582.
Thanks a lot
original -
Sender: Daniel Kulp [mailto:dk...@apache.org]
Date: 2011/8/9 22:13
Here's the endpoint
jaxws:endpoint
id=MyServiceRQ
name={http://www.mycompany.com/websvcs}MyServicePortType;
address=/websvc/
implementor=#myServicePortType
wsdlLocation=classpath:com/mycompany/websvcs/wsdl/MyServiceRQ.wsdl
jaxws:properties
I removed them entirely and it worked ok. Since I'm trying to put together
a bear minimum implementation without optional/distracting code or config
this is useful to know for when I want to put these back in later (as per
Prisca's recommendation).
Thanks all.
beans.xml:
--
On Wednesday, August 10, 2011 11:06:18 AM Prisca POLYTE wrote:
Hi,
In my case this is an extract of my configuration file
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-http.xml /
import
As CXF jaxws:endpoint just try to get the reference of myServicePortType
once, even you defined the bean of myServicePortType to be prototye, the
MyServicePortTypeImpl just is just created once.
If you want to make the implementor to Non singleton, you may need to
create a new Invoker[1]
I solved the problem by adding a ResponseHandler that clears the headers
(response.getMetadata(),clear()). Here's what I found while debugging:
JAXRSOutInterceptor puts headers in message from response.getMetadata()
The writer (BinaryDataProvider) copies the inputstream to the
Hi,
I've a problem with the validation of SOAP headers. I found out that some
errors are not detected but I don't know why.
If I send a request with an invalid namespace in the SOAP header the request
passes instead of returning a fault. If I do the same in the SOAP body, a
fault is returned.
11 matches
Mail list logo
