hi gabo...
many thanks for your help...
this was the solution to my problem...
cheers,
ernst
Hi Ernst,
I do not think that is how Exchange works. My suggestion is for your
client's out interceptor to place those values as header parameters.
Then your server in interceptor to catch those
Hello there,
I have a problem with D-OSGI and I can't find an explanation.
I am trying to register a service with multiple interfaces.
properties.put(osgi.remote.interfaces, interfaces.toArray(new
String[interfaces.size()]));
properties.put(osgi.remote.configuration.type, pojo);
On 04/26/2010 04:39 PM, Thomas Koenig wrote:
https://issues.apache.org/jira/browse/WSS-146
which allows you to build a OpenSAML 2.0 compatible wss4j jar. I have just
started myself to look into this.
I see https://issues.apache.org/jira/browse/WSS-146 but failed to apply
the patch to the
Hi,
I have a client side outbound interceptor added to the interceptor chain with
the following overridden method
public void handleMessage(SoapMessage message)
throws Fault
{
SoapVersion version = message.getVersion();
try
{
SOAPMessage soapMessage =
Since the patch uses features of Java 1.5 I had to modify the
wss4j/build.xml file. You also have to copy opensaml-2.3.1.jar and its
dependencies (look at opensaml-2.3.1/pom.xml) into the wss4j/lib directory.
Doing this I successfully build a wss4j-1.5.8-patchSAML2.jar file, but
haven't tested it
Hi All,
I just encountered this problem while trying to use the same message as
input for 2 different operations:
WSDLToJava Error: Non unique body parts, operation [ GetImageFileName ] and
operation [ GetImageFormat ] in binding
{http://theSoftwareArchive.com}SoftwareArchiveBinding have
Using cxf 2.0.12 as well as 2.2.7, working from Java first model using
JAXB/SOAP
My Beans contain List collections and when I operate the service over
http:// an empty list returned is reported by the client generated classes.
That is the desired behavior.
However if I use the local://
I suspect that the key to your question lies in your binding. If we are
talking about a SOAP binding, you have two main options: RPC and Document
style. If you are attempting to do document style SOAP Web services, the
operation that is being invoked is tied to the contents of the SOAP body.
In
In case anybody comes across this, I think it's a bug, because I can't see
why anybody would want a different exception thrown from local:// then
http://, but I found an easy work around in any case. Create the 2 classes
below and then use the new ClientProxyFactoryBeanSubstitute class below
Hi
I noticed that the PhaseInterceptorChain is different in CXF-2.2.7 than in
CXF-2.2.2
Is that the reason it return nulll when I call message.getContent()?
Steve
CXF2.2.7
Chain org.apache.cxf.phase.phaseinterceptorch...@a68e82. Current flow:
setup [PolicyOutInterceptor]
pre-logical
On Wednesday 28 April 2010 11:06:25 am Steven Thein wrote:
Hi
I noticed that the PhaseInterceptorChain is different in CXF-2.2.7 than in
CXF-2.2.2 Is that the reason it return nulll when I call
message.getContent()?
If you need the SAAJ model, you would need to also configure in the
I am seeing some really bizarre behavior for a jaxrs service I've written. I'm
a little at a loss at one's going on and this may not be the appropriate place
as it may be in the bowels of stax or my servlet api.
I am trying to stream a large resultset straight from my database to the
response
Ok I did a further test, created mock back end, moved over the same service
class/marshalling code over to Tomcat and it all worked as expected (my unit
test that use a mock http servlet response work too). I then moved the mock
stuff back over to Websphere (6.1) and still doesn't work :(.
Hi
It is bizarre indeed, but I'm not quite sure if/how I can help. One possible
reason is that you write the start of the document using STAX writer but
then marshall the individual nodes directly into output stream.
Perhaps you might want to try avoiding doing the marshalling code and let
Hi. We're attempting to send large (from 55MB to 400MB) files over CXF, but
we're running into OutOfMemory exceptions even at the lower end, and it
appears that our attempts at configuring MTOM, so far, are unsuccessful,
because the data is being inlined within the XML rather than sent as a
I would like the consumer of my API to be able witch fields (elements)
they actually want returned in an effort to keep the content as small as
possible, similar to what Solr allows in search. What is the best way
to accomplish this with JAX-RS and CXF?
Jason
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Wednesday, April 28, 2010 2:45 PM
To: users@cxf.apache.org
Subject: filtering elements in jaxrs
I would like the consumer of my API to be able witch fields (elements)
they actually want returned in an effort
Jason,
The simplest thing to do is simply set only the fields in your bean that the
client is interested in, since null fields are ignored by JAXB. I do this
programatically via a simple switch statement, where each case calls the
proper setter for the field the user is interested in (for instance
By default, the WSS4JOutInterceptor turns off MTOM since the attachments would
not be signed/encrypted. Basically, it takes the secure route.
You can tell it to not do that by:
bean class=org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor
constructor-arg
/contructor-arg
Any chance you could create a testcase and log a JIRA? I'm really not sure
where the other namespace would be coming from.
Dan
On Monday 26 April 2010 9:46:37 pm Nikolay Elenkov wrote:
On 2010/04/24 0:24, Daniel Kulp wrote:
On Friday 23 April 2010 5:09:00 am Nikolay Elenkov wrote:
I am
20 matches
Mail list logo
