RE: Problem with validation of SOAP headers

Hi Dan, Thanks for the explanation! Regards, Andi -Original Message- From: Daniel Kulp [mailto:dk...@apache.org] Sent: Freitag, 12. August 2011 21:35 To: users@cxf.apache.org Cc: Kuhtz, Andreas Subject: Re: Problem with validation of SOAP headers On Wednesday, August 10, 2011 9:23:56

Re: Sticky Load Balancing and Failover

Hi On Fri, Aug 12, 2011 at 10:37 PM, anucekay anuce...@gmail.com wrote: Hai  I am trying to get some inputs on how best to implement the following:  - Let us say we have a service that is implemented by a set of servers. The service   basically provides leaderboard. They expose SOAP

Re: Sticky Load Balancing and Failover

If you're already using a HW-loadbalancer for other parts of your infrastructure you could use this as well ... -Bernhard On 08/12/2011 11:37 PM, anucekay wrote: Hai I am trying to get some inputs on how best to implement the following: - Let us say we have a service that is implemented

Null strings

All: I'm having a peculiar problem and can't seem to find an easy solution using the CXF documentation. When a value passed via SOAP is empty (say, the middle name if it's an optional value), the JavaBean is filled in with an empty string, not null. This conflicts with JSR 303, which mostly only

Soap Response Interceptor

Hello, I consider myself as a beginner in CXF so pardon me if these are naive questions. We are using CXF to expose a java service/api as a soap webservice. The service works well accepting an incoming soap request, unmarshalling to java objects, exeuting the webmethod and marshalling the xml

RE: ws-security.sts.client

Hi Oliver, Thanks for the information. I copied the IssuedTokenOutInterceptor code in IssuedTokenInterceptorProvider. In the client I first got the Security token from the STS and then provided all the information the out interceptor needs in the context(like AssertionInfoMap, SecurityToken

Re: Convert Byte Array to Base64Binary

Couple of options: 1) Turn off mtom. That should keep it inlined. 2) Add @XmlInlineBinaryData to the managerNonce field 3) Depending on how mtom is turned on, you can control the threshold size. For example, if using the @MTOM annotation, you can do @MTOM(threshold=1024) or similar to

Re: Initializing beans and session factory types

The EASIEST way to do this is to no stick a @FactoryType thing on there at all and just do: bean id=sadlServiceProvider scope=session class=com.ge.research.sadl.sadlserver.cxf.provider.SadlServiceProvider aop:scoped-proxy/ property name=serviceNameMap map . /map

Re: Aegis binding that property value becomes null

BTW, from the websphere console, I often saw this system out when it receive request from client: org.apache.axis2.jaxws.message.databinding.JAXBUtils createJAXBContextValue Both ObjectFactory package-info not found in package hierachy This sounds like you aren't even using CXF, or

Re: Null strings

In almost all cases with CXF, it does set it to null.Can you capture the soap message that is being sent and see what is in there? If there is an empty element (like middleName/) then it would be an empty string which would be correct. If the element is missing entirely, it would

Re: Soap Response Interceptor

This really depends on what your third party transformer expects. If the thirdparty thing expects a DOM or is optimized for a DOM type thing, the easier thing to do is configure in the SAAJOutInterceptor. See:

Re: LoggingOutInterceptor shows wrong or no payload if StaxTransformFeature is active

Hi Andi, okay. This jaxb-commons-lang-plugin-2.2 was the one that I couldn't locate. This jar seems to have been intentionally removed from the repo. So I used your attached one temporarily to run your test program. And there is indeed a problem in TransformOutInterceptor which can interfere with

Re: rewrite soap body namespace declaration.

Hi, If you use CXF 2.4.x, you can set the namespace prefix association by setting a mapping property soap.env.ns.map in the request context. For example, if you used the CXF Greeter example and wanted to use the default namespace for the soap envelope, you could do something like: Greeter