Encoding in WSRP message - MarkupRequestState

Hi all!
I have successfully executed the different samples given at this location.
http://edocs.bea.com/wlp/docs81/wsrp/custxfer.html
I was especially intrested in testing the sample which allows the Consumer to send some arbitrary data to the Producer when a portlet is being refreshed.
(com.bea.wsrp.ext.holders.MarkupRequestState)
This all works behind the scene when the Producer and Consumer is WLS / WLP. However, I have a scenario where I have a .Net Producer and the WLP acts as a WSRP portlet Consumer.
Then, I send the data to the .Net Producer and using the SOAP message monitor supplied by WLP I see the following.
(I.e. an extract that represents the two attributes that I have put in the request using the MarkupRequestState.)
<urn1:MarkupRequestState xmlns:urn1="urn:bea:wsrp:ext:v1:types">
<urn1:state>rO0ABXNyACpjb20uYmVhLndzcnAuZXh0LmhvbGRlcnMuU2ltcGxlU3RhdGVIb2xkZXKnP+aldExARAIAAUwABGRhdGF0ABNMamF2YS91dGlsL0hhc2hNYXA7eHBzcgARamF2YS51dGlsLkhhc2hNYXAFB9rBwxZg0QMAAkYACmxvYWRGYWN0b3JJAAl0aHJlc2hvbGR4cD9AAAAAAAAMdwgAAAAQAAAAAnQAHnNlLnNsbC5iYXRwb3J0YWwud3NycC51c2VybmFtZXQABGFwYW50ACNzZS5zbGwuYmF0cG9ydGFsLndzcnAuaGFuZGljYXBzdHlsZXQAA2JpZ3g=</urn1:state>
</urn1:MarkupRequestState>
As you all can see the data enclosed with the <urn1:state> tag is encoded.
I have tried to Base64 decode the string, but that does not give me a clean string whithout control characters so I suppose that the decoding must be done using a different algorithm.
The question are:
1)
What encoding is used?
2)
How does the .Net Producer decode the data enclosed with the <urn1:state> tag?
Thanks in advance!
Best regards/ Thomas Lindbom :-)

I have got it to work with Apache Soap. Much simpler to extract the reply body from the soap message too.
Bill

Similar Messages

Bug with Cyrillic-UTF-8 encoding in Outlook messages sent from iphone

Some time, during replay or forwarding mails, written in Cyrillic form iPhone3GS (iOS 4.0), iPhone send a format of the message UTF-8 and did not field the charset field.
In such case most of the windows client(Outlook, The BAT, Firefox) cannot recognize the message encoding automatically. Advanced clients have to use manual setting of the encoding.
In older iOS in iPhone2G i have't met such problem

