[ http://issues.apache.org/jira/browse/HIVEMIND-183?page=comments#action_12434073 ] Knut Wannheden commented on HIVEMIND-183: -----------------------------------------
Vinicius, How does this no-op service interceptor factory class solve the problem? Do you declare it in a hivemodule.xml and apply it instead of the LoggingInterceptorFactory (I think that's the one you had problems with)? Would be nice if we could nail this one down. Did you check whether you have two commons-logging jars deployed or whether the same commons-logging jar is loaded by multiple class loaders? I think that could be the source of your problem. > Problems with LoggingInterceptor and OC4J 10.1.3 > ------------------------------------------------ > > Key: HIVEMIND-183 > URL: http://issues.apache.org/jira/browse/HIVEMIND-183 > Project: HiveMind > Issue Type: Bug > Components: framework > Affects Versions: 1.1.1 > Environment: Oracle OC4J 10.1.3 (both standalone and AS versions) > Reporter: Vinicius Carvalho > > Seems to be a bug with OC4J and Hivemind. When creating the interceptor, it > seems to have a conflict between versions of the commons-logging. I'm sorry I > can't provide more information. I've solved this issue after a big help from > Jesse Kuhnert. To solve it, I've provide an empty class: > public class OC4JHivemindLoggingInterceptor implements > ServiceInterceptorFactory { > public void createInterceptor(InterceptorStack stack, Module module, > List list) { > } > } > I just post it as a major priority, since it affects every possible user of > tapestry that has OC4J as an app server. > Regards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
