Hi all,
we are testing our mid-tier functionality and specifically "Deploy Manually"
fail when try to deploy an application that use a form with name that have
special characters "NB-BR:Dialog Confirma Creacion"( with accent like o in
this case) , basically Mid-Tier transform form name to "NB-BR:Dialog
Confirma Creaci?n"

Nevertheless, our Mid-Tier configuration file had configured enUS locale,
and our locale utility show that "enUS" exist in our current locale
environment, BUT Mid-Tier Log Show that couldn?t find enUS in the
configDictionary...

Does anybody have some idea about this problem???

thanks in advance,
Victor

1) Mid-Tier Config properties: arsys/WEB-INF/classes/config.properties
arsystem.configlocale=enUS

2) Locale environment: locale -a
POSIX
common
enUS.UTF-8
C
iso88591
iso885915
enCA
enCA.ISO8859-1
enUS
enUS.ISO8859-1
enUS.ISO8859-15
enUS.ISO8859-15@euro
frCA
frCA.ISO8859-1
th
thTH
thTH.TIS620


3) midtier.log
<2003-10-16 11:10:23,138>


<2003-10-16 11:10:23,142>


....
<2003-10-16 11:11:40,938>

NB-BR:Dialog Confirma Creaci?n>
<2003-10-16 11:11:40,942>


<2003-10-16 11:11:40,945>


<2003-10-16 11:11:40,948>


<2003-10-16 11:11:40,952>
3391:952)> Confirma Creaci?n from server>
<2003-10-16 11:11:40,967>
3391:965)> NB-BR:Dialog Confirma Creaci?n from server>

MessageType: 2
MessageNum: 303
MessageText: Form does not exist on server
AppendedText: NB-BR:Dialog Confirma Creaci?n
at com.remedy.arsys.api.Proxy.ARGetSchema(Native Method)
at
com.remedy.arsys.api.SchemaFactory.findByKey(SchemaFactory.java:80)
at
com.remedy.arsys.cache.definition.SchemaCache.getSchemaObjFromServer(DashOB3
391:959)
at
com.remedy.arsys.cache.definition.SchemaCache.CreateSchemaDefinitions(DashOB
3391:445)