Hello everybody,
I have created a Web Service using Sun's Metro stack (i.e., JAX-WS + WSIT).
For this, I also created a policy file that works well with the WSIT
implementation of WS-Policy/WS-SecurityPolicy/... Now, I would like to create
a CXF-based Web Service + client for the same
Hi
Unfortunately, no WS-SecurityPolicy is supported by CXF at this point of time
though I believe people are planning to gradually add the support for it.
The only workaround I can suggest at this point of time is to translate
WS-PolicySecurity settings into corresponding
CXF configuration
Jiang, Ning (Willem) wrote:
Hi Gilles,
Do you need to use the Client to invoke the service in your unit test?
If so , you need to use the below code to trigger the LocalConduit direct
dispatch.
Thank you.
It works
But now I have to find why I get a NullPointerException in
SoapOutInterceptor
Hi Roger,
If you want to use the https transport by leveraging the Servlet
transport , you do not need to specify the httpj:engine-factory in your
bean.xml.
httpj:engine-factory only take effect if you use the jetty as your http
transport engine.
After I went through your bean.xml, I can't found
Sorry, I forget to attach the url.
It is
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
Willem.
Willem Jiang wrote:
Hi Roger,
If you want to use the https transport by leveraging the Servlet
transport , you do not need to specify the httpj:engine-factory in your
Willem:
thanks a lots for your help.
you are right.we do not need to add httpj:engine-factory to our spring config
file --beans.xml.
i solved this problem. i config ssl on my weblogic9.2. and i can use the client
generated from WSDL call the webservice with web security over https protocal.
This a well know issue, you can find the issues from the below URLs.
[1]CXF JIRA 922
https://issues.apache.org/jira/browse/CXF-922
[2]Set the SSL parament with Java API
http://www.nabble.com/Error-when-trying-to-contact-service-over-SSL-on-a-specific-port-tf4424617.html#a12654695
BTW, here is
Hi,
It is the endpoint url, not the base address.
For your case, it is
http://localhost:8080/erh-backoffice/services/backoffice;
HTH...
Jeff
Jean-François Daune wrote:
Hi,
I try to create a client using JaxWsProxyFactoryBean, but I don't know what
'address' property refers to.
Must it
Hi Willem,
I know that I have to set the CXFServelt Bus, but I do not see a way to get a
reference of the CXFServlet in my test JSP. I find some mails where the setting
of the CXFServlet bus was described, but I did not find any info, on how the
obtain this reference.
Is there maybe a way
Hi,
Which CXF version are you using?
Can you access the service with http transport?
I just checked the code in the trunk
XMLStreamWriter xtw = message.getContent(XMLStreamWriter.class);
* xtw.setPrefix(soapVersion.getPrefix(), soapVersion.getNamespace());
I guess the NPE is came from xtw, but
Hi,
I try to create a client using JaxWsProxyFactoryBean, but I don't know what
'address' property refers to.
Must it point to a WSDL URL?
The CXF doc
(http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html) is
suprising.
It points to the 'base address' of the web service. For
Hi ,
You can have a look at the CXFServlet code[1] to see how it setup the
default transport to servlet transport :)
I remember there is a way to get the servlet's reference from other
servlet , may be you need use google to find them.
It works fine, thank you.
But I guess the documentation is wrong.
J-F
-Message d'origine-
De : Jeff.Yu [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 21 septembre 2007 11:46
À : cxf-user@incubator.apache.org
Objet : Re: Address to put in JaxWsProxyFactoryBean
Hi,
It is the endpoint
We started some discussion the other day about CXF+Acegi out there the
other day, but hadn't seen anything since. Any discussion after I sent
the source code or my findings with integrating the two?
On Tue, 2007-09-18 at 11:18 -0400, Eric Miles wrote:
Actually, here is the code. Attached is
Hi Dan,
Yes, the 2.1 migration guide is very important.
Merging the utilities and rt-core modules with the api module makes
sense as they are all part of the api but there may be an argument for
keeping some separation between must have and can have api
functionality.
For example, to create and
Hello everyone,
i'm a newbie of CXF and webservices in general, so sorry if my
question is somehow dumb.
I create a webservice using the SimpleFrontEnd. Once
wsServerFactoryBean.create() method is invoked, the corresponding wsdl
is made available at the expected address.
Also, i see this output
I'm testing my newly converted XFire to CXF services and so far I haven't
gotten a single request to complete successfully. Currently when I make a
request to one of my methods that simple returns a preconstructed JAXB
object, I get the following exception. This used to work with XFire, so I'm
Sorry, I didn't finish that message, at the end is a line of code. This is
line 76 in JBIDestinationOutputStream where the exception occurs:
ByteArrayOutputStream baos = (ByteArrayOutputStream)getOut();
On 9/21/07, Ryan Moquin [EMAIL PROTECTED] wrote:
I'm testing my newly converted XFire to
Benson,
Do you know how to do that? If it does not work, I would have to choose
different framework instead.
Regards,
Ramanand Singh
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 19, 2007 6:18 PM
To: cxf-user@incubator.apache.org
There seems to be an renewed interest for Aegi on the list (thanks Benson ;-) )
Can someone comment if what I want to achieve is do-able ? According
to Dan D. it is. I am clueless regarding step 4 (quoted below)
Thanks
Guillaume
-- Forwarded message --
From: tog [EMAIL PROTECTED]
The complaint you are getting is that
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl, which is what is in
your jaxp.properties, is incompatible with
javax.xml.parsers.DocumentBuilderFactory.
This doesn't make much sense to me. I'm a bit rusty on the curious
behavior of webapp class loaders.
Jonas,
I believe this is fixed in 2.0.2. There definitely was a bug where
methods that had no params, but did have headers, would cause this
error. Is there any chance you could give the 2.0.2 release candidate a
try to make sure?
One more note... if you use anything that requires the SAAJ model
(ws-security being one, JAX-WS SOAP Handlers being another), you may run
into a different issue. The Sun reference impl of SAAJ doesn't work on
the IBM JDK that they usually use for websphere unless you grab the sun
jaxp
Brad,
I've made some changes to make sure we try and map any charset values
that are passed in into the canonical forms the parser may expect. The
result is that in your case, the ENCODING does get set to UTF-8 on the
message instead of utf-8. Hopefully that solves the problem.
I'll try
I don't have a clue why DefaultTypeMappingRegistry is final. It looks
like a mistake. Why put protected methods in a final class?
Here's my temporary prescription.
1) make a subclass of XMLTypeCreator. You'll probably have to override
createClassInfo(PropertyDescriptor). If you get one of the
Is there any furtur information down the stack trace? It would be nice
if it could say it couldn't create it due to a class not found or
something.
You might want to put the jboss-saaj stuff back and then remove ours.
That might work.
Dan
On Wednesday 19 September 2007, Axel
FYI:
The ws_addressing sample we ship does have a client.xml spring config to
configure the a few things on the client side including the
http-conduit.
Dan
On Tuesday 18 September 2007, Glen Mazza wrote:
Thanks...it just occurred to me to Google an example, this one (which
uses a CXF
Should I patch the latest CXF in the source repository, build it and then
check out the latest servicemix and build that?
Do I need to do anything to the service archives in the snapshot I
downloaded and deployed the other day? I guess I'm not sure the proper way
to build and test, versionwise.
Ah, I was curious to check everything out and build it since I haven't done
that with an open source project before, only stuff within companies I've
worked for, so just trying to understand how to do it. :)
I can just do a junit test, but then how would I go about patching what I
have if the fix
Ramanand,
Is this on an IBM JDK? If so, you will probably need to grab the Sun
jaxp implementation and add to you jre/lib/endorsed dir. You can grab
it from:
http://download.java.net/maven/1/com.sun.xml.parsers/jars/jaxp-ri-1.4.1.jar
This is a limitation of the Sun reference implementation
Anyway, you'd have to checkout cxf trunk, apply the patch, build.
Then checkout servicemix trunk, change the cxf version in the root pom
to the cxf version you just built, compile ... and test.
Well, i suppose it may be easier to create a junit test to reroduce
the problem and test the fix.
On
All...
I'm trying to get handlers working on my JAX-WS service without success. I
based my work off of the logging example that ships with CXF v2.0.1. My
handler is registering fine and get called but I get the following errors
showing up in my Tomcat logs as soon as I call
Hi,
You need to set the factory with the address that you got from the wsdl
(http://localhost:8080/Service?wsdl).
It must be something like this http://localhost:8080/Service/***;
Willem.
-Original Message-
From: Valerio Schiavoni [mailto:[EMAIL PROTECTED]
Sent: Sat 9/22/2007 0:07
33 matches
Mail list logo
