[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
SV: [equinox-dev] Double loading of resource?

Pascal,
Im somewhat sharing your opinion. When I explicitely set the Classloader for Tapstry to only take the current bundles classpath, and move over the hivemodule.xml, it only appears once and everything goes better. However, when imported classes and their classloaders are scanned, there are resources listed twice, and it seems with different location URLs. No idea why that is, I think the questino persists. Will try to get a better classloading definition in place and see if that can resolve the symptom.
 
/peter

________________________________

Från: Pascal Rapicault [mailto:Pascal_Rapicault@xxxxxxxxxx]
Skickat: to 2006-05-18 19:30
Till: Equinox development mailing list
Kopia: Equinox development mailing list; equinox-dev-bounces@xxxxxxxxxxx
Ämne: RE: [equinox-dev] Double loading of resource?



Simon what you are mentionning about ContextFinder would possible if the
jars were on the app classpath to start with (note that there is a flag to
avoid this now), however the URL for the resource would not be of type
bundleentry://
What looks weird to me is the 1:6 segment in the URL and more precisly the
:6 since this refer to a port. It still looks to me like if the jars
appear twice on the classpath.




"Kaegi, Simon" <Simon.Kaegi@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
05/18/2006 01:17 PM
Please respond to
Equinox development mailing list


To
"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
cc

Subject
RE: [equinox-dev] Double loading of resource?






Hi Peter,

Looks pretty tough...
I think the easiest way to figure out what's going on is to *GULP* walk
the "getResource(...)" in the DefaultClassResolver.

I wonder if it's possible that the ContextFinder would report a different
URL for the same resource based on whether it's looking locally or through
the BundleClassLoader??

-Simon


From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter Neubauer
Sent: Thursday, May 18, 2006 1:02 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Double loading of resource?

Thomas,
I'm running this as a normal OSGi debug launch config with just -console
enabled. Will try out if there is a difference setting the -dev option.

/peter
On May 18, 2006, at 5:41 PM, Thomas Watson wrote:


Are you Self-hosting Equinox or running in dev mode (using -dev or setting
the osgi.dev property)?  I have seen a similar issue when self-hosting or
in dev mode because of the extra classpath entries the framework adds when
in dev mode.

Tom



Peter Neubauer <peter@xxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
05/18/2006 05:52 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>



To
equinox-dev@xxxxxxxxxxx
cc

Subject
[equinox-dev] Double loading of resource?








Hi,
I'm having a strange problem getting tapestry to run in the
Jetty-PDE-RSP-UI scenario.

The tapestry libs are located in a special lib bundle, only .jar files,
and a manifest that looks like

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Tapestry Plug-in
Bundle-SymbolicName: org.apache.tapestry;singleton:=true
Bundle-Version: 4.0.0
Bundle-ClassPath: commons-codec-1.3.jar,
commons-fileupload-1.0.jar,
commons-logging-1.0.4.jar,
hivemind-1.1.1.jar,
hivemind-lib-1.1.1.jar,
javassist-3.0.jar,
log4j-1.2.8.jar,
ognl-2.6.7.jar,
oro-2.0.8.jar,
tapestry-4.0.1.jar,
tapestry-annotations-4.0.1.jar,
tapestry-contrib-4.0.1.jar,
tapestry-portlet-4.0.1.jar
Bundle-Localization: plugin
Export-Package: javassist,
javassist.bytecode,..........

Now, when the tapestry classloader scans the classpath, apparently there
is a double resource discovered from 2 different URLs, the hivemodule.xml
from the hivemind.jar:
........
DEBUG - Processing modules visible to
org.apache.hivemind.impl.DefaultClassResolver@9e4585
DEBUG - Parsing bundleresource://1/META-INF/hivemodule.xml
DEBUG - Result: ModuleDescriptor[moduleId=hivemind version=1.1.0]


<<attachment: winmail.dat>>