[
http://jira.codehaus.org/browse/XFIRE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Sztelak closed XFIRE-601.
--------------------------------
Assignee: Tomasz Sztelak (was: Dan Diephouse)
Resolution: Won't Fix
You should report this to oc4j support. For a now marking as no fix
> Aegis mapping files are not found in OC4J Weblayer
> --------------------------------------------------
>
> Key: XFIRE-601
> URL: http://jira.codehaus.org/browse/XFIRE-601
> Project: XFire
> Issue Type: Bug
> Components: Aegis Module
> Affects Versions: 1.1.1
> Environment: oc4j10.1.3; jdk1.4.2_10
> Reporter: Olaf Boede
> Assignee: Tomasz Sztelak
>
> Aegis mapping files (which work fine with jetty and tomcat) are ignored when
> my webservice implementation is deployed in the servlet container of oc4j.
> I suspect that the web classloader structure of oc4j causes the problem.
> The classloader that is related to the loaded classes is not able find
> resourcefiles. In the oc4j weblayer we always have to use the context
> classloader of the current thread to access resource files.
> In code:
> myObject.getClass().getClassLoader().getResource("myresfile.xml");
> returns always null.
> But the code:
>
> Thread.currentThread().getContextClassLoader().getResource("myresfile.xml");
> returns a stream to the resource file when it can be found in the classpath.
> Possibly that effect may have a relation to the not found aegis mapping files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
