Hi Surya, I think I had a similar problem some weeks before (regarding your error message and not more information ...) and I had to add some packages to etc/jre.properties:
I think I added some of the packages listed below, but for your problem I guess others are needed. It could be that you need to add some "com.sun.*" packages to jre.properties that are used by the TibjmsInitialContextFactory... com.sun.org.apache.xerces.internal.dom, \ com.sun.org.apache.xerces.internal.jaxp, \ com.sun.jndi.ldap, \ com.sun.org.apache.xalan.internal.res, \ com.sun.org.apache.xml.internal.utils, \ com.sun.org.apache.xpath.internal, \ com.sun.org.apache.xpath.internal.jaxp, \ com.sun.org.apache.xpath.internal.objects Regards, Andi 2011/12/1 surya aditya <[email protected]> > Hi: > > Tried the following: > > 1. MyApp bundle does import the "com.tibco.tibjms.naming" package. I still > get 'ClassNotFound' exception, double checked if the tibco ems libraray jar > has the file in questions and it does. Fyi Tibco Ems jar is copied into > /deploy folder. Tibco Ems bundle is active, on doing 'headers' i see > everything is ok. no red lines. verified using 'imports' as well. > > 2. 'headers' on MyApp bundle is clean as well. This bundle has created > manifest.mf and looks ok on manual inspection as well. > > Problem still persists "Cannot instantiate class: > com.tibco.tibjms.naming.TibjmsInitialContextFactory > [Root exception is java.lang.ClassNotFoundException: > com.tibco.tibjms.naming.TibjmsInitialContextFactory]" > > Any other pointers to look into will be helpful? this looks straight > forward use case where i am trying to connect to EMS server, sure I guess > this is doable in Karaf, just need to get things in right place I hope. > > Appreciate any further help. > > regards, > Surya > > > > > > On Thu, Dec 1, 2011 at 3:53 PM, mikevan <[email protected]> wrote: > >> >> >> Andreas, >> >> >> >> It looks like it should from reading his Import-Package statement. >> However, if the maven-bundle-plugin isn't working, it wouldn't be creating >> the MANIFEST.MF file properly. Perhaps he should look at the .jar file >> created to verify that the MANIFEST.MF is actually being created. >> Alternatively, the headers command should show what the bundle thinks it >> should be looking for. Additionally, the imports command could be used to >> verify this also. >> >> >> >> ----- Original Message ----- >> >> >> From: "Andreas Pieber [via Karaf]" < >> [email protected]> >> To: "mikevan" <[email protected]> >> Sent: Thursday, December 1, 2011 3:49:41 PM >> Subject: Re: karaf and tibco ems >> >> >> >> Sorry for the standard question, but does the bundle containing the code >> you've posted in your first mail imports com.tibco.tibjms.naming? >> >> Kind regards Andreas >> On Dec 1, 2011 9:31 PM, "surya aditya" < [hidden email] > wrote: >> >> >> I verified the class exists in jar. on executing the 'exports'. I get >> the following: >> >> >> karaf@root> exports | grep com.tibco.tibjms >> 45 com.tibco.tibjms; version=0.0.0 >> 45 com.tibco.tibjms.naming; version=0.0.0 >> 45 com.tibco.tibjms.naming. tibjmsnaming; version=0.0.0 >> >> >> >> >> i see version=0.0.0, but MyApp does not specify any version on imports! >> should that be the issue here? thanks for helping again. >> >> >> from bundles:headers on my application jar: >> Import-Package = >> com.google.inject;version="[1. 3,2)", >> com.google.inject.binder; version="[1.3,2)", >> com.google.inject.name ; version="[1.3,2)", >> com.tibco.tibjms, >> com.tibco.tibjms.naming, >> com.tibco.tibjms.naming. tibjmsnaming, >> javax.jms,........................ >> >> >> regards, >> Surya >> >> >> >> >> >> On Thu, Dec 1, 2011 at 3:25 PM, mikevan < [hidden email] > wrote: >> >> <blockquote> >> >> >> First, try to manually verify that the tibco jar file you're using >> actually contains the correct class: com.tibco.tibjms.naming. >> TibjmsInitialContextFactory . Once you've done that, if the class is >> present, verify that the package has been properly exported into your >> environment by executing: >> >> karaf@root> exports | grep com.tibco.tibjms.naming >> >> >> >> Please let me know what happens. >> >> >> >> ----- Original Message ----- >> >> >> >>
