Chad,
Exactly - that willwork but is “polluting” the lib directory. We put the absolute minimum amount we can in there. It is, essentially, only those things that are required to start the application. Everything else goes in NAR’s. You can get the appropriate ClassLoader from your code by calling Thread.currentThread().contextClassLoader(). Then, you can use that ClassLoader to load the class: Class.forName( “my.class”, true, Thread.currentThread().contextClassLoader() ); Thanks -Mark From: Chad Zobrisky Sent: Tuesday, February 24, 2015 12:17 PM To: [email protected] Toivo In regards to the driver jar, I'm not sure if it is okay to place a jar in the lib directory, but it does work if you place, for example, ojbdc.jar in that directory and load it via the Class.from() method. I'm not sure if the community wants to use that directory this way though, if it would be seen as polluting or not. -Chad On Tue, Feb 24, 2015 at 11:59 AM, Mark Payne <[email protected]> wrote: > Toivo, > > > Yes, exactly. You will also want to update the standard-services-api-nar > to pull in your nifi-dbcp-service-api. > > > Thanks > > -Mark > > > > > > > From: [email protected] > Sent: Tuesday, February 24, 2015 11:57 AM > To: [email protected] > > > > > > I created nifi-dbcp-service-api under nifi-standard-services. > nifi-dbcp-service-api contain service interface only. > > So current structure is: > > + nifi-standard-services > + nifi-dbcp-service-api > > next I must create nifi-dbcp-service-bundle > > So final structure will be : > > + nifi-standard-services > + nifi-dbcp-service-api > + nifi-dbcp-service-bundle > + nifi-dbcp-service-nar > + nifi-dbcp-service > > Is this correct? > > toivo > > > > > -- > View this message in context: > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/New-Database-Connection-Pooling-Controller-Service-tp582p838.html > Sent from the Apache NiFi (incubating) Developer List mailing list archive > at Nabble.com. >
