[
http://issues.apache.org/jira/browse/HIVEMIND-183?page=comments#action_12434167
]
Vinicius Carvalho commented on HIVEMIND-183:
--------------------------------------------
Knut,
Yes, in order to solve my issue, I've replaced the default
LoggingInterceptorFactory declaring the dummy class on my hivemodule.xml:
<implementation service-id="hivemind.LoggingInterceptor">
<create-instance
class="*.*.*.*.OC4JHivemindLoggingInterceptor"/>
</implementation>
Hum, I haven't check that. But I'll this weekend, I'll try to gather more
specific information. I'm pretty sure its a classloader issue, Oracle's
classloader is very very problematic.
Best regards
> 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
