=?iso-8859-1?Q?html_tools_&_fort=E8_webenterprise?=

Hi,
we are dealing with fortè webenterprise development and we are looking for
an HTML tool for writing html templates.
We started an evaluation for some of them ( such us homesite, pagemill,
dreamweaver, .. ) but we still have some problems in managing and mixing
fortè tags ( <?forte execut , ....) and html tags.
I know that there is a fortè technote about this, but is quite old.
Have you got any experiences in using third party html authoring tool for
fortè web development ?
Any suggestion would be appreciated.
Thanks
Fabrizio
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Similar Messages

Re: =?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=

Massimilano,
We have just experienced this with
Forte 3.0.L.2
WebEnterprise 1.0.D.1
on DEC alpha OSF environment.
There is a forte defect report #48399
relating an unfixed problem in this version of Web Enterprise
"HTTPRequest missing CGI variables, including REMOTE_ADDR and REMOTE_HOST"
which looks like the problem.
Have you had any suggestions to get around this?
John
To: <[email protected]>
Subject: =?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=
From: "Massimilano Delsante" <[email protected]>
Date: Fri, 10 Sep 1999 14:59:27 +0200
Reply-To: "Massimilano Delsante" <[email protected]>
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
=20
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
John Soper, Information Systems Development, ITS, The University of Melbourne
email: [email protected] >>>> Tel: 9344 5612

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

=?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=

Messaggio a più sezioni in formato MIME.
------=_NextPart_000_00A9_01BEFB9D.13EFC330
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
*------------------------------------------------------------------------=
Massimiliano Delsante
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
-----Messaggio originale-----
Da: Massimilano Delsante <[email protected]>
A: forte users <[email protected]>
Data: venerd=EC 10 settembre 1999 14.56
Oggetto: Fort=E9 CGI problem
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
=20
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
------=_NextPart_000_00A9_01BEFB9D.13EFC330
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<DEFANGED-META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN">
<DEFANGED-META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY><DEFANGED-BODY bgColor=3D#ffffff>
<DIV> </DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV>
<DIV>-----Messaggio =
originale----- Da:=20
Massimilano Delsante <<A=20
href=3D"<a href=
"mailto:[email protected]">mailto:[email protected]</a>">[email protected]</A>&g=
t; A:=20
forte users <<A=20
href=3D"<a href=
"mailto:[email protected]">mailto:[email protected]</a>">[email protected]</A>> =
Data:=20
venerdì 10 settembre 1999 14.56 Oggetto: =
Forté CGI=20
problem </DIV>
<DIV>
<DIV>
We have encountered the following problem:

Using the basic authentication on a web server, there =
is an=20
problem passing the information between web server and Forté.
In the attribute REMOTE_USER in the object =
Request.cgienv=20
should be present the value of the user authentication, so in =
Forté we=20
should access to it.
Instead, many of the values in the Request.cgienv not =
exists=20
and we show the list: 

