Jump to content

Search the Community

Showing results for tags 'pegaonline'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Music Forums
    • By The Decade
    • Soul/Blues/Funk/Jazz
    • Classical
    • Country/Folk
    • Electronica
    • Metal
    • Pop
    • Reggae / Ska
    • Rock
    • Soundtracks
    • Urban
    • World/Ethnik
  • Beatking News
    • Music & Entertainment News
    • Digital/Internet News
    • General News
    • Filesharing News
  • Jukebox
    • Music Questions
    • DJ / Musician's Corner
    • Music Downloads
    • Music Suggestions
    • Music Videos
  • Lounge
    • App Talk
    • Poet's Corner: Lyrics
    • Kickin' it
    • Beatking Recommends
    • Movie Talk
    • Tours, Festivals and DJ Sets
  • Site News
    • Announcements
    • Feedback

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Twitter


Facebook


Location


Interests


Favorite Music Type


Favorite Artist

Found 1 result

  1. We have a PEGA frontend, from where we are entering in twofold byte characters like Japanese and being send to disseminated java webservice through pivot. This is working fine when we send singlebyte characters. Just falling flat while utilizing twofold byte characters. The encoding utilized is UTF-8 in the xml which is being passed. Twofold byte characters are by and large appropriately rendered in PEGA front end. Indeed, even the PEGA logs indicates characters in place. Pivot adaptation: 2 PEGA gets the reaction while summoning webservice... Error:problem getting to the parser. Parser as of now got to! Did different mix testing and found the accompanying... single byte-working chinese - working japanese Hiragana - working katakana - working kanji - not working For kanji, PEGA isn't notwithstanding hitting the circulated code, it comes up short with parser blunder "issue getting to the parser. Parser as of now got to!
×
×
  • Create New...