Eclipse Community Forums: Virgo » ClassNotFoundException inside PAR

Help

Home

Home » Eclipse Projects » Virgo » ClassNotFoundException inside PAR

Show: Today's Messages :: Show Polls :: Message Navigator

ClassNotFoundException inside PAR [message #588074]

Tue, 13 July 2010 16:30

No real name

Messages: 15
Registered: June 2010

Junior Member

We are trying to use Dozer in an OSGi application and are experiencing class path visibility issues. The objects are exported in one of our manifests; however, Dozer bundle does not import the object types being mapped (via it's manifest). According to some other threads on the Spring dm Server forum this should be addressed by using a PAR. We checked and the types are imported through the PAR's synthetic context; however, we still get a runtime exception:

org.dozer.MappingException: java.lang.ClassNotFoundException: ca.company.object.

What is the suggested way to address this?

Thanks in advance.

- Paul

Report message to a moderator

Re: ClassNotFoundException inside PAR [message #588088 is a reply to message #588074]

Tue, 13 July 2010 16:53

Dmitry Sklyut

Messages: 279
Registered: January 2010

Senior Member

You might need to import dozer classes in your bundle similar to hibernate set-up

http://www.eclipse.org/virgo/documentation/virgo-documentati on-2.1.0.M02-incubation/docs/virgo-programmer-guide/html/ch0 8.html#common-libraries-hibernate

i.e. import-scope:=application should do the trick for you.

Report message to a moderator

FIXED - Re: ClassNotFoundException inside PAR [message #590414 is a reply to message #588074]

Tue, 13 July 2010 20:15

No real name

Messages: 15
Registered: June 2010

Junior Member

K, I resolved my issue.

While debugging the issue I noticed that the BundleClassLoader that was being used to instantiate the object type inside the dozer bundle had visibility of only the webapp imported components even though it was located inside a PAR where the synthetic context should have caused all included bundle's exports to be imported. Further, the webapp was calling a service (inside a service bundle) that was using dozer and hence this should have been abstracted from the webapp. I'm not sure why this is the case, but adding the dozer (application scope) imports explicitly to the webapp manifest satisfied the classloader.

For reference, this is what I added to both the service and webapp bundle to resolve my issue:
org.dozer;import-scope:=application,
org.dozer.util;import-scope:=application,
ca.company.types;import-scope:=application

Thanks,
- Paul

Report message to a moderator

Re: FIXED - Re: ClassNotFoundException inside PAR [message #590434 is a reply to message #590414]

Wed, 14 July 2010 08:32

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

I would be surprised if there was a bug in the synthetic context bundle. If you are interested, please examine the wiring in the failing case and see if the synthetic context bundle really is in error and raise a bug with details if so.

However glad to see you are in business now!

Report message to a moderator

Previous Topic:	ClassNotFoundException inside PAR
Next Topic:	Virgo tooling for Eclipse

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 10:44:53 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter