Sergey Beryozkin wrote:
This means that
AbstractPojoConfigurationTypeHandler.createClientProxyFactoryBean()
won't be able to return a JAXRSClientFactoryBean.
What do you think about this idea. The factory which returns handlers
can check first if a given service intents include "HTTP" but
I think we've reached a lazy consensus on this. I'll send a note to the user
list as a warning that 2.0.12 will be the last so people are aware.
Dan
On Fri June 5 2009 11:37:41 am Daniel Kulp wrote:
> This may be a "thorny" issue, but I'd like to bring it up and start a
> discussion.
>
> Jul
Hmm I think this is a bug in CXF. The CXF HttpHeaderHelper is
defaulting to UTF-8 if the charset is not specified. That's wrong. It
should be defaulting to ISO-8859-1.
Dan
On Tue June 9 2009 4:06:43 am anoopPrasad wrote:
> Dear Dan,
>
> 1)Do you mean that if client request has t
Ideally, to me, this type of fault mapping needs to be in the SOAP binding,
not the JMS transport.The JMS transport needs to be somewhat independent
of soap so that it's usable for things like XML over JMS and possibly even
some resty things.
Basically, the SOAP binding should examine it's
I BELIEVE this is due to using the Sun's StAX parser. Two options to fix
this:
1) Make sure you pickup woodstox instead of the sun parser.
2) Upgrade to CXF 2.2.2 which works around this issue.
Dan
On Tue June 9 2009 8:19:06 am Naresh Tallapelli wrote:
> Hi All,
>
> I am Naresh. Iam us
Hi All,
I am Naresh. Iam usig cxf-2.1.2 version. I was able to execute my web
service successfully. But sometimes, when web service client tries to send
message to web service server, the soap message was in the following form
shttp://sc hxemmlanss.:xSm=l"soap.orhgt/tspo:a/p//secnhveemlaosp.ex/m
+1,
-- Ulhas
Daniel Kulp wrote:
Alessio has been one of the primary driving forces behind getting CXF to be a
certified JAX-WS provider for JBoss. As part of that work, he has identified
several bugs/issues in CXF and has provided patches for many of them. He has
also been helping in the co
+1
David
2009/6/8 Daniel Kulp :
>
> Alessio has been one of the primary driving forces behind getting CXF to be a
> certified JAX-WS provider for JBoss. As part of that work, he has identified
> several bugs/issues in CXF and has provided patches for many of them. He has
> also been helping i
+1
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: 08 June 2009 20:32
To: dev@cxf.apache.org
Subject: [VOTE] Alessio Soldano for committer
Alessio has been one of the primary driving forces behind getting CXF to
be a
certified JAX-WS provider for JBoss. As part o
+1
/Eoghan
2009/6/8 Daniel Kulp :
>
> Alessio has been one of the primary driving forces behind getting CXF to be a
> certified JAX-WS provider for JBoss. As part of that work, he has identified
> several bugs/issues in CXF and has provided patches for many of them. He has
> also been helping
+1
cheers, Sergey
Daniel Kulp wrote:
Alessio has been one of the primary driving forces behind getting CXF to be a
certified JAX-WS provider for JBoss. As part of that work, he has identified
several bugs/issues in CXF and has provided patches for many of them. He has
also been helping i
Dear Dan,
1)Do you mean that if client request has the Encoding information in the
specified attribute then server
side does not have to explicitly perform any additional operation to handle
this?
2) there is an open defect on CXF about encoding here
http://www.mulesource.org/jira/browse/MULE-40
+1
Freeman
Daniel Kulp wrote:
Alessio has been one of the primary driving forces behind getting CXF to be a
certified JAX-WS provider for JBoss. As part of that work, he has identified
several bugs/issues in CXF and has provided patches for many of them. He has
also been helping in the com
13 matches
Mail list logo
