To log soap message, you can use Handler. There should be plenty of examples
on the web to show how to use do it.
Jack
On Mon, Oct 6, 2008 at 9:12 PM, Joshua Partogi <[EMAIL PROTECTED]>wrote:
> Dear all,
>
> I am currently using CXF with JAX-WS. Is it possible for me to get the
> SOAP message gen
Dear all,
I am currently using CXF with JAX-WS. Is it possible for me to get the
SOAP message generated by CXF/JAX-WS from the Java file? because we
need to log down every SOAP message that is generated by the API. If
so is there any resources for me to read regarding this?
Thanks in advance
--
I have deployed CXF as a RAR in JBoss and see the following deployment errors
(though it doesn't seem to affect operations):
17:50:37,309 ERROR [STDERR] Oct 6, 2008 5:50:37 PM
org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl
INFO: ManagedConnectionFactoryImpl constructed without props by apps
I just ran the WSI-I compliance check in SOAP-UI and have attached the
report.
The check failed because of the import element I mentioned in my other
post. When I removed it the check passed.
Greetings
Christian
Alexandre Costa schrieb:
Christian,
Though our WSDL is not "made by hand", i
One thing I found is the following import:
namespace="http://spring.server.webservices.wsadapter.sigasadt.zilics.com.br/";
xmlns="http://www.w3.org/2001/XMLSchema"/>
I do not really understand what this does.
The other thing is the import of the WSDL containing the porttype. When
using .Net ma
The w3c Element is what JAXB unmarshals to if there isn't a real java
class that it knows about that is bound to the element name. This
USUALLY occurs if the parameter is an interface or some other class that
JAXB cannot handle. The other time is if you have a subclass, but the
interface u
By "optional", I assume you mean the minOccurs="0" we put in the wsdl.
Correct?
If so, this is technically a spec compliant thing. Any non-primitives
are optional. Only primitives are required.
With 2.1.2 and earlier, the ONLY way to control this would be to run a
java2ws -wsdl or similar
Good Morning,
I'm using CXF 2.0.7 to publish and acess a WebService in my application.
The project was going well till one of the partners decide to create its
WebService client in Delphi 2007 and other one in .Net (don't know the
language or version for sure).
The result detected is that they f
The best suggestion I would have is to create a CXF client from the WSDL
and try that. Capture the SOAP message from it and then also capture
the message from the Delphi client and compare them.
USUALLY, a null param is the result of the client doing the namespaces
wrong. For example, your s
Christian,
Though our WSDL is not "made by hand", it could lacks some needed
definition.
Follow the file, hoping any one could lend us hints (the time is getting
short critically to us)
Thanks for the attention.
--
Alexandre Augusto Leite Costa
Desenvolvimento
Dextra Sistemas
www.dextra.com.br
Are you allowed to post the WSDL? Perhaps we can help then.
Did you create the WSDL by hand?
Greetings
Christian
Alexandre A. L. Costa schrieb:
Thanks for the tip.
There aren't much "abornal" details for this service. No Exceptions to
be thrown or Security Policy yet. (Though in near futur
Thanks for the tip.
There aren't much "abornal" details for this service. No Exceptions to
be thrown or Security Policy yet. (Though in near future we'll need to
use SSL conection)
Just send an String and receive an String for response.
We have been doing same tests that make us think os pro
I would have them test your web service with SOAP UI. If it works with SOAP
UI but not their client, greater focus should be on the client instead of
the web service provider.
Can you tell us something about the web service operation--anything strange
or out-of-the-ordinary about the parameters
Can you try with 2.1.2 and/or the 2.1.3 snapshots? A bunch of fixes for
this went into 2.1.1 so 2.1.2 should help. A couple more smaller fixes
are going in for 2.1.3. Confirmation that it does fix the issue would
be great.
Dan
On Monday 06 October 2008, Teva BREDIN wrote:
> Hi,
>
> I ha
On Monday 06 October 2008, jmdev wrote:
> One additional data point in case it will help... Once the
> interceptors remove the "wsu" namespace declaration, it is not defined
> anywhere else in the document. Even though it is used for the
> attribute, the out-of-the-box interceptors remove the dec
Hi,
I had the same error when i was using to include a schema in my
wsdl (like you did)
I used instead and it worked.
Example of use:
http://www.w3.org/2001/XMLSchema";>
Perhaps it could helps.
Best regards,
Teva.
Nikolaj A. wrote:
>
> System specs.
> CXF 2.1
> Tomcat 5.5.17 (I know
Good Morning,
I'm using CXF 2.0.7 to publish and acess a WebService in my application.
The project was going well till one of the partners decide to create its
WebService client in Delphi 2007 and other one in .Net (don't know the
language or version for sure).
The result detected is that they f
One additional data point in case it will help... Once the interceptors
remove the "wsu" namespace declaration, it is not defined anywhere else in
the document. Even though it is used for the attribute, the out-of-the-box
interceptors remove the declaration.
I hope you can provide some assistan
Im kinda a newb to using jax-ws annotations. I have created a WebService
using jax-ws annotations that I'm exposing using CXF. I have explicitly
marked it as DOC, LITERAL and all my java clients & SOAP-UI can use it fine.
Unfortunately a FLEX client is having issues and I think it maybe because
Thank you for replying so soon
It works , thanks a lot.
2008/10/6 Sergey Beryozkin <[EMAIL PROTECTED]>:
> Hi,
>
> Try @ProduceMime("application/json;charset=UTF-8")
>
> Cheers, Sergey
>
Hi,
Try @ProduceMime("application/json;charset=UTF-8")
Cheers, Sergey
- Original Message -
From: "smallufo" <[EMAIL PROTECTED]>
To:
Sent: Monday, October 06, 2008 1:04 PM
Subject: JAX-RS : How to change encoding or charset ?
I am using cxf 2.1.2 to publish my service to json objec
I am using cxf 2.1.2 to publish my service to json objects.
But all Chinese/Japanese characters are all truncated.
I tried to find something @charset or @encoding annotation , want to
change the encoding to "UTF-8"
But cannot find an answer ...
Can somebody tell me how to accomplish this ? Thanks
Hi
JAX-RS 0.8 api is supported at the moment.
Cheers, Sergey
[1] https://jsr311.dev.java.net/nonav/releases/0.8/index.html
- Original Message -
From: "sabernard" <[EMAIL PROTECTED]>
To:
Sent: Friday, October 03, 2008 7:52 PM
Subject: Setting up REST services with CXF - which versio
23 matches
Mail list logo
