Here I sent you our config:
1. application_xml_initilaize_in_order: we faced the iisue that codi wont
start properly when the wars are not initialized in order.
2. application_xml_war_order: we ha to initiliaze the new war first
because it uses codi, jsf, cdi and so on.
3.
Hi all,
We are tying to migrate from Mojarra 2.0.2 to MyFaces 2.1.10 and made a strange
observation regarding entities.
Any entities are accepted by the parser but only valid XML entities are
rendered into the output. E.g. 'gt;' or '#160;' are rendered into the output
as expected, but 'nbsp;'
Danke schoen Thomas, you answered my question.
The key thing here for you is using deployment_xml_classloader_policy: single classloader ( WAR classloader policy
=application) which is not supported by IBM.
This is what we were using, this was the only way we found to have our apps working
Take a look at this post. I googled a bit and it seems that all of the issues
got resolved by application classloader.
Maybe this helps you a little bit.
http://grokbase.com/p/myfaces/users/12cchrh53c/codi-codi-v1-0-5-websphere-v8-5-0-1-problem
Just for test. Try to put codi dependencies in each webapp lib and not in
ear lib.
El 18/01/2013 02:07, Thomas Herzog t.her...@curecomp.com escribió:
Here I sent you our config:
** **
**1. **application_xml_initilaize_in_order: we faced the iisue that
codi wont start properly
5 matches
Mail list logo