Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Srinivas T <tsrinivas7@gm...> - 2009-06-19 14:41:28
We have couple of staf services written in Java and are using a lot of
Error codes/messages and some constants, There are many error
codes/messages and constants which are common across various services.
We have them in a single class and using in all services, but this
makes them all loaded by all the services(though they're not
required/used by a service), hence duplicating the error messages for
all services. On the other hand if we have separate error
messages/constants defined for individual services, we may end of
re-writing constants across services, which I think is not a very
efficient way, when we have some common and some un-common error
codes/messages being registered.
Is there a better way to manage them ??, off late we also have
services with bigger size and some memory leaks too, though we're
working on fixing them all. I thought of trying out these by
registering as STAF variables and resolving based on need in service
codes, does this sound a better idea..??
Any comments/suggestions are welcome.