try this
-----------------------------------------------message I send:
Return-Path: <[email protected]>
Received: from FS011 ([10.10.10.11])
(authenticated user [email protected])
by mail.xxx.ru
for [email protected];
Wed, 28 Jul 2010 12:54:53 +0400
Message-ID: <12ED165C69BD4E59B70551BC5AF7A0F4@FS011>
From: =?koi8-r?B?8MXexc7Lyc4g88XSx8XK?= <[email protected]>
To: <[email protected]>
Subject: TEST
Date: Wed, 28 Jul 2010 12:54:49 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=NextPart_000_043C01CB2E54.10472660"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
Sender: <support-owner@xxx>
List: <[email protected]>
List-Help: <mailto:[email protected]>
List-Post: <mailto:[email protected]>
List-Subscribe: <mailto:[email protected]>
List-Owner: <mailto:[email protected]>
List-Id: <support.xxx.ru>
List-Unsubscribe: <mailto:[email protected]>
Errors-to: <[email protected]>
X-BeenThere: <[email protected]>
Precedence: list
This is a multi-part message in MIME format.
------=NextPart_000_043C01CB2E54.10472660
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
=F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD
=F2=D5=CB=CF=D7=CF=C4=C9=D4=C5=CC=D8 IT =CF=D4=C4=C5=CC=C1
------=NextPart_000_043C01CB2E54.10472660
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dkoi8-r">
<META content=3D"MSHTML 6.00.6001.18183" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DL>
<DT>------------------------------------------</DT>
<DT>=F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD</DT>
<DT>=F2=D5=CB=CF=D7=CF=C4=C9=D4=C5=CC=D8 IT =
<SPAN=20
lang=3Dru-RU>=CF=D4=C4=C5=CC=C1</DT>
<DT>=EF=EF=EF «=E6=C9=D2=CD=C5=CE=CE=D9=CA =
=D3=C1=CC=CF=CE»</DT>
<DT>=F0=C5=DE=C5=CE=CB=C9=CE =F3=C5=D2=C7=C5=CA</DT>
<DD><FONT face=3DArial =
size=3D2>
</DD></DL></BODY></HTML>
------=NextPart_000_043C01CB2E54.10472660--
-------------------------------------------- message from iphone
Return-Path: <[email protected]>
X-Envelope-To: [email protected]
Received: from [192.168.0.82] ([10.10.10.10])
(authenticated user [email protected])
by mail.xxx.ru
for [email protected];
Wed, 28 Jul 2010 13:00:27 +0400
Message-Id: <[email protected]>
From: =?koi8-r?B?8MXexc7Lyc4g88XSx8XK?= <[email protected]>
To: =?koi8-r?B?8MXexc7Lyc4g88XSx8XK?= <[email protected]>
In-Reply-To: <12ED165C69BD4E59B70551BC5AF7A0F4@FS011>
Content-Type: multipart/alternative;
boundary=Apple-Mail-1--794833101
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7D11)
Mime-Version: 1.0 (iPhone Mail 7D11)
Subject: Re: TEST
Date: Wed, 28 Jul 2010 12:59:18 +0400
References: <12ED165C69BD4E59B70551BC5AF7A0F4@FS011>
--Apple-Mail-1--794833101
Content-Type: text/plain;
charset=windows-1251;
format=flowed;
delsp=yes
Content-Transfer-Encoding: quoted-printable
=CE=EA
=D1 =D3=E2=E0=E6=E5=ED=E8=E5=EC
=D1=E5=F0=E3=E5=E9
28.07.2010, =E2 12:54, =CF=E5=F7=E5=ED=EA=E8=ED =D1=E5=F0=E3=E5=E9 =
<[email protected]> =ED=E0=EF=E8=F1=E0=EB=20
(=E0):
=D1 =F3=E2=E0=E6=E5=ED=E8=E5=EC
=D0=F3=EA=EE=E2=EE=E4=E8=F2=E5=EB=FC IT =EE=F2=E4=E5=EB=E0
--Apple-Mail-1--794833101
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><body bgcolor=3D"#FFFFFF">=D0=9E=D0=BA
------------=
=D0=A1 =
=D0=A3=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC
=D0=A1=D0=
=B5=D1=80=D0=B3=D0=B5=D0=B9
28.07.2010, =D0=B2 =
12:54, =D0=9F=D0=B5=D1=87=D0=B5=D0=BD=D0=BA=D0=B8=D0=BD =D0=A1=D0=B5=D1=80=
=D0=B3=D0=B5=D0=B9 <<a =
href=3D"mailto:[email protected]">[email protected]> =
=D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
</di=
v>
<dl>
<dt>------------------------------------------</dt>
<dt>=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC</dt>
<dt>=D0=A0=D1=83=D0=BA=D0=BE=D0=B2=D0=BE=D0=B4=D0=B8=D1=82=D0=B5=D0=BB=D1=
=8C IT <span =
lang=3D"ru-RU">=D0=BE=D1=82=D0=B4=D0=B5=D0=BB=D0=B0</dt>
<dt>=D0=9E=D0=9E=D0=9E =C2=AB=D0=A4=D0=B8=D1=80=D0=BC=D0=B5=D0=BD=D0=BD=D1=
=8B=D0=B9 =D1=81=D0=B0=D0=BB=D0=BE=D0=BD=C2=BB</dt>
<dt>=D0=9F=D0=B5=D1=87=D0=B5=D0=BD=D0=BA=D0=B8=D0=BD =D0=A1=D0=B5=D1=80=D0=
=B3=D0=B5=D0=B9</dt>
<dd>
</dd></dl>
</body></html>=
--Apple-Mail-1--794833101--

Mixed encoding in soap message reply

