The way Apache DS has implemented this is pretty ugly. Why the solution of copying to CARBON_HOME/lib will not work in all cases is because, many of our customers deploy Carbon as a webapp on different appservers. So, in that case, you will have to copy the jar into the appserver specific lib directory (which you cannot do through feature installation). Perhaps we should try to get this fixed in ApacheDS.
Azeez On Mon, Aug 9, 2010 at 3:38 PM, Amila Jayasekara <[email protected]> wrote: > ApacheDS version 1.5.7 finds default ".ldif" files by searching through its > own classpath. The default ".ldif" files are archived into a jar file called > "shared-ldap-schema-0.9.18.jar". Anyhow i didnt find a proper documentation > which states this, but after doing some debugging i found following piece of > code in apacheds source > (org.apache.directory.shared.ldap.schema.ldif.extractor.impl.ResourceMap.java), > > HashMap<String,Boolean> retval = new HashMap<String,Boolean>(); > String classPath = System.getProperty( "java.class.path", "." ); > String[] classPathElements = classPath.split( File.pathSeparator ); > > for ( String element : classPathElements ) > { > getResources( retval, element, pattern ); > } > > Thus mail thread in [1] also confirmed above conclusion. > > [1] http://www.mail-archive.com/[email protected]/msg03205.html > > Placing "shared-ldap-schema-0.9.18.jar" in > ${carbon.home}/repository/components/plugin will not be helpful as it is not > visible to classpath. But if i place "shared-ldap-schema-0.9.18.jar" in > ${carbon.home}/lib, the library "shared-ldap-schema-0.9.18.jar" is visible > to the classpath. > > I hope this explains why i wanted to place a jar in ${carbon.home}/lib. > > Thank you > AmilaJ > > Afkham Azeez wrote: > >> I'm not questioning the validity of this scenario. I was wondering why a >> jar needs to be placed into CARBON_HOME/lib which is outside the OSGi >> environment. >> >> Azeez >> >> On Mon, Aug 9, 2010 at 10:59 AM, Lahiru Gunathilake <[email protected]<mailto: >> [email protected]>> wrote: >> >> Hi Azeez, >> >> I think this is a valid requirement during a scenario like, we do >> not ship a particular feature with any of our products and it's an >> optional feature and during the installation of that particular >> feature we need to put some configuration files or may be some jar >> files in to different locations likes like CARBON_HOME/lib >> CARBON_HOME/repository/conf. >> >> Since we are not shipping this with product we need to put them >> during feature installing time. >> >> Lahiru >> >> >> On Mon, Aug 9, 2010 at 10:53 AM, Sameera Jayasoma >> <[email protected] <mailto:[email protected]>> wrote: >> >> This is possible. You need to configure the carbon-p2-plugin >> properly. I will let you know how to do that. >> >> Thanks >> Sameera >> >> >> On Mon, Aug 9, 2010 at 10:36 AM, Afkham Azeez <[email protected] >> <mailto:[email protected]>> wrote: >> >> Please let us know why you are trying to do this. >> >> It is always better to explain the problem first before >> describing the solution so that others may be able to give >> you a better solution. >> >> thanks >> Azeez >> >> On Sun, Aug 8, 2010 at 9:57 PM, Amila Jayasekara >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi Sameera, >> I need to have a jar file in the classpath when >> running ApacheDS >> component. Is it possible to install a jar file to >> ${carbon.home}/lib >> when installing a feature ? If yes, please let me know >> how to configure >> the feature. >> >> Thankx >> AmilaJ >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] <mailto:[email protected]> >> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> >> >> -- Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; >> http://wso2.com, Lean . Enterprise . Middleware >> Member; Apache Software Foundation; http://www.apache.org/ >> email: [email protected] <mailto:[email protected]> cell: +94 77 >> >> 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> >> >> >> -- Sameera Jayasoma >> Technical Lead >> WSO2, Inc. (http://wso2.com) >> email: [email protected] <mailto:[email protected]> >> >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] <mailto:[email protected]> >> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> >> >> -- Lahiru Gunathilake >> Senior Software Engineer - WSO2 Inc. www.wso2.com >> <http://www.wso2.com> >> >> Email:[email protected] <email%[email protected]> <mailto: >> email%[email protected] <email%[email protected]>> Blog: >> www.lahiru.org <http://www.lahiru.org> >> >> Mobile: +94716381143 >> >> Lean . Enterprise . Middleware >> >> >> >> >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> Lean . Enterprise . Middleware >> Member; Apache Software Foundation; http://www.apache.org/ >> email: [email protected] <mailto:[email protected]> cell: +94 77 3320919 >> >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> ------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > -- Afkham Azeez Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: [email protected] cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
