Thanks for reply.
Could you please elaborate "proprietary policy assertion to activate custom
interceptors". Please share some samples/links, if you have any sample
proprietary policy assertion to activate custom interceptors to achieve
similar to what I was looking for.
--
View this message
Thanks Dan, it solve my problem I am able to test the services now.
Also Can you please provide me list of required JARs?
Thanks
Prashant Saraf
--
View this message in context:
http://cxf.547215.n5.nabble.com/Weblogic12c-JAXWS-without-Spring-CXFNonSpringServlet-not-working-tp5753372p5753433.
Hi Colm-
Wow - thanks for the quick action.
What about OnBehalfOf/ActAs handling in the non-status validate invocation?
The idea is to treat the non-status validate as semantically equivalent to
an issue operation, where the input token passed to the validate invocation
is equivalent to the Suppo
Hi,
I added support to CXF master + 3.0.x-fixes to send a KeyType, KeySize +
Renewal semantics in a non "Status" Validate request. The KeyType defaults
to Bearer.
Colm.
On Tue, Jan 20, 2015 at 6:25 PM, dhogan wrote:
> Hi-
> I am working on an STS implementation. I would like to emphasize token
Yes, I have already solved the issue.
Thank for the support.
BR,
Giovanni
Enviado do meu iPhone
No dia 22/01/2015, às 13:16, André Costa Lima [via CXF]
escreveu:
> I believe you sent in an e-mail (see below) stating that you already solved
> this?
>
> ---
>
> Dear Daniel,
>
>
>
> F
I believe you sent in an e-mail (see below) stating that you already solved
this?
---
Dear Daniel,
Finally it worked. Thank you for your support to both you and André. The
trick was the SEi, in particular the UseAsyncMethod on the implementation
and the @ResponseWrapper notation on the synch m
Dear André,
I have added the polling method and it starts to work, or better the error
is different. Now I have the following excpetion:
Jan 07, 2015 3:27:26 PM pt.uninova.proseco.services.async.TestAsyncHandler
handleResponse
SEVERE: null
java.util.concurrent.ExecutionException: java.lan
The problem here is that you are mixing up the WS-SecurityPolicy
configuration properties (which are set as JAX-WS properties), and the
WSS4J Out/In Interceptors, where you supply the configuration tags to the
constructor. You can't configure the WSS4JOutInterceptor via
@EndpointProperty annotation
I am trying to develop a apache cxf soap webservice and in the generated
wsdl, for the mapping types which are simple types defined in the imported
schema, simply uses basic xml types instead of the actual enums or simple
types, for example.
I have a base xsd, that has an element called Language d
Hi Stephen,
See here for the valid values for JDK 7:
http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#SSLContext
So you can use "TLSv1.2" as the secureSocketProtocol, and exclude other TLS
protocols via excludeProtocols if you wish.
Colm.
On Wed, Jan 21, 2015 a
Actually it should be "InitiatorEncryptionToken" and not
"RecipientEncryptionToken". I tried this with the CXF master branch and it
works fine. Just bear in mind that if the input message Body is not
encrypted, then the EncryptedParts policy should be referenced from the
output message binding, and
Hi Alexey,
Yes. For instance, if you work on bare mode, wsdl2java can generate an
empty class. In case of wrapped mode, a method with no input arguments is
generated.
André Costa Lima
Em 22/01/2015 09:16, "Alexey Markevich" escreveu:
> Hello,
>
> Its possible to have an operation with empty inp
Hello,
Its possible to have an operation with empty input message:
...
On Thu, 22 Jan 2015 12:02:04 +0300, Andrei Shakirin
wrote:
Hi,
Using Solicit-Response(Output-Input) and Notification (Output-Only)
operations are prohibited by WS-I Basic Profile 1.2 and not cur
Hi,
> 1. Can WS-Policy be used to control the access to a service, like limited
> number
> of access to a service in day and only particular users are allowed to access
> the
> service etc.
Limited number of access (throttling) cannot be specified by standard
WS-Policy. Basically you can add p
Hi,
Using Solicit-Response(Output-Input) and Notification (Output-Only) operations
are prohibited by WS-I Basic Profile 1.2 and not currently supported by CXF:
"4.5.2 Allowed Operations
Solicit-Response and Notification operations are not well defined by WSDL 1.1;
furthermore, WSDL 1.1 does not
Hello,
I updated cxf from 2.3.3 to 2.7.10. The jars are bundles with JBoss 6.2. I
am using the DynamicClientFactory to create a proxy which invokes the
service.
In the old version the name-attribute of the parameter element within the
schema was considered. In the newer version it replaces the val
16 matches
Mail list logo