[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Jboss Migrating to Virgo
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Fri, 12 Nov 2010 06:13:06 -0800
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: AcuCc7o5PyGVMPbzQeCh7aIttl2xOw==
- Thread-topic: [virgo-dev] Jboss Migrating to Virgo
This sounds like a fascinating project. Others have expressed interest in supporting EARs on top of Virgo in the past. Essentially, I see this as a variant of a PAR file. The kernel was designed with the ability to add custom artifact types in mind, but no-one outside the kernel has achieved this yet AFAIK. There are some enhancement bugs that you should take a look at:
Then I would start to look in the kernel at:
and associated types. Please then continue the discussion on this thread and raise bugs as appropriate as you see the need to change the kernel (probably to expose more types for your EAR support to use). Ultimately, you should develop one or more bundles that provides a kernel extension to support an EAR artifact type. This can then be configured into the Virgo web server so it is available before any applications get deployed and so you'll then be able to deploy EARs using any of the standard techniques.
One other wrinkle is that you'll probably need to add EARs to the set of artifact types that the Virgo repository component can regcognize. I can give you some pointers on this when you are ready. You'll then be able to store EAR files in a Virgo repository and deploy them as part of a plan.
Given the apparent size of your project, I would hope you may be able to develop some Virgo internals skills and submit patches for the bugs you raise so that we can get this implemented approximately at your pace rather than being held back waiting for committers to implement changes on your behalf, but let's see how we go and we'll do our best to help you.
PS. I hope it's ok to address you as "Lin".
On 12 Nov 2010, at 06:25, Linfengqi wrote:
We have investigated the Virgo project, and the Virgo is a powerful server to support the OSGI and SOA architecture. So we planned to migrate from Jboss to Virgo, currently we use EAR deployment, but we didn't use EJB in EAR package, we use the Spring Dynamic Modules and Nuxeo OSGI module to implement distributed services, and other third part library.
For now I saw the Virgo doesn't support the directory structure of EAR package, in order to migrating to Virgo, We have to modify EAR package or implement new EAR deployment in Virgo. We compared these two approaches, and we prefer to the second one which implements the EAR deployment in Virgo, because we have hundreds of projects, it's a big risk and huge workload to modify the whole EAR packages.
And I want to know if we decide to implement a new EAR deployment, what should we to do? Is there any interface or procedure to do this? I read the User guide and Programmer Guide, but there are a few content talks about this. Do you have any ideas or suggestions for us, thanks a lot!
The directory structure of EAR package which we used is bellowing:
ââconfig -----------------> contains some configuration file, like log4j.xml
ââcore -----------------> contains the core module for application
ââinfrastructure -----------------> contains the core module for framework
ââlib -----------------> contains the third part library
ââMETA-INF -----------------> the meta data for package
ââOSGI-INF -----------------> the meta data for OSGI
ââplatform -----------------> contains the core module for framework
ââplugins -----------------> contains the core module for application
ââtrade.war -----------------> the web part for application
ââsystem -----------------> contains the core module for framework