Hello,
I got
"org.apache.cxf.binding.soap.SoapFault: Message part {
http://schemas.xmlsoap.org/ws/2005/02/rm}CreateSequence was not recognized."
Here is a code how I create a jaxws client:
[code]
public static T getProxyWSHandleReliable(Class clazz, String url)
{
JaxWsProxyFactoryBe
Hi, there
We have SAML Token (STS) policy defined as below (saml.policy):
http://www.w3.org/ns/ws-policy";
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
Andrei,
Thanks again for the detailed information.
Regards
Sachin
On Tue, Aug 20, 2013 at 9:06 AM, Andrei Shakirin wrote:
> Hi Sachin,
>
> > 1. For all these models, can I just create 1 instance of Service or
> Client and reuse it across multiple threads.
>
> Generally speaking client proxies ar
Be aware that gsoap does not appear to have a commercial friendly license
which is different to cxf
Sent from my Android phone
On 24/09/2013 2:49 AM, "Tim Fulmer" wrote:
> You may want to check on the gsoap mailing lists ;)
>
> On Sep 21, 2013, at 11:05 AM, Faz wrote:
>
> > Thanks you Benson,
I've fixed the parsing issue, but decided not to default to Bearer type
in case of the early OAuth2 implementation incorrectly not returning a
token_type - as it will inevitably lead to the error as soon as
ClientAccessToken is used and it is also non-compliant.
However I added an option to spec
You may want to check on the gsoap mailing lists ;)
On Sep 21, 2013, at 11:05 AM, Faz wrote:
> Thanks you Benson, does gsoap has security specifications? I mean, we have
> CXF service with security settings which authenticates the Client. so does
> gsoap has that capability in store?
>
>
>
>
Hi Glan / Freeman
I am getting similar error while accessing the webservice(digest auth
protected) through a java client. I am able to see the wsdl from browser but
when running the client I am getting below error.
Could you please assist ?
javax.xml.ws.WebServiceException:
org.apache.cxf.service
Hi All,
I'm having some problems with CXF on Jboss.
CXF version: 2.3.1
Jboss version: 5.1.0.GA
There are two servers: one on windows, second on linux, as far as I can see,
they are configured the same (maybe there are some differences).
There is one ear-file, which published my web service in thi
I don't think I understand what you mean because that sounds very bad.
If I have two different WSDLs Services in Servicemix that use SSL, they both
have to use the same port?!
So if port 8999 is my ssl port then WSDL A would need to do
https://45.61.30.1:8999/A and WSDL B would need to do
https://
Hi,
comments below,
On 23/09/13 14:11, Messina Andrea wrote:
Hi.
I found an error in the OAuthClientUtils class that prevents(throwing a
*server_error* exception) to receive the access token which was
correctly delivered from an OAuth2 server
(https://login.salesforce.com/services/oauth2/token)
If you don't setup the interceptor on the Bus, I think it should be safe to
share the same bus within these two camel context.
BTW, you can only set the SSL configuration on one port, no matter if they use
the same bus or not.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: ht
Hi.
I found an error in the OAuthClientUtils class that prevents(throwing a
server_error exception) to receive the access token which was correctly
delivered from an OAuth2 server
(https://login.salesforce.com/services/oauth2/token).
Against of the invocation of the statement:
So what do I do about the same bundle, same camel route, but two instances of
my WSDL? How do I prevent the Bus from being shared at all!?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Custom-Camel-Component-WSDL-First-SSL-tp5734356p5734365.html
Sent from the cxf-user mailing
Hi,
You cannot assume that different bundles are not share the same thread in
ServiceMix.
You need to create a new bus to avoid the side effect of share the bus in
different bundle.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willem
14 matches
Mail list logo
