Encoding Problems with WRT300N V2

Hello guys,
i have following problem:
I have a WRT300n Router and it seems to have problems with WPA2 encoding. I have 2 different deviceses (a SMC Ethernet Bridge and a PS3) trying to connect to my Linksys wireless router. No chance in WPA2 mode but when I try in WEP-Mode, both devicec can connect to it.
Are there known encoding problems?
Any idea what i can do?

It is able to use. But my router always drops the connection. WEP is no problem, but ... what about low security and Wirless N is not enabled ??

Similar Messages

Encoding problem with XSL

Hi,
I have problems when printing the result of processing XML with an XSL that contains locale specific chars.
Here is a sample:
XML :
<?xml version="1.0" encoding="ISO-8859-1"?>
<ListePatients>
<Patient>
<Nom>Zeublouse</Nom>
<NomMarital/>
<Prinom>Agathe</Prinom>
</Patient>
<Patient>
<Nom>Stick</Nom>
<NomMarital>Laiboul</NomMarital>
<Prinom>Ella</Prinom>
</Patient>
<Patient>
<Nom>`ihnotvy</Nom>
<NomMarital/>
<Prinom>Jacques</Prinom>
</Patient>
</ListePatients>
XSL :
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html"/>
<xsl:template match="*|/"><xsl:apply-templates/></xsl:template>
<xsl:template match="text()|@*"><xsl:value-of select="."/></xsl:template>
<xsl:template match="/">
<HTML>
<HEAD>
<META http-equiv='Content-Type' content='text/html; charset=iso-8859-1'/>
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<xsl:apply-templates select='ListePatients'/>
</BODY>
</HTML>
</xsl:template>
<xsl:template match='ListePatients'>
<TABLE>
<xsl:for-each select='Patient'>
<xsl:sort select='Nom' order='ascending' data-type='text'/>
<TR TITLE='`ihnotvy'>
<TD> <xsl:value-of select='Nom'/> </TD>
<TD> <xsl:value-of select='NomMarital'/> </TD>
<TD> <xsl:value-of select='Prinom'/> </TD>
</TR>
</xsl:for-each>
</TABLE>
</xsl:template>
</xsl:stylesheet>
Test program (from Oracle sample) :
import java.net.URL;
import java.io.*;
import oracle.xml.parser.v2.DOMParser;
import oracle.xml.parser.v2.XMLDocument;
import oracle.xml.parser.v2.XMLDocumentFragment;
import oracle.xml.parser.v2.XSLStylesheet;
import oracle.xml.parser.v2.XSLProcessor;
public class XSLSampleOTN
* Transforms an xml document using a stylesheet
* @param args input xml and xml documents
public static void main (String args[]) throws Exception
DOMParser parser;
XMLDocument xmldoc, xsldoc, out;
URL xslURL;
URL xmlURL;
try
if (args.length != 2)
// Must pass in the names of the XSL and XML files
System.err.println("Usage: java XSLSampleOTN xslfile xmlfile");
System.exit(1);
// Parse xsl and xml documents
parser = new DOMParser();
parser.setPreserveWhitespace(true);
// parser input XSL file
xslURL = DemoUtil.createURL(args[0]);
parser.parse(xslURL);
xsldoc = parser.getDocument();
// parser input XML file
xmlURL = DemoUtil.createURL(args[1]);
parser.parse(xmlURL);
xmldoc = parser.getDocument();
// instantiate a stylesheet
XSLStylesheet xslSS = new XSLStylesheet(xsldoc, xslURL);
XSLProcessor processor = new XSLProcessor();
// display any warnings that may occur
processor.showWarnings(true);
processor.setErrorStream(System.err);
// Process XSL
XMLDocumentFragment result = processor.processXSL(xslSS, xmldoc);
// print the transformed document
result.print(System.out);
// an other way to print, it doesn't print the same !!!!
processor.processXSL(xslSS, xmldoc, System.out);
catch (Exception e)
e.printStackTrace();
When printing the transformed document with DocumentFragment.print() it work fine but when using processXSL(xslSS, xmldoc, System.out) it don't works for locale specific chars and a second <META> balise appears, Why ?
with DocumentFragment.print(), it's Ok :
<HTML>
<HEAD>
<META http-equiv="Content-Type"
content="text/html; charset=iso-8859-1"/>
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<TABLE>
<TR TITLE="`ihnotvy">
<TD>`ihnotvy</TD>
<TD/>
<TD>Jacques</TD>
</TR >
<TR TITLE="`ihnotvy">
<TD>Stick</TD>
<TD>Laiboul</TD>
<TD>Ella</TD>
</TR>
<TR TITLE="`ihnotvy">
<TD>Zeublouse
</TD>
<TD/>
<TD>Agathe</TD>
</TR>
</TABLE>
</BODY>
</HTML>
With processXSL(xslSS, xmldoc, System.out), it's not Ok :
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html">
<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<TABLE>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>C C)C(C.C/C4C6C9</TD>
<TD></TD>
<TD>Jacques</TD>
</TR>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>Stick</TD>
<TD>Laiboul</TD>
<TD>Ella</TD>
</TR>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>Zeublouse</TD>
<TD></TD>
<TD>Agathe</TD>
</TR>
</TABLE>
</BODY>
</HTML>
TIA
Didier
null

Two other problems with XSL and print:
first one :
XSL :
<SCRIPT langage="Javascript" type="text/javascript" src="scripts/erreur.js"></SCRIPT>
DocumentFragment.print() produce :
<SCRIPT langage="Javascript" type="text/javascript" src="scripts/erreur.js"/>
=> IE5.5 don't load the file !!, it required syntaxe like <SCRIPT ...></SCRIPT> to load.
the second one :
XSL:
<TD><IMG src="images/menuleft.gif"/></TD>
DocumentFragment.print() produce :
<TD>
<IMG src="images/menuleft.gif">
</TD>
processXSL(xslSS, xmldoc, System.out) produce :
<TD><IMG src="images/menuleft.gif">
</TD>
Why a cariage return ?? it cause prisentation failure when you want to specifie the size off the cell !!
TIA
Didier
null

Problems with WRT300n & WPC300n

Hi guys!
I have a problem. I am reviewing the two Linksys-thingys WRT300n & WPC300n for a pc-mag, and for the last 4 hours I have been all over the internet trying to get a clue...
First of all both items works (not well (low range/falls out once in a while), but there is a connection after all). My main prob is, that I cant get the WPC300n to go faster then 54 Mbps... In the Linksys-control it says Wide Channel: N/A... like this is just regular G-speed...?
I have tried to turn on all the encryptionfacilities but it doesnt help. All the drivers and firmware are the newest...
Any of you got a clue?

I'm having the same problem with the same equipment. I hope there is someone that can help us. PLEASE

Encoding problem with Application adapter for OEBS

Hello All!
We going to pass value via app adapter from EBS Forms to Content Server page. Link to documentation Configuring the Managed Attachments Solution - 11g Release 1 (11.1.1)
We have done all setting, and this function is working now .
It is good working with English letters and numbers, but when we try to use Cyrillic we have a problem with Encoding in Content server page.
Data on Oebs table use ''CL8ISO8859P5'', but service xml for adapter has allays a title with charset=utf-8
System are:
OEBS 12.1.3
Webcenter Content 11.1.1.6
Adapter 11.1.1.6 + patch 16463891
Could you help us?

Hi Denis ,
Try this solution :
1) Log on to the APPS EBS schema and re-create the AXF_SOAPCall function using the following SQL:
create or replace
function AXF_SOAPCall (url varchar2, soapmsg varchar2, secure varchar2, walletid varchar2, walletpass varchar2) return varchar2 as
http_req utl_http.req;
http_resp utl_http.resp;
response_env varchar2(32767);
v_newcharset VARCHAR2(40 BYTE) :='UTF8';
v_Dbcharset VARCHAR2(40 BYTE);
v_Raw1 RAW(32767);
v_Stmt1 VARCHAR2(6000 BYTE);
begin
v_newcharset := 'AMERICAN_AMERICA.'|| v_newcharset ;
v_Dbcharset := 'AMERICAN_AMERICA.'||utl_i18n.map_charset(fnd_profile.value('ICX_CLIENT_IANA_ENCODING'),0,1);
v_Raw1 := UTL_RAW.CAST_TO_RAW (soapmsg);
v_Raw1 := UTL_RAW.CONVERT (v_Raw1,v_newcharset,v_Dbcharset);
if ( secure = 'true' or secure = 'TRUE' ) then
utl_http.set_wallet (walletid, walletpass);
end if;
http_req := utl_http.begin_request(url , 'POST', utl_http.HTTP_VERSION_1_1);
utl_http.set_header(http_req, 'Content-Type', 'text/xml; charset=utf-8');
utl_http.set_header(http_req, 'Content-Length', utl_raw.length(v_Raw1));
utl_http.write_raw(http_req, v_Raw1);
http_resp := utl_http.get_response(http_req);
utl_http.read_text(http_resp, response_env);
dbms_output.put_line('Response: ');
dbms_output.put_line(response_env);
utl_http.end_response(http_resp);
return response_env;
end;
2) Log on to the EBS and confirm that you can now open the Managed Attachments window for all records & forms, regardless of the use (& length) of multibyte string values.
This was caused by multibyte characters used with non UTF-8 language strings .
I presumed that you are seeing that when "Managed Attachments" option through the ZOOM button from an E-Business Suite (EBS) forms, nothing happens.If you have a support id then check the following note : 1409703.1 from MyOracleSupport portal.
Hope this helps.
Thanks,
Srinath

