Unfortunately this doesn't work either. I use Log4J and tried to set the
levels for the interceptor to FATAL even, but the exception gets logged on
the server anyway.
This is very annoying. My testcases are flooded with exceptions.
Has anyone even encountered this problem? Is it a bug? How would
Liu, Jervis wrote:
-Original Message-
From: Charles W. Stanton [mailto:[EMAIL PROTECTED]
Sent: 2008年1月15日 23:38
To: cxf-user@incubator.apache.org
Subject: REST with different return formats
I want to write RESTful services, utilizing some of the same Service
classes
I've
-Original Message-
From: James.Strachan [mailto:[EMAIL PROTECTED]
Sent: 2008年1月16日 18:54
To: cxf-user@incubator.apache.org
Subject: RE: REST with different return formats
Liu, Jervis wrote:
-Original Message-
From: Charles W. Stanton [mailto:[EMAIL PROTECTED]
Hi Pawel,
please see the documentation for the handleUsernameToken method:
http://ws.apache.org/wss4j/apidocs/org/apache/ws/security/processor/User
nameTokenProcessor.html#handleUsernameToken(org.w3c.dom.Element,%20javax
.security.auth.callback.CallbackHandler)
namely
If the password is of
On Tuesday 15 January 2008, Mayank Thakore wrote:
Actually that is what I had tried initially. I added an interceptor at
the end and used a flag on the message to decide on reprocessing. But
it didn't work after 2 and half days of effort so I gave in to
modifying cxf code.
Most likely, the
Well, customer is king. With all the advantages, customer says it is an
overhead to maintain state info. So they want a way to send extra responses
from inside the service implementation code :)
My boss, already sent me some sample code on how to create an outgoing
interceptor chain to do this.
So after some thought and tweaking I adjusted my JSON service, but I am getting
the 'Invalid URL/Verb combination. Verb: POST Path: /message' exception.
My service looks like this:
@WebService(targetNamespace = http://com.cbs.bos.ws.json;)
public interface BoardService {
@Post
Hello, at work I'm having slight difficulties in upgrading from CXF 2.0.2 to
2.0.3. I'm noticing a strange CXF dependency in one of our pom.xml files:
dependency
groupIdorg.apache.cxf/groupId
where to find classpath:META-INF? Could you pls give me the link?
---
willem.jiang wrote:
They are the spring description files of cxf components.
import resource=classpath:META-INF/cxf/cxf.xml / this is the cxf core
component.
import
Hi,
I'm using java 6 and was wondering what (if any) jars I can remove from
my libs when using cxf?
It seems I can remove the following and everything still compiles:
jaxws-api.jar
saaj-api.jar
jaxb-api.jar
jaxb-impl.jar
stax-api.jar
is this correct?
anything else?
- Jonathan
I need to integrate CXF to my existing web application. My existing web
application has integration with Spring. Spring will load configuration from
a rootConfiguration.xml
//rootConfiguration.xml
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
It's just a directory in the jar files.
On Wed, 2008-01-16 at 10:04 -0800, yulinxp wrote:
where to find classpath:META-INF? Could you pls give me the link?
---
willem.jiang wrote:
They are the spring description files of cxf components.
import
Hello,
I'm not sure if this is an issue or lack of correct configuration on my
part.
I found that it is real easy to bypass the security checks (UsernameToken,
Timestamp, and/or Signature) for the WS Security settings.
All you have to do is setup the client request to pass a wsse:Security
tag
I found them. They're in the cxf-xxx-jar/META-INF/cxf/
-
yulinxp wrote:
where to find classpath:META-INF? Could you pls give me the link?
---
willem.jiang wrote:
They are the spring description files of cxf components.
When I specify these three xml files, tomcat loads them:
INFO: Loading XML bean definitions from ServletContext resource
[/WEB-INF/beans.xml]
Jan 16, 2008 1:45:42 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefini
tions
INFO: Loading XML bean definitions from class
I actually made progress - I can submit the data in but it is being marshalled
out incorrectly and exceptionin - I believe I have set up the xml attributes
correctly on each of my objecrs, there are akin to:
@XmlType(name = wsResponse, namespace = http://json.ws.bos.cbs.com/;,
On Wednesday 16 January 2008, jonathan doklovic wrote:
Hi,
I'm using java 6 and was wondering what (if any) jars I can remove
from my libs when using cxf?
It seems I can remove the following and everything still compiles:
jaxws-api.jar
saaj-api.jar
jaxb-api.jar
jaxb-impl.jar
I'd be
Glen,
Yep, it exists. It's the original implementation for the REST stuff in
CXF. Long term, it may be superceeded by the jaxrs/jsr311 stuff, but
it is there today. That said, you probably don't need it.
Dan
On Wednesday 16 January 2008, Glen Mazza wrote:
Hello, at work I'm having
More info.
Looking at the latest wss4j code (1.5.3), the routine ignores the fact
that the wsse:Security is empty and falls out indicating that all is well.
They have the code to catch this hole commented out for some reason.
protected boolean checkReceiverResults(Vector wsResult, Vector
Hi all,
I am wondering if there has been any progress on JIRA issue CXF-927?
If not, I'd like to encourage the CXF team to give this issue some
attention. :-)
I guess the provided WSDL file can serve as a test case.
The WSDL at the bottom of this post produces the following interface
public
Hi all,
I am wondering if there has been any progress on JIRA issue CXF-927?
If not, I'd like to encourage the CXF team to give this issue some
attention. :-)
I guess the provided WSDL file can serve as a test case.
The WSDL at the bottom of this post produces the following interface
public
[ I posted this accidentally under cxf-issues, so I'm reposting here]
The summery:
-
I'm trying to use wsdl2java to generate a simple test REST client, with HTTP
binding (not SOAP).
It seems that either:
A) There is a problem with the wsdl2java which somehow expects a SOAP
P.S: I'm using wsdl2java from CXF-2.0.3
Thanks,
Erez.
--
View this message in context:
http://www.nabble.com/wsdl2java-generates-SOAP-annotations-for-non-soap-portType-tp14893452p14893455.html
Sent from the cxf-user mailing list archive at Nabble.com.
WSS4J actually has a bug logged on this point. See
http://issues.apache.org/jira/browse/WSS-70 .
The question now is - should CXF fix this or should all users of CXF be
aware of the need to check the actions size yourself?
[EMAIL PROTECTED]
01/16/2008 02:20 PM
Please respond to
I'll third this notion of being able to override the accept headers with a
change to the URL (like a query parameter) because we don't always have
control over our clients, right? If we are offering publicly-facing web
services, we don't know who is consuming our services or how. It is far
This technique doesn't seem to work for exceptions. I have an exception
package with all exception classes defined. When I use package-info with a
namespace definition, JAXB seems to ignore it. I am able to get the
exception class map to a namespace only by using @WebFault. Any pointers on
how to
You got 'Invalid URL/Verb combination. Verb: POST Path: /message' exception
when the combination of Verb: POST and Path: /message did not find a method
from your service. Not sure why though as your service looks alright. You may
want to paste out the initialization information when your server
27 matches
Mail list logo