Hi @,
i am currently developping a Web Application Front-End, which ist communcating
with a Web-Service Back-End. For SOAP Handling we decided to use CXF (with
MTOM!). The Front-End Rendering etc. is being done with JSP / JSF (MyFaces
Implementation).
Now everything works fine and
Details please.
1) What version of CXF?
2) What frontend and data binding?
3) I read you to be saying that Strings are mishandled in the actual java
object fields, not in the MTOM attachment content, but please confirm.
4) What is the client? The most straightforward explanation here is that the
Hi Benson,
first of all, thanks for your fast reply.
Based on your questions, i checked some stuff, where i thought YOU could base
your next answer on.
So i checked the CXF versions of Service and Client, and i found out, that the
client was running v2.1.6 and the service was running 2.1.4.
Daniel,
I suspect that your problem is in your JSP pages. Does the problematic data
come from HTML form posts? Are you sure that the Content-Type on the html
page with the form says 'charset=utf-8'?
Are you using the client proxy directly from JSP, or is there an intervening
bean? I ask because
We do not have the web services feature pack installed.
oakridge wrote:
Those of you who have fixed this issue, do you have the web services
feature pack installed?
Thanks.
--
View this message in context:
http://old.nabble.com/CXF-and-WAS-6.1%28.0.19%29-tp26028639p26128961.html
Alright, i once again debugged it, and found out the following:
Soap Message have the Attribute ENCODING set to ISO-8859-1 but in the
Content-Type attribute charset in the Payload is set to UTF-8.
Is Payload MTOM specific?
Ok this is the one aspect. The other aspect is, that the String comes
We got it working with some differences described in this thread:
http://www.nabble.com/Re%3A-CXF-and-WAS-6.1%28.0.19%29-p26119183.html
We did not include the metadata jar in the shared lib - this jar is only in
web-inf/lib.
oakridge wrote:
So I've followed the documentation here:
We got it working with some differences described in this thread:
http://www.nabble.com/Re%3A-CXF-and-WAS-6.1%28.0.19%29-p26119183.html
We did not include the metadata jar in the shared lib - this jar is only in
web-inf/lib.
oakridge wrote:
So I've followed the documentation here:
Please send a complete dump of the soap message. That encoding disturbs me.
On Fri, Oct 30, 2009 at 8:22 AM, Daniel Weidele weid...@esteam.de wrote:
Alright, i once again debugged it, and found out the following:
Soap Message have the Attribute ENCODING set to ISO-8859-1 but in the
(1) Alright so this what the client sent tot he server when creating a
Composition. You can find the problematic String at the Tag
collection_name. This is what i want to SAVE at service side.
30.10.2009 13:40:06 org.apache.cxf.interceptor.LoggingInInterceptor logging
INFO: Inbound Message
I need Dan Kulp's help at this point, I'm not sure if I'm right that that
Encoding: ISO... is a problem.
On Fri, Oct 30, 2009 at 8:48 AM, Daniel Weidele weid...@esteam.de wrote:
(1) Alright so this what the client sent tot he server when creating a
Composition. You can find the problematic
On Thu October 29 2009 9:07:16 pm Arik Gorelik wrote:
Basically, I am wondering if it is possible to set something in the soap
response header in the interceptor (not in the service method
implementation) during PRE_STREAM phase.
Well, yea, but in an interceptor you have two options:
1)
On Thu October 29 2009 5:16:03 pm Benson Margulies wrote:
I've got an object with some internal state. I want the state to travel
across the wire to a client, and come back, but I don't want a public
setter.
Is there a way of using JAXB annotations to achieve this?
I THINK if you use the
Hi there!
I was wondering how long the cxf-dosgi-ri-dsw-cxf bundle takes until it is
started.
I'm using equinox org.eclipse.osgi_3.5.0 with the cxf multibundle SNAPSHOT
and it takes about 20 seconds until the bundle (not the framework!) is
started and some seconds more until the endpoints are
Anyone?
On Thu, Oct 29, 2009 at 2:59 PM, Craig Tataryn crai...@tataryn.net wrote:
Repeatedly running into a problem in our project where we have a
multi-module Maven project structured such that a set of 3rd party
schemas are held in one module (packaged as a Jar) and several web
service
Great. Thank you for the pointers. I am able to get the 'SoapMessage'
reference and call getHeaders, get the List, etc, etc. My interceptor is in
the PRE_STREAM phase and I am also experimenting in the MARSHAL phase as
well.
However, I cannot seem to figure out how to bind my string literal id to
If it's something as simple as just a String, it's probably easier to just use
a DOM and don't bother with the Databinding stuff. Using some CXF utils:
Document doc = XMLUtils.newDocument();
Element el = XMLUtils.createElementNS(doc, qname);
el.appendChild(XMLUtils.createTextNode(doc,
Any chance you could package up a small test case with a couple dumb schemas
and log some JIRA's. The relative includes should be relative from the
schema that defines that include, not the root wsdl. Thus, that part MAY be a
bug.
The validation thing is another issue and really surprises
Can you retry with 2.1.7?
There was a bug in the attachment deserializer that was causing it to not
reset the message encoding to the encoding in the part. Basically, it always
used the encoding from the HTTP header (which, in your case, there wasn't one
so defaulted to ISO-8859-1 as per
Can you kill -3 the container during this and see the stack trace? I'm
wondering if it's downloading a schema off the internet or something.
Dan
On Fri October 30 2009 10:47:38 am florian.gru...@icw.de wrote:
Hi there!
I was wondering how long the cxf-dosgi-ri-dsw-cxf bundle takes until
I've managed to get this working by including the needed JAXWS Geronimo JARs
and not including the web services feature pack or a custom class loader. I
don't have all the CXF required JARs due to internal conflicts, but in the
end no special configuration was needed outside adding the Geronimo
That's awesome! I am able to get the value back in the header response. Just
need to figure out how to set the name of the element (default is 'Header').
Still, the header part seems kind of tricky to me. Perhaps the
@WebParam(header=true) way is much simpler, but unfortunately I cannot use
I figured out how to change the element name, it is just the 'localPart'
attribute of the QName. Still struggling on how to get the correct
targetNamespace (for the service endpoint) instead of the default one
xmlns=http://schemas.xmlsoap.org/soap/envelope/
On Fri, Oct 30, 2009 at 10:31 AM, Arik
On Thu October 29 2009 12:22:35 pm Benson Margulies wrote:
Has anyone ever run a CXF service for maven integration tests by putting
one of the container plugins into pre-integration/post-integration?
No, but I've often wondered if doing something like that for the systests
might be better.
You need to check the versions of the jars you are picking up. You seem to
be picking up an older version of cxf-api jar, but newer versions of cxf-rt-
transport-http.
Most likely, you are conflicting with things already built into Mule. If they
would upgrade their
I got it to work it is not too bad. mvnDebug is your friend.
On Oct 30, 2009, at 2:13 PM, Daniel Kulp dk...@apache.org wrote:
On Thu October 29 2009 12:22:35 pm Benson Margulies wrote:
Has anyone ever run a CXF service for maven integration tests by
putting
one of the container plugins
Is there a way to retrieve the targetNamespace from the message, its QNames
(from Version of the message)?
For example if I have something like this on the service classt:
@WebService(portName = TestService,
serviceName = TestServiceService,
*targetNamespace =
I think I figured it out as well.
I looked at the generated code (from wsdl2java) and my TestServiceService
had a public static Qname called TestService which has the correct
targetNamespace. I am just using that QName to create the Header reference
and add to the list of headers in the
Just an update, ran into a problem with SAAJ so I had to make it so
the Sun SAAJ jars weren't being bundled with the war, and I added them
to a shared library along with the Sun jaxp-ri jar (as Sun's saaj
implementation directly references the Sun jaxp-ri classes)
Here's what my shared lib now
Cool. What did your web-inf/lib end up including?
oakridge wrote:
I've managed to get this working by including the needed JAXWS Geronimo
JARs and not including the web services feature pack or a custom class
loader. I don't have all the CXF required JARs due to internal conflicts,
but
I´ll try it ASAP, thank you
On Tue, Oct 27, 2009 at 2:24 PM, Daniel Kulp dk...@apache.org wrote:
Other than the soapenv:encodingStyle attribute which I don't think you'll
ever
get output other than writing an interceptor to add it, you could probably
do
something like:
Hi,
I'm using FUSE ESB 4.1.0.2 that I believe has CXF 2.2.2.1-fuse installed.
I'm trying to achieve the same but i can not upgrade CXF . Is there another
solution ?
Thanks,
-Marcel
dkulp wrote:
What version of CXF?Definitely upgrade to the latest.There was
some
bugs in
32 matches
Mail list logo
