You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Alex Magdenko <ma...@pisem.net> on 2008/03/03 11:35:02 UTC
Integration with Geronimo.
I'm new to Geronimo and I would like to get some help about the following
problem.
I'm working on GridGain(www.gridgain.com) integration with Geronimo.
I need to start my specific service(loader) inside Geronimo server. I have
set of jars which used in my service. All my EAR, WAR applications should
use that service. I need to use the same classLoader with classes from my
service in EAR and WAR applications (no need to load these gridgain classes
per application).
I understand that my service will be declared as GBean and implements
GBeanLifecycle interface.
Could you help me with depoyment-plan.? Ideas?... links?...
Thanks
-----
--
Best regards.
--
View this message in context: http://www.nabble.com/Integration-with-Geronimo.-tp15799944s134p15799944.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Integration with Geronimo.
Posted by Alex Magdenko <ma...@pisem.net>.
Thank you for your help.
I will investigate it and GridGeronimoLoader will be added in future
GridGain releases.
djencks wrote:
>
>
> On Mar 3, 2008, at 2:35 AM, Alex Magdenko wrote:
>
>>
>> I'm new to Geronimo and I would like to get some help about the
>> following
>> problem.
>>
>> I'm working on GridGain(www.gridgain.com) integration with Geronimo.
>> I need to start my specific service(loader) inside Geronimo server.
>> I have
>> set of jars which used in my service. All my EAR, WAR applications
>> should
>> use that service. I need to use the same classLoader with classes
>> from my
>> service in EAR and WAR applications (no need to load these gridgain
>> classes
>> per application).
>>
>> I understand that my service will be declared as GBean and implements
>> GBeanLifecycle interface.
>> Could you help me with depoyment-plan.? Ideas?... links?...
>
>
>
> First, your life will be simpler if you start with geronimo 2.1 and
> package everything as geronimo plugins.
>
> If will also be much simpler if you use maven.
>
> I recommend doing something like what is described here:
> http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a
> +special-purpose+server+using+maven
> (I'm working on this documentation so it may not be completely
> accurate yet).
>
> For your specific circumstances, you'll need:
>
> 1. a project to build and jar the gbean(s) that wrap the gridgain
> classes.
> 2. a project to build a geronimo plugin that starts your gridgain
> service(s) (corresponding somewhat to the liferay-derby project in
> the example. Examples more similar to what you need are e.g. the
> framework/config/rmi-naming plugin in the geronimo server source).
> This project will list the GridGain jars as dependencies and the
> plugin when deployed will provide the single classloader for GridGain.
> 3. a project for each ear, war application that packages the app as a
> plugin (corresponding somewhat to the liferay-jetty project in the
> example). These projects will each include a dependency on the
> gridgain plugin from (2) which will make the classloader from (2)
> that contains the gridgain jars a parent classloader of the
> application classloader.
> 4. (optional but convenient) a project to assemble a server
> containing gridgain (2), the apps (3), and whatever other geronimo
> services you want. (corresponding to geronimo-jetty-liferay)
>
> At this time you unfortunately have to package jetty and tomcat
> versions of your apps separately.
>
>
> Hope this helps.... please ask questions, and if you want to help
> with docs (or the server) that would be great!
> thanks
> david jencks
>
>>
>> Thanks
>>
>> -----
>>
>> --
>> Best regards.
>> --
>> View this message in context: http://www.nabble.com/Integration-
>> with-Geronimo.-tp15799944s134p15799944.html
>> Sent from the Apache Geronimo - Users mailing list archive at
>> Nabble.com.
>>
>
>
>
-----
--
Best regards.
--
View this message in context: http://www.nabble.com/Integration-with-Geronimo.-tp15799944s134p15811412.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Integration with Geronimo.
Posted by David Jencks <da...@yahoo.com>.
On Mar 3, 2008, at 2:35 AM, Alex Magdenko wrote:
>
> I'm new to Geronimo and I would like to get some help about the
> following
> problem.
>
> I'm working on GridGain(www.gridgain.com) integration with Geronimo.
> I need to start my specific service(loader) inside Geronimo server.
> I have
> set of jars which used in my service. All my EAR, WAR applications
> should
> use that service. I need to use the same classLoader with classes
> from my
> service in EAR and WAR applications (no need to load these gridgain
> classes
> per application).
>
> I understand that my service will be declared as GBean and implements
> GBeanLifecycle interface.
> Could you help me with depoyment-plan.? Ideas?... links?...
First, your life will be simpler if you start with geronimo 2.1 and
package everything as geronimo plugins.
If will also be much simpler if you use maven.
I recommend doing something like what is described here:
http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a
+special-purpose+server+using+maven
(I'm working on this documentation so it may not be completely
accurate yet).
For your specific circumstances, you'll need:
1. a project to build and jar the gbean(s) that wrap the gridgain
classes.
2. a project to build a geronimo plugin that starts your gridgain
service(s) (corresponding somewhat to the liferay-derby project in
the example. Examples more similar to what you need are e.g. the
framework/config/rmi-naming plugin in the geronimo server source).
This project will list the GridGain jars as dependencies and the
plugin when deployed will provide the single classloader for GridGain.
3. a project for each ear, war application that packages the app as a
plugin (corresponding somewhat to the liferay-jetty project in the
example). These projects will each include a dependency on the
gridgain plugin from (2) which will make the classloader from (2)
that contains the gridgain jars a parent classloader of the
application classloader.
4. (optional but convenient) a project to assemble a server
containing gridgain (2), the apps (3), and whatever other geronimo
services you want. (corresponding to geronimo-jetty-liferay)
At this time you unfortunately have to package jetty and tomcat
versions of your apps separately.
Hope this helps.... please ask questions, and if you want to help
with docs (or the server) that would be great!
thanks
david jencks
>
> Thanks
>
> -----
>
> --
> Best regards.
> --
> View this message in context: http://www.nabble.com/Integration-
> with-Geronimo.-tp15799944s134p15799944.html
> Sent from the Apache Geronimo - Users mailing list archive at
> Nabble.com.
>