Encoding problem with convert and CLOB involving UTF8 and EBCDIC

Hi,
I have a task that requires me to call a procedure with a CLOB argument containing a string encoded in EBCDIC. This did not go well so I started narrowing down the problem. Here is some SQL to illustrate it:
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> select value from v$nls_parameters where parameter = 'NLS_CHARACTERSET';
VALUE
AL32UTF8
SQL> select convert(convert('abc', 'WE8EBCDIC500'), 'AL32UTF8', 'WE8EBCDIC500')
output from dual;
OUT
abc
SQL> select convert(to_char(to_clob(convert('abc', 'WE8EBCDIC500'))), 'AL32UTF8', 'WE8EBCDIC500') output from dual;
OUTPUT
╒╫¿╒╫¿╒╫¿
So converting to and from EBCDIC works fine when using varchar2, but (if I am reading this right) fails when involving CLOB conversion.
My question then is: Can anyone demonstrate how to put correct EBCDIC into a CLOB and maybe even explain why the examples do what they do.

in order to successfully work with xmldb it is recommended that you use 9.2.0.4
and above. Its seems to have lower version.
Okay now related to the problem , if your data that you want to send to the attributes are not greater than 32767, then you can use the pl/sql varchar2 datatype to hold the data rather then CLOB and overcome this problem.
here is the sample. use function with below pl/sql to return the desired output.
SQL> declare
2   l_clob     CLOB := 'Hello';
3   l_output   CLOB;
4 begin
5    select xmlelement("test", xmlattributes(l_clob AS "a")).getclobval()
6      into l_output from dual;
7 end;
8 /
select xmlelement("test", xmlattributes(l_clob AS "a")).getclobval()
ERROR at line 5:
ORA-06550: line 5, column 44:
PL/SQL: ORA-00932: inconsistent datatypes: expected - got CLOB
ORA-06550: line 5, column 3:
PL/SQL: SQL Statement ignored
SQL> declare
2   l_vchar     varchar2(32767) := 'Hello';
3   l_output   CLOB;
4 begin
5    select xmlelement("test", xmlattributes(l_vchar AS "a")).getclobval()
6      into l_output from dual;
7    dbms_output.put_line(l_output);
8 end;
9 /
<test a="Hello"></test>
PL/SQL procedure successfully completed.

