(invalid encoding)

Okay so I have this problem with invalid characters. For ex. I have an external hdd that i have used on windows and on debian/ubuntu and some of my folders contains åäö, but i get a "?" . And it is the same with gnome terminal but there i can change the charecter encoding to unicode(UTF-8) and then i works fine, but it keeps jumping back to the old charecter settings.
In rc.conf i use "en_US.UTF8" and have tried "en_US"
(Sorry for any miss spelling)

catwell wrote:
Yes, by the way I'm working on Debian (what a pain...) at the moment and I noticed the names of the locales were not the same. For example, where in Arch it's en_US.utf8, in Debian it's en_US.UTF-8. This caused a few bugs when I tried to use my Arch-based scripts...
/dev/sdxy /mnt/part vfat user,noauto,iocharset=utf8 0 0
I know, but since this is archlinux.org...
And I realy hate distroes that uses 'custom' names for the encoding, including that arch call it UTF-8 in locale.gen (not that that's arch's fault afaik)

Similar Messages

The font 'Didot' contains an invalid encoding. Some characters may not display.

I am receiving this message:
"The font 'Didot' contains an invalid encoding. Some characters may not display."
The message appears only in one form, not others. It appears only once, the first time I click on the form after opening it, then not again until I reopen the form.
The font is not embedded in the form and does not exist on my computer. The font is not employed in any field in the form or in its static elements.
Would appreciate any help in getting rid of this very annoying message.

