+1
Willem
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 helpin
+1
On Tue, Jun 9, 2009 at 1:01 AM, 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. H
I just want to find a way without any configuration, and soap jms
transport can use it out of box.
Willem
liucong wrote:
> Hi,
>
> Willem Jiang 写道:
>> Hi,
>>
>> I think you mean how to throw the fault from the JMS transport.
>> Basically , if you throw the fault from a CXF interceptor, CXF's
>>
Hi ,
You can leverage the Features[1] to install the interceptors which you
need for soap/jms, and you can find some basic CXF Architecture document
[2] here.
[1]http://cwiki.apache.org/confluence/display/CXF20DOC/Features
[2]http://cwiki.apache.org/CXF20DOC/cxf-architecture.html
Willem
liucong
Hi,
Willem Jiang Writes:
> Hi,
>
> I think you mean how to throw the fault from the JMS transport.
> Basically , if you throw the fault from a CXF interceptor, CXF's
> interceptors chain will take care of it and build the fault message and
> throw it out.
>
> If you want to check the Content type
Hi,
Willem Jiang 写道:
> Hi,
>
> I think you mean how to throw the fault from the JMS transport.
> Basically , if you throw the fault from a CXF interceptor, CXF's
> interceptors chain will take care of it and build the fault message and
> throw it out.
>
> If you want to check the Content type , yo
Just to make sure: is this what you fixed with [WSTX-209] (such that
validation problem handle now gets properly invoked, and prevents
exception)?
On Fri, Jun 5, 2009 at 6:14 PM, Benson Margulies wrote:
> Next question: Exception mapping. Woodstox throws what it throws, in
> the middle of StaxUtil
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" b
Right. As of WSTX-209 I can get the right exception with no further ado.
On Mon, Jun 8, 2009 at 7:25 PM, Tatu Saloranta wrote:
> Just to make sure: is this what you fixed with [WSTX-209] (such that
> validation problem handle now gets properly invoked, and prevents
> exception)?
>
> On Fri, Jun 5,
+1
On Mon, Jun 8, 2009 at 8:47 PM, Benson Margulies wrote:
> +1
>
> On Jun 8, 2009, at 3:31 PM, 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
>> seve
+1
On Jun 8, 2009, at 3:31 PM, 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
a
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 communities, especially related to
Hi Camel/CXF dev's
I'm working in an environment where classloaders are heavily used to
isolate components of the system. No, it's not quite OSGI, but has some
similarities.
One of the issues I'm trying to address is having multiple, separated
CXF bus'es and Camel contexts with routes ref
I THINK if you set the Message.ENCODING attribute on the message (for
instance, in the RequestContext) to a string denoting the encoding you want,
it should be used. I haven't tested that though.
On the server side, it should respond in whatever encoding the client sent it
in.
Dan
On Mo
This seems to make sense to me. Since 2.1.x is based on 0.8 spec, it's not
something that could even be "certified" and such. Thus, JAX-RS users really
should be encouraged to try and migrate up to the 1.0 spec version.
Dan
On Mon June 8 2009 10:13:26 am Sergey Beryozkin wrote:
> Hi,
There are really two ways to handle it:
1) When you set the schema into the wstx StreamReader, then wrapper it with a
new stream reader delegate that would override the "next" method to catch it
and map it to a fault.
2) Add an interceptor to the FaultOut chain that would check the class of t
Hi,
CXF 2.1.x branch supports a 0.8 version of JAX-RS api.
We put quite a lot of effort into ensuring 2.1.x users can write functional
RESTful applications with the help of JAX-RS 0.8 api, by not only back merging
all the fixes needed but also adapting some of the code from the CXF 2.2 lines
(
I wonder is it actually an issue with the spaces or have you just exceeded a
max path length in windows : looking at the error below it looks like your
classspath is truncated in a strange way at activeio-c...
If that is the issue - I tend to use c:\.m2 as my local repo dir to overcome
such pat
Ah. Documentation. That's a good thing.However, to grant access to
edit the wiki, we need to have ICLA's on file. Thus, we should add to the
list:
4) Each of the GSoC students should sign and submit the "Individual
Contributor Agreement" from http://apache.org/licenses/#clas
so tha
On Sun June 7 2009 9:22:38 am Willem Jiang wrote:
> Hi,
>
> It may relate to your default maven repository directory "C:\Documents
> and Settings\jason\". It has space in the maven repository directory,
> which will cause the process starting error.
Patches to fix that would be appreciated. :-)
Doesn't sound like there are any objections so I'm going to go ahead and do
this.
Thought of a couple more things for 2.3.x: jaxrs 1.1, jaxws 2.2.
Dan
On Fri June 5 2009 11:25:27 am Daniel Kulp wrote:
> With 2.2.2 out the door, I think it's probably time to create a 2.2.x fixes
> branch a
Brilliant! Can't wait to see Distributed OSGi over JAX-RS / REST!
David
2009/6/7 Sergey Beryozkin :
> Hi Josh
>
>> Yes, I would like to work on integrating your JAX-RS work with the
> JAX-WS patch I put together.
>
> It sounds great :-) Lets chat about all the issues in this thread,
> hopefully w
+1
Freeman
Daniel Kulp wrote:
This may be a "thorny" issue, but I'd like to bring it up and start a
discussion.
July 4th will mark the 2 year anniversary of the CXF 2.0 release. Since
then, we have released 11 patches to that branch, along with 2.1 (and 5
patches for it) and 2.2 (and 2 p
Hi all,
In most scenarios, soap/xml message is encoding with UTF-8.
But if i want to use another encoding ,such as UTF-16, GBK...
What i do with CXF?
Regards
Hubert.
--
View this message in context:
http://www.nabble.com/Soap-message-encoding-tp23920250p23920250.html
Sent from
24 matches
Mail list logo