JSF encoding problem with Russian

Hi,
I am new to JSF, trying to build prototype i18n JSF app with MyFaces 1.1.5
Mostly care about IE6/7, do not officially support other browsers.
I do have resource bundles, it is localized and internationalized.
So user is supposed to work in either English or Russian.
It all works except a few issues:
1) When user enters something in Russian in inputText field on the first page,
trying to pass it to the next page via managed bean.
But instead of showing it in Russian, it shows some garbled text in outputText or outputLabel: Îëåã
FF3 & Chrome show it as: Олег [&#xxxx, where xxxx us a 4 digits]
It does pick up labels from correct bundle on the next page, so locale is changed correctly.
Actually, when I switch locale on the same first page, getting the same problem (after it's refreshed).
Seems to work OK with Spanish
Is that incorrect Cyrillic encoding, JSF encoding or broken Unicode or locale?
How can we fix that ?
Less important issues:
2) When we switch locale (correct values in bundles), on the screen it can not change currencyCode, currencySymbol, TimeZone,
it always shows the first one it picked, although dateTime and Number formatting changes correctly;
3) In IE6 "alt" tag attribute produces garbled characters in Russian (black vertical squares), looks like IE6 bug; FF3 & Chrome work fine.
Please help !
TIA,
Oleg.

For 1, you are not passing the characters in the correct encoding from one page to the next when you pass the parameter (most likely).

Encoding Problems with 16:9