I am trying to send a soap message to a service that uses UTF-16 encoding. I sent a UTF-8 encoded request. The reply was UTF-8 but the body was UTF-16.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAPSDK1:GetCountryStateAreaResponse xmlns:SOAPSDK1="http://tempuri.org/message/">
<Result xmlns:SOAPSDK2="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAPSDK3="http://www.w3.org/2001/XMLSchema" SOAPSDK2:type="SOAPSDK3:string"><?xml version="1.0" encoding="UTF-16" ?><atdw_data_results><country id="500001" code="AU" name="Australia" isd_code="61" states_allowed_flag="1" product_id="503928"><state id="500006" code="TAS" name="Tasmania"><area id="500361" code="NNE">North - North East</area><area id="500362" code="NW">North West</area><area id="500363" code="S">South</area></state></country></atdw_data_results></Result>
</SOAPSDK1:GetCountryStateAreaResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I used an xslt transform to indent the xml but it could only understand the UTF-8 soap envelope.
Should I encode the request in UTF-16 and how can this be done in SAAJ ?
Should I try Apache Soap instead ? It seems very difficult to extract the body of the message using SAAJ.
Thanks
Bill

I have got it to work with Apache Soap. Much simpler to extract the reply body from the soap message too.
Bill

Change encoding of input message sent by J2EE Adapter

Hi all,
I get a input message with a wrong encoding (Sender SMTP Adapter). Within XML prolog, there's a declaration of UTF-8. Having a look at the message, it's ISO-8859-1 encoded. That mean's I've to do one of the following options:
a) change encoding declaration in XML prolog to the correct one: ISO-8859-1
b) reencode the entire message from ISO-8859-1 into UTF-8, so that the message encoding matches the XML prolog
I've found two possible solutions, but I don't know if they're working:
1. usage of XMLAnomyzerModule: reading the documentation, it seems to be that I cannot use that module in a sender adapter, right? If I'm wrong: what does the module do? Does it just exchange the encoding declaration in the prolog or does it reencode the message?
2. running that small XSLT mapping before my own mapping: would it change the encoding declaration from UTF-8 to ISO-8859-1 in the XML prolog?
<xsl:stylesheet version="1.0"
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>
BR
Holger

Hi Stefan,
thanks for your reply. Unfortunately it's not my application who's sending the wrong message and it's not possible to change it on sender side. I don't know why but it's like that
So it's exactly like you've mentioned: when using special characters where ISO-8859-1 codepage differs from UTF-8, we've a problem.
When I understand you correct there's a adapter module TextCodepageConversionBean which changes the encoding, right? Then I could use it to encode the inbound ISO-8859-1 message to UTF-8 (which is declaration in XML prolog).
Where can I find more information how to use it? Searching SDN I've just found one other thread where the same module is mentioned, but without further hints.
BR
Holger

Wrong character encoding in error messages

The Java compiler can be adjusted to source file encoding with the option javac -encoding ...
The Java runtime can be adjusted to terminal encoding with java -Dfile.encoding=...
While this appears somehow inconsistent, it works and can be used e.g. when running the tools from Cygwin (the POSIX layer on Windows) which uses UTF-8 by default, while Java, following the Windows mechanism, uses some other character encoding by default (this works more seemlessly on Unix/Linux, by the way).
Now if I compile UTF-8 source with non-ASCII characters, and there is an error message related to them, the error message printed to the console will not be UTF-8 encoded, resulting in mangled text output.
(Arguably, source and terminal encoding could be different, but then there is no option available to the compiler to adjust this;
it does not accept -Dfile.encoding=....)
Example: Error message looks like this:
FM.java:1: error: class, interface, or enum expected
b▒h
While the string is actually "bäh" in the source.
This is a bug. Any proper place to actually report a bug?
Edited by: 994195 on 15-Mar-2013 09:42

I'll ignore you just blatantly assuming it is a bug because you say so, you did not think to type "java report bug" into Google?

Handling of base64 encoded body for message/rfc822

As I understand the mime spec allows only "7bit", "8bit", or "binary" for the body of a "message/rfc822" entity
However, it looks like Outlook is generating these under some circumstances (I have supplied a sample below). When attempting to read these via the JavaMail API the message content is empty and instead ends up in the header fields.
Is there a workaround or setting to handle these base64 RFC822 attachments in JavaMail?
Here's a stripped down sample of the message with the RFC822 attachment that I'm trying to handle:
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-Type: multipart/mixed; boundary=00235400e66249e8d9047d9b2ab3
--00235400e66249e8d9047d9b2ab3
Content-Type: multipart/alternative;
     boundary=00235400e66249e8cf047d9b2ab1
