Thanks to both of you.
I can now fight the requirements team :-)
Dan,
Thanks for the extra note on true .
I tried to do the same by adding an "out" interceptor and was confused
getting the name space error in soap ui.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Header-Vali
The server has strict validations on namespaces and report soap fault while
parsing the envelope. Is there any way to override the actual soap envelope
by implementing the interceptors before invoking the webservice?
Thanks,
Deepak
On Wed, Jan 21, 2015 at 1:21 AM, Andrei Shakirin
wrote:
> Hi,
>
Definitely a strange use case. Normally if the user cannot be validated, a
fault would have been raised so if a fault isn’t raised, then we know the user
was validated and no need for a strange header.
That said, an Interceptor on the “out" chain could look at the incoming message
and add a
Ok. Thanks at all!
I appreciate the very good support here.
--
View this message in context:
http://cxf.547215.n5.nabble.com/included-xsd-s-are-not-resolved-for-wadl-generation-tp5753451p5753677.html
Sent from the cxf-user mailing list archive at Nabble.com.
It looks like this is the issue that I've run into before, where it is
continually looping + getting new tokens. Could you attach the WSDL so that
I can see the exact security policy?
Colm.
On Tue, Jan 27, 2015 at 2:23 PM, Mark Durant wrote:
> Hi Colm,
> I don’t see any obvious errors, but I’l
Why does the user validation result need to be in the header? This is not
standard behaviour.
Colm.
On Wed, Jan 28, 2015 at 12:04 PM, sdm wrote:
> I need to develop webservice using cxf and WS-security which i have done
> (standard recommendation)and looks like
>
> public class ServerPasswordCa
Could you put together a test-case + I will take a look? The issue *may* be
due to the fact that in 2.7.x, the client only caches the token for as long
as it is valid. This is changed in 3.0.x. However, this might not be the
issue at all.
Colm.
On Wed, Jan 28, 2015 at 1:05 PM, Laci Gaspar wrote:
Hi,
I have a service side JAX-WS handler that is attached to the JAX-WS service
using the @HandlerChain annotation and the handler chain configuration file
(). How do I pass some initialization parameters into the JAX-WS
handler in ServiceMix?
In a JavaEE container with the WAR packaging, I
Hi
I've opened an enhancement request:
https://issues.apache.org/jira/browse/CXF-6132
CXF AsyncConduitFactory creates a default manager, but perhaps a custom
instance can be passed to it as a CXF Bus property and set as a factory
field. Later, when a client instance is created, the code deali
On 28/01/15 12:20, srinivas thallapalli wrote:
Basically what I am trying to do is, I have some SOAP services and I want
write an engine which can give the REST resources for those SOAP services.
The input to SOAP to REST is only the WSDL.
I am trying to find, if there are any best practices to
I'm using 2.7.14.
My feeling is that the server configuration is not correct. I'm
following the example at:
http://svn.apache.org/viewvc/cxf/trunk/services/sts/systests/advanced/src/test/resources/org/apache/cxf/systest/sts/renew/cxf-sts-pop.xml?view=markup
I noticed though that I cannot confi
Basically what I am trying to do is, I have some SOAP services and I want
write an engine which can give the REST resources for those SOAP services.
The input to SOAP to REST is only the WSDL.
I am trying to find, if there are any best practices to do this.
Thanks
--
View this message in conte
I need to develop webservice using cxf and WS-security which i have done
(standard recommendation)and looks like
public class ServerPasswordCallback implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException,
UnsupportedCallbackException {
WSPasswordCallba
On 28/01/15 07:38, MayBee wrote:
Sergey Beryozkin wrote
I can add a property to WADLGenerator to avoid updating the relative
import/include references. Can you give some example of where your
schemas are located, how is a root schema includes/imports one of them,
and which URI you use (where is
Hi
here is some info:
http://cxf.apache.org/docs/jax-rs-and-jax-ws.html
Sergey
On 28/01/15 09:06, srinivas thallapalli wrote:
Hello,
Any guidelines to develop a framework to expose SOAP operations as REST
resources.
Thanks
--
View this message in context:
http://cxf.547215.n5.nabble.com/G
What version of CXF is your client using? Try with the latest version of
2.7.x if you aren't already. Failing that, try enabling debug logging to
see what is going wrong.
Colm.
On Wed, Jan 28, 2015 at 7:58 AM, Laci Gaspar wrote:
> Yes, you're right, the Renew operation was not configured. I did
Hello,
Any guidelines to develop a framework to expose SOAP operations as REST
resources.
Thanks
--
View this message in context:
http://cxf.547215.n5.nabble.com/Guidelines-to-develop-Rest-interface-for-SOAP-services-tp5753652.html
Sent from the cxf-user mailing list archive at Nabble.com.
Yes, you're right, the Renew operation was not configured. I did that
and now the token seems to get renewed.
Unfortunately I get another exception now, and I don't know if that is
related to the previous problem.
I configured the token lifetime to 20 seconds.
After 5 minutes I get the following
18 matches
Mail list logo