I don't think there should be any services in common, only utility type classes. The server module seems like the approriate place for core utility services that are not needed by the bootstrap server footprint.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Dain Sundstrom" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 10, 2003 6:32 PM Subject: Re: [JBoss-dev] Move MarshalledValue* to common module? > I have another issue now... should have checked before sending this > email. > > I have a written new basic service ObjectCopier, which is an MBean that > knows how to *efficiently* deep copy objects. This means that I track > metadata so we can avoid serialize/ deserialize. Anyway, I wanted add > this to the common module, because it is a generic service that will be > used by several modules (CMP and Cache for now). The problem is common > does not build after system, so I can't use ServiceMBeanSupport. > Should we add a new module for common services or move the > ServiceMBeanSupport stuff to common or something else or should I put > my code server? > > -dain ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
