Re: encoding of SOAP responses
No problem! It used to be ok when Axis2 was on 1.1 and Axis1 was on
1.3. Its only going to get worse when they are both on 1.4!!!
Paul
On Feb 11, 2008 12:30 PM, Rushikesh Thakkar <[EMAIL PROTECTED]> wrote:
> Oh yeah,
> excuse me..
>
> Thanks Paul.
>
>
>
> On Feb 11, 2008 1:25 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Unfortunately you've explained how to do it with Axis1 not Axis2.
> >
> > In Axis2 do:
> >
> >
> stub._getServiceClient().getOptions().setProperty(org.apache.axis2.Constants.Configuration.CHARACTER_SET_ENCODING,
> > "ISO-8859-1");
> >
> > No need to edit the generated stub.
> >
> > Paul
> >
> >
> >
> >
> > On Feb 11, 2008 10:57 AM, Rushikesh Thakkar <[EMAIL PROTECTED]>
> wrote:
> > > Yes, It is possible. Please change the following line in your Stub
> generated
> > > by WSDL2Java
> > >
> > > File: XxxxBindingStub.java
> > >
> > >
> > >
> > > In createCall() method:
> > >
> > >
> > >
> > > protected org.apache.axis.client.Call createCall() throws
> > > java.rmi.RemoteException {
> > >
> > > …
> > >
> > > …
> > >
> > > while (keys.hasMoreElements()) {
> > >
> > > java.lang.String key = (java.lang.String) keys.nextElement();
> > >
> > > _call.setProperty(key, super.cachedProperties.get(key));
> > >
> > > }
> > >
> > > // change it to the encoding you want..
> > >
> > > _call.setProperty(org.apache.axis.client.Call.CHARACTER_SET_ENCODING,
> > > "ISO-8859-1");
> > >
> > >
> > >
> > > synchronized (this) {
> > >
> > > …
> > >
> > > }
> > > }
> > >
> > > See if this works!!
> > >
> > > cheers,
> > > Rushikesh
> > >
> > >
> > > On 2/8/08, Jan Philipp Seng <[EMAIL PROTECTED]> wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > >
> > > >
> > > > I am using Axis2 1.3 with ADB. There is a demand to deliver the SOAP
> > > responses in latin1 (ISO-8859-1) instead of UTF-8. Can I change the
> encoding
> > > of SOAP responses?
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Jan
> > > >
> > > >
> > > >
> > > > Gruß,
> > > >
> > > > Jan
> > > >
> > > > __
> > > >
> > > >
> > > >
> > > > Jan Philipp Seng
> > > >
> > > > IT-Entwicklung
> > > >
> > > >
> > > >
> > > > TravelTainment AG
> > > >
> > > > Carlo-Schmid-Straße 12
> > > >
> > > > 52146 Würselen/Aachen
> > > >
> > > > Germany
> > > >
> > > > Tel: +49 (0)2405 - 4484-50
> > > >
> > > > Fax: +49 (0)2405 - 4484-90
> > > >
> > > > email: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > > > Amtsgericht Aachen, HRB 8173
> > > >
> > > > Vorstand: Ralf Usbeck (Vors.), Michael Kalt; Aufsichtsratvorsitzender:
> > > Philippe Chérèque
> > > >
> > > >
> > > >
> > > > http://www.traveltainment.de
> > > >
> > > > http://www.vidado.com
> > > >
> > > >
> > >
> > >
> >
> >
> >
> > --
> > Paul Fremantle
> > Co-Founder and VP of Technical Sales, WSO2
> > OASIS WS-RX TC Co-chair
> >
> > blog: http://pzf.fremantle.org
> > [EMAIL PROTECTED]
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding of SOAP responses
Unfortunately you've explained how to do it with Axis1 not Axis2.
In Axis2 do:
stub._getServiceClient().getOptions().setProperty(org.apache.axis2.Constants.Configuration.CHARACTER_SET_ENCODING,
"ISO-8859-1");
No need to edit the generated stub.
Paul
On Feb 11, 2008 10:57 AM, Rushikesh Thakkar <[EMAIL PROTECTED]> wrote:
> Yes, It is possible. Please change the following line in your Stub generated
> by WSDL2Java
>
> File: XxxxBindingStub.java
>
>
>
> In createCall() method:
>
>
>
> protected org.apache.axis.client.Call createCall() throws
> java.rmi.RemoteException {
>
> …
>
> …
>
> while (keys.hasMoreElements()) {
>
> java.lang.String key = (java.lang.String) keys.nextElement();
>
> _call.setProperty(key, super.cachedProperties.get(key));
>
> }
>
> // change it to the encoding you want..
>
> _call.setProperty(org.apache.axis.client.Call.CHARACTER_SET_ENCODING,
> "ISO-8859-1");
>
>
>
> synchronized (this) {
>
> …
>
> }
> }
>
> See if this works!!
>
> cheers,
> Rushikesh
>
>
> On 2/8/08, Jan Philipp Seng <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > Hi,
> >
> >
> >
> > I am using Axis2 1.3 with ADB. There is a demand to deliver the SOAP
> responses in latin1 (ISO-8859-1) instead of UTF-8. Can I change the encoding
> of SOAP responses?
> >
> >
> >
> > Thanks
> >
> > Jan
> >
> >
> >
> > Gruß,
> >
> > Jan
> >
> > __
> >
> >
> >
> > Jan Philipp Seng
> >
> > IT-Entwicklung
> >
> >
> >
> > TravelTainment AG
> >
> > Carlo-Schmid-Straße 12
> >
> > 52146 Würselen/Aachen
> >
> > Germany
> >
> > Tel: +49 (0)2405 - 4484-50
> >
> > Fax: +49 (0)2405 - 4484-90
> >
> > email: [EMAIL PROTECTED]
> >
> >
> >
> > Amtsgericht Aachen, HRB 8173
> >
> > Vorstand: Ralf Usbeck (Vors.), Michael Kalt; Aufsichtsratvorsitzender:
> Philippe Chérèque
> >
> >
> >
> > http://www.traveltainment.de
> >
> > http://www.vidado.com
> >
> >
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding of SOAP responses
Yes, It is possible. Please change the following line in your Stub generated
by WSDL2Java
File: XxxxBindingStub.java
In createCall() method:
protected org.apache.axis.client.Call *createCall*() throws
java.rmi.RemoteException {
…
…
*while* (keys.hasMoreElements()) {
java.lang.String key = (java.lang.String) keys.nextElement();
_call.setProperty(key, *super*.cachedProperties.get(key));
}
// change it to the encoding you want..
_call.setProperty(org.apache.axis.client.Call.*CHARACTER_SET_ENCODING*,
"ISO-8859-1");
synchronized (this) {
…
}
}
See if this works!!
cheers,
Rushikesh
On 2/8/08, Jan Philipp Seng <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
>
>
> I am using Axis2 1.3 with ADB. There is a demand to deliver the SOAP
> responses in latin1 (ISO-8859-1) instead of UTF-8. Can I change the encoding
> of SOAP responses?
>
>
>
> Thanks
>
> Jan
>
>
>
> Gruß,
>
> Jan
>
> __
>
>
>
> Jan Philipp Seng
>
> IT-Entwicklung
>
>
>
> TravelTainment AG
>
> Carlo-Schmid-Straße 12
>
> 52146 Würselen/Aachen
>
> Germany
>
> Tel: +49 (0)2405 - 4484-50
>
> Fax: +49 (0)2405 - 4484-90
>
> email: [EMAIL PROTECTED]
>
>
>
> Amtsgericht Aachen, HRB 8173
>
> Vorstand: Ralf Usbeck (Vors.), Michael Kalt; Aufsichtsratvorsitzender:
> Philippe Chérèque
>
>
>
> http://www.traveltainment.de
>
> http://www.vidado.com
>
>
>
Re: encoding of SOAP responses
Oh yeah,
excuse me..
Thanks Paul.
On Feb 11, 2008 1:25 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Unfortunately you've explained how to do it with Axis1 not Axis2.
>
> In Axis2 do:
>
> stub._getServiceClient().getOptions().setProperty(
> org.apache.axis2.Constants.Configuration.CHARACTER_SET_ENCODING,
> "ISO-8859-1");
>
> No need to edit the generated stub.
>
> Paul
>
> On Feb 11, 2008 10:57 AM, Rushikesh Thakkar <[EMAIL PROTECTED]>
> wrote:
> > Yes, It is possible. Please change the following line in your Stub
> generated
> > by WSDL2Java
> >
> > File: XxxxBindingStub.java
> >
> >
> >
> > In createCall() method:
> >
> >
> >
> > protected org.apache.axis.client.Call createCall() throws
> > java.rmi.RemoteException {
> >
> > …
> >
> > …
> >
> > while (keys.hasMoreElements()) {
> >
> > java.lang.String key = (java.lang.String) keys.nextElement();
> >
> > _call.setProperty(key, super.cachedProperties.get(key));
> >
> > }
> >
> > // change it to the encoding you want..
> >
> > _call.setProperty(org.apache.axis.client.Call.CHARACTER_SET_ENCODING,
> > "ISO-8859-1");
> >
> >
> >
> > synchronized (this) {
> >
> > …
> >
> > }
> > }
> >
> > See if this works!!
> >
> > cheers,
> > Rushikesh
> >
> >
> > On 2/8/08, Jan Philipp Seng <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > >
> > >
> > > I am using Axis2 1.3 with ADB. There is a demand to deliver the SOAP
> > responses in latin1 (ISO-8859-1) instead of UTF-8. Can I change the
> encoding
> > of SOAP responses?
> > >
> > >
> > >
> > > Thanks
> > >
> > > Jan
> > >
> > >
> > >
> > > Gruß,
> > >
> > > Jan
> > >
> > > __
> > >
> > >
> > >
> > > Jan Philipp Seng
> > >
> > > IT-Entwicklung
> > >
> > >
> > >
> > > TravelTainment AG
> > >
> > > Carlo-Schmid-Straße 12
> > >
> > > 52146 Würselen/Aachen
> > >
> > > Germany
> > >
> > > Tel: +49 (0)2405 - 4484-50
> > >
> > > Fax: +49 (0)2405 - 4484-90
> > >
> > > email: [EMAIL PROTECTED]
> > >
> > >
> > >
> > > Amtsgericht Aachen, HRB 8173
> > >
> > > Vorstand: Ralf Usbeck (Vors.), Michael Kalt; Aufsichtsratvorsitzender:
> > Philippe Chérèque
> > >
> > >
> > >
> > > http://www.traveltainment.de
> > >
> > > http://www.vidado.com
> > >
> > >
> >
> >
>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
RE: encoding of SOAP responses
Hello Rushikesh and Paul, thank you very much for your answers. Unfortunately my question was not precise enough. I am not consuming a web service, but offering it. Can I determine the encoding of the SOAP responses my server delivers at runtime depending on a parameter transmitted in the SOAP Header of the request also? Thanks for your help, Jan
Re: encoding of SOAP responses
Do you mean you need to use the same encoding as the client sent? Paul On Feb 13, 2008 5:35 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: > > > > > Hello Rushikesh and Paul, > > > > thank you very much for your answers. Unfortunately my question was not > precise enough. I am not consuming a web service, but offering it. Can I > determine the encoding of the SOAP responses my server delivers at runtime > depending on a parameter transmitted in the SOAP Header of the request also? > > > > Thanks for your help, > > Jan -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: encoding of SOAP responses
Hello Paul, My idea was to search the SOAP header for a parameter like "charSet" defined by the client to determine the encoding of the SOAP response which should be independent from the encoding of the SOAP request. Or is this idea completely rubish? Is Axis2 1.3 always responding with the same encoding the client uses for the request? The requirement is just to choose the encoding of the SOAP response at runtime by the client. Some clients need utf-8, others need latin1. I don´t know the best way to implement this. I cannot find notes on this topic in the documentation. When I take a look at the SOAP-Monitor, I see always utf-8 as encoding in the XML header. Jan -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 13, 2008 6:42 PM To: axis-user@ws.apache.org Subject: Re: encoding of SOAP responses Do you mean you need to use the same encoding as the client sent? Paul On Feb 13, 2008 5:35 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: > > > > > Hello Rushikesh and Paul, > > > > thank you very much for your answers. Unfortunately my question was not > precise enough. I am not consuming a web service, but offering it. Can I > determine the encoding of the SOAP responses my server delivers at runtime > depending on a parameter transmitted in the SOAP Header of the request also? > > > > Thanks for your help, > > Jan -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding of SOAP responses
On 14 Feb 2008, at 11:01, Jan Philipp Seng wrote: Some clients need utf-8, others need latin1 Why would a client need latin1? Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding of SOAP responses
If you read the XML spec http://www.w3.org/TR/2006/REC-xml-20060816/ You will see that [] \ ^ and a number of other characters are not supported within XML tag names. I suggest you change your format to be: Paul On Wed, May 7, 2008 at 1:46 PM, Stadelmann Josef <[EMAIL PROTECTED]> wrote: > Hello Paul, > hello AXIS2 (J/C) experts > hello XML, XSL, XSLT, LIBXML2, encoding experts! > > I have to pass the following result back top my client also receive it at > the server later? > > Regarding encoding (better allowed and non-allowed characters) I have to > transive > the following XML between client and server out from a larger legacy > integration. > > : > > > > XXX > FKT_PUTCODES > AVT > 3X > ZDK / BMWP > AVT > > > > > this should now be converted to a OMElement and without "[" and "]" it works. > however - today - I was told that "[" and "]" are used very frequently > indexing fields. > > I was further told - today - that we have "<" amd ">" and that we carry "&" > as well as a few others. > According W3C Specs I can find how to substitute "&", "<" ">" and a few more > but not "[" and "]" > > The interesting thing is that I get field-name field-value pairs in to > AXIS2/C hash tables, then > create an OMModel from it, then serialize this model to what you see above, > and pass this > XML string from C Legacy code through JNI back to my Java Axis2 Web-Service. > > And only then, when this string is again converted into an OMElement, > AXIS2/C raises > an exception. > > I agree that certain characters can be parsed while others must be > substituted before > parsing by an XML reader/parser occures, I ask the following: > > 1. What is the prefered way to substitute this "forbiddent" characters using > hopefully AXIS2/C > and or AXIS2/J AXIOM AXUTIL SW components? > > 2. Is XSLT technic the rigth thing to do it; I am still a novice in this > regards. > > 3. Would it be possible that "[" and "]" would not lead to an exception if I > would tell AXIS2/J > webservice server to use for this deserialization a different encoding > schema? > > 4. How would you best transive over AXIS2 a PS formatted document? > > 5. How would you best transive over AXIS2 a LaTex document? > > 6. Binary as MTOM OK? > > > Very thanksfull for a ASAP answer. > Josef.Stadelmann > @axa-winterthur.ch > > > > -Ursprüngliche Nachricht- > Von: Paul Fremantle [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 13. Februar 2008 18:42 > An: axis-user@ws.apache.org > Betreff: Re: encoding of SOAP responses > > > > > Do you mean you need to use the same encoding as the client sent? > > Paul > > On Feb 13, 2008 5:35 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hello Rushikesh and Paul, > > > > > > > > thank you very much for your answers. Unfortunately my question was not > > precise enough. I am not consuming a web service, but offering it. Can I > > determine the encoding of the SOAP responses my server delivers at runtime > > depending on a parameter transmitted in the SOAP Header of the request > also? > > > > > > > > Thanks for your help, > > > > Jan > > > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding of SOAP responses
No. The "XML" fragment you have sent is invalid XML, and so no XSLT processor will be able to read it. Paul On Wed, May 7, 2008 at 2:08 PM, Stadelmann Josef <[EMAIL PROTECTED]> wrote: > Thanks Paul, > > can I do that with an XSL / XSLT approach? > > Josef > > > -Ursprüngliche Nachricht- > Von: Paul Fremantle [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 7. Mai 2008 14:59 > > > An: axis-user@ws.apache.org > Betreff: Re: encoding of SOAP responses > > > If you read the XML spec http://www.w3.org/TR/2006/REC-xml-20060816/ > > You will see that [] \ ^ and a number of other characters are not > supported within XML tag names. > > I suggest you change your format to be: > > > Paul > > > On Wed, May 7, 2008 at 1:46 PM, Stadelmann Josef > <[EMAIL PROTECTED]> wrote: > > Hello Paul, > > hello AXIS2 (J/C) experts > > hello XML, XSL, XSLT, LIBXML2, encoding experts! > > > > I have to pass the following result back top my client also receive it at > the server later? > > > > Regarding encoding (better allowed and non-allowed characters) I have to > transive > > the following XML between client and server out from a larger legacy > integration. > > > > : > > > > > > > > XXX > > FKT_PUTCODES > > AVT > > 3X > > ZDK / BMWP > > AVT > > > > > > > > > > this should now be converted to a OMElement and without "[" and "]" it > works. > > however - today - I was told that "[" and "]" are used very frequently > indexing fields. > > > > I was further told - today - that we have "<" amd ">" and that we carry > "&" as well as a few others. > > According W3C Specs I can find how to substitute "&", "<" ">" and a few > more but not "[" and "]" > > > > The interesting thing is that I get field-name field-value pairs in to > AXIS2/C hash tables, then > > create an OMModel from it, then serialize this model to what you see > above, and pass this > > XML string from C Legacy code through JNI back to my Java Axis2 > Web-Service. > > > > And only then, when this string is again converted into an OMElement, > AXIS2/C raises > > an exception. > > > > I agree that certain characters can be parsed while others must be > substituted before > > parsing by an XML reader/parser occures, I ask the following: > > > > 1. What is the prefered way to substitute this "forbiddent" characters > using hopefully AXIS2/C > > and or AXIS2/J AXIOM AXUTIL SW components? > > > > 2. Is XSLT technic the rigth thing to do it; I am still a novice in this > regards. > > > > 3. Would it be possible that "[" and "]" would not lead to an exception > if I would tell AXIS2/J > > webservice server to use for this deserialization a different encoding > schema? > > > > 4. How would you best transive over AXIS2 a PS formatted document? > > > > 5. How would you best transive over AXIS2 a LaTex document? > > > > 6. Binary as MTOM OK? > > > > > > Very thanksfull for a ASAP answer. > > Josef.Stadelmann > > @axa-winterthur.ch > > > > > > > > -Ursprüngliche Nachricht- > > Von: Paul Fremantle [mailto:[EMAIL PROTECTED] > > Gesendet: Mittwoch, 13. Februar 2008 18:42 > > An: axis-user@ws.apache.org > > Betreff: Re: encoding of SOAP responses > > > > > > > > > > Do you mean you need to use the same encoding as the client sent? > > > > Paul > > > > On Feb 13, 2008 5:35 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > Hello Rushikesh and Paul, > > > > > > > > > > > > thank you very much for your answers. Unfortunately my question was not > > > precise enough. I am not consuming a web service, but offering it. Can I > > > determine the encoding of the SOAP responses my server delivers at > runtime > > > depending on a parameter transmitted in the SOAP Header of the request > also? > > > > > > > > > > > > Thanks for your help, > > > > > > Jan > > > > > > > > -- > > Paul Fremantle > &