KKKRRRGGG wrote:
I have a 2 page PDF form that is getting this error message every time I open the document.
"The font "HelveticaNeue" contains an invalid encoding. Some characters may not display."
The document has been in use for a year (never having this error message) and needed some updates. All that was changed was the addition of some extra fields and some options in one java script to reflect extra addresses in a drop down menu.
HelveticaNeue was in a PDF layout (from Illustrator) for the background but this variable was removed when I converted all fonts to curves (outlines) and replaced it in to my form. Under Properties>Fonts HelveticaNeue isn't even listed. All fields are Myriad Pro (triple checked) so I cannot understand how it is still an issue. It does not seem to have any impact on the document apart from the error message. It is hard to remove when it does not appear anywhere in the document except for the error message.
I have worked backwards and deleted all java scripts and it is still an issue. I have re-imported the background with active HelveticaNeue fonts and it is still an issue. Deleted any fields that relate to java scripts and it is still an issue. Tearing the hair out.....
Any help would be hugely appreciated as I would prefer to not have to start again from scratch.
Run FontBook and verify the Font. If defective open your System Install CD open Fonts. Drag this font to Desktop.
If you can Remove the defective font by draging to Trash (if system font you'll have to give username and Password) .
Then drag the copy on Finder in same folder dective was removed from
THen Restart Computer with shift key down. Hold down until a screen comes up where you must sign in. wait until screen fully loads. Now try the PDF. If works shut down Acrobat (or Reader) and the restart computer normally.
If this doesn't work do the repair located at: http://support.apple.com/kb/DL1377

[solved] Various MP3s are marked as [invalid encoding] with Quod Libet

Various MP3s are marked as [invalid encoding] when I attempt to open them in Quod Libet. These same MP3s open fine in VLC. I checked and I have everything related to gstreamer installed: good, bad, ugly, ffmpeg. My thinking is that should do it but it doesn't. The error listed is "Resource not found." But of course Quod Libet does have the correct path to the file. Also, in case this could be related, the files all appear to show raw unicode in the comments tag rather than the comments. LIke so: 000010A3 000010E3 000057E6 000062C2 0004F705 0005B198 00008000 00008000 00005A9C 00005A3F. Rather than... well I'm not sure what that's supposed to be.
I checked the wiki on gstreamer but and glanced at Pulse's but Pulse, ALSA, and OSS don't seem to be relevant.
Last edited by xidar (2012-06-28 21:36:29)

Yep I went back and looked and it's everything, except one song, that has an "é" and also the bôa album. I'll file a bug report about and call it solved.
Also, I cleared all the extra tags and the junk text (which was probably a custom tag at one point) that was in comments and it works. So maybe iTunes screwed up the formatting and Ex Falso took and mangled all of my comments because of it and something to do with unicode.
Last edited by xidar (2012-06-28 22:01:26)

Error: The font 'HelveticaNeue-UltraLight' contains an invalid encoding.

Keep getting this warning everytime I open a form I'm working on. "The font 'HelveticaNeue-UltraLight' contains an invalid encoding. Some characters may not display." Have found several threads about this but none with any good answers it seems. Anybody encounter this one yet?
Thanks!

Might have solved it in a round about way. Exported all pages out seperately and then re-assembled them and the error went away.

Audio invalid encoding

Hi!
I want to run all au files but only the ones which have the proporties below are allowed:
ulaw,8000,8,signed,big endian,mono
How can i change this state?
I suppose, ok, I use this format then...But I can't convert any file to this format.
AudioFormat newFormat = new AudioFormat(
                     AudioFormat.Encoding.PCM_SIGNED, 8000 8,
                     1,2,8000
                    true);
             AudioInputStream newStream = AudioSystem.getAudioInputStream(newFormat, audioInputStream);
           audioFormat = newFormat;
          audioInputStream = newStream;
           AudioSystem.write(audioInputStream,AudioFileFormat.Type.AU, fout);
The error:
java.lang.IllegalArgumentException: Unsupported conversion: ULAW 8000.0 Hz, 8 bit, mono, 2 bytes/frame, from PCM_SIGNED 8000.0 Hz, 8 bit, mono, 1 bytes/frame,
at javax.sound.sampled.AudioSystem.getAudioInputStream(AudioSystem.java:955)
How can i solve this problem?Thanks...
Edited by: abouttechnology on Apr 7, 2008 1:56 PM
Edited by: abouttechnology on Apr 7, 2008 1:57 PM

"How silly of me to be using device nodes!" I thought to myself. I should be using the ALSA hardware names, and it seemed like such a simple solution!
So I tried basically every combination of ALSA:HW:1,0 I could think of, with and without the ALSA, the HW, or both. Nothing seems to work.
Audacity, and many other programs can record audio from HW:1,0 (as long as tvtime is running)
VLC tries to open a file named "HW:1,0" in my home directory, in spite of suggesting it as an audio input in the drop-down menu .
The frontend for MythTV is now repeating this ad nauseam no matter what I change (almost like it isn't actually changing anything):
2014-02-26 13:57:21.026126 E AudioOutput Error: AOOSS: Error opening audio device ():
eno: No such file or directory (2)
While the backend is obsessed with this:
2014-02-26 14:09:34.250884 E NVR(/dev/video0): Unknown audio codec
2014-02-26 14:09:34.250906 E AudioIn: unknown or unsupported audio input device 'hw:1,0'
2014-02-26 14:09:34.250911 E NVR(/dev/video0): Failed to create audio device: hw:1,0
2014-02-26 14:09:34.250914 E NVR(/dev/video0): Failed to init audio input device
2014-02-26 14:09:34.312487 E NVR(/dev/video0): VIDIOC_S_CTRL:V4L2_CID_AUDIO_MUTE:
eno: Invalid argument (22)
2014-02-26 14:09:34.313888 E NVR(/dev/video0): Invalid audio device (hw:1,0), exiting
I am stumped here. Thank you in advance for any wisdom you may contribute to this conundrum ^_^!

C++ XML parser error 201 - invalid encoding

When I make a call:
xmlpar.xmlparse((oratext *)filename, (oratext *)"UTF-8", flags)
it results in error 201 - encoding is not valid. The same happens when I try KOI-8 encoding.
I use XML Parser 2.0.2.0.0 (C++)/Linux,egcs-2.91.66.
Any suggestions?

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by xmlteam ([email protected]):
Hi,
You need to have an Oracle home with the NLS data files in it.
Thanks,
Oracle XML Team<HR></BLOCKQUOTE>
I have the oraclehome with NLS files in it but stil have the problem
null

Error(3): Invalid encoding specified, expecting ISO-8859-1, got windows-125

What to do about this??Don't know why this isn't working even when I change the charset to ISO-8859-1in my code file,,,what's the solution??please help here.....

I was missing the pageEncoding parameter in my included line but even after having included it it's giving me this error msg,
" Error: recursive include directive "
I just feel some conflict might be arising between my code file and web.xml.The web.xml file's code is:-
<?xml version = '1.0' encoding = 'ISO-8859-1'?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee">
<description>Empty web.xml file for Web Application</description>
<session-config>
<session-timeout>35</session-timeout>
</session-config>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<jsp-config>
     <jsp-property-group>
     <url-pattern>*.jsp</url-pattern>
     <include-prelude>/header2.jsp</include-prelude>
     <include-coda>/footer2.jsp</include-coda>
     </jsp-property-group>
</jsp-config>
</web-app>
-----------------------------------------------------------------------------------------------

File sender adapter - Encoding issue

Hi,
On my customer site, we have an interface taking a file and sending an IDoc to the non Unicode ERP system. Unfortunately, when we have cyrillic characters in the file, the processing files with the error:
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x6(:main:, row:17776, col:893)
This is of course the result of using an invalid encoding in the communication channel. Until now, it was left blank, so UTF8 was used. I want to improve this interface in order to never again have this error because it involves some manual work fixing it and it's getting annoying in production to see this once a month.
What I want to do next is finding out the encoding from the guys delivering the file and then placing it in the communication channel. Pretty straightforward, right? On SAP, I think the cyrillic, non ASCII character will be replaced by #, but this is acceptable by the business. Not acceptable is this constant error.
Because I want to be sure of my assessment before I ask for approval on doing this modification with the associated testing, communication and everything, my question to you is: have you experienced this before in PI? Are all my conclusions accurate? How would you solve the problem?
Thanks in advance and best regards,
George

did you try giving the encoding as ISO 8859-5 in the file adapter?
File Type
Specify the document data type.
u25CB Binary
u25CB Text
Under File Encoding, specify a code page.
The default setting is to use the system code page that is specific to the configuration of the installed operating system. The file content is converted to the UTF-8 code page before it is sent.
also ref: http://en.wikipedia.org/wiki/Cyrillic_alphabet#Computer_encoding
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm

Trying to understand character encoding.

I am new to Java, new to our appliction and I am seeing something being done in the code that I do not understand. It works, sort of, so maybe I should not care, but it puzzles me why it is being done and was hoping someone out there could clue me in.
We are using Oracle 8i configured for UTF8 and connecting to it with JDBC.
When we are loading data from a text file we are using something like:
InputStreamReader isr = new InputStreamReader(fis, "UTF8");
Later we write it to the database:
statement.execute(new String(sLine.getBytes("UTF-8"), "8859_1"));
If we retrieve the data (to write to the browser for example) we seem to need to use a routine to convert the data to UTF8:
return new String(strIn.getBytes("ISO8859_1"), "UTF8");
It appears as though we are converting the input data from UTF8 to 8859_1 prior to the write to the database and then we have to convert back to UTF8 to use it in our application. Why do we do that if the database is already set up for UTF8?
As a side question, is the fact that we seem to interchange 8859_1 and ISO8859_1 (and similarly UTF8 and UTF-8) a problem?
Thanks for your help.

It appears as though we are converting the input data
from UTF8 to 8859_1 prior to the write to the database
and then we have to convert back to UTF8 to use it in
our application. Why do we do that if the database is
already set up for UTF8?Shouldn't you ask that from the people who wrote the code?
As a side question, is the fact that we seem to
interchange 8859_1 and ISO8859_1 (and similarly UTF8
and UTF-8) a problem?It would throw an exception if you were attempting to use an invalid encoding, so apparently it accepts both forms.

How to Convert to Document with Encoding to GBK!

I get a String from SOCKET,eg:
<?xml version="1.0" encoding="GBK"?>
<YHPP ACTION="YHPP_SEND">
     <needReply/>
     <msgLevel>1</msgLevel>
     <serviceID>ECMY</serviceID>
     <msgFormat>15</msgFormat>
     <feeType>01</feeType>
     <feeCode>000010</feeCode>
     <validTime>0</validTime>
     <atTime>0</atTime>
     <srcTermID/>
     <destTermID/>
     <msgLen>70</msgLen>
     <msgContent>��</msgContent>
     <msgID/>
     <msg_IDBM/>
     <feeUserType>3</feeUserType>
     <feeTerminalId/>
     <tpPid>0</tpPid>
     <tpUdhi>0</tpUdhi>
     <ipAddr>192.168.0.59</ipAddr>
</YHPP>
and I hava use org.w3c.dom.Document doc = javax.xml.parsers.DocumentBuilderFactory.newInstance().newDocumentBuilder().parse(new ByteArrayInputStream(str.getBytes()));
this method to Convert to Document,but System print error
org.xml.sax.SAXParseException: Invalid encoding name "GBK".
? How to ??????????Help

Tell the people sending you that string to encode it in some other encoding. Or write your own little program to read it in and write it out in some other encoding before feeding it to the parser.

Best Audio Encoder for Java???

In my program, I can only play .au files in Java.. I have a few .wavs that I would like to incorporate into my program, but I need to change them into .au . Ive tried using COOL EDIT PRO 2 and SOUND FORGE 6.0 to open up the .wavs, then save them as .au .. I run my Java program, but an error comes up saying INVALID ENCODING and INVALID FILE TYPE.. Does anyone have a solution for this frustrating problem I have? It's very urgent and I need your help, thanks...

It took me 4 clicks and 12 keystrokes to find this.
http://java.sun.com/docs/books/tutorial/sound/problems.html
I clicked Tutorials
I clicked The Java Tutorial
I clicked in the Tutorial Search textField
I typed sound files <enter>
The first one looked good to me, click!
Live and learn,
Radish21

OSCP CRL request not working!!!

Hello, I have a Cisco router that I am trying to get a certificate based VPN working on, I have most of the parts working correctly, however I would like to have OCSP crl lookup working. however everytime I go to do a CRL lookup I get this error:
*Mar 26 17:54:22.209: CRYPTO_PKI: Removing cached pubkeys for CRL issuer
*Mar 26 17:54:22.209: CRYPTO_PKI: create new ca_req_context type PKI_POLL_CRL_CONTEXT,ident 42
*Mar 26 17:54:22.209: CRYPTO_PKI: (0)Retreive CRL using HTTP URI
*Mar 26 17:54:22.209: CRYPTO_PKI: Bypassing SCEP capabilities request 0
*Mar 26 17:54:22.209: CRYPTO_PKI: (0) Requesting CRL at http://192.168.4.104:8080:
*Mar 26 17:54:22.209: CRYPTO_PKI: (0) Fetch 0
*Mar 26 17:54:22.209: CRYPTO_PKI: locked trustpoint OPENSSL, refcount is 1
*Mar 26 17:54:22.213: CRYPTO_PKI: http connection opened
*Mar 26 17:54:22.213: CRYPTO_PKI: Sending HTTP message
reda(config)#
*Mar 26 17:54:22.213: CRYPTO_PKI: Reply HTTP header:
HTTP/1.0
Host: 192.168.4.104
reda(config)#
*Mar 26 17:54:24.213: CRYPTO_PKI: unlocked trustpoint OPENSSL, refcount is 0
*Mar 26 17:54:24.213: CRYPTO_PKI: Send HTTP header:
GET HTTP/1.0
Host: 192.168.4.104
*Mar 26 17:54:24.213: CRYPTO_PKI: HTTP data
47 45 54 20 20 48 54 54 50 2F 31 2E 30 0D 0A 48
6F 73 74 3A 20 31 39 32 2E 31 36 38 2E 34 2E 31
30 34 0D 0A 0D 0A 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
*Mar 26 17:54:24.213: CRYPTO_PKI: locked trustpoint OPENSSL, refcount is 1
*Mar 26 17:54:24.217: CRYPTO_PKI: unlocked trustpoint OPENSSL, refcount is 0
*Mar 26 17:54:24.217: CRYPTO_PKI: Reply HTTP header:
HTTP/1.0 200 OK
Content-Type: application/ocsp-response
Content-Transfer-Encoding: Binary
Content-Length: 5
Date: Mar 26 17:57:15 2015 GMT
Expires: Mar 26 18:02:15 2015 GMT
*Mar 26 17:54:24.217: CRYPTO_PKI: HTTP header content length is 5 bytes
*Mar 26 17:54:24.217: CRYPTO
reda(config)#_PKI: FETCH IO data 30 03 0A 01 01
*Mar 26 17:54:24.217: CRYPTO_PKI: processing CRYPTO_INSERT_CRL but session id (0) is not valid
*Mar 26 17:54:24.217: CRYPTO_PKI: (0) Verify incoming CRL
*Mar 26 17:54:24.217: ../cert-c/source/crlobj.c(504) : E_BER_ENCODING : invalid encoding format for input data
*Mar 26 17:54:24.217: %PKI-4-CRLINSERTFAIL: Trustpoint "OPENSSL" failed to parse CRL (error 1793:E_BER_ENCODING : invalid encoding format for input data)
*Mar 26 17:54:24.217: CRYPTO_PKI: transaction Unknown completed
on the OCSP side I get this error:
Network Error while reading Request!
I am using cisco 881 routers and my OCSP server is OPENCA OCSPD
When I do a wireshark trace of the incomming and outgoing packets on the OCSP server I see a http get request comming in, and a ocsp reply "responseStatus: malformedRequest (1)" going out
here is my router configuration
reda#show run
Building configuration...
Current configuration : 3985 bytes
! Last configuration change at 18:04:27 UTC Thu Mar 26 2015
version 15.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname reda
boot-start-marker
boot-end-marker
aqm-register-fnf
no aaa new-model
crypto pki trustpoint OPENSSL
enrollment terminal
fqdn reda.engageinc.com
revocation-check ocsp
ocsp url http://192.168.4.104:8080
ocsp disable-nonce
rsakeypair BRANCH_KEY
crypto pki crl cache size 2048
crypto pki certificate chain OPENSSL
certificate ca 00A3A5C798F3C3312A
308203EF 308202D7 A0030201 02020900 A3A5C798 F3C3312A 300D0609 2A864886
F70D0101 05050030 18311630 14060355 04030C0D 42564341 206E756D 62616820
32301E17 0D313530 33323631 37343935 345A170D 31363033 32353137 34393534
5A307431 0B300906 03550406 13025553 31133011 06035504 08130A43 616C6966
6F726E69 61311D30 1B060355 040A1314 456E6761 67652043 6F6D6D75 6E696361
74696F6E 31143012 06035504 0B130B65 6E67696E 65657269 6E67311B 30190603
55040313 12726564 612E656E 67616765 696E632E 636F6D30 82012230 0D06092A
864886F7 0D010101 05000382 010F0030 82010A02 82010100 A58DD944 7A6F5BD4
DA6BFE90 B2470DC0 1A3C8226 6EC8B7E1 55DF83B8 4A85BA36 76A52A40 278A6658
8A630B52 1C95B216 FE9A7CC3 A9393AAB CEC76AF1 96983EA2 57A721AD 7B34D746
4EF92844 FFA2ABF0 46E88E48 7F2BD4FE D6FF1666 A7305664 82127826 97615B40
262173FE 03C75FCB 89A0CB34 E17F33CB C37021BB B9EC10F4 33C556BC 40DD562B
CD70B17D F3736F1B AF614249 1D3C1944 DBEC101B CD9A44BB 044595A6 67B97541
85631A15 5CCFDBBD F9BA44A6 458E585F EDE279DC BDFB4252 FABC2925 2FA13F4A
466ECE7F 35832216 FCAF26A9 81431984 F327DC8A E24DE0C1 26E6098C 827BF6F0
3475D9E7 43321F7E 6A3CFBD5 045CBF9F E5402137 05AE0C77 02030100 01A381DF
3081DC30 09060355 1D130402 3000302C 06096086 480186F8 42010D04 1F161D4F
70656E53 534C2047 656E6572 61746564 20436572 74696669 63617465 301D0603
551D0E04 1604141D 6BCA5313 5483C2D2 3174EF6D 4E4984DC 27815E30 1F060355
1D230418 30168014 A82D5098 9F656D45 F5CE357D 2E42EBAC 29EBFF00 302A0603
551D1F04 23302130 1FA01DA0 1B861968 7474703A 2F2F3139 322E3136 382E342E
3130343A 38303830 30350608 2B060105 05070101 04293027 30250608 2B060105
05073001 86196874 74703A2F 2F313932 2E313638 2E342E31 30343A38 30383030
0D06092A 864886F7 0D010105 05000382 0101005E AC863E65 F8D79A7A BA7C7487
46BC088D 7E1258E2 E5BCA564 5C00EB24 1BD9D596 63699A89 55168389 9D539BED
FA8262E3 0F815E7F 247BC37B 29482BBE 9B491C83 5608F46D E01C3DDC 05524BB9
33E9B24D BF1E2428 B719FF9A 714A0D64 78431A46 53A49009 A8A421C1 0D1A069A
B1B18D1B DBBE900D 98C8EE3B 9B2973EE 4E8993F3 97703F91 6F05F7EE 69436DBD
72998F37 AD454795 76015884 E2E634B6 EDC1D7F0 12725682 D52CAD1F 72F6CD45
5ED20D7B 7FB36364 7631B39F F71F73BE DDE0E708 FC709E80 793E60FE F4F3B178
A7C8384D A42A9729 18E0AABB 704F98E3 D2446963 79355C47 D16B5E91 D14740B4
5F6B1668 415E3669 397FB43A F793471E 498068
quit
ip cef
no ipv6 cef
multilink bundle-name authenticated
license udi pid C881-K9 sn FTX190485K6
interface FastEthernet0
no ip address
interface FastEthernet1
no ip address
interface FastEthernet2
switchport access vlan 104
no ip address
interface FastEthernet3
no ip address
interface FastEthernet4
no ip address
shutdown
duplex auto
speed auto
interface Vlan1
no ip address
interface Vlan104
ip address 192.168.4.1 255.255.255.0
ip forward-protocol nd
no ip http server
no ip http secure-server
control-plane
mgcp behavior rsip-range tgcp-only
mgcp behavior comedia-role none
mgcp behavior comedia-check-media-src disable
mgcp behavior comedia-sdp-force disable
mgcp profile default
line con 0
logging synchronous
no modem enable
line aux 0
line vty 0 4
login
transport input all
scheduler allocate 20000 1000
end
reda#
help?

Hi Wolfgang,
yes, we solved the problem indeed.
The solution for us was to upgrade the portal to the following releases:
sap.com SAP_ESS 603 SP2
sap.com SAPPCUI_GP 603 SP2
sap.com BP_ERP5ESS 1.31 SP2
I believe that these releases must be used when you have EhP3 in the HR backend.
Hope this will help you too.
Alex

Unable to run ADFBC JUNIT Test Classes with JDEV11G 11.1.1.6

Dear All,
I upgraded my project to the latest release JDEV 11G 11.1.1.6
Previously we are on JDEV 11G 11.1.1.5
I have a JUNIT class that I am running which test my ADFBC components.
public class MyTestClass {
@Test
public void testVOAccess()
    //assertions
}Unfortunately, I am hitting an error like this from the messages.
Mar 9, 2012 1:28:07 PM oracle.adf.share.ADFContext getCurrent
WARNING: Automatically initializing a DefaultContext for getCurrent.
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
For more information please enable logging for oracle.adf.share.ADFContext at FINEST level.
Mar 9, 2012 1:28:08 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: org.xml.sax.SAXParseException: Invalid encoding name "Cp1252".
Mar 9, 2012 1:28:10 PM oracle.mds
NOTIFICATION: PManager instance is created without multitenancy support as JVM flag "oracle.multitenant.enabled" is not set to enable multitenancy support.
Mar 9, 2012 1:28:12 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: org.xml.sax.SAXParseException: Invalid encoding name "Cp1252".
Mar 9, 2012 1:28:12 PM oracle.adf.share.jndi.ReferenceStoreHelper getReferencesMapEx
WARNING: Incomplete connection reference object for connection:MYDATASOURCEAt the JUNIT Test Runner, I see this.
java.lang.ExceptionInInitializerError: null
     java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:171)
     org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:216)