--00235400e66249e8cf047d9b2ab1
Content-Type: text/plain;
     charset=iso-8859-1
Content-Transfer-Encoding: 8bit
... [plain text version of message]
--00235400e66249e8cf047d9b2ab1
Content-Type: text/html;
     charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
... [html version of message]
--00235400e66249e8cf047d9b2ab1--
--00235400e66249e8d9047d9b2ab3
Content-Disposition: attachment
Content-Type: message/rfc822
Content-Transfer-Encoding: base64
UmVjZW...
--00235400e66249e8d9047d9b2ab3--

Thanks for the info and suggested workaround. Would be neat to have a configurable option in 1.4.4 since info on the web suggests there are other email systems generating this rubbish.
The customer who generated the emails is using Outlook 2007 with the Google Apps Sync for Outlook. I haven't been able to replicate in Outlook 2007 so might be related to the connector. I'll do some more testing before reporting the problem to the appropriate organization!

Bug with Cyrillic encoding in Outlook messages forwarded/sent from iphone/ipad

When forwarding mail that is written in Russian from iPhone or iPad using mail.app, the message turns to unreadable and the recipient needs to change the encoding manualy(if he/she knows how).
The only solution is to use a third-party app, such as ibis mail. Or if you prefer to use the mail.app by Apple,therefore, you need:
To add a symbol like "י" letter in hebrew to your signature (you can add a hebrew keyboard in iOS for this and uninstall it when you are done) and that's it.all your messages that you write or forward from iPad/iPhone will be decoded correctly on any mail client the recipient has.

If the user prefers something other than Hebrew, I think the same result can be had by adding a dingbat. These can easily be found in an app like Unicode Map. ✈✌✩❄➳

Bug with Cyrillic encoding in Outlook messages forwarded/sent from iPad

When forwarding mail that is written in Russian from iPhone or iPad using mail.app, the message turns to unreadable and the recipient needs to change the encoding manualy(if he/she knows how).
The only solution is to use a third-party app, such as ibis mail. Or if you prefer to use the mail.app by Apple,therefore, you need:
To add a symbol like "י" letter in hebrew to your signature (you can add a hebrew keyboard in iOS for this and uninstall it when you are done) and that's it.all your messages that you write or forward from iPad/iPhone will be decoded correctly on any mail client the recipient has.

If the user prefers something other than Hebrew, I think the same result can be had by adding a dingbat. These can easily be found in an app like Unicode Map. ✈✌✩❄➳

Allow users to choose encoding while composing message on JES webmail ?

Dear All,
#imsimta version
Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)
libimta.so 7.0-5.01 64bit (built 01:46:29, Feb 19 2009)
Is it possible to allow users to choose encoding type while composing message on JES webmail ? The default encoding type is "charset=utf-8". But some of our users want to make the encoding be restriced to big5. Any idea ?
Best Regards,
Steve

Hi Shane,
What do you mean by "JES webmail"? Is this Messenger Express, UWC/CE or Convergence?
==> UWC/CE
Why? What is wrong with UTF-8?
==> Most of our users are using traditional Chinese mail client(outlook/outlook express), and some of them have problems to read the UTF-8 encoding messages because these messgages have become a mess(uhreadable). So I hope there is a way to let users choose the encoding type.
Regards,
Steve

Premiere Pro CS5. Media Encoder .dll interace message.

Out of the blue, when I am working in Premiere Pro CS5 and want to export media, I get an error message about "this software could not find the required software interface .dll. Reinstall the software and try again..."
This just started several days ago. I have changed nothing. I did do as asked and reloaded the Adobe Premiere program and that worked for about a day. And now it is back. Also, my Premiere CS5 is starting to crash fairly often where as before it never did. I haven't changed anything on the computer. No new software added. No windows 7 updates of any kind.
Any ideas on what to do.

I experienced this at one point. Searching the WEB I saw suggestions that there was a problem with a recent version of Quicktime. (I have no idea why the quicktime player would have an impact.) However, reverting to an earlier version of Quicktime fixed the problem. Search this board using quicktime as a search phase. The quicktime web site allows you to download the earlier versions. I'm not at my editing machine, but I believe that I am at version 7.5.2.

Improper character encoding in SMS message to T-Mobile user