**************** Attributes CGI in Request.cgienv=20
**************** 
Value of AUTH_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of CONTENT_LENGTH 0 <FONT=20
face=3DArial size=3D2>
Value of CONTENT_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of GATEWAY_INTERFACE (nil)<FONT=20
size=3D2> 
Value of HTTP_ACCEPT (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_COOKIE (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_USER_AGENT (nil) <FONT=20
face=3DArial size=3D2>
Value of PATH_INFO /frte_cs0 <FONT=20
face=3DArial size=3D2>
Value of PATH_TRANSLATED (nil) <FONT=20
face=3DArial size=3D2>
Value of QUERY_STRING=20
 ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm</F=
ONT><FONT=20
size=3D2> 
Value of REMOTE_ADDR (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_HOST (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_IDENT (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_USER (nil) <FONT=20
face=3DArial size=3D2>
Value of REQUEST_METHOD GET <FONT=20
face=3DArial size=3D2>
Value of SCRIPT_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_PORT 0 <FONT=20
face=3DArial size=3D2>
Value of SERVER_PROTOCOL (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_SOFTWARE (nil) <FONT=20
face=3DArial size=3D2>
In the environment are installed the followings versions of =
products:
Forté 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Forté 3.G.2 and WebEnterprise 1.B, =
the=20
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of =
the=20
basic authentication in a Forté variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.</DIV></DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV></BODY><=
/HTML>
------=_NextPart_000_00A9_01BEFB9D.13EFC330--

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Como deixar a codificação padrão "iso-8859-1" ao invés de "utf-8" no navegador?

Quando faço o acesso ao banco do meu cartão de crédito, a primeira pagina deles é codificada com "UTF-8" e também existe o comando "charset=utf-8" no código HTML, após digitar o número do cartão, ele direciona para outra página, porém codificada com "iso-8859-1", mas sem nenhuma codificação no código HTML.
Identifiquei que o navegador usa por padrão o "utf-8" quando não existe codificação no código HTML, então gostaria de modificar esse padrão para "iso-8859-1".
O único lugar que encontrei para essa codificação foi ao pressionar o botão de avançado em "Fontes e cores", porém não funcionou.
A versão do meu navegado é 23.0.1, entretanto desde a versão 18 que encontro esse problema.

It is possible that the server sends the file(s) by default with UTF-8 and in such a case this encoding send by the server prevails over all other settings.
You can see the encoding here: Tools > Page Info > General
*Press the F10 key or tap the Alt key to bring up the hidden "Menu Bar" temporarily.

Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default]

When trying to load data into Essbase I get this error dialogue
Object [65313270] is locked by user [admin@Native Directory]
Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default] and [English_UnitedStates.Latin1@Binary] are not compatible
Object [65313270] unlocked by user [admin@Native Directory]
Unexpected Essbase error 1019057
Have checked essbase.properties files (all 10 of them!) and the 2 references that I could find both point to the default value of [English_UnitedStates.Latin1@Binary]
So is the problem with the CSV file?

Have you looked at the Load Rule (yes, I know, developed in Studio, but it generates Load Rules which I believe you can open in EAS)? Is the dimension that contains BON accounted for?
Your second issue(s) seems to be that you have conflicting locales -- are you in SA? Could it be that Studio is installed with English as the language and EAS with Arabic (or vice versa)? Sorry, I have hardly any experience in languages other than English. Maybe one of the non-English language posters can chime in.
I can't say whether that load buffer issue means anything at all or not -- it could be a red herring.
Regards,
Cameron Lackpour

UTF-8 encoding vs ISO 8859-1 encoding

The iTunes tech specs call for UTF-8 encoding of the XML feed file; a friend of mine uses feed generator software through his blog that uses ISO 8859 encoding. Is there a way to convert the latter to UTF-8 so that iTunes tags may be successfully added?
When I tried editing his XML file, I got error messages when I submitted the file to RSS feed validator sites (such as http://feedvalidator.org/. Any help or knowledge is appreciated because I am not the least bit expert in this coding arena.

You don't need to convert iso 8859-1 (us-ascii) to utf-8 unless you have nonstandard characters. Basically, ascii is a subset of utf-8 and for English it will serve you just fine. You can have iTunes tags in the xml file even if the file itself is encoded in iso 8859-1.
The error you see at feedvalidator.org is most likely a warning.
Hope this helps!
- Andy Kim
Potion Factory
http://www.potionfactory.com

Mail Receiver - Send file in ISO-8859-1 encoding

Hi,
I'm sending mail with an attachment using mail adapter, but instead of specified ISO-8859-1 it is converted to UTF-8 no BOM,. Because of that, some characters (ñ,ç, etc) are not transferred properly.
Settings:
Message protocol: XIPAYLOAD
No mail package.
Transform.ContentType: multipart/mixed; boundary=--AaZz; charset=ISO-8859-1
Payload:
multipart/mixed; boundary=AaZz; charset=ISO-8859-1</Content_Type><Content>--AaZz
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
File attachment
AaZz
Content-Type: text/plain; charset= ISO-8859-1
Content-Disposition: attachment; filename=TestFile
iso-8859 characters ñ ç ñ ñ
AaZz--
</Content></ns:Mail>
I need advice in how to force the file to be created with ISO-8859-1 enconding.
Thanks in advance.
Regards,
Iván.

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

Codepage coverting error utf-8 from System codepage to iso-8859-1 (PI 7.1)

Hello Experts,
In our Prcess, we receive an Idoc from an IS-U system and then we send this Idoc with some Header-Information via http-Adapter to a Seeburger System.
In the outbound communication Channel we have a XI Payload manipulation with xml-Code iso-8859-1.
We get the Error: Codepage coverting error utf-8 from System codepage to iso-8859-1, and only for this Idoc, where othe similar Idocs runs correctly.
Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
PS: another XI in our landscape uses a http-Channel with the same configuration in a similar process, an it work, so guess the Problem is not in the communication channel.
thanks,
best regards

> Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
A would rather think, that there could be any non-iso-8859-1 character be in the IDoc. For example an czech or polish character.

HTTP adapter - change encoding from UTF-8 to ISO-8859-1

Hi,
I am trying to change the encoding used by the HTTP sender adapter in a scenario.
However, when I enter ISO-8859-1 in the XML Code under XI Payload Manipulation on the comms channel it has no effect - the paylad still shows as UTF-8 in SXI_MONITOR.
Am I missing a step or entering the field incorrectly ??
Thanks
Colin.

Hi,
From help
Enhancing the Payload
Some external systems, for example, Web servers in marketplaces, can only process data if it is sent as an HTML form using HTTP.
A typical HTML form comprises named fields. When transferring a completed form to the server or a CGI program, the data must be transferred in such a way that the CGI script can recognize the fields that make up the form, and which data was entered in which field.
The plain HTTP adapter constructs this format using a prolog and an epilog. Therefore, there is a particular code method that separates form fields and their data from each other. This code method uses the following rules:
     Individual form elements, including their data, are separated from each other by the character &.
     The name and data of a form element are separated from each other by an equals sign (=).
     Blanks in the entered data (for example, in multiple words) are replaced by a plus sign (+).
    All characters with the (enhanced) ASCII values 128 to 255 (hexadecimal 80 to FF) are transcribed using a hexadecimal sequence, beginning with a percentage sign (%) followed by the hexadecimal value of the character (for example, the German umlaut ö in the character set ISO-8859-1 is transcribed as %F6).
   All characters that occur in these rules as control characters (&, +, =, and %) are also transcribed hexadecimally in the same way as high value ASCII characters
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Regards
Chilla

File adapter ISO-8859-1 encoding problems in XI 3.0

We are using the XI 3.0 file adapter and are experiencing some XML encoding troubles.
A SAP R/3 system is delivering an IDoc outbound. XI picks up the IDoc and converts it to an external defined .xml file. The .xml file is send to a connected ftp-server. At the remote FTP server the file is generating an error, as it is expected to arrive in ISO-8859-1 encoding. The Transfer Mode is set to Binary, File Type Text, and Encoding ISO-8859-1.
The .xml file is encoded correctly in ISO-8859-1, but the problem is that the XML encoding declaration has the wrong value 'UTF-8'.
Does anybody know of a work around, to change the encoding declaration to ISO-8859-1 in the message mapping program?

An example of the XSL code might be as follow:
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method='xml' encoding='ISO-8859-1' />
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>

Converting from CP1252 (Windows) to ISO 8859-1 doesn't work with java.nio?

Hi
I'm trying to write some code that checks whether an InputStream contains only characters with a given encoding. I'm using java.nio for that. For tests, I downloaded some character set examples from http://www.columbia.edu/kermit/csettables.html
When creating the CharsetDecoder, I want to get all errors:
    Charset charset = Charset.forName( encoding );
    CharsetDecoder decoder = charset.newDecoder();
    decoder.onMalformedInput( CodingErrorAction.REPORT );
    decoder.onUnmappableCharacter( CodingErrorAction.REPORT );I then read an InputStream and try to convert it. If that fails, it can't contain the desired encoding:
    boolean isWellEncoded = true;
    ByteBuffer inBuffer = ByteBuffer.allocate( 1024 );
    ReadableByteChannel channel = Channels.newChannel( inputStream );
    while ( channel.read( inBuffer ) != -1 )
      CharBuffer decoded = null;
      try
        inBuffer.flip();
        decoded = decoder.decode( inBuffer );
      catch ( MalformedInputException ex )
        isWellEncoded = false;
      catch ( UnmappableCharacterException ex )
        isWellEncoded = false;
      catch ( CharacterCodingException ex )
        isWellEncoded = false;
      if ( decoded != null )
        LOG.debug( decoded.toString() );
      if ( !isWellEncoded )
        break;
      inBuffer.compact();
    channel.close();
    return isWellEncoded;Now I want to check whether a file containing Windows 1252 characters is ISO-8859-1. From my point of view, the code above should fail when it gets to the Euro symbol (decimal 128), since that's not defined in ISO-8859-1.
But all I get is a ? character instead:
(}) 125 07/13 175 7D                 RIGHT CURLY BRACKET, RIGHT BRACE
(~) 126 07/14 176 7E                 TILDE
[?] 128 08/00 200 80 EURO SYMBOL
[?] 130 08/02 202 82 LOW 9 SINGLE QUOTEI also tried to replace the faulty character, using
    decoder.onUnmappableCharacter( CodingErrorAction.REPLACE );
    decoder.replaceWith("!");but I still get the question marks.
I'm probably doing something fundamentally wrong, but I dont get it :-)
Any help is greatly appreciated!
Eric

As a suggestion....create a complete example demonstrating the problem. It shouldn't have channel in it since that wouldn't appear to be the problem (decoding is.) You should create the byte array in the example code - populate it with the byte sequence that you think should work. And your code should then demonstrate that it doesn't. Then post that.

Xslt ecc6 ISO-8859-1 problem when download xml file

Hello,
i create an ABAP test program:
*& Report Z_ABAP_TO_XML *
*& Write the data from an internal ABAP table into an XML document, *
*& and write it onto your frontend computer *
REPORT z_abap_to_xml.
TYPE-POOLS: abap.
CONSTANTS gs_file TYPE string VALUE 'C:\Users\Marco Consultant\Desktop\test.xml'.
* This is the structure for the data to go into the XML file
TYPES: BEGIN OF ts_person,
cust_id(4) TYPE n,
firstname(20) TYPE c,
lastname(20) TYPE c,
END OF ts_person.
* Table for the XML content
DATA: gt_itab TYPE STANDARD TABLE OF char2048.
* Table and work area for the data to fill the XML file with
DATA: gt_person TYPE STANDARD TABLE OF ts_person,
 gs_person TYPE ts_person.
* Source table that contains references
* of the internal tables that go into the XML file
DATA: gt_source_itab TYPE abap_trans_srcbind_tab,
 gs_source_wa TYPE abap_trans_resbind.
* For error handling
DATA: gs_rif_ex TYPE REF TO cx_root,
 gs_var_text TYPE string.
* Fill the internal table
gs_person-cust_id = '3'.
gs_person-firstname = 'Bill'.
gs_person-lastname = 'Gates'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '4'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
* Fill the source table with a reference to the data table.
* Within the XSLT stylesheet, the data table can be accessed with
* "IPERSON".
GET REFERENCE OF gt_person INTO gs_source_wa-value.
gs_source_wa-name = 'IPERSON'.
APPEND gs_source_wa TO gt_source_itab.
* Perform the XSLT stylesheet
TRY.
 CALL TRANSFORMATION z_abap_to_xml
 SOURCE (gt_source_itab)
 RESULT XML gt_itab.
CATCH cx_root INTO gs_rif_ex.
 gs_var_text = gs_rif_ex->get_text( ).
 gs_var_text = gs_rif_ex->get_text( ).
 MESSAGE gs_var_text TYPE 'E'.
ENDTRY.
* Download the XML file to your client
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
 filename = gs_file
CHANGING
 data_tab = gt_itab
EXCEPTIONS
 file_write_error = 1
 no_batch = 2
 gui_refuse_filetransfer = 3
 invalid_type = 4
 no_authority = 5
 unknown_error = 6
 header_not_allowed = 7
 separator_not_allowed = 8
 filesize_not_allowed = 9
 header_too_long = 10
 dp_error_create = 11
 dp_error_send = 12
 dp_error_write = 13
 unknown_dp_error = 14
 access_denied = 15
 dp_out_of_memory = 16
 disk_full = 17
 dp_timeout = 18
 file_not_found = 19
 dataprovider_exception = 20
 control_flush_error = 21
 not_supported_by_gui = 22
 error_no_gui = 23
 OTHERS = 24.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
and i created XSLT test conversion:
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output encoding="iso-8859-1" indent="yes" method="xml" version="1.0"/>
<xsl:strip-space elements="*"/>
<xsl:template match="/">
 <CUSTOMERS>
 <xsl:apply-templates select="//IPERSON/item"/>
 </CUSTOMERS>
</xsl:template>
<xsl:template match="IPERSON/item">
 <item>
 <customer_id>
 <xsl:value-of select="CUST_ID"/>
 </customer_id>
 <first_name>
 <xsl:value-of select="FIRSTNAME"/>
 </first_name>
 <last_name>
 <xsl:value-of select="LASTNAME"/>
 </last_name>
 </item>
</xsl:template>
</xsl:transform>
Seem all correct infact the program download a file XML but the file have the encoding="UTF-16" also if i have specified "iso-8859-1" and if i tried to opend the xml file the file appears not correct because is generated with as first character "#", why?
Below the xml generated..
What i have to do to generate a correct XML without errors?
#<?xml version="1.0" encoding="utf-16"?>
<CUSTOMERS>
<item>
 <customer_id>0003</customer_id>
 <first_name>Bill</first_name>
 <last_name>Gates</last_name>
</item>
<item>
 <customer_id>0004</customer_id>
 <first_name>Frodo</first_name>
 <last_name>Baggins</last_name>
</item>
</CUSTOMERS>

hello all!
i resolve the problem using:
* Perform the XSLT stylesheet
g_ixml = cl_ixml=>create( ).
g_stream_factory = g_ixml->CREATE_STREAM_FACTORY( ).
g_encoding = g_ixml->create_encoding( character_set = 'utf-16' "unicode
 byte_order = 0 ).
resstream = g_stream_factory->CREATE_OSTREAM_ITABLE( table = gt_xml_itab ).
call method resstream->set_encoding
 exporting encoding = g_encoding.
I think it's the right way, i put all my ABAP program updated:
*& Report Z_ABAP_TO_XML *
*& Write the data from an internal ABAP table into an XML document, *
*& and write it onto your frontend computer *
REPORT z_abap_to_xml.
TYPE-POOLS: abap.
CONSTANTS gs_file TYPE string VALUE 'C:UsersMarco ConsultantDesktop est.xml'.
data: g_ixml type ref to if_ixml.
data: g_stream_factory type ref to IF_IXML_STREAM_FACTORY.
data: resstream type ref to if_ixml_ostream.
data: g_encoding type ref to if_ixml_encoding.
* This is the structure for the data to go into the XML file
TYPES: BEGIN OF ts_person,
cust_id(4) TYPE n,
firstname(20) TYPE c,
lastname(20) TYPE c,
END OF ts_person.
* Table for the XML content
DATA: gt_xml_itab TYPE STANDARD TABLE OF char2048.
* Table and work area for the data to fill the XML file with
DATA: gt_person TYPE STANDARD TABLE OF ts_person,
 gs_person TYPE ts_person.
* Source table that contains references
* of the internal tables that go into the XML file
DATA: gt_source_itab TYPE abap_trans_srcbind_tab,
 gs_source_wa TYPE abap_trans_resbind.
* For error handling
DATA: gs_rif_ex TYPE REF TO cx_root,
 gs_var_text TYPE string.
* Fill the internal table
gs_person-cust_id = '3'.
gs_person-firstname = 'Bill'.
gs_person-lastname = 'Gates'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '4'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '5'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '6'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '7'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '8'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '9'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '10'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '88'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
* Fill the source table with a reference to the data table.
* Within the XSLT stylesheet, the data table can be accessed with
* "IPERSON".
GET REFERENCE OF gt_person INTO gs_source_wa-value.
gs_source_wa-name = 'IPERSON'.
APPEND gs_source_wa TO gt_source_itab.
* Perform the XSLT stylesheet
g_ixml = cl_ixml=>create( ).
g_stream_factory = g_ixml->CREATE_STREAM_FACTORY( ).
g_encoding = g_ixml->create_encoding( character_set = 'utf-16' "unicode
 byte_order = 0 ).
resstream = g_stream_factory->CREATE_OSTREAM_ITABLE( table = gt_xml_itab ).
call method resstream->set_encoding
 exporting encoding = g_encoding.
TRY.
 CALL TRANSFORMATION z_abap_to_xml
 SOURCE (gt_source_itab)
 RESULT XML gt_xml_itab.
CATCH cx_root INTO gs_rif_ex.
 gs_var_text = gs_rif_ex->get_text( ).
 gs_var_text = gs_rif_ex->get_text( ).
 MESSAGE gs_var_text TYPE 'E'.
ENDTRY.
* Download the XML file to your client
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
 filename = gs_file
 FILETYPE = 'BIN'
CHANGING
 data_tab = gt_xml_itab
EXCEPTIONS
 file_write_error = 1
 no_batch = 2
 gui_refuse_filetransfer = 3
 invalid_type = 4
 no_authority = 5
 unknown_error = 6
 header_not_allowed = 7
 separator_not_allowed = 8
 filesize_not_allowed = 9
 header_too_long = 10
 dp_error_create = 11
 dp_error_send = 12
 dp_error_write = 13
 unknown_dp_error = 14
 access_denied = 15
 dp_out_of_memory = 16
 disk_full = 17
 dp_timeout = 18
 file_not_found = 19
 dataprovider_exception = 20
 control_flush_error = 21
 not_supported_by_gui = 22
 error_no_gui = 23
 OTHERS = 24.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
*-- we don't need the stream any more, so let's close it...
CALL METHOD resstream->CLOSE( ).
CLEAR resstream.

Translation UTF8 - ISO-8859-1

Hi there,
When translating a UTF8 file to ISO-8859-1 during loading of that file (using dbms_lob.loadclobfromfile)
I notice that an UTF8 right single quotation mark ' (2019) is converted to an inverted quotation mark ¿.
The left single quotation mark is (correctly) translated to 0060 Grave accent `
My question is; how can I get the (2019) right single quatation mark to be converted to 00B4 Acute Accent ?
Thanks in advance,
Art

It looks like during the insertion from ASP the Latin 1 string has not been converted to UTF8. Hence you are storing Latin-1 encoding inside a UTF-8 database.
I thought it would automatically be handled by OO4O.True. Did you specify the character set of the NLS_LANG env variable for the OO4O client to WE8ISO8859P1 ? If it was set to UTF8 then Oracle will assume that the encoding coming thru' the ASP page are in UTF-8 , hence no conversion takes place ..
Also may be you should check the CODEPAGE directive and Charset property in your ASP ?
null

Not a valid SOAP Content-Type: text/html; charset=iso-8859-1

Friends
JDEV and SOA suite 10134
I have multiple domains on my BPEL Server. In one of the domain since I deployed the new process, all the processes of that domain are now failing on execution with following error in opmn/soa_instance/*.err log files. No errors in domain.log
+"Caused by: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; cha+
+rset=iso-8859-1"+
At the same time we get Internal Server Error on BPEL Console.
I have sync processes with 1 or two invokes, so I am generally losing the instances, cannot provide the details in the process execution. All BPEL processes are invoking Siebel Web Services, that is the common part.
When I restart my system, it may or may not work; even if it works then within few instances execution again starts giving the same error. I can see that after the errors the instance are going through and getting completed successfully few times. All these processes were working successfully earlier.
Any idea about this !!!!
Thanks

Thanks Anirudh,
I don't use compensation handlers. Moreover I have properly defined the scopes and sequences throughout the bpel process. My processes are sync in nature and I'm not able say at what step exactly the processes are failing and throwing the SOAP content Type error though the instances are getting completed with delay soemtimes.

Unsupported Content-Type: text/html; charset=iso-8859-1

Originally posted on JBI forum -
It was helpfully suggested there that I check on JAX-WS forum whether this was an issue with utf-8/16 encodings...
I have been experimenting with the openESB composite application described here
http://jlorenzen.blogspot.com/2007/08/using-jbi-javaee-serviceengine.html
This works fine as it appears on this webpage.
I have tried to adapt it to act as a proxy to a secure version of Hello EJB that runs on the SSL port of glassfish AS.
To do this I edited the EJB to set up the security properties. Edited the BPEL wsdl file and created a new composite application using the updated BPEL project.
This leads to an Unsupported Content-Type exception when a test case is run on the composite application from SOAP-UI
Does anyone know how I can explicitly set the content type of the proxied request to the secure WS?
Thanks
Joss Armstrong
HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/HelloBPEL}HelloBPELService] endpoint [HelloBPELPort] responded with an error status. Error detail is: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=EJBPartnerLink, portType={http://hellopack/}Hello, operation=sayHello)
BPCOR-6129:Line Number is 29
BPCOR-6130:Activity Name is Invoke1
at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:968)
at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:538)
at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:181)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148)
at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:407)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:239)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
*Caused by: com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]*
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:171)
at com.sun.xml.ws.tx.client.TxClientPipe.process(TxClientPipe.java:177)
at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at com.sun.xml.ws.client.Stub.process(Stub.java:248)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Request doesnt have a Content-Type
com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:372)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)

Jossarm/Jeff,
The Cryptography forum is not the right forum for this question; have you tried posting to the Glassfish forum on java.net?
But, here is what I think the problem might be:
SOAP-based web-service security uses XML Signature and XML Encryption to secure the message - not SSL; as a result it uses text/xml at the start of its message (which is what SOAP messages are). SSL assumes that the secure session has been established and all messages thereafter, are expected to begin with text/html (as expected in HTTP). You cannot mix-and match this - unless the service is an HTTP-based service that expects a SOAP-based message embedded in the HTTPRequest.

=?iso-8859-1?Q?html_tools_&_fort=E8_webenterprise?=

Similar Messages

Maybe you are looking for