What is the designated procedure to do timeout handling in asynchronous
clients? My client uses ClientCallbacks but I'm unsure how to abort the
invocation after a user-specified timeout. Is that to be done in my client
code (e.g. via ClientCallback.cancel(boolean)) or can I set some properties
We find a solution :
Add a META-INF directory in the classpath :
META-INF/
META-INF/spring.schemas
META-INF/xsd
META-INF/xsd/2003-02-11.xsd
within spring.schemas
http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd=META-INF/xsd/2003-02-11.xsd
and
Hey,
I am using CXF DynamicClientFactory from Groovy to call a web service
developed with apache Axis2. The method has this signature:
Pair[] executeRunbook(String token, Pair[] params)
Pair is a complex object defined as:
public class Pair {
private String name;
private
Hmm... What version of CXF? We already have that line in our spring.schemas
file:
./api/target/schemas/META-INF/spring.schemas:
http\://schemas.xmlsoap.org/wsdl/2003-02-11.xsd=schemas/wsdl/wsdl.xsd
and that wsdl.xsd in our jar.Not sure why it wouldn't have been picked up.
Dan
On Thu
I honestly don't have any idea how hard that would be to do. The jre's on
those devices are usually quite limited and I'm not sure how much of it CXF
would hit. It might not be limited to CXF either. CXF uses things like JAXB
and such that also might have issues.
Dan
On Wed September 2
I wonder if this is somehow related to:
https://issues.apache.org/jira/browse/CXF-2415
(mostly just thinking)
Dan
On Thu September 3 2009 1:20:02 pm Yu L wrote:
Hey,
I am using CXF DynamicClientFactory from Groovy to call a web service
developed with apache Axis2. The method has this
On Thu September 3 2009 11:10:40 am Bernd Wiswedel wrote:
What is the designated procedure to do timeout handling in asynchronous
clients? My client uses ClientCallbacks but I'm unsure how to abort the
invocation after a user-specified timeout. Is that to be done in my client
code (e.g. via
CXF is a streaming stack. The OutputStream that you removed from the
message is where you would write your data.That is most likely a wrapper
around the HTTP output stream.
Dan
On Wed September 2 2009 7:56:54 pm rkapur wrote:
Hi All,
(I am new to this - so please excuse if I
USUALLY, this kind of error is a result of the message not actually matching
the schema in the wsdl. Normally, that is due to the schema not saying
elementFormDefault=qualified and then sending a message like you have below
that qualifies everything.I would double check the wsdl that was
Hi,
I believe that, at least, some Mobile Phones do support JSR 172 J2ME
Web Service API; and you can use it as Web Service Client API to
make SOAP Call from Mobile Phones.
Hope this information would be helpful.
Thanks,
Jian
On Thu, Sep 3, 2009 at 2:07 PM, Daniel Kulpdk...@apache.org wrote:
All I can suggest is to check the server logs for any information there as
well as try setting the system property:
-Djavax.net.debug=all
and kind of trace through what the ssl handshake is doing. Might reveal a
strange key being used or something.
Dan
On Wed September 2 2009 10:47:53 am
Just FYI: I have a (2 line) fix for this I'm testing now. We were binding the
operation to the method prior to checking if we have to go back and re-check
for the extra rules such as the element references. Just moved the bind
line down a bit and it works.
Dan
On Tue September 1 2009
That's great. If you send me a patch I can test against my more
elaborate example as well.
Scott
* Sent from my phone.
On Sep 3, 2009, at 5:32 PM, Daniel Kulp dk...@apache.org wrote:
Just FYI: I have a (2 line) fix for this I'm testing now. We were
binding the
operation to the method
On Thu September 3 2009 6:26:11 pm Oster, Scott wrote:
That's great. If you send me a patch I can test against my more
elaborate example as well.
I've include below. Definitely nothing big.
The SNAPSHOTs should be deployed tonight with the fix in it.
Dan
Index:
Closer, but not quite...
The osgi.remote.endpoint.location does show up in the Zookeeper entry with the
IP address properly externalized, but there is no org.apache.cxf.ws.address
entry. That appears to be what the client will bind against, not the enpoint
location.
It's also more than
Hi All,
I'm writing a request handler which deals with the method going to be
invoked and the parameters provided (both query and path, both name and
value of each parameter). However i'm having some problem getting at the
path paramter names and values - well I can ge the names but i need the
Hi Kynan,
I am not sure if this answers your question, I'll try:
These are what I use for an inbound handler extending
AbstractPhaseInterceptorMessage at phase Phase.RECEIVE
1. message.get(Message.BASE_PATH) would give you the path
2. message.get(Message.QUERY_STRING) should give you
Hi Gabo,
Thanks for the reply. Yes I had seen all these values but none quite fits
what i'm after.
There's another set of info which is set after request handlers in the
JAXRSInInterceptor which is
message.get(URI_TEMPLATE.TEMPLATE_PARAMETERS), which contains the path
parameters in key/value
18 matches
Mail list logo
