As I already told you: 1. put the shared jars into the folder <your SMX install folder>/lib/optional 2. modify your SU's pom.xml to have a dependency entry for the shared libs 3. do NOT deploy the shared lib jar file into hotdeploy folder if you want to do it like me
Hope this helps. Lars Am Freitag 15 August 2008 15:24:26 schrieb Anderson Nielson: > It did not work. :-( > > The stack trace: > > java.lang.ClassNotFoundException: com.ddtek.jdbc.openedge.OpenEdgeDriver in > clas > sloader com.ddtek.jdbc.openedge.OpenEdgeDriver > at > org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiPa > rentClassLoader.java:206) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:169) > at com.hengst.artikel.dao.ArtikelDao.insertPS(ArtikelDao.java:38) > at com.hengst.artikel.ArtikelImpl.insert(ArtikelImpl.java:25) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > > I have just put three jars (base.jar, openedge.jar,util.jar) and deployed > it as a SL. When in a standalone Java App the JDBC connection works fine. > BUt when using it in a CXF service engine it does not. > > lhe77 wrote: > > This is in the pom.xml's dependency sections of the SU which uses the > > shared > > lib. > > > > For example: > > <dependency> > > <groupId>my.group.id</groupId> > > <artifactId>my-shared-lib</artifactId> > > <version>1.0</version> > > <scope>provided</scope> > > </dependency> > > > > Regards > > Lars > > > > Am Freitag 15 August 2008 14:35:53 schrieb Anderson Nielson: > >> Lars, > >> > >> Where did you puts this <scope>provided</scope> tag? > >> Which file? > >> > >> Thank you > >> > >> lhe77 wrote: > >> > I decided to simply put the shared lib jar file into folder > >> > "<SMX>/lib/optional" and each SU which needs the lib just > >> > has the dependency defined with <scope>provided</scope>. > >> > This will prevent each SU which uses this shared lib to ship with > >> > the shared lib which will save you a lot of space depending on > >> > your use case. > >> > > >> > Until now I can't see any backdraws doing so. > >> > > >> > Regards > >> > Lars > >> > > >> > Am Freitag 15 August 2008 13:49:03 schrieb Anderson Nielson: > >> >> I am facing the same problem. A good question: when and how to use a > >> >> shared > >> >> library or not? > >> >> > >> >> Best Regards > >> >> > >> >> pratibhaG wrote: > >> >> > I have created a jar using maven and added a dependency as you > >> >> > said. > >> >> > >> >> Now > >> >> > >> >> > everything works fine. > >> >> > If I use this as an alternative to shared library what harm do you > >> > >> see > >> > >> >> in > >> >> > >> >> > it? Can I use it? > >> >> > > >> >> > What am I missing while using shred library? > >> >> > > >> >> > Pratibha
