Fred,
Thanks for the tip. Forgive me (I'm most likely wrong!) but that looked like
a Username token not an X.509 token request. I've been digging around in
http://xfire.codehaus.org/WS-Security but I can't see any wisdom there.
Anything else?
:)
Sincerely,
Ada
Fred Dushin-3 wrote:
All I
Glen,
I tried several variations. Again, I've read the paragraph that you've
pointed to and tried out two possibilities:
1. Literally interpreted: the service's namespace= {Webservice_Server}. The
portname= Webservice_ServerSOAPPort
So we get:
I guess we could preserve the existing behavior while still use the correct
bean. We just need to take into account the path separator / and only
select the one that has a full match.
On Mon, Apr 14, 2008 at 4:15 AM, Willem Jiang [EMAIL PROTECTED]
wrote:
That is because CXF support to map a
Hello,
I'm looking into providing some REST based services with CXF. The examples
are great but I can't see something demonstrating error handling. While
error handling with REST doesn't seem to be particularly well defined,
HTTP status codes would surfice. How easy is this to achieve with
Thanks a lot.
My tests are ok now.
Regards
Brice Vandeputte
-Message d'origine-
De : Benson Margulies [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 11 avril 2008 20:25
À : cxf-user@incubator.apache.org
Objet : Re: [HelloWorld JavaScript client] problem on IE.
There's a new snapshot.
Hi
This would be fairly easy to do with JAX-RS. There's a number of ways to
propogate HTTP errors with JAX-RS from your application code :
1. throw WenApplicationException
public void putIt(String s) {
throw new WebApplicationException()
}
By default it will cause 500.
2. You can also
That's great. Is this included in one of the examples, or do you have
something you can zip up and send me? The example set with CXF is
brilliant - running stuff that actually works (with ant) makes the product
so much easier to comprehend.
John Baker
--
Web SSO
IT Infrastructure
Deutsche
Is jax-rs included with CXF?
John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank London
URL: http://websso.cto.gt.intranet.db.com
---
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error)
Hiya,
I'll look at 2.1. This document is very useful:
http://cwiki.apache.org/CXF20DOC/jax-rs-jsr-311.html
It probably just needs a little work to expand on some of the topics to
answer questions covering status codes, security, etc.
John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank
Hi all,
I have an interoperability problem when calling an Apache CXF Web
service (CXF version is 2.0.4) running under Apache Tomcat 6 from a VBA
client program using MS Office 2003 Web Services Toolkit 2.03. When
sending a request from the VBA client to the server, the response fails
with
Tryed also with CXF 2.0.5.. same results.
Oh, in the last post i mess with copy/paste.. this is my endpoint
definition:
jaxws:endpoint
id=ese6ordine
serviceName=s:OrdineService
implementor=isi.esercitazione.java2wsdl.Server
address=/ordine
yes, this was the problem, I was using Artix IDE to generate jar. As i was
not compiling from the SOURCE folder in my Java Project, it did not put
the package-info.java file in the jar, and hence getting this problem.
Thanks again.
dkulp wrote:
On Thursday 10 April 2008, mmansoor wrote:
Ok... it don't seems a configuration error...
In my wsdl i have 2 operation, a request/response and a Oneway.
If i remove the Oneway it works!!
If i add it all operations are threated as Oneway..
Seems a bug.. someone can try to reproduce it?
Cencio wrote:
Tryed also with CXF 2.0.5..
Pierre,
The WSI-Basic Profile specifically states that in RPC/Literal, the part
accessor elements are ALWAYS to be unqualified. This is per WSI-BP
spec. Basically, in RPC/Literal, the wrapper element (operationName)
is qualified, the part accessor elements are unqualified, and the
On Monday 14 April 2008, Cencio wrote:
If i remove the wsdlLocation, the wsdl is correctly generated and
everything works fine (all calls are replyed with my message). If i
leave, the http://localhost:8080/ese6/ordine?wsdl is correctly showign
WEB-INF/ordini.wsdl but all calls are threat as
Are there any plans on implementing ws-transaction specs with apache cxf or
is there any work going on regarding this yet?
Thanks,
I got the testcase, thanks.
Just to clarify, I need to uncomment the operation in the wsdl as well.
That said, if I do that, it actually works for me with the 2.1 trunk. I
get:
[java] Invoking notifica...
[java] Invoking submitOrdine...
[java] submitOrdine.result=123456
I am trying to setup a UserService via Spring that takes a userId, and
returns a User object.
I setup a LoggingInterceptor, and I seem to be getting a user object back:
*INFO: Outbound Message
---
Encoding: UTF-8
Headers: {SOAPAction=[], Accept=[*]}
Messages:
Payload:
Hi all,
where can I find more information regarding jetty-configuration?
I took a look at the
http://cwiki.apache.org/CXF20DOC/jetty-configuration.html page, but some
things are still unclear to me, e.g. how does this fit in the server
configuration/initialization and what should be done on the
Few questions:
1) Is there a wsdl for this service?
2) How is your factory configured/created? Do you have the code?
3) Is your factory a simple frontend or jaxws? If jaxws, is the
UserManager class properly annotated?
It looks like the service is either RPC/Literal or it's using a mix
Hm... well, this isn't quite as easy as I had hoped it would be due to a
protected method that probably should be public.
Right now, the ONLY way to configure the session support is via a spring
config. Thus, in your test, you could have a spring xml config to
configure the session
This is now fixed on trunk. I'll get another 2.1 snapshot out later
today as there are several other fixes that need to get out to people to
test as well.
Dan
On Monday 14 April 2008, Daniel Kulp wrote:
I got the testcase, thanks.
Just to clarify, I need to uncomment the operation in
Even this?
!-- --
!-- This bean is an Out interceptor which will add a Timestamp,
--
!-- sign the Timstamp and Body, and then encrypt the Timestamp --
!-- and Body. It uses 3DES as the symmetric key algorithm. --
!-- --
bean
That message is coming out of the Sun reference implementation, not CXF.
Somehow, the RI is being picked up in stead of CXF. Can you make sure
the CXF jars are properly in the war or available in the app server
classpath? In particular, if you aren't using the CXF bundle jar, you
would
Hi dkulp,
First, tks a lot for the first post! :D It seems like I am now nearer than
I was before ;). So... After changing from JVM 1.6 to 1.5 and adding a few
(missing) libraries to classpath I got this exception:
java.lang.RuntimeException: Could not find destination factory for transport
Hello CXF gurus,
I have a question related to using WSS to delegate auth calls to JAAS.
I obtain the user name and password at run-time and send it in a Web
Services Security (WSS) UsernameToken to the server and on the server
side I would like to use JAAS authentication to authenticate the
So my service names should start with a unique name like... 1Address,
2Address, 3Address.
Is this a limitation of this implementation?
Thanks!
Arul
Willem Jiang wrote:
That is because CXF support to map a Http request to a soap request,
such as
I am getting this error now:
*INFO: Interceptor has thrown exception, unwinding now
java.lang.RuntimeException: org.apache.cxf.aegis.DatabindingException: No
write method for property {http://domain.baselogic.com}version in class
com.baselogic.domain.Address
at
28 matches
Mail list logo
