When I changed the bootstrap mechanism last year to accomodate proper child
first classloading for Tomcat webapps, I set the classpath to
CARBON_HOME/bin. Then on bootup we created a bootup classloader which
included all jars from CARBON_HOME/lib, and everything was working fine.
Perhaps, after the Tomcat OSGification, something is broken?

On Tue, May 15, 2012 at 10:07 AM, Isuru Wimalasundera <[email protected]>wrote:

> Hi All
>
> The $Subject occurs due to latest changes made in carbon. And after going
> through the server script I have noticed that the classpath is pointed to
> the CARBON_HOME/bin. What is the reason behind this change of behavior ? ,
> this causes an issue with Greg UDDI API services since some of the services
> looks for commons-lang jar in class path. commons-lang jar is currently
> there inside the CARBON_HOME/lib and
> CARBON_HOME/repository/components/plugins but does not get added to class
> path. This works fine when the common-lang jar is moved inside the bin.
>
> How is it possible to overcome this issue? probably by adding
> CARBON_HOME/lib to classpath would make it work or else is there any other
> way we can overcome this issue.
>
> Thanks
> Isuruw
>
> --
> *Isuru Wimalasundera*
> Software Engineer;  WSO2, Inc.; http://wso2.com,
>  mobile: +94 77 920 5641
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* <http://www.apache.org/>**
email: **[email protected]* <[email protected]>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to