hi, just started creating 16:9 projects, however i dont think idvd likes 16:9 as anytime i try t burn it fails and says that "there was a problem during encoding" anyway else experience this?

This may be of assistance to you and others experiencing the wonderfully enigmatic " Encoding Video - There was an error during movie encoding. "
SHORT VERSION of SOLUTION: Downloaded Handbrake. Converted source video using Handbrake's default settings. Imported resulting videos into iDVD. Everything worked.
LONG VERSION of SOLUTION: I have a few 16:9 mp4 videos that I was attempting to burn onto a relatively simple DVD. No matter what theme I chose, I received the encoding error. After reading a number of other posts on the subject, on a lark, I thought I would try to change the encoding of the movies to some other format. Turns out this solved the problem in a roundabout way. Handbrake (http://handbrake.fr/?article=download) was key to the solution. I tried converting to MKV first; that didn't work. Then I noticed something. When I chose the mp4 original and left Handbrake with default settings, the specifications for the source video showed 1280x720, but the specifications for the output video showed 1278x720. I converted the mp4 video to ... well ... mp4 (Handbrake's default format). Handbrake's resulting file had an m4v extension, but I don't think that has any relevance. So, back in iDVD, I imported the new versions of the video and everything worked. I hope that is of some assistance to you.

Media Extender Problem with WRT300N

I have the Linksys WRT300N wireless router. I am having problems using the wireless connection with my Xbox 360 and my PS3. The internet portions of the consoles works fine. Im running into problems when I try and use either one as a media extender. Both the PS3 and the Xbox 360 are using the wireless adapters. Ive made sure that my computer is set up for media sharing and that my Windows Firewall is configured correctly. Ive looked at the setting of the router but it seems pretty complex and I dont know what to change if anything to resolve the problem. Could anyone tell me what the setting should be on the router to enable media sharing?

I dont think that there is some settings on the router .... but you can follow this settings ....
Access router setup page ....
Please click on the tab "Application and gaming" and click on sub
tab "Port range forwarding"
1) On the first line in Application box type in "Xbox", in start box
type in 88, in end box type in 88, in protocol keep it both, in ip
address type in 192.168.1.20 and give a check mark on enable box.
2)   On the second line in Application box type in "Xbox", in start box
type in 3074, in end box type in 3074, in protocol keep it both, in ip
address type in 192.168.1.20 and give a check mark on enable box.
3) Now save the settings
4) Once you return to the setup page, click on the tab "Administration"
and disable the UPNP and save the settings.
5) Now assign the given ip address on your xbox
   ip address :- 192.168.1.20
   subnet mask :- 255.255.255.0
   default gateway :- 192.168.1.1
Please assign the dns address on the xbox
primary dns :- 4.2.2.2
secondary dns :- 192.168.1.1
6) Please try to test your xbox live.

Encoding problem with xml

Hello,
I'm trying to save on disk an xml with utf-8 codification and compressed with "gzip" algorithm. For some reasons, I have to use a BufferedWriter, then I must convert the byte[] to String.
Afterwards, I read this document and I try to decompress it and save on a String variable.
If I do all this process using utf-8 encoding, the decompressing process throws an exception: Not in GZIP format.
But if I use iso-8859-1, then everything works OK.
I don't understand why using iso works, and why using utf-8 does not work (when the webservice specification says that the xml documents are sent in utf-8).
The code is the following (the static "myCharset" is the key: when I set iso works, and setting utf-8 does not work):
public class testCompress
public static String xmlOutput     = "<?xml version=\"1.0\" encoding=\"utf-8\"?><soap:Envelope xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"><soap:Body><consultaCiudadesPorPaisResponse xmlns=\"http://tempuri.org/\"><consultaCiudadesPorPaisResult><xml funcion=\"ConsultaCiudadesPorPais\" xmlns=\"\"><ROK>TRUE</ROK></xml></consultaCiudadesPorPaisResult></consultaCiudadesPorPaisResponse></soap:Body></soap:Envelope>";
public static String myCharset     = "iso-8859-1";
// Writes the compressed document to disk.
public static void writeDocument() throws Exception
BufferedWriter writer = null;
try
   // Compress the "xmlOutput" converting this string to bytes using "utf-8" as specification says (in "compress" method)
   // Afterwards, I convert this byte[] to String using "myCharset".
   String compressedFile = new String(CompressionService.compress(xmlOutput, "utf-8", "gzip", 8), myCharset);
   // And write to disk using "myCharset" as the encoding used by "OutputStreamWriter".
   writer = new BufferedWriter(new OutputStreamWriter(new FileOutputStream("c:/cache"), myCharset), 8192);
   writer.write(compressedFile);