I've recently found that when I sent a text message to users on T-Mobile, the @ and $ are replaced by a ¿ (upside-down question mark). This occurs with all iphone messages as well as Treo users.
Can anyone tell me if this is a phone issue or a T-Mobile issue. I'm assume its a T-Mobile issue since the problem is only with them. Any idea how to get them to fix it. I'm stumped.
Fish

Didn't understand from what starting point you want me to "select the mail account name", but closed and re-opened T'bird.
Then I started to run your tests.
To my HUGE AMAZEMENT!!! - everything seems to be working today!!
This leaves me with a couple of old files that seem to have gotten trashed a long time ago and won't simply "revover" - but I did keep back-up copies of them elsewhere, and can now go about rebuilding them if necessary.
Thank you for your help - whatever it is that I did, seems to have worked. After how many years?! If I have trouble in the future, I'll be back - but for right now, what a RELIEF!
Best, Martha

Forcing utf8 encoding on viewing sent messages

Hi.
I have forced Mail.app to send all my messages as UTF-8 by using the well-known command:
defaults write com.apple.mail NSPreferredMailCharset "UTF-8"
That's working fine and my messages are received and viewed as UTF-8. But in Leopard, Mail exhibits the following weirdness: say I get a mail which used English (or any Latin-based script), I reply to it using Cyrillic -- everything looks fine when I write it, and the person I reply to receives it without problems as UTF-8. But when I view my own sent mail, the Cyrillic portion comes out as mumbo jumbo. When I go to Message>View Encoding, no encoding is selected, not even Automatic. When I select UTF-8 there, the message is displayed properly.
Now that's horrible, because it means that I have to fix every single sent message of mine if I want to view it properly. That can't be right.
Is there a way to force Mail.app to use UTF-8 as default encoding for viewing messages?
Thanks a lot.
Tench

The second one clearly says UTF-8 and that should normally make Mail show the text correctly. But the first one seems to indicate you are using some kind of special digital signature, and perhaps that is confusing the situation, causing Mail to apply Latin-1 or another default instead.
I only added the digital signature yesterday and the problem is not related to it -- I had the same behavior before the digital signature. Mail.app is for some reason not displaying these messages as UTF-8 by default.
I've narrowed it down a bit. If I get a UTF-8 encoded mail, and respond to it, there is absolutely no problem. But if I get a Central European charset=ISO-8859-2 mail and respond to it using Cyrillic, the mail is sent as UTF-8 (my forced default) but Mail.app gets confused when viewing my sent mail.
My workaround now is to ask my correspondent to send me UTF-8 (you can force UTF-8 in gmail for instance), I just tested it with a friend and it works.
I still find it strange that there is no way to force the viewing encoding the way one can force the outgoing mail encoding.
Thanks for your help.

Encode a message into the picture

Hi,
regarding the subject above, i know how to encode a static message (which mean predefined the message) into a picture..
But when it come to the dynamic message (user can enter message), i really no idea on how to encode it in the picture..
example for how i encode it for static msg :
predefined msg = "ON"
O = 79 = 01 00 11 11 c1, c2, c3, c4
N = 78 = 01 00 11 10 d1, d2, d3, d4
//0xFC = 1111 1100 <-- used this to remove the last 2 bits
int c1=1, c2=0, c3=3, c4=3;               //O
int d1=1, d2=0, d3=3, d4=2;               //N
int alpha, red, green, blue;
//unpack the individual pixel n process
alpha     = (pixels[1]>>24) & 0xFF;
red     = ((pixels[1]>>16) & 0xFC) + c1;
green     = ((pixels[1]>>8) & 0xFC) + c2;
blue     = (pixels[1] & 0xFC)     + c3;
//repack the pixels
pixels[1] = (alpha<<24) | (red<<16) | (green<<8) | blue;
//unpack the individual pixel n process
alpha     = (pixels[2]>>24) & 0xFF;
red     = ((pixels[2]>>16) & 0xFC) + c4;
green     = ((pixels[2]>>8) & 0xFC) + d1;
blue     = (pixels[2] & 0xFC)     + d2;
//repack the pixels
pixels[2] = (alpha<<24) | (red<<16) | (green<<8) | blue;
//unpack the individual pixel n process
alpha     = (pixels[3]>>24) & 0xFF;
red     = ((pixels[3]>>16) & 0xFC) + d3;
green     = ((pixels[3]>>8) & 0xFC) + d4;
blue     = (pixels[3] & 0xFC); // no use.... finish used all the bits
//repack the pixels
pixels[3] = (alpha<<24) | (red<<16) | (green<<8) | blue;
But when came to dynamic msg.. i really no idea on how to continue..
when i get everything ready.. (the msg length, each char value) in the for loop..
for(int j=0; j<length; j++){
msg[j] = message.charAt(j);
value[j] = (int) msg[j];
//this is to get the binary no.
c1= (value[j]>>6) & 0x03;
c2= (value[j]>>4) & 0x03;
c3= (value[j]>>2) & 0x03;
c4= value[j] & 0x03;
Encode(); //call a method to encode the msg into the picture
wanted to encode it in the picture..
but the requirement is encode only in the RGB and not alpha..
so when i get the value (O = 01 00 11 11)
c1 = 1 c2 =0 c3=3 c4=3
alpha     = (pixels[1]>>24) & 0xFF;
red     = ((pixels[1]>>16) & 0xFC) + c1;
green     = ((pixels[1]>>8) & 0xFC) + c2;
blue     = (pixels[1] & 0xFC)     + c3;
pixels[1] = (alpha<<24) | (red<<16) | (green<<8) | blue;
but the c4 is not encoded yet... so how ?? what should i do in this method ? because after processing this, it should go back to the for loop to continue the next char.
c1,c2,c3,c4 will be initialized with the new value again...
As you can see in the static example, c4 is used in the pixels[2]... then continue with the next char's 1st 4 bit (d1,d2)..
d3 & d4 is used in the pixels[3]...
err.. hope you can understand my question and give me some ideas on "encoding a message into the picture"
thanks and appreciate every single idea & help ;)