Caused by: oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
     oracle.jbo.server.ConnectionPool.createConnection(ConnectionPool.java:207)
     oracle.jbo.server.ConnectionPool.instantiateResource(ConnectionPool.java:166)To validate the issue, I tried to run my same project using the older release which is JDEV 11G 11.1.1.5
and I see that I am not hitting any error. All my test classes runs fine.
Has anybody replicated this?
Thanks

Didier Laurent wrote:
I logged the following bug for this issue:
bug 14030895 - REGR: JDEVELOPER 11.1.1.6.0 JUNIT JBO-26061 ERROR WHILE OPENING JDBC CONNECTION
Regards,
Didier.So its really a bug..
I abandon this already since I cannot find any solution to look up for this.
On the other hand, I am maintaining two jdeveloper version just to get around this problem.
When testing ADFBC, I used the 11.1.1.5 while for non-junit test I used the 11.1.1.6
Hopefully this gets fixed on the next release as I am having a hard time swithcing between two JDev version.
Thanks
Edited by: Neliel on May 3, 2012 11:42 PM

Create a PDF as attachment in custom module in mail receiver adapter

I'm trying to create a PDF attachment to an email using a custom module with the following codes. The attachment was created and sent, but when I tried to open it, I got the following error message: the file cannot be read either because a invalid encoding or the file is damaged.
Anybody knew if I did anything wrong in the way I'm opening and creating the PDF attachment below?
// add a new pdf attachment to the message
FileInputStream fi = new FileInputStream("c:/ftmailxi.pdf");
byte[] attachmentContent = new byte[fi.available()];
Payload attachmentPDF = msg.createPayload();
attachmentPDF.setName("ftmailxi.pdf");
attachmentPDF.setContentType("application/pdf");
attachmentPDF.setContent(attachmentContent);
//adding our this pdf as an attachment
msg.addAttachment(attachmentPDF);
//provide the XI message for returning
inputModuleData.setPrincipalData(msg);

