To clarify, I only have the one component module (the WebsiteTagsModule) and it is only in that .jar that I specify the Tapestry-Module-Classes property in the MANIFEST.MF.
Cheers for thinking about this, Steve. On 05/12/2007, Chris Lewis <[EMAIL PROTECTED]> wrote: > Nice catch :-). Does TIoC 'know' which modules it has loaded? If so > perhaps an exception should be thrown, or at least a log message made, > if an app attempts to (indirectly) load a module more than once. > > Thiago HP wrote: > > On 12/5/07, Steve Eynon <[EMAIL PROTECTED]> wrote: > > > >> java.lang.RuntimeException: > >> Service id 'AssetFinder' has already been defined by > >> com.alienfactory.websitetags.WebsiteTagsModule.buildAssetFinder > >> (AssetSource) > >> (at WebsiteTagsModule.java:28) > >> and may not be redefined by > >> com.alienfactory.websitetags.WebsiteTagsModule.buildAssetFinder > >> (AssetSource) > >> (at WebsiteTagsModule.java:28). > >> > > > > It surely looks like your WebsiteTagsModule is being loaded at least twice. > > Each of your jars has a Tapestry-Module-Classes including WebsiteTagsModule? > > If so, Tapestry-IoC will load it once for each jar in the classpath. ;-) > > Howard, maybe this could be checked and a warning raised by Tapestry-IoC. > > What do you think about it? JIRA? > > Thiago > > > > > > -- Steve Eynon 0780 390 5424 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
