dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

OK.

The thing is that you cannot select a module as start module if it is not in
the portal. I guess the problem arises when you build a war with a certain
module, set that module as start module, build a new war without that module
and try to open. This can be annoying as you cannot then access the system.


I have added a method "moduleExists( String name )" to ModuleManager in
dhis-web-commons ... portal. I suggest we use this method to verify that the
module is included in the war.

On Wed, Aug 25, 2010 at 5:40 AM, Thanh Tri Tran
<tranthanhtri84@xxxxxxxxx>wrote:

> Public bug reported:
>
> In system setting we have configuration to set start module for DHIS2.0.
> But if start module was not exist , system will throw exception. Now we
> can redirect to dhis-web-portal module.
>
> ** Affects: dhis2
>     Importance: Undecided
>         Status: New
>
> --
> Exception if start module was not exist.
> https://bugs.launchpad.net/bugs/623738
> You received this bug notification because you are a member of DHIS 2
> coordinators, which is the registrant for DHIS.
>
> Status in DHIS 2 - District Health Information Software: New
>
> Bug description:
> In system setting we have configuration to set start module for DHIS2.0.
> But if start module was not exist , system will throw exception. Now we can
> redirect to dhis-web-portal module.
>
>
>

-- 
Exception if start module was not exist. 
https://bugs.launchpad.net/bugs/623738
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in DHIS 2 - District Health Information Software: New

Bug description:
In system setting we have configuration to set start module for DHIS2.0. But if start module was not exist , system will throw exception. Now we can redirect to dhis-web-portal module.