Yes, the changes to settings.xml helped. That got me past that issue.
However, I ended up having some problems with the GPG side of things
(GPG on Mac OSX) - similar to [1] so I couldn't close the stage repo.
It seems like the artifacts were signed by a subkey which apparently
doesn't work. So it
Hi David
On 22/03/12 08:47, David Bosschaert wrote:
Yes, the changes to settings.xml helped. That got me past that issue.
However, I ended up having some problems with the GPG side of things
(GPG on Mac OSX) - similar to [1] so I couldn't close the stage repo.
It seems like the artifacts were
On Thursday, March 22, 2012 08:47:16 AM David Bosschaert wrote:
Yes, the changes to settings.xml helped. That got me past that issue.
However, I ended up having some problems with the GPG side of things
(GPG on Mac OSX) - similar to [1] so I couldn't close the stage repo.
It seems like the
On 22 March 2012 11:13, Daniel Kulp dk...@apache.org wrote:
On Thursday, March 22, 2012 08:47:16 AM David Bosschaert wrote:
Yes, the changes to settings.xml helped. That got me past that issue.
However, I ended up having some problems with the GPG side of things
(GPG on Mac OSX) - similar to
Hi David
On 22/03/12 12:50, David Bosschaert wrote:
On 22 March 2012 11:13, Daniel Kulpdk...@apache.org wrote:
On Thursday, March 22, 2012 08:47:16 AM David Bosschaert wrote:
Yes, the changes to settings.xml helped. That got me past that issue.
However, I ended up having some problems with
On 22 March 2012 13:41, Sergey Beryozkin sberyoz...@gmail.com wrote:
I'm seeing 1.4-SNAPSHOT in poms, I guess I can update that easily later on
to 1.3.2-SNAPSHOT as I won't have enough 'material' to call a 1.4 release in
few months time, the upgrade to Blueprint would of course go to 1.4 :-),
Hi Dennis,
While ago, I mentioned the problem that I was having with the protocol
variations in WS-RM.
http://cxf.547215.n5.nabble.com/a-quesiton-on-CXF-2-5-WS-RM-s-protocol-variation-handling-td4710027.html
I would like to come back to this problem, as I am having a few
problems with server
Team, the CXF js_browser_client_java_first sample, which works fine in both
CXF 2.4.x and CXF 2.5.x, is inoperative in the CXF 2.6 trunk branch. While
Jetty starts OK, the page the README tells us to go to:
http://localhost:9000/Beverages.html is inaccessible. I think the problem
is that the
Yep. Just a missing spring dep. I'm on it.
Dan
On Thursday, March 22, 2012 07:54:48 AM Glen Mazza wrote:
Team, the CXF js_browser_client_java_first sample, which works fine in
both CXF 2.4.x and CXF 2.5.x, is inoperative in the CXF 2.6 trunk branch.
While Jetty starts OK, the page the
Hello,I see that the list does not admit attachment. Here is then the new wsdl
as a text (sorry for double message presenting the issue):
?xml version=1.0 encoding=UTF-8?!-- Licensed to the Apache Software
Foundation (ASF) under one or more contributor license agreements. See the
NOTICE file
On Wednesday, March 21, 2012 06:50:05 PM rajesh babu wrote:
I am struck for more than 3 days can anyone please help me out in this
Issue?
How is the camel route defined? How is the CXF client created? Are you
specifying a bus created from that config file?
Dan
Thanks in advance
Hello,This issue is because the Soap12FaultInInterceptor.unmarshalFault
receives a XMLStreamReader only for the Fault element. This is because it is
what the SAAJInInterceptor.handleMessage does with the XMLSreamReader content
when the message is a fault.Well, I think this issue requires a lot
12 matches
Mail list logo
