You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by David Bergman <Da...@remoteproximity.com> on 2005/08/11 15:54:50 UTC

[tapestry] Strict error handling when contructing HiveMind registry

Hi,

I posted a thought in the HiveMind developer list about the handling of
duplicate modules in the registry building. The problem is that some J2EE
configurations, such as JBoss with the shared class loader, will find many
hivemind jars, and thus many "hivemind" modules, when multiple
HiveMind-empowered (read "Tapestry-empowered") applications are deployed.

I am fully acquainted with the Devil of Multiple Class Instances in such a
scenario, but wonder whether we could create a less strict error handler
than the HiveMind StrictErrorHandler in
ApplicationServler.constructErrorHandler? Issuing a warning is nicer than
throwing a runtime exception.

That would allow for multiple Tapestry applications in a rather common J2EE
setting, where it today does not work.

Thanks,

David


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org