Take a look in the indesign-server-plugin-techniques.pdf in the section on MessageLog for more info.
Something interesting is that code that calls CAlert methods get converted into MessageLogs.
Your use of the word "console" makes me think that you are coding for Mac. If that's the case you could create some Mac code and use NSLog to dump to console.
Create a MyLog.mm file with something like:
#import <Foundation/Foundation.h>
void MyLogMessage(char *msg)
NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
NSLog(@"%s", msg);
[pool release];
Remember to add the Foundation framework to your project, and change the compile option from compile all files as C++ to compile according type.

I can no longer encode a sequence in PP CC after the Dec 2013 update

II have had to shut down and restart PP CC about 5 times when just creating a very simple sequence of clips from a family get together for Thanskgiving. I had to shut down since everything just quite responding. Fortunately, when I reopened the project, I could resume. I finally got my sequence created, but, now I can't export the sequence. The encode has failed 8 times in a row. I've tried direct export, and exporting to the AME queue. Sometimes I get the error sound and the absolutely useless error message "Error compiling movie. Unknown Error." Other times it just stops making any progress in the encode with no message at all, but there are zero CPU cycles being consumed by PP or AME. It just plain stops, wiht no eror message. That happened 3 times when used the Media Queue approach, and in the preview window in AME, it just stopped encoding at very different places in the sequence.
It appears as though I can no longer encode a movie. And I'm paying big bucks for this every month? What a sap.
I'm glad I'm not a Pro, whose income and life depends on these tools! But, I have a full time job, and only a very small amount of free time. I do not want to spend my small amount of free time as an Adobe Beta Tester. I've been using Adobe tools for years, which is why I signed up for CC, but...at this point: I can't even encode a simple sequence!
I can't express my disappointment. I wanted to be loading the encoded MP4 onto VIMEO for my friends and family to see by now, but.....I can't even encode a very simple sequence. And, I not a newbie. I have hundreds of videos on VIMEO, and many more on Youtube and Smugmug. Every one was produced with Adobe PP (from v4 on).
But now: I'm dead in the water.
I gurantee you that i will not 're-up' when my CC subscription expires, and, I guess right now, I have to start from scratch with my raw clips and find some other tools to use? I wish all my expensive plug-ins (like MB Suite) would work in whatever the tools I will move to...but...I guess I'll just have to write them off as a loss, just like the next 8 months of paying for my Adobe CC Software that no longer works.
I wish there was a way I could take the Thanksgiving Project and its sequences I've created in PP CC and convert the Project to PP 6.0, since I never had any issues with it PP v6.0.
But, from what I understand, if you make a project in PP CC, you are lost. You can't go backwards.
And, you know what? I'm done. I quit. I won't even try starting over in PP 6.0. I'm going to find some other tools. I know they won;t be as full-featured as Adobe's, but...I'm not a pro. I just need something that works reliably.
Disgusted beyond words.
John
Win 7 Pro
24 GB Ram
NVidia GTX 470
PS: So, does Adobe have any kind of disaster recovery plan when an update like this fails? Can you please send out a "new update" that rolls me back to the prior version on PP CC?

