Am i the only one with this problem?
--
View this message in context:
http://old.nabble.com/org.xml.sax.SAXParseException%3A-cvc-elt.1%3A-Cannot-find-the-declaration-of-element-%27MCCI_IN02UV01%27-tp28094095p28105598.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi, try adding @Consumes(application/x-www-form-urlencoded)
cheers, Sergey
On Thu, Apr 1, 2010 at 1:48 AM, atest12 ariela...@yahoo.com wrote:
This is my implemented class:
public class HelloWorldServiceImpl implements HelloWorldService {
public String sayHelloPost(String msg,
Hi Todd,
I do not have any xml configuration file.
I tried with java code like:
System.setProperty(org.apache.cxf.Logger,
org.apache.cxf.common.logging.Log4jLogger);
before invoking the cxf operation.
But no luck for me.
Please suggest me what I did mistake.
Regards
Saravanan Ramamoorthy
Dan,
I successfully used this technique to patch my stubs. Thanks! I do
have a remaining question:
Is there a best practice here? Is calling XxxFault(...,
xxxFaultInstance) the way things are supposed to be done? I'm just
trying to understand the etiology of my issue.
Greg
-Original
Well, largerly as an FYI, there's mojo in 2.2.7 that resolved the
problem. In the hail mary have you updated the firmware spirit, I
built a version on the latest 2.2.7 and it appeared to make the problem
go away for the customer. Unfortunately, I haven't been able to
duplicate the problem on
Hi,
I've got multiple WSDLs and I don't know how to make maven generate code for
all of them at once using wsdl2java plugin (cxf-codegen-plugin). I've tried
adding another execution but it didn't work:
plugin
groupIdorg.apache.cxf/groupId
Multiple executions would work if the id of the executions are each unique.
Like generate-sources-wsdl1, generate-sources-wsdl2, .etcc...
However, you would get better performance by having a single execution. The
wsdlOptions element can have several wsdlOption children, each configuring a
please tell me how can I check the httperror code?, I sent you the complete
stack trace,
should I enable the logging and send you the complete log ?
dkulp wrote:
Any chance you could wireshark this and get the raw transfer bytes. It
LOOKS
like to be that the response coming back is
Hello,
I have tried same truststore and keystore with plain jsse example and I am able
to get response back. Handshake works fine.
However same keystore and truststore I use with CXF webservice client it throws
following exception ..
RECV TLSv1 ALERT: fatal, handshake_failure which means
Thank you Sergey, your suggestion worked when I've added the annotation on my
interface.
Sergey Beryozkin-5 wrote:
Hi, try adding @Consumes(application/x-www-form-urlencoded)
cheers, Sergey
--
View this message in context:
How do I configure CXF to follow redirects? I have a CXF client which fails
because of:
Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking
https://server:/path/to/web/service: Read timed out
However, an older AXIS client I have works with the same URL. I'm fairly
the server is deployed in https , does this have anything to do with this
exception ,mine is a simple client
here is the code
jaxws:client id=findGrantsClient
serviceClass=gov.hhs.acf.webservice.grantsSearch.service.GrantsSearchService
address=${find.grants.service.url}
I checked the http code it is not error code it is response code 200
here is the complete output
2010-04-01 18:33:57,542 [http-8080-4] DEBUG
org.apache.cxf.endpoint.ClientImpl - Invoke, operation info:
[BindingOperationInfo: {http://artms/acf.gov}findGrants], params:
The main thing to look at is:
null: [HTTP/1.1 200 OK]
Date: [Thu, 01 Apr 2010 22:32:56 GMT]
Content-Length: [0]
Set-Cookie:
The Content-Length of 0 means that there is no content in the response. Thus,
something is happening on the server side or something that is causing an
See:
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html
There is an AutoRedirect setting that would be set to true.
That said, with AutoRedirect, we cannot stream. We have to buffer so if a
redirect is triggered, we can resend. Thus, performance would be slightly
On Thursday 01 April 2010 10:01:35 am Vanore, Gregory wrote:
Dan,
I successfully used this technique to patch my stubs. Thanks! I do
have a remaining question:
Is there a best practice here? Is calling XxxFault(...,
xxxFaultInstance) the way things are supposed to be done? I'm just
16 matches
Mail list logo
