logged and tracked here [1]
Cheers,
Bo
[1] https://issues.apache.org/jira/browse/CXF-857
Dan Diephouse wrote:
Hi jeff,
Could you file a JIRA issue for this? I think we (the CXF devs) need to do
some debugging within GlassFish.
http://issuses.apache.org/jira/browse/CXF
Thanks,
- Dan
On 7/25/07, Jeffrey Metcalf <[EMAIL PROTECTED]> wrote:
Hi All,
I have an update on this issue. Apparently the problem is that glassfish
(sun appserv 9.0) requires that all resource-refs be found on the Thread
context classloader. which is a parent to the web application classloader
for the deployed CXF service. I believe that this translates to an
application server classloader. From the CXF and Spring framework
perspective, this would be a glassfish problem/limitation. If I append
all
the CXF modules and dependencies to the application server classpath, all
problems go away and my service deploys and operates without a hitch. To
me
this is wrong and violates best practice. I don't want the CXF modules
and
dependencies (like spring framework) on the application server classpath.
Has anyone run into this problem on glassfish or other appservers and have
a
workaround consistent with J2EE application server best practices?
Best regards,
-Jeff
