[
http://mifosforge.jira.com/browse/MIFOS-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen updated MIFOS-4602:
-------------------------------
Priority: Critical (was: Minor)
Not sure what the final recommended architecture will be. Likely Jetty
everywhere. But until we are using Jetty across the board, we need to support
Tomcat too.
Bumped up priority since this is currently blocking Stanley.
> cannot deploy mifos.war in Tomcat 7.0.6
> ---------------------------------------
>
> Key: MIFOS-4602
> URL: http://mifosforge.jira.com/browse/MIFOS-4602
> Project: mifos
> Issue Type: Dev Task
> Environment: 64-bit Ubuntu 10.04.1 LTS. Oracle Java 1.6.0_20
> (32-bit). Tomcat 7.0.6 stable.
> Reporter: Adam Monsen
> Assignee: Michael Vorburger
> Priority: Critical
>
> Error seen:
> {noformat}
> SEVERE: The display name was defined in multiple fragments with different
> values
> including fragment with name [Mifos Application Core] located at
> [jar:jndi:/localhost/mifos/WEB-INF/lib/mifos-webapp-1.8-SNAPSHOT.jar!/]
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
