Hi Dan,
migrating to CXF 2.2 fixes the issue! Thanks!
Marco
dkulp wrote:
>
>
> Any chance you can package this up as an example and post to the jira?
>
> Also, try updating to CXF 2.2. I know a couple of fixes went in around
> this
> that MAY be affecting this.
>
> Dan
>
>
> On Wed Ap
Hi cxf gurus,
I know that this problem has been discussed in several threads and is due to
the fact that the underlying framework on the server side is not following
the standard (WS-I Profile) but I would like to get guidance on how to solve
it
Using the following wsdl (in groovyws) -
proxy = ne
So everything in my CXF application works perfectly... until I attempt
to enable SSL. I'm using the method outlined in the wsdl_first_https
example. As soon as I add the code to enbale HTTPS to my xml configs,
the client errors out with the exception below which boils down to no
valid cert
Hi
It's a very good question, have a look here please :
http://svn.apache.org/repos/asf/cxf/trunk/systests/src/test/resources/ja
xrs/WEB-INF/beans.xml
This is somewhat unrelated example, but it shows how you can register a
JAXB provider, and it shows how to define utils:map, so you can do
someth
Any chance you can package this up as an example and post to the jira?
Also, try updating to CXF 2.2. I know a couple of fixes went in around this
that MAY be affecting this.
Dan
On Wed April 1 2009 5:54:32 am marcob wrote:
> Hi,
> I've been experiencing an unexpected behaviour with cxf 2.1
On Tue March 31 2009 4:25:18 pm Bryan Kearney wrote:
> Next dumb question... is it possible to do top-down development with
> existing classes?
Sometimes yes, sometimes no. :-)
> I have some classes which are shared between client and server. Is it
> possible to tell wsdl2java to use/augement t
The answer is "probably not". Normally, the "list" things are mapped to
something like:
However, your "object" would go to:
That definition only allows a single object in it.You COULD change it to:
Object attribute[];
and set it via setAttribute(list.toArray(new Object[]));
That wou
On Tue March 31 2009 3:41:40 pm hanasaki jiji wrote:
> Hmmm really good input back to the Sun folks... Any idea of how to get
> them to take notice?
Oh, we've bitched about it quite a bit already. They know. They just aren't
really willing to do much about it. Basically, each "team" is respon
On Tue March 31 2009 6:49:32 pm Arby wrote:
> Right. So in order to use the Java service's upload method, I have to
> provide a DataHandler object (that references a file) and from what I
> understand, DataHandler is just a wrapper for an InputStream. So if I were
> to construct my own DataHandler
On Wed April 1 2009 1:52:24 am Roderic Green wrote:
> Thanks for you answer Daniel,
>
> Attachment I need to send is different for each WS method invocation (it
> is like an additional merthod argument). Are interceptors designed for such
> use? What about synchronisation etc.
Well, they CAN be.
Forgive me if this is the wrong forum or off topic or plain stupid!I want to
add an xml-stylesheet reference to the document created by CXF-2.2 JAX-RS
via JAXB.
The JAXB documentation indicates something like this code to add the
xml-stylesheet to the header:
Marshaller marshaller = myContext.getJ
Hi,
I've a Ws interface annotate like this:
@WebService(name="boc",
targetNamespace="http://com.boc.webservice";)
@SOAPBinding(style = Style.RPC)
public interface BocInterface {
...
and the implementation annotate like this:
@WebService(portName="bo
On Wed April 1 2009 5:43:58 am Vassilis Virvilis wrote:
> It works. I tried it with
> apache-cxf-2.2.1-SNAPSHOT.tar.gz Wed Apr 01 07:28:56 GMT+00:00
> 2009
> 29806907 The date and time is important otherwise I tested it wrongly
> (won't be the first time :-))
>
> I was able t
Thanks Eoghan.
-Original Message-
From: Eoghan Glynn [mailto:eogl...@gmail.com]
Sent: Wednesday, April 01, 2009 11:14 AM
To: users@cxf.apache.org
Subject: Re: Message processing direction
Hi Eric,
The usual approach is to check if the current message is the same thing
as
the out or out-
Gmail in its wisdom added some 'orrible formatting to that example
code. Here it is in plain-text:
/**
* Determine if message is outbound.
*
* @param message the current Message
* @return true iff the message direction is outbound
*/
public static boolean isOutbound(Mess
Hi Eric,
The usual approach is to check if the current message is the same thing as
the out or out-fault message on the exchange.
So even if the out message on the exchange is non-null, it won't be the same
the current message in the outbound client-side case.
Here's some example code from the W
2009/3/31 Bryan Kearney
> Daniel Kulp wrote:
>
>> On Tue March 31 2009 5:03:59 am Eoghan Glynn wrote:
>>
>>> Now we could follow WCF's example and allow WS-RM 1.0 to be used with the
>>> 2005/08 version of WS-A. While I don't think this is correct from a spec
>>> point of view, we could just be p
Hi,
I've been experiencing an unexpected behaviour with cxf 2.1.3. When the
client invokes the service passing it a long attachment (~120 Kb), the
service receives just a part of it (~ 3Kb). Below my code:
Service Interface:
@WebService(name = "BatchManagerGUIService", targetNamespace =
"http://
On Tuesday 31 March 2009, Daniel Kulp wrote:
>
> This one should now be fixed. It would be great if you can try tomorrows
> snapshots (will deploy overnight) to double check. Thanks for catching it.
>
> Dan
Dan,
It works. I tried it with
apache-cxf-2.2.1-SNAPSHOT.tar.gz Wed
For clients that don't support attachments properly, you can always
save the file to a temporary static location on your webserver with a
non-guessable name, and send a URL instead. Then have a scheduled task
that removes such files older than a certain age.
I believe we've done this before with o
20 matches
Mail list logo