This will surly help u
/people/sravya.talanki2/blog/2006/11/28/e-mail-xml-messages-in-pdf-format-from-sap-xi
Check this out
Mail with attachment.
Regards,
Prateek

Reading UTF-7 XML document in Java

I have an XML document and I want to add PrcessingInstruction to it.
<?xml version="1.0" encoding="UTF-7" ?>
<root_element>
<sections>
<section_introduction>
<order-no>108800674</order-no>
<order-type>219</order-type>
<created-date>5. november 2008</created-date>
when trying to parse it like
File tmpFile = new File("C:\\ProvisioningEventError58412.xml");
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setValidating(false);
Document doc = factory.newDocumentBuilder().parse(tmpFile);
System.out.println("end");
I get an exception on Document doc = factory.newDocumentBuilder().parse(tmpFile);
org.xml.sax.SAXParseException: Invalid encoding name "UTF-7".
[Fatal Error] ProvisioningEventError58412.xml:1:40: Invalid encoding name "UTF-7".
Is it possible to set encoding on DocumentBuilder, so it can work with UTF-7 or is there any other was to parse it for adding ProcessingInstruction. Actually I want to add a CSS/XSL file for formatting the XML File.
Edited by: aamaam on Jul 15, 2009 5:18 AM

As you will see from [this Supported Encodings document|http://java.sun.com/javase/6/docs/technotes/guides/intl/encoding.doc.html], it's Java which doesn't support UTF-7, not just DocumentBuilder.
So you have a couple of options. You could send the document back to whoever produced it and tell them that you can't process it the way it is. That's a legitimate thing to do because [the XML Recommendation|http://www.w3.org/TR/REC-xml/] only requires parsers to support UTF-8 and UTF-16. Support for other encodings is optional.
Or you could write your own subclass of InputStreamReader which converts a stream of UTF-7 bytes into a stream of chars, and use that as a Reader which you pass to the parser. Somebody may even have done that already and posted it on the web somewhere.

(invalid encoding)

Similar Messages

Maybe you are looking for