catch (Exception e) { throw e; }
finally
    if (writer != null)
     try { writer.close(); writer = null; } catch (IOException ioe) {}
// Reads the compressed document from disk.
public static byte[] readDocument() throws Exception
BufferedReader reader = null;
StringBuilder sb           = new StringBuilder();
char[] buffer           = new char[8192];
try
   // Open the file using "myCharset" for reading chars.
   reader = new BufferedReader(new InputStreamReader(new FileInputStream("c:/cache"), myCharset));
   int numchars = 0;
   while ((numchars = reader.read(buffer, 0, 8192)) >= 0) sb.append(buffer, 0, numchars);
   // And return the result as a byte[] encoded with "myCharset".
   return (sb.toString().getBytes(myCharset));
catch (Exception e) { throw e; }
finally
   if (reader != null)
    try { reader.close(); } catch (IOException ioe) {}
public static void main(String[] args) throws Exception
writeDocument();
byte[] file = readDocument();
// DECOMPRESS FAILS IF myCharset = "utf-8", and works if myCharset = "iso-8859-1"
System.out.println(com.vpfw.proxy.services.compress.CompressionService.decompress(file, "utf-8", "gzip", 8));
}

Okay, here's what's happening. You created a byte[] by encoding some text as UTF-8, then you ran that byte[] through a gzip deflater. The result is binary data that can only be understood by a gzip inflater; to any other software it just looks like garbage. Now you're taking a randomly-chosen encoding and pretending the binary data is really text that was encoded with that encoding.
Most encodings have limits on what kinds of input they can accept. For example, US-ASCII only uses the low-order seven bits of each byte; any byte with a value larger than 127 is invalid. When the encoder encounters such a byte, it inserts the standard replacement character, U+FFFD, in that spot. When you try to decode the string again as US-ASCII, the replacement character is what you see in that position; the original byte value is lost. In UTF-8, the bytes have to conform to [certain patterns|http://en.wikipedia.org/wiki/UTF-8#Description]; for example, any byte with a value greater than 127 has to be part of a valid two-, three- or four-byte sequence.
ISO-8859-1 is different. It's a single-byte encoding like ASCII, but it uses all eight bits of every byte. Furthermore, every possible byte value (0..255) maps to a character, so you can throw any random byte at it and tell it the byte represents a character, and it will believe you. Some of those values may map to control characters that would look like garbage if you displayed them, but they're valid. That means you can re-encode the string as ISO-8859-1 and get back the exact byte sequence you started with.
So that's why your code "works" when you use ISO-8859-1, but I strongly recommend that you find another way; making binary data masquerade as text is dangerously fragile. Why do you have to use a Writer anyway? Is it for transmission over a medium that only accepts text data? If so, you should use a Base64 encoder or similar tool that's designed for that purpose.

Encoding problem with servlet

I am using java servlet to submit an Arabic string to some java class and save this Arabic string in text file.
The problem is in the encoding, where the Arabic query is not saved correctly inside the text
file. The same program is work fine using java.
Getting the query (Unicode: Arabic windows) from servlet:
     String query = request.getParameter("query".trim());
Saving it in the text file:
     ps = new PrintStream(new FileOutputStream(
                    "C:/file/1.txt"),true,"utf-8");
          ps.println(query);
As I said the same task is done correctly using java. Where I submit a utf-8 string and save it inside the text file.
I tried also to convert the Arabic windows code to utf and then save it inside the text file but this also doesnt help: query = new String (query.getBytes("utf-8"));
Any suggestions?
Thanks
Edited by: [email protected] on Oct 6, 2009 6:52 AM

I've tried the following code and it worked for me :
               response.setContentType("text/html");
          String param = request.getParameter("test");
          String query =new String(param.getBytes("ISO-8859-1"),"UTF-8");
          PrintStream ps = new PrintStream(new FileOutputStream(
          "C:/1.txt"));
          ps.write((query.getBytes("UTF-8")));
          ps.close();

Character encoding problem with german umlaut in propertie files

Hi,
I use propertie files to translate application to multiple languages.
These files contains german umlaut (e.g.: Wareneingänge).
If I rebuild my application then this files are copied from ../src/view to ../classes/view.
The file in ../classes/view contains "Wareneing\ufffdnge" instead of "Wareneingänge" which is displayed as "Wareneing�nge".
My browser-, project- and application settings are UTF8.
Previously the settings for project and application where "Windows-1252"
I have found an workarounds but maybe this is a bug in Jdeveloper TP4.
Therefore I post this problem. Maybe someone can confirm this behaviour.
Workaround:
Replace "Wareneingänge" with "Wareneing\u00e4nge" in the ../src/view file
(Zaval JRC Editior does this for you :-) )
regards
Peter

