Hi thanks a lot for information. I am not very experienced regarding binding
styles but I presume that we are using doc/lit/wrapped. We are suing stubs
and here is how the stub looks like:
@WebService(targetNamespace = http://sapdev06.webmeth65.osl.no/;, name
=
Hi,
I cannot enable a fully MTOM connection on client side using Spring (I've
already seen previous similar posts but not very useful indeed). My
client.xml is:
beans
xmlns=http://www.springframework.org/schema/beans;
No The whole thing runs in an app server and the bus is initialized and the
policy engine is enabled as part of server startup.
-Bharath
On 9/26/07, Sergey Beryozkin [EMAIL PROTECTED] wrote:
Can it be that you enabled the policy engine too late ?
Cheers, Sergey
- Original Message -
The problem here seems to be that the WS-RM layer cannot retrieve the
addressing properties that WS-A layer should have stored in the context.
A couple of questions:
1. In a previous mail on this thread you talked about adding the
RMInterceptors explicitly in code - I presume you're no longer
Hi Glynn
1. In a previous mail on this thread you talked about adding the
RMInterceptors explicitly in code - I presume you're no longer doing
this and are now just relying on the RMAssertion Addressing policies
attached to the WSDL and the PolicyEngine config bean?
Yes Glenn, now I do not add
Hi all,
finally I found the primary cause and fortunately it has nothing with
saaj-impl or cxf at all.
The problem is that all the wars deployed on AIX were obfuscated and know we
have found that when we deploy nonobfuscated wwar, everything is ok.
Still the problem is little bit mysterious,
Benson, Dan,
Could you elaborate a bit on this or detail the steps because I am not
familiar with this. I will then try to test it.
Basically, I have only POGO for which I would like to remove
systematically a property.
Thanks
Guillaume
On 9/21/07, Benson Margulies [EMAIL PROTECTED] wrote:
I
1) Create a brand new java POJO that implements TypeCreator, has a field
of type TypeCreator, and (initially) delegates all the abstract methods
to the field.
2) take your method of TypeCreator that delivers the entire type for a
class, and change it from pure delegation to throwing out the
OK in CXF 2.0.2, there's no need for the UsingAddressing element, so
you can scratch that.
I've put together a quick'n'dirty variant on the ws_rm sample which
illustrates usage of the policy framework to enable WS-RM WS-A, and it
works fine against 2.0.2 CXF.
I'll tar this up and mail it to
Ich werde ab 26.09.2007 nicht im Büro sein. Ich kehre zurück am
27.09.2007.
Bitte kontaktieren Sie in dringenden Fällen das Porsche Informatik Customer
Care Center:
http://www.porsche-informatik.at/sup_kontakt.htm
oder per Web:
http://support.porscheinformatik.at/
Grüße,
Christian Köberl
Hello,
I am learning to use cxf (migrated from xfire) and in previous cxf 2.0
release, I had no problem running the following client creating by using
some of the sample code for cxf with spring.
JaxWsProxyFactoryBean jf = new JaxWsProxyFactoryBean();
Hi,
I have included all jars from cxf 2.0.2 lib directory when running client
and I did not have any problems after that.
Regards,
Aurelije
On 9/26/07, mule1 [EMAIL PROTECTED] wrote:
Hello,
I am learning to use cxf (migrated from xfire) and in previous cxf 2.0
release, I had no problem
I have generated my web service using wsdl/wsd and xml catalogs, but
when I deploy the service fails on deployment when it tries to find
the sources that I used in the xml catalog.
How do I configure cxf when deployed to use the xml catalogs?
On Wednesday 26 September 2007, DSL wrote:
I have generated my web service using wsdl/wsd and xml catalogs, but
when I deploy the service fails on deployment when it tries to find
the sources that I used in the xml catalog.
How do I configure cxf when deployed to use the xml catalogs?
Put
Hello Aurelije,
Were you having this problem before? And after adding some jars the problem
went away? Or you tried with all jars first with no problems?
I verified again that I do have all the necessary exact jars from the cxf
2.0.2 lib directory and I still have the same problem. So, not sure
Hello,
actually in my first email, I was trying to create client two ways and both
ways are resulting in error.
If I use this:
ClientProxyFactoryBean f = new ClientProxyFactoryBean();
f.setAddress(http://localhost:8080/serviceurl;);
f.setServiceClass(MyCxfWebService.class);
Any chance you can wireshark/tcpdump the interaction so we can see what
it on the wire? From the error, it looks like the return message is
messed up somehow.
You could try adding to the SEI interface:
@Features(features = org.apache.cxf.feature.LoggingFeature)
to turn on the logging. If
Which version are u using? 2.0.2?
Are u using ant run your project?
You have to check if the following jars
cxf-rt-bindings-soap
cxf-rt-transports-http
cxf-rt-transports-http-jetty
are in your classpath?
Regards,
James
Hi
I am using web service client that i generated using wsdl2java.
I am
Hi anthony,
I am the developer of GroovyWS and I am currently looking into running
a service into tomcat which looks close to what you are trying to do.
Could you describe a bit more what you're doing currently ? Are you
using GroovyWS or directly CXF ?
If you are using GroovyWS, is your service
19 matches
Mail list logo