OK. I have successfully encoded this very simple sequence, but, I *can't* get it to encode using my "standard" custom H.264 preset that I have been using for years.
But, I was not able to encode in many plain vanilla codecs either, but, I got a notice that there was a CC update for AE, so I took the time to install those updates, and, as I always do, I re-booted after the update of AE.
But, of course I had re-booted a couple times last night when I couldn't get the sequence to encode. That's somethinf I always try b4 writing to a form.
So, here's the sequecne of events this morning:
1) Try to encode sequecne to uncompressed AVI (Cineform AVI 1920x1080). It SUCCEEDED. But, even though the AVI was large > 3.6 GB the quality was horrible, I did not pay much attention to the quality settings.
2) Try to encode to Quicktime H.264 codec. FAILED.
3) Try to encode to Quicktime Codec=Uncompressed 4:2:2. FAILED
4) CC UPdate notice for AE CC and AE 6.0
5) Perform update
6) Reboot
7) Try to encode to Quicktime Codec=Uncompressed 4:2:2. SUCCEEDED - but ENORMOUS FILE SIZE *very nice quality though* :-)
8) Try to encode to Quicktime Codec=H.264. SUCCEEDED.
9) Try to encode to my 'usual' H.264 Preset FAILED, just hung up during the 2nd of two passes. My preset is a VBR with 2 passes, see bitmap below. In this particular case it got 'hung' at this frame. But, It never 'hangs' in the same place?
So, I don't know why I was able to encode the sequence using the Quicktime Wrapper and botn Uncompressed and H2.264 Codecs after updating AE CC and rebooting, but not before. Surely there is no interaction between AE and AME?
But, the re-boot should not have caused it alone, since I had rebooted several times last night, and I've installed nothing but the new update for AE since last night?
So, I guess I'm OK now. Please excuse my tone last night, I was very frustrtated.
It is interesting that I still can't encode this particluar sequence using my "standard" H.264 preset.
And, BTW Jim: What I mentioned in my previus post was not that I had brought and old PP 6.0 sequecne into CC and encoded it successfully, but that I just re-encoded one of my most complex sequences AGAIN in PP 6.0, just to wanted to make sure nothing was haywire with "good old" PP 6.0.
But, I did just re-encode a sequence from PP CC from before the Dec 13 update using my "standard" H.264 preset, and...yes...it DID encode.
SOOOOO...Jim, you were correct. My inability to encode was not due to the DEC 13 PP CC update, but something very peculiar about this one sequence. But, it is a very simple sequence. The only effects applied is some light color grading using MB Colorista, and Warp Stabilizer to a stabilize a few hand held shots. No other effects. And...the encode that fails using my standard preset, never fails at the same frame.
But...at this point I'm OK. Instead of an encoded file in MP4 I have an ecnoded H.264 rendition in the QuickTime MOV wrapper. At least I've got that sequence done and can move on to the ton of others I need to get to (without having to learn an entirely new tool). :-)
John

Change Encoding in Graphical Mapping

Hello guys,
I have an interface like File-> PI 7.1 -> Proxy
The problem is that some characters are not correct at the proxy, and I have an error when the proxy is executed.
I have at the sender file adapter the encoding ISO-8859-1, but the problem is that in my Operation mapping, I java a Java code, where I put iso-8859-1, and after a message mapping. After the java mapping the encoding is iso-8859-1, but after the message mapping and when the message arrives at the proxy is UTF-8.
There is any way to change the encoding during the message mapping or in the Proxy adapter? There is also the possibility to change the encoding at the ABAP code of the proxy?
Many thanks in advance.
Regards,
Xavi.

H Xavi,
--Unfortunately no because the standard format in PI is utf-8-
Try this http://www.dataxstream.com/2009/06/pi-message-mapping-editor-hidden-menu/
Also we cannot use XMLAnonymizer bean here as the receiver adapter is XI adapter
Regards
Suraj

Encoding in WSRP message - MarkupRequestState

Similar Messages

Maybe you are looking for