Hi,
I think to remember that the same was required for properties in 10.1.3 as well. Not sure if this is an issue in JDeveloper 11. I'll take anot and have a look though
Frank

JSON encoding problem with entities

I am trying to pass actionscript strings that have entities such as the Degrees symbol (as in 175°, not sure if the degree symbol shows here)
I have a string like:
private var step7b:String = "Cool the custard to below 70° F by stirring it over the ice bath. ";
When the PHP attempts to write out this line of text it either fails completely, or prints the wrong entity code. such as "Preheat oven to 325% u02DAF"
What do I need to do to correctly pass symbols such as the degree sign from an Actionscript string to PHP?
Note: Entities loaded from XML work fine. It's only AS string variables. And this whole setup worked correctly when I used to use a WSDL service, the JSON is new and it's when this problem arose. I am using this code block:
// create the JSON
                    var objSend:Object = new Object();
                    var dataString:String = JSON.encode(packagedData);
                    dataString = escape(dataString);
                    objSend.jsonSendData = dataString;

Hi,
You are using something like dataString = escape(jsonString);
the escape function in actionscripts does about the same as urlencode(addslashes(jsongString) in php.
So you could try what happens if you leave out the escape or if you're able to adjust the php side, then
use a urldecode(jsonString) or something.

Character encoding problems with weblogic stax implementation?

Hello all,
While using Stax to parse some XML, we encounter the following exception when the processor reaches the UTF-8 character C3 B1, ('ñ'):
Caused by: Error at Line:1, token:[CLOSETAGBEGIN]Unbalanced ELEMENT got:StudentRegistration expected:LastName
at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:374)
at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:199)
We suspect that the processor's encoding might somehow be set to ANSI instead of UTF-8. I have read, in other posts, of a startup property related to web services:
-Dweblogic.webservice.i18n.charset=utf-8
However, this XML is not a web service request, but rather a file being read from disk after an MDB's onMessage() method is called.
Could this setting be affecting stax parsing outside of webservices? Any other ideas?
Thanks!

As far as I know, we don't support changing outbound message encoding charset in 9.x. Both 8.x and 10.x support it. Check [url http://docs-stage/wls/docs100/webserv/client.html#wp230016]here

Flash cs5.5 FLVplayback Encoding Problems with Air for Android

Dear All,
I'm trying to play flv in my air application by using FLV playback in flash cs5.5.
I can play flv in the pc but not on the samsung galaxy tab andriod platform.
if anyone out there has tried out FLV playback with either an Air For Android application, where the FLV files are packaged within the app, or either streaming via normal http//:, any help would be greatly appreciated.
Thanks!

First disable autoplay. It gave errors for me. Try to make the movie play with the play() command.
to embed the movie in your air bundle, just go to publish settings for your flash project. Then in that screen go to the player settings.
In the first GENERAL tab you'll see a the bottom that you can add files to your project
Propably there is allready your .swf and an .xml file in there.
Using the + icon you can add your video.
Make sure that your video is in the same directory as your . FLA file and you can use it as is (by name)
If for example your flashfile is in c:\mytest\mytest.fla and the video in c:\mytest\videos\myvideo.flv , then you will have to load your video as "videos/myvideo.flv" with a FORWARD slash, never use \
Good luck

Encoding problems with iDVD 7 (newest update included)

Hey Guys,
I am trying to burn a film on to iDVD using all options...no errors messages on the DVD map. This is an 86 minutes long film as well as a slideshow.
Once I try to burn it though it tells me I have 'there was an error during encoding movie' but does not say anything more specific than that (trying to use a DL DVD as well as regular DVD disc)...what is going on?
Ideas? What can I do?
Thank you for any input.
Joel
[email protected]

Then
• Codec of video used ?
• file format on Photos to slideShow
• audio file format - I never use .mp3 - all is converted to .aiff 16-bit 48kHz or on Audio-CD 44.1kHz
• Brand of DVD used - I only use Verbatim
• DVD type - I use DVD-R as they play on more DVD-players
• Burn speed set down to x4 or less
Yours wildly guessing - Bengt W

Encoding Problems with WRT300N V2

Similar Messages

Maybe you are looking for