assumptions about the classloader make it difficult to use linkedin-j in an OSGi environment

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use linkedin-j in an OSGI environment

I get an exception: "javax.xml.bind.JAXBException: 
com.google.code.linkedinapi.schema doesnt contain ObjectFactory.class or 
jaxb.index", even though the class is there...

The problem and my solution are outlined in detail here:
http://thudev.blogspot.co.at/2012/07/wrapping-linkedin-j-as-osgi-bundle.html

I suggest making the modifications in your codebase, as outlined in my 
blog-entry above.

Additionally, it should be considered to make the linkedin-j JAR OSGi compliant 
by using the attached manifest file.

All the best,
Martin

Original issue reported on code.google.com by martin.t...@gmail.com on 24 Jul 2012 at 12:56

Attachments:

• MANIFEST.MF

[GoogleCodeExporter]

I encountered the same issue. Attached is a patch for enabling linkedin-j in 
OSGi environment. Please review and add to the project.

Original comment by m.satyad...@gmail.com on 27 Jul 2013 at 5:19

Attachments:

• linkedin-j-osgi.patch

[GoogleCodeExporter]

Can you please explain how this patch is applied. Not able to move forward with 
this

Original comment by lalitkum...@gmail.com on 29 Jul 2013 at 11:12

[GoogleCodeExporter]

>>Can you please explain how this patch is applied. Not able to move forward 
with thi
Its a patch created using svn. So you can use any tool which applies an svn 
patch. I use eclipse. Just sync the linkedin-j source, apply the patch and 
rebuild it. It should now be deployable in an OSGi container.

Original comment by m.satyad...@gmail.com on 31 Jul 2013 at 1:41